After doing a full wipe and flashing I get an endless boot loop. Restarting, reflashing and re wiping does not help. Any ideas?
anyone?Hello,
do anyone use the tablet to develop applications?
I installed this ROM, and then, when i try to install my app from from Eclipse to the tablet i always got an error:
Logcat report this:Code:"Installation error: Unknown failure Please check logcat output for more details. Launch canceled!"
I haven't this error with previous ROM version or with original samsung one.Code:"04-24 16:25:46.368: E/JavaBinder(4161): !!! FAILED BINDER TRANSACTION !!! 04-24 16:25:46.368: E/ServiceManager(4161): error in getService 04-24 16:25:46.368: E/ServiceManager(4161): android.os.TransactionTooLargeException 04-24 16:25:46.368: E/ServiceManager(4161): at android.os.BinderProxy.transact(Native Method) 04-24 16:25:46.368: E/ServiceManager(4161): at android.os.ServiceManagerProxy.getService(ServiceManagerNative.java:123) 04-24 16:25:46.368: E/ServiceManager(4161): at android.os.ServiceManager.getService(ServiceManager.java:55) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.commands.pm.Pm.run(Pm.java:87) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.commands.pm.Pm.main(Pm.java:77) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:297) 04-24 16:25:46.368: E/ServiceManager(4161): at dalvik.system.NativeStart.main(Native Method) 04-24 16:25:46.368: E/JavaBinder(4161): !!! FAILED BINDER TRANSACTION !!! 04-24 16:25:46.368: E/ServiceManager(4161): error in getService 04-24 16:25:46.368: E/ServiceManager(4161): android.os.TransactionTooLargeException 04-24 16:25:46.368: E/ServiceManager(4161): at android.os.BinderProxy.transact(Native Method) 04-24 16:25:46.368: E/ServiceManager(4161): at android.os.ServiceManagerProxy.getService(ServiceManagerNative.java:123) 04-24 16:25:46.368: E/ServiceManager(4161): at android.os.ServiceManager.getService(ServiceManager.java:55) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.commands.pm.Pm.run(Pm.java:88) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.commands.pm.Pm.main(Pm.java:77) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) 04-24 16:25:46.368: E/ServiceManager(4161): at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:297) 04-24 16:25:46.368: E/ServiceManager(4161): at dalvik.system.NativeStart.main(Native Method)"
Could anyone have a suggestion?Thank you so much!
Hello hanspampel,
@StNickZA
It didnt have multiuser support. There wasnt any For p605 that has it. We must be waiting for KK.
I totally agree,I positively can't believe Samsung doesn't give a flying rat's a..s to release KK for the P605 still after all this time. An absurd amount of money spent on the P605 for categorically mediocre build quality (mine is a squeak galore and cracks around the pseudo-metal ring around the unit I already gave up counting), plus a deplorable screen to match (mine is a total yellow tint that I find no solution for and Samsung tells me is "normal") and now no firmware upgrade at sight.. I'm so done with Samsung.. so done..
Too good to be true..Some excellent news for us all. Samsung have started rolling out P605 4.4 kit kat update. South Korea at the minute but its here.
---------- Post added at 09:41 AM ---------- Previous post was at 09:10 AM ----------
Sorry I didnt notice that is was the LTE-A version. Got a little excited lol.
here it is! http://www.sammobile.com/firmwares/3/?download=30325 :good::fingers-crossed:Yepp, still waiting for a downloadable fw.![]()
Sweet... Hopefully it will work out OK.. We have faith in you.... :laugh:Yeah i know. But it could be a bit tricky without a working recovery on the new bootloader. I hope it works with the old one too. Ill try my best.![]()