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
Related
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...
Hi guys,
I'm a bit lost and unsure what to do.
I installed GummyJar, and like an idiot, didn't read that I need to be on 2.3.320 or 2.3.340.
I was previously on ZapX for 2.2 (purchased phone in early October). So I'm not sure what to do. Is there an SBF that will directly put me on 2.3.340? Would it be wiser to flash to my original SBF (the_gift2.zip I believe), and let my phone automatically get the OTA update?
I'm not really sure what the best thing to do is.
Thank you for any advice and help.
Did you create a back up before you installed Gummy? I know that is praobably a stupid question since you are asking how to SBF -but I thought maybe you didn't think about restoring your backup?
How to perform the sbf:
I did this. It worked for me. I TAKE NO RESPONSIBILITY IF THIS DOES NOT WORK FOR YOU OR IF YOU MUFF IT UP.
ok- so here is the link that I used as a guide - IMPORTANT!!! - the directions are for restoring 2.1 so you do not do some of the steps! They were the best I could find. I followed them except for things that did not apply.
http://www.intomobile.com/2010/09/21/droid-x-stock-android/
instructions:
1. First off, choose the right version of Motorola USB drivers for your computer and install them (32bit) (64bit)
You probably have already done this.
2. Download & install RSD Lite 4.7 (download)
I did not use 4.7 as it is not current. I used 4.9 download here...
http://dl.dropbox.com/u/7782384/RSD%20Lite%204.9.rar
3. You will need to patch this after installing. There is an .ini file included in the folder that needs to be placed in your install directory. /Program Files/Motorola/RSD Lite
I used 4.9 and did not have to patch any files- the above step was unnecessary.
4. Download the Droid X Android 2.1 SBF file, which you can find here
of course I used the 2.2 SBF file. Make sure you use the right sbf file or you will really be hosed!!! if you are on 2.2 you can get the full sbf file from here...
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
5. Unzip the SBF file to your desktop
i did not unzip mine to the desktop- i put it where i stash my android files- it made no difference.
6. Run RSD Lite, and click the “…” button, then find the SBF file that you just unzipped to your desktop and select it.
Starting here i followed the directions to the "t". Went through all the steps.
!!!!!MAKE SURE YOU START WITH 100% BATTERY!!!!!! It takes a long time and if your phone dies during the process it is a nightmare.
7. Plug your Droid X into your computer and power it down
8. Go into the Bootloader (with phone off, hold the CAMERA button and VOLUME DOWN, then hit the POWER button)
9. After holding for 2-3 seconds, release the buttons and RSD Lite should recognize your Droid X
10. Click the start button to flash Android 2.1 to your phone.
of course we are flashing 2.2
11. When the flashing is complete, unplug your phone
12. The Droid X will likely not boot up all the way, so pull the battery out
Put the battery back into the phone and reboot into Recovery mode ( Hold the HOME button and press POWER until you get an exclamation mark. Release the HOME button and press the SEARCH button)
13. Using the VOLUME UP/DOWN buttons, navigate to “wipe data/ factory reset” option on the screen, and press the CAMERA button halfway down to execute.
When complete, choose to reboot your phone
14. It takes a while. Hope this helps. And I hope it goes smoothly. It was nerve racking for me. After you have finished the process you will not be rooted.
15. good luck.
Thank you very much. An extra question to go along with this.
Once I SBF, I'm assuming I'll be back at stock (ick). How long will it take for the OTA to apply? Can I manually update it from there?
EtherBoo said:
Thank you very much. An extra question to go along with this.
Once I SBF, I'm assuming I'll be back at stock (ick). How long will it take for the OTA to apply? Can I manually update it from there?
Click to expand...
Click to collapse
Well- of everything goes right you should be able to go to your phone settings, scroll down to the bottom to "About phone", then "System updates". You should be able to manually update from there.
If you get a "your device is up to date message," then something went haywire. Hopefully that won't happen.
Oh yeah - here is the link for "z4root" -you can use it to root your phone after the update...
http://dl.dropbox.com/u/7782384/z4root.1.3.0.apk
If your phone won't manually update, there is an update.zip floating around here. I have it - but not on the computer I am currently working from -sorry.
Again I want you to know - I am not an expert at this - if something goes wrong I will not be able to help you fix it (probably). I just followed the guide and it worked for me. So if something happens when you follow the guide -I am sorry but I won't be much help.
Thank you. Everything took about 2 hours (SBFing, downloading and installing update, reinstalling apps, etc), and I have the newest Kernel version from the OTA update, and GummyJar 2.5 back on.
I had a bit of trouble SBFing, it kept failing for some reason, but I found a fix via googling around the various Droid forums.
Thank you again, you've been extremely helpful.
Help with Droid X in Buffalo NY
ive tried everything I could for almost a week now.... Stuck in Bootloader Screen 30.04 Err A5,70,70,00,1F MEM_MAP Blank Service Reqd Battery Ok OK To Program..... I came to a Droid X last week from a Rooted for over a year Droid 1 with never a problem flashing... With new Droid X tried to flash Gummy Jar last sat without a wipe ( I know my stupidity thought coming from stock phone could get away with it trying to rush but boy was I wrong) after being stuck at loading gummy jar icons tried to factory reset... been stuck at the bootloader screen since.. tried flashing 1.13.6.2_1sbf and 2.3.32_1FF sbf... got newest drivers and rsd 4.8... ran as administrator... phone never shows either... got it once to do something in rsd saying phone was being programmed with 2.3.32 but when it said finished waited hours never rebooted .... stuck dont know what to do....anyone local want to give it a go email me please [email protected] or try to walk me through what i have to do step by step.... thanks
Here is what I have done.
I rooted with z4root. I have not done anything else (no roms or changes to the software) I do have adfree and wireless tether installed.
I have read the directions for the two part download to root, but I’m stuck at this.
IF YOU DO NOT HAVE THE MOST CURRENT RADIO .12P THEN YOU WILL NEED TO SBF BACK TO .340 AND THEN USE METHOD 2.
If I’m reading it correctly my radio is at .07P (Baseband version?)
Will I be able to use the patched update.zip process, or will It cause me issues.
Yes I am a noob, and I have no problem admitting it.
The 2 part download is for method 2 - that's what I used. I was rooted, but still on stock .340. Make sure you use a MD5 checker to verify the integrity of your 2 downloads! I put the 2 zip files in the root of the SD card and installed the Droid2 bootstrap program (not Droid X).
Start the bootstrap program, click on Bootstrap Recovery, click OK at the success dialog box, then click Reboot Recovery. Your X will reboot to a text interface. Use the volume keys to move up and down, camera button to select, and the Back button to go back.
Select install zip from the list and install the first zip file. DO NOT REBOOT YET!!!! Install the second zip file, then reboot. You should be on rooted Gingerbread with all your settings, homescreens, etc. intact.
Also, make sure you have USB debugging (Settings-Applications-Development-USB debugging) enabled.
First thanks for the help.
The radio difference is my hang up.
just noticed Im getting pushed the update now. I hpe i can stop it from running so I can get root again.
I had your same issue. I had rooted stock froyo, but my radio was 7 not 12. I read it a bunch of times, then came to the conclusion that he was talking about folks already on GB.
Everything worked fine using method 2. Only issue I have is with corporate sync, but that is busted for a coworker who did OTA update too. I think it is a separate issue.
I used droid2 recovery.
so, download away!
rooted fine. everything looks good, but I am one of those who can not find a wifi tether to work.
Here is the link to the new update to install just rename to update.zip place on the root of your sdcard then reboot recovery and install update.zip
http://www.4shared.com/file/ov_2h3JM/Blur_Version2320A955VerizonenU.html
Why would someone need to download this, shouldn't everyone be able to update over the air.
FYI really like 2.3 runs very nice on droid2
To answer your question, I would. I recently left verizon and now I cannot get the OTA update. I still use my Droid 2 for android development. I just don't use it for a phone.
That said. I can't use the above update. I SBFed my phone back to stock Froyo System version 2.3.20, installed z4root to load clockworkmod Droid 2 recovery, and finally attempted to flash the above file from the SD card. I get the following error:
assert failed: getprop("ro.product.device") == "cdma_droid2" || getprop("ro.build.product") == "cdma_droid2"
blah blah blah
(Status 7)
From the failed assertions I'm assuming this update doesn't recognize my phone as a Droid 2 and refuses to install the update. Does anyone know why that might be? Like I said I restored to stock before attempting this.
Wait a second. The file linked is called Blur_Version.2.3.20.A955.Verizon. That's the stock Froyo version. Is it called that because you need to be on that version or is this just an older file? I'm confused. Is this or isn't this the just released Gingerbread update?
It's an oddly named file, but the last time I saw that one linked it was the OTA. I still feel one is better off SBFing to stock and downloading it that way.
What's going on, I was following the steps on theunlockr but when I tried to extract the OG firmware my laptop said it was probably damaged, any way I can get the firmware somewhere else? I am running on Fission right now and want to go back to stock so I can scoop this update, it looks pretty nice. Please help me out if you can, thank you.
If you want to go back to stock to force the update the right way, the above file won't help you.
1. Get RSD Lite http://www.multiupload.com/HL0ZAL9GK8
2. Get Moto Drivers http://dl.dropbox.com/u/7632904/USB_Drivers_bit_4.7.1.zip
3. Get Froyo SBF http://bit.ly/dir7fq
Install the Moto Drivers on your pc, then boot into your bootloader and connect via usb. Then run RSD and load the SBF file. Once you complete that, reboot the phone and go to settings > phone info > check for updates. The new GB should be waiting for you, all official like.
Good looking out fam, will check in when finished!
Despite the odd name it is the correct file. But do not use CWM or bootstrap to flash it! Rename it to update.zip on root of sd card then use Stock recovery to flash it.
Sent from my DROID2 using XDA App
You're right it worked! I'm finally gingerbreaded. Thanks so much everyone.
Hello again, so my phone is just stuck on the Droid loading screen (Droid followed by the red symbol) I have no idea what to do although I followed the steps stated above.
**EDIT**
So I was able to fix this problem by wiping the cache as well as my data, thank you all!
idefiler6 said:
If you want to go back to stock to force the update the right way, the above file won't help you.
1. Get RSD Lite
2. Get Moto Drivers
3. Get Froyo SBF
Install the Moto Drivers on your pc, then boot into your bootloader and connect via usb. Then run RSD and load the SBF file. Once you complete that, reboot the phone and go to settings > phone info > check for updates. The new GB should be waiting for you, all official like.
Click to expand...
Click to collapse
I tried this exactly as stated and I cant get me droid 2 to be seen in the RSD. I get a drive letter when I reboot to recovery but nothing shows in RSD. Any ideas? I tried wiping data and cache and did a factory reset still nothing.
Back to a rom manager backup from yesterday atm.
Make sure your phone is in PC Mode (and possibly Debugging Mode) so RSD can recognize it.
JDunc said:
Make sure your phone is in PC Mode (and possibly Debugging Mode) so RSD can recognize it.
Click to expand...
Click to collapse
Thanks I made sure I have debugging on and in pc mode. I see Droid 2 when I have my phone powered on but when I reboot in recovery just a drive letter and nothing in RSD.
I just saw this
D2user said:
Despite the odd name it is the correct file. But do not use CWM or bootstrap to flash it! Rename it to update.zip on root of sd card then use Stock recovery to flash it.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Must have missed it the first time I read the thread I will try to install it as update.zip through the standard recovery and see if that works.
Ok I was able to get this on my phone with RSD the trick is to have your phone in PC mode and NOT to reboot it yourself the program will do it automatically. I got my phone updated but now it wont even give me the option to download the update OTA.
Yea I could've told you not to manually reboot. So you did a SBF to 2.3.2 and went into Settings > About > and System Updates and got nothing?
Correct I redid the sbf twice more to make sure it took.. when I go to settings > about > and system updates its greyed out.
UPDATE: I dededeee it, forgot to reactivate my phone after sbf the 3rd time. trying the OTA now
Ok phone is upgraded and rerooted.
1. sbf with RSD 3 times till it took
2. upgrade with OTA
3. rerooted with One Button Root
4. replaced progs with titanium
phone is fast right now, lovin it.
Glad you FINALLY got it working. Try out CM7 for GB. Do a backup before doing so and see if you like it. If not you can always restore back.
I think I may have done something wrong. My phone works but it restarts randomly, is there a way I can get it to stop this? Should I start from scratch or just get a different ROM?
Since Josuearisty has tested my sbf on his phone, it makes me think the method only works on the phone it was created on. Its actually really simple and easy to do, and I can give instructions for both Linux and Windows on how to make it. I posted instructions a few posts down, but they're vague cause I don't like typing a lot of text on my phone. Who does?
***Your always in the danger zone when messing with SBF files, I've done this method multiple times and it worked. If you follow the instructions word for word, you should be safe. Since I got this working for my phone, I thought everyone would like to know how I did it to make their own Custom SBF for when that bad time comes.***
Things Required
RSDLite or sbf_flash
stock sbf
adb setup and working
MotoAndroidDepacker
Thread With RSDLIte, SBF, and most everything needed..
Page with MotoAndroidDepacker and other helpful tools.
Step 1
Flash your phone with the Stock sbf from The thread also contains RSDLite, SuperOneClick, and MotoDrivers if you need them.
Step 2
Use the eeblueoffee trick to bypass blur setup.
Step 3
Enable Debugging at Settings/Applications/Development/Android Debugging
***Enable Screen Always on--its directly below Android Debugging. This is very important, the phone likes to freeze while doing dd commands and the screen shuts off midway.***
Step 4
Root Phone With SuperOneClick and Enable Non-Market Apps. Then Reboot Phone.
Step 5
Open A Terminal Or Command Prompt When Phone Boots Up
5a. adb shell
5b. su
5c. dd if=/dev/block/system of=/sdcard/CG39.smg then exit adb
5d. adb pull /sdcard/ E:\ (or whereever on your system you want it, E: is my ntfs shared partition)
Step 6
Open MotoAndroidDepacker
6a. Open Sbf and unpack it
Step 7
Replace unpacked CG39.smg with the dd CG39.smg from phone
Step 8
Open MotoAndoridDepacker
8a. Open folder with all the smg's
8b. Compile Sbf
Step 9
Your done, flash the phone with the newly created sbf.
***Its a good idea to wipe data\factory reset in between stock and custom sbf flashes. SBF Flashing doesn't wipe the \data\ directory and latent crap from the previous flash can be left behind. That's why you have to wipe data\factory reset after SBFing from a custom rom, if you're curious***
Step 4.5 (Advanced and Experemental)
You can add in any extras you want between steps 4 and 5. And they have to be added to the SYSTEM PARTITION ONLY. I've only added in 2nd-init Defy, and while it got the bootmenu DIRECTLY after an sbf flash, the only links that worked were Reboot and Shutdown. I'll look for a fix when I feel up to hours of sbf flashing again. You could try to either install Titanium Backup Pro and move apps like Bravo Sideload Enabler to the system partition, or use adb to install as a system app. To be safe, I'd do as little as possible, in as few of steps as possible, for example, I only touched my phone to enter eebluroffee and to enable debugging, that's all. Then uninstall TB Pro, and continue on to Step 5. Sorry for the Wall of Text, but all this is important.
HOW THIS WORKS
After the phone is flashed with the sbf, the system partition is signed DURING the first boot. By doing a diskdump, you're able to get the CG39.smg plus the key it gets on first boot, and since the signature is already there on your custom CG39.smg from the dd, it doen't get recreated when flashing your custom sbf and booting up. I was hoping the one I made was universal, but it doesn't seem to be. I'll try to make one for us (a universal preroot) if its even possible.
***Original Post*****
Like the title says, a prerooted sbf. I've tested this three times, with a stock sbf and full data\fatcory reset in between each flash. Only tested on Linux with sbf_flash. No RSDLite on Windows since I don't have it installed to test with.
You still have to use Bravo Sideload Enabler from market for non market apps. I plan to change that. I'm halfway there already, I know which xml to edit to enable non market apps, but am unsure of the syntax used in AndroidManifest.xml to edit it before compiling the apk. Another idea is to make Bravo Sideload Enabler a system app and part of the sbf, but I didn't think of it until just now, literally, right now.
With this sbf, to flash CM7 or any custom rom, the steps are simply Flash sbf, Bravo Sideload Enabler, Defy 2nd-init, flash rom.....that's it.
Also, to get around the blur setup, type eebluroffee on the soft-keyboard on the very first screen you get to, just press the menu "button" for a second or so. Sometimes it takes a few times to work.....but eventually it does.
Link to sbf: http://www.mediafire.com/?tx1sdgftp9ng5b6
Thank Josuearisty for giving me the idea, and Epsylon3 for his informative post with all the information I needed to make this.
I also tried adding in Defy 2nd-init. After flashing, it would go to the custom bootmenu, but nothing worked.
skeevy420 said:
Like the title says, a prerooted sbf. I've tested this three times, with a stock sbf and full data\fatcory reset in between each flash. Only tested on Linux with sbf_flash. No RSDLite on Windows since I don't have it installed to test with.
You still have to use Bravo Sideload Enabler from market for non market apps. I plan to change that. I'm halfway there already, I know which xml to edit to enable non market apps, but am unsure of the syntax used in AndroidManifest.xml to edit it before compiling the apk. Another idea is to make Bravo Sideload Enabler a system app and part of the sbf, but I didn't think of it until just now, literally, right now.
With this sbf, to flash CM7 or any custom rom, the steps are simply Flash sbf, Bravo Sideload Enabler, Defy 2nd-init, flash rom.....that's it.
Also, to get around the blur setup, type eebluroffee on the soft-keyboard on the very first screen you get to, just press the menu "button" for a second or so. Sometimes it takes a few times to work.....but eventually it does.
Link to sbf: http://www.mediafire.com/?tx1sdgftp9ng5b6
Thank Josuearisty for giving me the idea, and Epsylon3 for his informative post with all the information I needed to make this.
I also tried adding in Defy 2nd-init. After flashing, it would go to the custom bootmenu, but nothing worked.
Click to expand...
Click to collapse
Great, I always thought about it, its a good thing for us.
I'd like to try on Windows and RSD Lite but I'm afraid of damaging my phone.
It shouldn't hurt. Like I said, I've already flashed it 3 times. Or 7 sbf flashes in the past few hours, including stock flashes. I'd appreciate an RDS Test. I don't really want to flash the sbf again....I restored my WR1.4 nandroid only 45 mins ago after about 6 hours of testing this. I'll be back on in the morning, it's 1am here and I'm getting tired.
skeevy420 said:
It shouldn't hurt. Like I said, I've already flashed it 3 times. Or 7 sbf flashes in the past few hours, including stock flashes. I'd appreciate an RDS Test. I don't really want to flash the sbf again....I restored my WR1.4 nandroid only 45 mins ago after about 6 hours of testing this.
Click to expand...
Click to collapse
at least if we are rooted, we can download terminal emulator from play store and install bravo sideloader enabler from sd card.
I cant download sideloader from market cause I dont live in US, at least is a great advantage for us!
I could make sideload enabler a system app installed by default. Give me a day or two for that.
Error on Windows with Rsd Lite, just showed me the logo and then back to bootloader.
Thanks God I was able to flash the original sbf file again.
Damn. Maybe the method I used only works on my phone. It's easy to do.
After stock sbf flash, do the eebluroffee trick.
Root with SuperOneClick
Adb shell
su
dd if=/dev/block/system of=/sdcard/CG39.smg
adb pull /sdcard/CG39.smg E:\
Decompile stock sbf with MotoAndroidDepacker
Replace stock CG39.smg with created one
Repack sbf with Depacker
Flash
See, its not that hard. That's all I did and it worked perfectly for me.
It's possible it only works on the phone that makes it. And you HAVE to edit the system dump. If you edit stock sbf's CG39.smg, it gives bootloader error. With this method, you could technically make a CM7 sbf.
Anybody with linux try my sbf with sbf_flash?
skeevy420 said:
Damn. Maybe the method I used only works on my phone. It's easy to do.
After stock sbf flash, do the eebluroffee trick.
Root with SuperOneClick
Adb shell
su
dd if=/dev/block/system of=/sdcard/CG39.smg
adb pull /sdcard/CG39.smg E:\
Decompile stock sbf with MotoAndroidDepacker
Replace stock CG39.smg with created one
Repack sbf with Depacker
Flash
See, its not that hard. That's all I did and it worked perfectly for me.
It's possible it only works on the phone that makes it. And you HAVE to edit the system dump. If you edit stock sbf's CG39.smg, it gives bootloader error. With this method, you could technically make a CM7 sbf.
Anybody with linux try my sbf with sbf_flash?
Click to expand...
Click to collapse
I have done that before, not decompile sbf with motoandroiddepacker, I made a backup of system using those commands.
I think that SBF will not work with any other phone, but at least is a big advance.
If everybody can do it, they will be able to flash their custom SBF alredy rooted and maybe with any other apps.
---------------------------------------------------------
The thread you posted with rsd lite and sbf file is dead, links are not working, use this post in the same thread:
http://forum.xda-developers.com/showpost.php?p=22706722&postcount=66
I uploaded the files again, I'll create a post with these files.
That thread worked 4 months ago dammit.
I hope it does lead to better things, but its worth the 10 minutes of effort to make you own personal preroot sbf, and easy to do in my opinion.
Also sort of related, I think we have version 3 bootloader. That explains why if you flash a Defy sbf, you can't go back. It changes efuse level and you can't change efuse down, only up.....its what screws Defy users who go sbf crazy and flash the first thing they see. We don't have that problem cause we only have the one sbf..... Damn you Motorola.
skeevy420 said:
That thread worked 4 months ago dammit.
I hope it does lead to better things, but its worth the 10 minutes of effort to make you own personal preroot sbf, and easy to do in my opinion.
Also sort of related, I think we have version 3 bootloader. That explains why if you flash a Defy sbf, you can't go back. It changes efuse level and you can't change efuse down, only up.....its what screws Defy users who go sbf crazy and flash the first thing they see. We don't have that problem cause we only have the one sbf..... Damn you Motorola.
Click to expand...
Click to collapse
I made a custom SBF now and it didnt work, what version of motodepacker did you use?
Is there anything else to do?
What about sbf calc, I think it is to determinate if sbf is good or not, I dont know.
Version 1.3, not the mono one. I didn't use sbf-recalc, only used it once ever 8 hours ago actually. Do you have access to Linux and have a blank cd handy? Try flashing with sbf_flash since its what I used. I'll try with RSDLite tomorrow night, about 20 hours from now. I just installed White Rabbit Test2 and I'd like to run it for a day to see how it performs and it likes my tweaked smartass.
The instructions I posted were the ones I used, on both Windows and Linux, and worked twice. The first time I tried, all I did was edit it with " mount ./cg39.smg ./cg39 -o loop" and that didn't work. The only thin you could do different is to replace dd if=/dev/block/system with dd if=/dev/block/mmcblk1p25 the of= part stays the same.
Another possible problem is your memory card became full during the dump. It will just quit without error. You should have at least 400mb free to be safe, 330mb BARE minimum and probably not very safe. With only adding root\superuser, the created sbf should only be 378,546,533 Bytes & 378,546,533 Bytes. Those are the exact filesizes of the first two sbf's I made. Yes, they're the same size. The md5 is different.
92cb645d5a04d1221f81ee566072149f ./firmware.sbf (1)
fc4e49adf931377c8ccbd3943b3664ba ./custom.sbf (2)
I used the second one I made two more times before I posted to make sure it did work, and once earlier this evening when I flashed the wrong defy zip.
I first came across this method on a post from Epsylon3 at Defy dev on a post about BL7 sbf's not being able to root. I came across it a second time somewhere here on xda and it explained it with a bit more detail, but I had already made my second sbf by then and it worked....and I was ecstatic.
skeevy420 said:
Version 1.3, not the mono one. I didn't use sbf-recalc, only used it once ever 8 hours ago actually. Do you have access to Linux and have a blank cd handy? Try flashing with sbf_flash since its what I used. I'll try with RSDLite tomorrow night, about 20 hours from now. I just installed White Rabbit Test2 and I'd like to run it for a day to see how it performs and it likes my tweaked smartass.
The instructions I posted were the ones I used, on both Windows and Linux, and worked twice. The first time I tried, all I did was edit it with " mount ./cg39.smg ./cg39 -o loop" and that didn't work. The only thin you could do different is to replace dd if=/dev/block/system with dd if=/dev/block/mmcblk1p25 the of= part stays the same.
Another possible problem is your memory card became full during the dump. It will just quit without error. You should have at least 400mb free to be safe, 330mb BARE minimum and probably not very safe. With only adding root\superuser, the created sbf should only be 378,546,533 Bytes & 378,546,533 Bytes. Those are the exact filesizes of the first two sbf's I made. Yes, they're the same size. The md5 is different.
92cb645d5a04d1221f81ee566072149f ./firmware.sbf (1)
fc4e49adf931377c8ccbd3943b3664ba ./custom.sbf (2)
I used the second one I made two more times before I posted to make sure it did work, and once earlier this evening when I flashed the wrong defy zip.
I first came across this method on a post from Epsylon3 at Defy dev on a post about BL7 sbf's not being able to root. I came across it a second time somewhere here on xda and it explained it with a bit more detail, but I had already made my second sbf by then and it worked....and I was ecstatic.
Click to expand...
Click to collapse
Im a little bit afraid of breaking my phone, just thinking about a hardbrick make not to follow with this now.
Well I used the mono one, I was not out of memory 16gb with only 2 in use.
I think the backup was fine, maybe it was something with motodepacker.
I'll try later, I think I'll try with a cliq xt I have, which has some problems, that way if something is wrong, I wont be losing a big thing!
I understand that hardbrick fear. This is my only phone. My backup (oldscool razr) crapped out a while back, so I sat there looking at that terminal with the first sbf for 5 mins before the first flash, then when it didn't boot, I was like oh f&^k. Flashed stock, made the 2nd, and it worked. Made a third and it's my new sbf.
skeevy420 said:
I understand that hardbrick fear. This is my only phone. My backup (oldscool razr) crapped out a while back, so I sat there looking at that terminal with the first sbf for 5 mins before the first flash, then when it didn't boot, I was like oh f&^k. Flashed stock, made the 2nd, and it worked. Made a third and it's my new sbf.
Click to expand...
Click to collapse
Well, I do it easy.
After flashing is completed:
I write eebluroff in the motoblur screen.
Enable debugger in applications.
Install sideloader enabler apk with adb
Install gingerbreak to root and 2nd init to install custom recovery from SD Card and restore my backup.
That's all I do when I flash with RSD Lite, I wish at least that the SBF file would come with sideload enabler pre-installed or the ability to install from sdcard!
I noticed quite a few market enabling apps yesterday. Couldn't test cause I'm on wr1.4.
Never used gingerbreak.
2nd-init didn't function properly after sbf flash. Only access to bootmenu, shutdown and restart.
Try SuperOneClick 1.9.5. Its version I used.
Also, enable screen always on. Stock became iffy during adb when screen went off.
skeevy420 said:
I noticed quite a few market enabling apps yesterday. Couldn't test cause I'm on wr1.4.
Never used gingerbreak.
2nd-init didn't function properly after sbf flash. Only access to bootmenu, shutdown and restart.
Try SuperOneClick 1.9.5. Its version I used.
Also, enable screen always on. Stock became iffy during adb when screen went off.
Click to expand...
Click to collapse
2nd init copies some files to a folder that maybe is in another code group.
At least with sideload enabler for bravo, it would be great.
We just have to install gingerbreak from sdcard to root and 2nd init defy.