Running ota ics
Wanted to install acer recovery from market, but *****ed about no root. Is this normal...? Do I need root to run acer recovery..?
Ran blackthunders ics 7.1 with the defult checks to get root
But still have no super user or busybox installed even though it is checked
Ran the unroot and it goes through the motions but does not change anything.
No says system updater has stoped. So I cleared data of system updater, still says system updater has stopped.
Also stuck at obtaining ip (reset) no fix.
Did I do it wrong, One click and I was screwed.
Also cmd box comes up adb server out of data.
Any ideas
Got fixed. Seems the 7.1 has no error checking when it roots and does it's thing, so with or without a connection it will run like its working whether or not its connected. And if you got a good connection and it drops during the rooting you won't know till you have a messed up tab.
Related
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Yesterday, I did the same thing you tried and I was successful in rerooting my phone after the OTA update. When you used the 1-click process did you choose option 1 or 2. I tried 2 and it didn't work. I had to chose option 1 (reload everything) to be successful. BTW, remember to make a new recovery backup of the system.
unrooted
xberry said:
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Click to expand...
Click to collapse
Same issue here - how I fixed
I had already made titanium backups of important stuff - you have to go into applications (that use root) and force stop and clear data. Once this is complete open titanium backup for instance, and you should be asked for super user and then be good to go. Same goes for rest of apps that need root
OTA update Loop?
i have my d2 rooted after the ota 2.2 update. i just received a notification to accept the most recent OTA update ... whatever it is... and assumed it was one of my apps as i didnt read it thru completely b4 tapping 'ok'. now it is stuck in a download, reboot, update, "update unsuccessfully installed", redownload, reboot...........
is there a way to cancel the update? i dont really care if i have it or not
or some way to stop this process aside from the airplane mode i had to set it to so it would stop this madness
So you can do the OTA update without having to unroot and reroot?
Great advice from all - thanks! I'm not sure exactly what fixed it, but I ran DOROOT several times, did the unplug/plug when it hung for a minute, force closed/cleared data from previously rooted items, and also put phone into 'charge only' mode when USB Debugger would not run.
Finally - success! My advice to users with this same issue - try and try again.
Thanks all!
I just gotten a DHD, and rooted it via Visionary, radio S-off with jkoljo's one click S-off, installed clockworkmod and flashed recovery.
then I followed sfjuocekr's guide and eng S-off, and proceed to install the kernel update utility into my PC, and flashed Buzz kernel v1.0.6 using the zimage method, and it was successful (says the kernel update app). Then I waited for the android to restart and upon completion, I pressed apply modules.
And now everytime i starts up my phone, i get the error messaging saying that Titanium backup, rom manager and flikie wallpapers has stopped, and I have to force close them. My wifi is also unavailable, when i checked into settings, it says wifi error.
Does anyone know what went wrong?
Thanks
I reflashed the kernel and the modules again, and my wifi is ok this time round.
But my 3 apps are still getting the error message, and this time round i got a message saying that my superuser is not responding and force closed.
I think that the superuser is causing all these problems, Ive reinstalled Rom manager and titanium backup, and when i tried to use titanium backup, it says it could not acquire root privileges, and for me to verify that my rom is rooted and includes busybox (which Ive done right at the beginning when i root my phone).
Im still able to access bootloader, so i guess i still hv root. Not sure why my superuser is not working. Anyone can help?
Thanks
I would always go radio s-off and eng s-off, it creates less errors and offers more flexability
Sent from my Desire HD Beastly Device
i reinstalled superuser app, and its working fine now.
Not sure why superuser was having error earlier on, but reinstalling it fixes everything.
I have a problem with superuser that I can't understand.
So I bought this new Samsung Galaxy Note 3, and I rooted it by flashing my phone with Clockworkmod 6.0.4.5(1116) with Odin, and then installing UPDATE-SuperSU-v1.65.zip through the recovery window.
To be honest the process didn't go ideally smooth. Since I misunderstood how to proceed with the process, I had to reinstall Clockworkmod a few times.
After finishing from that, I started trying to use software that needs root access (like LuckyPatcher), and lucky patcher was hanging at the beginning black screen and not proceeding. And I tried many other programs, and they always don't proceed and stop.
So eventually I went to the Application Manager and select Superuser, and chose to "Uninstall updates", and only then, all those Superuser prompt messages started popping up asking me to grant LuckyPatcher and all other software that tried to access root... and since I chose to Uninstall updates, the phone restarted.
Of course, after the phone restarts, we're back at square 1, but the programs, to whom I granted root access get root access for some time...
I tried updating Superuser from the market, but when the program starts, it says "The Superuser binary (su) must be updated.", and I have a option called "Recovery Install", when I choose it, the phone keeps showing a message saying "Installing Superuser..." and it never finishes. Yesterday I left it and went to sleep, and eventually it gave an error message. I would say that Superuser update itself requires root access which it couldn't get... but that's as far as I know. I tried the "Uninstall updates" trick but it never worked.
Also I have to say I tried to install Superuser versions 1.51, 1.60, 1.65, 1.80 through recovery with a zip file, and it didn't fix it. And I installed CrashROM from here:
http://forum.xda-developers.com/showthread.php?t=2535355
and it didn't help either.
What do you think? How can I repair that and have normal Superuser permission asked normally? Please advise.
Thank you.
Any help, please?
Problem solved
The solution was to specifically install SuperSU from the market and not superuser. That fixed it.
Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
bump
mrberta said:
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
Click to expand...
Click to collapse
BUMPITY BUMP BUMP, plz help my fwiend!