Hey guys,
I love everything people have done on here, and thought its about time for me to take the plunge and load a custom rom. I followed the instructions to manually root my hero, and everything "seemed" successful. I get to the Shell, get my #, enter the mount command in all of the walkthroughs, and.....nothing happens, it just hangs. I've let it sit there for half an hour and nothing happens. I then ctrl-c, re-opened the shell and enter basic commands (cd, pwd, ls) and nothing happens. Any ideas?? The sprint update seems like its never coming and I was so excited to play with a custom rom this weekend!
Hopefully others are seeing this and it will help them as well.
I was running stock 2.2, decided to root, no ROMS. Saw that the latest update was coming out so I unrooted, not problem (really). But since unrooting I would always boot in clockwork which pissed me off. So I started playing, tried the update that's floating around (update.zip) and that worked but still boots me in Clockwork. So then I tried factory reset, still no go. last night I decided to restore a backup from the past which was immediately after I rooted the first time. Everything was back, and botting was normal. Now, I think it gave me back root which was how the phone was when backed up, but not 100% sure. The SU icon was present, and I think the Ti loaded without error just can't remember, things getting blurry.... This am I rechecked for the OTA update and it was there. Updated figuring as others are finding that it will kill root and be fine, just re-root again. Well things not fine. since OTA I'm booting back to Clockwork and Ti says it can't find root, this leads me to believe that I don't have root, even though the SU icon (ninja) is present. Tried RootMyX2 which I used in past, but it gets hung up at "Waiting for Device" right after loading the arm5.bin file thingy. I've cycle USB modes, debugging is on. Tried Z4root which I can't even install because it says that the "file can not parse".
Someone please help, I can't take this **** anymore and getting very frustrated.
I think your at about where i am..
http://forum.xda-developers.com/showthread.php?t=867694
clockwork needs root to remove the signal file it creates that tells it the boot completed successfully. You will need to remove clockwork to fix or re-root.
That's fine, but how is this accomplished? The issue seems to come up alot, but no one has ever posted something (that I've seen) that actually addresses the removal of clockwork. I agree though, this is what I need to do. Any thoughts now?
I've not tried this method, so use at your own risk!
to remove it with adb shell:
first do this:
Code:
ls /system/bin/logwrapper.bin
If the file logwrapper.bin isn't found then you've lost the original due to flash/updates and can't remove clockwork until you locate it. Don't continue.
If the file is found then do the following:
Code:
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 / system
rm /system/bin/logwrapper
rm /system/bin/hijack
cp /system/bin/logwrapper.bin /system/bin/logwrapper
exit
exit
(you should have a command prompt back)
adb reboot
Thanks Slueth
But I don't really do the whole code thing. I know I have to start an emulator and such, but was hoping that I would have to go that route.
I was able to restore again to previous version when I had root, so now I have root again. Still don't feel like things are right in the world with it, but I'm kind of getting tired of searching for answers that don't seem to exist.
Basically now I would think that I can update, probably lose root, then re-root, but for some odd reason I can't find an app to root/unroot with. No clue why and at this point I would take going back to stock but I believe that requires coding too? Second part of this is I'm on Mac at home, only have access to PC at work and think I've spent enough wasted time there playing with my phone.
If you could come up with some way to get Z4 to work that would be swell.
On a side note, now my .mp3 ringtones wont recognize...
I just noticed that there seems to be some worried about rooting if you ran the verizon DL09 odin package. Don't worry. d2 root method for fascinate found on XDA works just fine. http://forum.xda-developers.com/showthread.php?t=779238
Have not found a one click root that works yet though. If you find one, post it!
**UPDATE**!!!
Looks like there are some that are hit or miss... may have to run them a few times and wait upwards of 5-10 minutes for some.
if you don't want to wait use perm d2 method. happy rooting!
I actually used the one click root method that is found on android central after i upgraded to DL09. Worked for me. It was strange because i had to do it 3 times until it finally ran.
To get it to run it needed over 5 mins (which the once click says if it takes more than 5 mins try again) I had run it then lost track of what i was doing because i was at work. Then next thing i know it completed itself. So i can confirm it does work.
jselden said:
I actually used the one click root method that is found on android central after i upgraded to DL09. Worked for me. It was strange because i had to do it 3 times until it finally ran.
To get it to run it needed over 5 mins (which the once click says if it takes more than 5 mins try again) I had run it then lost track of what i was doing because i was at work. Then next thing i know it completed itself. So i can confirm it does work.
Click to expand...
Click to collapse
Looks like patience is the key here people... if you are familiar with adb, you could probably root it faster. i ran z4 and let it run quite a few times myself before i said screw it (i actually got a FC or 2 as well) and just ran the perm d2 method.
thanks for the heads up!
Possible reason why
I'm gonna look for the page I got my 1 click method from, but it worked for me on the first time. I rooted immediately after flashing the odin file. Then I screwed something up before I pout clockwork on so I reflashed since I lost everything (not really, thanks to Titanium Backup). Then I immediately flashed the clockwork after and then the 1 click failed twice. Reflashed the official dl09 then 1 click and, boom, rooted on the first try.
After doing a little searching, apparently the clockwork.tar flashes a DI01 kernal. So if people are flashing clockwork before rooting, this could be the culprit. I use this method found here
http://m.forum.androidcentral.com/showthread.php?t=33899
Hope this helps some people out.
one click root worked for me
The one click root method from android forums worked for me (said it completed) but none of my root access apps are getting root access.
I rooted through the manual adb method.
I'm having trouble booting into clockwork though.
After grabbing clockwork recovery from ROM manger, it goes to stock recovery where it errors with "signature verification"
do I have to push the original clockwork.tar through odin?
edit: http://forum.xda-developers.com/showthread.php?t=913470 <<< fixed the issue. push through odin
I used the adb method from android central and I had to wait 5-10 minutes to be kicked back out to the windows command prompt after running rage.bin.
It's not just 1 click methods that sometimes take a long time to complete.
i used the 1 click method from dirkk. i had problems with my phone reading as a media driver(trying to sync to my pc) so that was causing the 1 click method to fail at first. once i disabled the media sync it was sucessful first try.
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
This process should un root and put you back on stock Froyo. This is a complete factory wipe, so if you're wanting to back anything up, do it before any of these following steps. Once complete, go to Settings > About Phone > Check for Updates and report back.
WARNING: Only run the first set of instructions, do not flash the Gingerbread leak, you can get the official after running RSDlite.
To get back to stock: http://www.mydroidworld.com/forums/...id-2-gingerbread-2-3-3-release-prerooted.html
1. Grab the SBF File
You must start the process with your phone running the official 2.3.20. If you have already upgraded to gingerbread grab this 2.3.20 sbf file .... Download
2. Grab RSDlite
You must use RSDLite to use the sbf file from step 1 .... RSDLite
3. Grab the Drivers Drivers ....Download now
4. Run RSDLite and sbf your phone back to 2.3.20
Didn't work
I was unable to get the OTA to work. I was rooted using OneClickRoot and unable to update like everyone else (FAILED). I tried to sideload from a post on another page, but that didn't work either (not even sure that was the correct file). So I followed the direction as mentioned above, SBFing to a stock 2.3.20, but only after I did a complete wipe of the phone. Now that I have SBFed I don't have any phone signal and cant get it to work with anything I have tried. I don't want to go crazy trying stuff and brick my phone. So at this point, how do I get my phone working again. Screw GB for now, I just need my phone to work. HELP!
It's pretty hard to brick a D2 unless you happen to flush it down the toilet. SBF again to 2.2, do NOT root. Go to the about phone menu and run the OTA update to GB. After that run the one click root for Droid 3.
working
I don't know why, but after re-installing (SBF) 2.3.20 the phone decided to stop working. I thought it could have been a bad SBF file, and it could have been. The step that seemed to work was wiping the phone after the install. Once I did this step, of course you have to set the phon up again, but it prompted me to "Activate" the phone. So I hit activate and the phone called Verzon and run a programming function. Once that completed the phone worked fine. I am currently downloading the OTA, so here's hoping!
I did actually get the sideload (update.zip) file to work before going back to 2.3.20 as mentioned above, but I still didn't have phone. At this point I was going to do a wipe but could not get the phone to enter recovery, I'm thinking there must be some other method that's different to get it there. If anyone know, that would be good info to have.
Still downloading.....
I believe if you dial *228 it will activate for you.
I am also unable to get the OTA GB update to work. It gets all the way to re-boot and about 1/3 of progress bar after accepting to install the 4.5.601.A955. Just like mentioned in one of these other posts. I have tried everything - uninstalling and reinstalling z4 root, deleting SU, Bootstrap recovery, root explorer etc. All of which were not done properly or in the right order. I have been working on this the last 2 days. Yesterday, I even called tech support at Verizon, they helped me do a factory reset, and when it failed again, offered to send me a new D2 because my phone is still under warranty and won't accept the update, so I took their offer.
But then I got nervous because my clockwork mod was still showing up on power up, so I finally figured out how to remove that. I have SBF'd at least a couple of times since I got clockwork removed and update still fails.
My memory is not to good, but I think I first rooted in late Dec 2010. It seems like the 2.3.2 OTA update came out in Jan or Feb 2011. I don't believe I had to unroot to get that update. My current System Version is 2.3.20 A955 - Android version 2.2, and that is what it goes to after doing the factory reset on the phone. The Verizon tech didn't act like it should have gone back to an earlier version.
I have only one other issue - a week ago the phone took a bath when I fell in the water. Dried it off quickly and the only thing wrong other than barely-noticeble water damage to the display, is that the power button now requires exactly 3 pushes every time to boot the display to the unlock screen.
Sorry for the long post. Here are my questions: I no longer have clockwork at power up, it boots like a normal out of the box D2, am I missing something? Will Verizon be able to tell that I had rooted my phone? Could the water and resulting power button issue be the cause of it not accepting the update? TIA
Im having a similar problem. I can get the ota update just fine, but it will install aboutt 1/3 of it and just stop and reboot. All i did was root. I unrooted and same thing happpens. Downloaded this thing like 6 times already and same thing each time. Although a long time ago i did uninstall nfs, blockbuster, and i think kindle but i cant remember...
Are you doing a full factory wipe back to 2.3.2 when you do this or are you just "wipe data/factory reset" in recovery? Because if you only do that in recovery you're just wiping data. There's another thread here with a .zip you can run in stock recovery, not clockwork. Rename to update.zip, put it on the main directory of SD, boot holding X and power, then press the volume buttons. Hit install update.zip.
On the D2 - I am doing Settings<Privacy<Factory Data Reset<Reset Phone< Confirm.
How do you get into stock recovery? Do I need to be rooted again?
I would imagine but I don't know. Boot up holding the X key and power, should bring you to a droid guy with a !. Hit the volume buttons, if you get a blue and red recovery menu, you're in. It's not going to ask you for superuser so it's worth a shot at least.
Thanks for your help idefiler6. I got into stock recovery, but when I did the update it also failed - some logwrapper error. I am now having difficulty getting back in to stock recovery.
I had deleted system/bin/hijack and renamed system/bin/logwrapper.zip to system/bin/logwrapper to remove or stop the clockwork mod from booting up, which did make clockwork go away using Root Explorer. I found a post here to do this droidxforums.com/forum/droid-x-help/22080-im-begging-help-please-help-3.html
Anyway, my new phone is supposed to get here Wed. So I guess I'll just take my chances of whether Verizon cares or figures out I had rooted my phone. Regardless, the power button failing to work properly, should qualify for warranty coverage.
Crossing my fingers for you.
im getting mine replaced under warranty due to it cannot install the update no matter, how many times we have wiped it with tech support.
I also was very lucky since I got my 2nd warranty phone right before the one year mark so it extened the phone i have now another 90 days.
Problems all around
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
When in Doubt Go Linux!
Here's how I fixed the problem. I'm not a big Windows guy and the issues I was having were frustrating me because I had to update drivers, download new versions, blah, blah, blah.
I found a solution that allowed me to use my Fedora OS and it took me 10 minutes, no hassles, no errors. The incredible thing is, it kept ALL of my data, apps and settings on the phone! I had to upgrade from 2.29 (the flash from below) to 2.30 OTA and then to Gingerbread OTA Awesome stuff.
Here are the steps provided by hwertz from modmymobile.
"Download sbf_flash (just goggle it)
Download DROID2WE_X6_2.4.29_FULL.sbf.zip" (google this too)
(You would download these with firefox, make sure Firefox saves in the directory "Download".)
Open a terminal (Applications->Terminal)
Plug in your phone via USB, turn it off. Flip open the keyboard and turn it on WHILE holding down the up arrow. You'll see this screen with blocky white text, like right away -- it doesn't even get to the Motorola logo."
-----
OK, so in the terminal, you will
type "cd Download"
(If you saved somewhere else, cd to there. For instance if you saved to "Desktop" you would "cd Desktop" instead.)
Type "gunzip sbf_flash.gz"
If this gives an error, it's ok, it means you already had "sbf_flash" instead of "sbf_flash.gz"
type in "chmod +x sbf_flash"
Type in "unzip DROID2WE_X6_2.4.29_FULL.sbf.zip"
Then type in "sudo ./sbf_flash DROID2WE_X6_2.4.29_FULL.sbf"
If you are running a "real" copy of Ubuntu this'll ask for your password. The LiveCD has no password so it won't.
That's it! It'll appear to do nothing for a few seconds while it loads the flash, then it'll start flashing your phone which takes 5 or 10 minutes.
Good luck!
Thank you hwertz and thank you Linux!
cbotd said:
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
Click to expand...
Click to collapse
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
that would explain it
idefiler6 said:
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
Click to expand...
Click to collapse
That makes sense. Either way, I'm happy as can be and in love with my phone all over again. GB is fast and smooth on my D2G and after gaining root access again last night all my SU apps are back in working order.
Droid 2 updated
I had to revert back to stock 2.3.20 using the RSDLite flashing method, I let it do its thing, then performed a factory reset.
Powered the phone on, activated it, then just downloaded the OTA update over wi-fi to make it faster, installed like a charm, then ran the rooting utility.
Phone is rooted, deBloated, and rockin steady already.
Gotta say, I love my D2 again.
A955 & A957 Gingerbread sbf
On September 15th an official Gingerbread sbf was released from Motorola for the Droid 2 (not the Global). Here are the exact file names in case anyone has access:
A955:
1FF-p2a_droid2_r2d2_cdma_droid2_r2d2-user-2.3.3-4.5.1_57_DR2-32-110726-release-keyssigned-Verizon-US.sbf.gz
A957 (R2D2):
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keyssigned-Verizon-US.sbf.gz
I''m reluctant to post about this, mainly because in my years of using Android devices I've always been able to solve the issue myself. This one though is a whole other story.
This morning I turned on my N7(it's the 2013 wi-fi version) and it got stuck on the google screen. My device has TWRP installed and had been rooted at one point, but I let a factory update break root and never tried to reroot it. I rebooted, I went into fastboot and tried to boot into recovery. Same problem. So I figured no problem, I've seen this before, let's try the N7 root kit to fix this. Every file it pushed failed. I tried the one click factory restore for a bricked device, same thing.
So I figured it was time to ADB commands to get this sucker sorted. I have my factory image downloaded, extracted into the platform tools file (I've done this a few times before), and started going through the commands. First one up? "fastboot erase boot". I entered that command nearly 30 minutes ago, and it still is stuck on "erasing 'boot' ..." .
Perhaps needless to say I've exhausted the methods known to me and have no clue what to do next. So any help, suggestions, advice on how to fix this would be much appreciated. I've accepted I'm going to lose all my data. At this point I just need to figure out how to get this running again period. Thanks in advance!
Have you tried the flash-all script bundled with the stock images?