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.
Related
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
lwright84 said:
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
Click to expand...
Click to collapse
I think you might be overreacting here.
First, I haven't flashed the SBF yet but I do remember seeing the fail screen on original Droid SBF flashes and it was something you could ignore. You booted back into Android, right? That means it worked.
Second, the Superuser app is supposed to show a blank screen because the purpose of it to manage apps to which you have granted to superuser permissions. If you just installed it, there would be nothing listed.
Third, Froyo restores apps if you have "back up my data" checked under Privacy settings.
Fourth, you never mentioned the Droid 2 bootstrapper. I wouldn't expect ROM Manager to work properly without it.
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
lwright84 said:
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
Click to expand...
Click to collapse
Captivate is not a Droid 2. I'd be surprised if it works without the bootstrapper, since that's the only way to flash anything on a Droid 2.
My suggestion is to keep trying the SBF. Once you get it to work, get the SW update and then root. From there, I wouldn't go messing with anything in ROM Manager until you confirm the files are 100% legit for the Droid 2. As far as I know, only a few themes are working without issue on the Droid 2 - the ROMs all have bugs.
The same thing happened to me. I am assuming we were using the same instructions to flash the .sbf. Here is a link to instructions I followed.
http://forum.xda-developers.com/showthread.php?p=8245826#post8245826
I did not heed the red flag I got when I unzipped the .jpg file. I saw some error message and ignored it, and went ahead with the procedure to end up as many others with "fail".
Long story short, I deleated the .jpg file and downloaded it again.
When I used 7 Zip to extract the files, this time I had no error msg and everything went smoothly.
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!
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.
On an old Sprint Hero with stock 2.1 Sense ROM, I recently rooted, wiped and installed CM 7.2. At first, Superuser was working and I was able to restore things like old SMS. However, after a day, Superuser is no longer able to grant root access to things like Titanium Backup or even itself. I tend to get a force close for Superuser when trying to elevate. I've tried downgrading the Superuser APK to the version that came with CM 7.2 (I had upgraded it). I've also tried booting into recovery to replace the binary su. Neither option works.
Has anyone else experienced this issue and found a way around it?
Try installing busybox from the play store also try updating the app from within the app if you haven't already
#Root-Hack_Mod*Always\=LTE
laie1472 said:
Try installing busybox from the play store also try updating the app from within the app if you haven't already
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
The problem was solved by downgrading both the Superuser APK and the binary file. I have root access again. For some reason Superuser 3.1 and the 3.1.1 binary weren't behaving.
Glad you got the problem solved.
#Root-Hack_Mod*Always\=LTE
i have the same problem
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.