I rooted using the nabi lab 2 (http://forum.xda-developers.com/showthread.php?t=2101277), after a prior root, gapps installation which had the update issue. I am on the current .37 update.
I downloaded dragonbox from the play store, and it loads but nothing on the screen responds to touch. Is there a way I can force this app to work on the Nabi? Or is this an issue with the software? (I'd be willing to get to the bones, rid the Monarch UI, etc. to have better functionality of the Nabi)
Thanks for any help!
I tried the Dragonbox v1.1 app and indeed it did the same thing on my Nabi 2. Is that the version you tried?
Related
Hi,
I've been using the prerooted r5a version of ICS on sony tablet s for sometime now. r5a update was done using Condi's automated update tool. Off late I've noticed some problems related to this rom.
Firstly, the tablet hangs suddenly and reboots when in the middle of using some apps, like browser, twitter, facebook.
Secondly, Google play store has stopped working completely since last few days. I've tried everything from cleaning up cache memory, tmp files, tweaks etc to get it running again, but nothing seems to get play store to work again.:crying::crying:
I'm really having a hard time using my tab now and wanna know if there's any way i can do a factory reset or a ROM downgrade without losing root.
I would be really grateful if anyone could help me out with this issue.
Thanks in advance
audiophile_adi said:
Hi,
I've been using the prerooted r5a version of ICS on sony tablet s for sometime now. r5a update was done using Condi's automated update tool. Off late I've noticed some problems related to this rom.
Firstly, the tablet hangs suddenly and reboots when in the middle of using some apps, like browser, twitter, facebook.
Secondly, Google play store has stopped working completely since last few days. I've tried everything from cleaning up cache memory, tmp files, tweaks etc to get it running again, but nothing seems to get play store to work again.:crying::crying:
I'm really having a hard time using my tab now and wanna know if there's any way i can do a factory reset or a ROM downgrade without losing root.
I would be really grateful if anyone could help me out with this issue.
Thanks in advance
Click to expand...
Click to collapse
Simple as use AiO install recscue back-door. Then choose your rom of choice US R5(NOT A) or R1a for your region. (needs to match to be able to pass checks) then install through recovery then re-root using AiO.
Stifilz
What exactly causes it to reboot like that? Ram error or maybe cache error?
Sent from my Sony Tablet S using xda app-developers app
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD
I Apologise for my ignorance in android in general.
I have rooted a Nabi 2 successfully installing Gapps etc using Nabilab, which was a pleasure to use. Now that the new OTA update is available which includes the Googleplaystore I would like to unroot and get the OTA updates. I thought I had unrooted it - using Nabilabs (twrp would not work, can't remember why but I think the touchscreen part wouldn't work for me). I returned to stock using (option 1. -1.9.37. Android can boot.) recovery using Nabilabs. I think I did a factory reset after that -sorry but it was weeks ago. Anyway, I suspected something wasn't right when I still had Gapps. I don't have TWRP on it now.
When I do the OTA update I get the dead android on reboot. Nabi is working fine apart from that. I read a lot of pages on this website but it ended up confusing me more than helping me unfortunately as I'm not android savvy.
I just need someone to tell me exactly what to do to properly unroot the Nabi so that it is truly back to original so I can use the OTA updates. I have no need to root the nabi again as the google play store is now officially available. And I've got a UK Nabi 2.
Many thanks in advance for any replies.
Awhile ago i rooted for the google play store, but i am sick of all the random, stuff that keeps.coming up, and want to go back.to normal, i installed the update prevention thing, and was wondering if someone could point me to the steps for updating my kindle, preferably without a factory reset.
Edit unrooting
ThellraAK said:
Awhile ago i rooted for the google play store, but i am sick of all the random, stuff that keeps.coming up, and want to go back.to normal, i installed the update prevention thing, and was wondering if someone could point me to the steps for updating my kindle, preferably without a factory reset.
Edit unrooting
Click to expand...
Click to collapse
You could use KFHDX toolkit to reenable updates and then upgrade to a higher version. but keep in mind there is no way to rollback on your own currently
I have two Verizon Samsung Galaxy Note 3 phones, SM-N900V. One has Android version 5.0 and I haven't been able to root that one. The other one has Android version 4.3, and I was able to root it from Windows using mobilego_setup_full818.exe.
Now that the second phone is rooted, I get daily unidentified popups, presumably from Verizon, asking me to let it update the phone. It doesn't say what it's going to update; I guess it's the Android version. My only choices are to let it happen, or postpone it; no option to refuse it permanently.
So question: If I let it update, will it undo my root? I'm worried that if it updates Android and I lose the rooting, I won't be able to root it again, like with the other phone.
On one hand I'd like to update the Android system because the current older one is preventing me from installing some apps, like Wells Fargo Banking, and Pokemon Go. On the other hand, I really want to keep the root, because I rely on it for using my phone as a wifi spot for my laptop, blocking ads, using Titanium Backup, etc.
Advice?
You can unlock the bootloader now, so updating, installing custom recoveries and root are no longer an issue:
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Don't update over the air though. Update via Odin, then unlock bootloader, install TWRP, and flash SuperSU zip. Make sure to back everything up to a safe place.
Thanks; I'll check this stuff out.