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.
Related
I just want to remove the clockworkmod recovery to regular or stock recovery? I found the info for EVO 4g and it said not to use for anything else. Could someone, please tell me how to remove clockworkmod recovery and change it back to stock?
First- this applies if you are on 2.2 ota- not 2.1 or leaked 2.2
The easiest way now might be simply starting from scratch. The 2.2 ota sbf was released last night so you can use it to restore your phone to factory state. You will need the SBF and the latest version of RSDLite. Google...
VRZ_MB810_2.3.15_1FF_01
and something should come up. It is a large file. 430mb or so. (unzipped)
Also google rsdlite 4.8 it is not a very large file. I have never done the sbf before- but there is a guide on the droid x rootzwiki...
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
WARNING!!! make sure you are using the FULL SBF for 2.2! there is a sytem sbf for 2.2 that you don't want and there is the 2.1 sbf that you definitely don't want.
There may be just a simple uninstall- but I don't know how. I am a newb. Maybe a veteran will chime in with some help?
Thank uou.
I was able to do that lastnight. before I got home from work, I downloaded SBF file with myDX. It took me an hour. By 8:00 pm my phone was rooted again without clockwork mod.
Cyc323 said:
Thank uou.
I was able to do that lastnight. before I got home from work, I downloaded SBF file with myDX. It took me an hour. By 8:00 pm my phone was rooted again without clockwork mod.
Click to expand...
Click to collapse
Cool. Since I have never done it before- did you just follow the rootzwiki guide? And was it pretty straight forward? And- how long once you actually started RSDLite did the process take (assuming you used RSDL)?
thanks.
It wasn't painful. I used rsd lite 4.8. I searched for info on 4.8 but everything is on 4.7, even on rootzwiki . On 4.7 you are suppose to move an .ini file to another place. I saw a similar file but without the .ini extension. I thought maybe this is one of the improvement of 4.8 over 4.7. You also have to do the bootloader thing. The whole process took about less than 10 minutes. I was surprised that nothing on the phone was erased other than titanium backup. Wallpaper and Launchpro's settings were still intact.
Alright, I wanna make sure I know how to do this, just in case.
If I need to fully unroot my phone and restore it to the way that I got it from Verizon Wireless, do I use the SBF from here? Just wanna make sure because I might need to bring in my Droid 2 in to Verizon within the next few days :\
Yup, that's the one. You'll also need RSD Lite 4.8 or 4.9 and a charged battery. Don't try flashing the SBF with a drained battery as you'll end up with a phone that's not flashed, won't charge, and can't be flashed until you get a charged battery.
Chiggins said:
Alright, I wanna make sure I know how to do this, just in case.
If I need to fully unroot my phone and restore it to the way that I got it from Verizon Wireless, do I use the SBF from here? Just wanna make sure because I might need to bring in my Droid 2 in to Verizon within the next few days :\
Click to expand...
Click to collapse
Yes if you have the 2.3.20 update (you should by now) then you need the 2.3.20 sbf. you can use two different ways to flash the sbf to your D2. You can do it in windows with RSDlite or you can do it in linux with the sbf_flash script. Don't have linux you say? well I made an ubuntu livecd that can be ran on any computer for a linux environment with adb and the sbf_flash file on it. All you need to bring is a CD to burn it to and the sbf file (couldn't include due to space issues) on a flash drive. Follow thistutorial for linux and thisone for windows. I've used the linux version myself even though I'm on windows right now. It's just a lot easier to do and you don't have to worry about driver issues or having the right version of RSDlite (some versions don't detect the phone as well for some people).
Also if you do use the windows tutorial. Just make sure you have the right SBF the rootzwiki one is outdated.
I'd read both tutorials twice just to be sure you know what you are doing before you get into it.
Alright cool. Yeah I have Linux so I'll just be doing it off of there.
Will this also take off any rooting at all and the ClockworkMod recovery?
Chiggins said:
Alright cool. Yeah I have Linux so I'll just be doing it off of there.
Will this also take off any rooting at all and the ClockworkMod recovery?
Click to expand...
Click to collapse
Yep back to stock before that stuff was installed. But your backups will still be on your sd card so if you decide to get tweaking again you can just reroot and reinstall bootstrap and restore from a backup to a ROM that has the 2.3.20 version.
Remember to update the baseband with the update file (before rerooting) as noted in the ubuntu thread if the sbf_flash script fails to update the baseband.
Is making a nandroid backup of your stock image first then restoring it and deleting bootstrap not the same?
Just need some clarification here, I know sbf will pretty much flash phone back to factory settings but are there really much traces when doing the process I mentioned?
Masx said:
Is making a nandroid backup of your stock image first then restoring it and deleting bootstrap not the same?
Just need some clarification here, I know sbf will pretty much flash phone back to factory settings but are there really much traces when doing the process I mentioned?
Click to expand...
Click to collapse
Yeah there are traces which is why it's recommended before flashing some ROM's that you should SBF or risk getting some fun bugs. I don't know what all residual stuff is left but I know that it can cause problems.
newk8600 said:
Yep back to stock before that stuff was installed. But your backups will still be on your sd card so if you decide to get tweaking again you can just reroot and reinstall bootstrap and restore from a backup to a ROM that has the 2.3.20 version.
Remember to update the baseband with the update file (before rerooting) as noted in the ubuntu thread if the sbf_flash script fails to update the baseband.
Click to expand...
Click to collapse
Alright, so I'm doing the sbf_flash script from my Linux computer. It recognizes my phone whenever I do adb devices. So, I turned off my phone, then turned it back on while holding the up arrow, so now its a the bootloader screen, D2.37. It says Battery OK, OK to Program, and that the transfer mode is USB. So I run the command to flash 2.3.20, and I get an error saying Segmentation fault. So, where do I go from here?
Chiggins said:
Alright, so I'm doing the sbf_flash script from my Linux computer. It recognizes my phone whenever I do adb devices. So, I turned off my phone, then turned it back on while holding the up arrow, so now its a the bootloader screen, D2.37. It says Battery OK, OK to Program, and that the transfer mode is USB. So I run the command to flash 2.3.20, and I get an error saying Segmentation fault. So, where do I go from here?
Click to expand...
Click to collapse
Are both the SBF and the sbf_flash file in your home folder?
Yep, as they should. I just said to hell with it though, and used your LiveCD.
Cool if you aren't already back up and you have any issues just post in there so I can be notified instantly.
Ok, I installed Clockwork a while ago, then removed it and unrooted (I no longer needed root access, and I'm not doing any image flashing or anything that requires it). But after removing clockwork, it still boots to that first when I reboot my phone. In case if I ever have to take my phone in to VZ or something, how do I stop it from booting to that? I'm guessing it's not just a normal app, since I've reset to factory since then to try to resolve another issue, and it's still appearing, so I'm guessing it installed itself into the ROM.
I basically rooted my phone originally to install Titanium Backup before doing the factory reset, then I was thinking of trying some custom ROM's, but I decided not to (other than a performance increase, there's nothing else I really care about right now that custom ROM's would provide). So I installed Clockwork Mod and everything else RLM703 listed (http://forum.xda-developers.com/showthread.php?t=814299&highlight=guide), then removed everything after I decided not to mod it.
I can understand your concern on the not flashing, however if you do not flash i think you also still have the Superuser app (even ifyou dont have root rights) that itself would also void your warranty. The easiest, fastest, and safest way is to Flash it using the Method below.
Go To (droid-life .com /2010/09/21/how-to-return-droid-x-back-to-android-2-1/)
((**As a new user i cant post outside links so delete the spaces after life com in order to get the proper working link.))
**
You will download 2 things. The SBF for 2.1 (Which afterwards you can use OTA to reupdate to 2.2).
RSD Lite: This program is used by Motorola to flash phones so its not some unstable application that will mess up.
After you install the drivers, THEN install RSD Lite. You must Run RSD Lite as an administrator. Shift Click RSD Lite and choose Run as Administrator (Even if you are on an administrative account). Afterwards you just navigate from RSD lite to where you have your SBF Saved, Boot your phone into bootloader, then press start. Takes about 5 minutes and you are back to a brand new Droid X.
Like i said i understand your concern on this, and im deeply sorry if you get a rare case and it does decide to mess up, but i just flashed my phone 3 times yesterday using this method and never had a problem.
Hope this helps!
Ok, I know I created a backup through ROM Manager before I stalled Clockword Mod Recovery, but now I can't find it... However, I've been having some minor issues with my phone ever since I updated to 2.2, so maybe I'll just find a stock SBF and flash back to that... That link I posted has a droid x guide, with a link to a stock 2.2 SBF, so I can just grab that and flash it tonight or something. Or even just download it at home and keep it in case if I need it down the road...
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
Hey!
I had CM10.2 on my Defy+, and tried to just follow Quarx simple post:
http://forum.xda-developers.com/showthread.php?t=2515036
I had some trouble with the update recovery (bad zip), reformatted my SD with sdcard.org's official formatting tool, and it worked.
The Quarx website seems to be down, so I downloaded the CM11 rom with the most recent date from http://defy.bytekiste.de/cm11-nightly-defy+/
Which is where I got the update-recovery as well, so I figured that would be fine.
Got a status 7 error (this package is for "MB526" but your device is ""), so I tried fiddling with the verification, editing the rom script (those few lines you have to delete), according to various topics on the status 7 subject. Nothing worked.
People in treads advice different recovery files, so I manually flashed TWRP from here:
http://teamw.in/project/twrp2/91
I rebooted into recovery again, an it just gives a blank (but lit) screen. I can still access the bootmenu, but not recovery, so I guess TWRP doesn't work with my phone. Should have read the comments on that downloadpage I guess... So I went on to find this "goomanager" people are talking about but all I get are dead links, so I tried the ROMManager and TWRPManager apps, but I can't find any reference to Defy+, Jordan or MB526 within those apps when they ask you to select a device.
I'm not an expert, so I was like, lets start all over from scratch to get recovery working again. Any recovery, I don't care. So I went back to:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which is what I used for when I bought the phone to get root, bootmenu & recovery through ADB from the windows command line.
I'm trying to follow that to at least recover the ICS recovery which I had, but I'm stuck there as well. When I switch USB from mass storage mode to "tools only", ADB disconnects, and when I leave it in mass storage mode, well, the sdcard is not mounted to the phone so I can't use ADB on it.
Can anyone give me a push in the right direction? Can I restore the update-recovery from Quarx CM11 thread somehow?
So I got adb to function (how, I do not know), ran the stuff here:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which gives me Bootmenu 0.6.1 (I had Bootmenu 2.0.0 before?). And it doesn't include a functional recovery, or a functional 2ndinit, so I completely (soft)bricked my phone now :laugh: Both recovery & boot give errors about missing sh scripts.
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
okdewit said:
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
Click to expand...
Click to collapse
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files -- yes, you have to go through several pages to get there and then you have to select the specific sbf that you want, but it's there (here for Defy: http://sbf.droid-developers.org/phone.php?device=27 or here for Defy+: http://sbf.droid-developers.org/phone.php?device=28).
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
JimboN said:
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files
Click to expand...
Click to collapse
Yesterday when I tried it, the whole droid-developers website just gave an Nginx server error, but I'm glad to see it's up again. Gonna load up RSDLite now and give it one last try!
JimboN said:
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
Click to expand...
Click to collapse
I fully realize that, it's mostly frustration with myself and a series of bad actions which led me to lock up my phone further and further with each action. I realized the risk in advance, so luckily I do have a full backup and a backup phone, but it still hurts a bit to see your beloved device dying on the operating table because of your own stupidity.
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
okdewit said:
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
Click to expand...
Click to collapse
Glad to hear you were successful.
Yep, know the frustration of my own stupid actions screwing up my phone and when you go to fix it, that don't work right either -- been there & done that.
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
I've found one BIG culprit in my previous methodology: copying files through motorola phone portal is just plain wrong. I kept getting "bad zip" and other verification errors. Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well. I've also used the windows program Teracopy (for CRC checks) instead of the built-in windows explorer file copier. :good:
Thanks a lot for the support, if you had not pointed out that the SBF filehost was working fine again, this nice phone would've been thrown away.
okdewit said:
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
Click to expand...
Click to collapse
Fantastic! CM11 works better for me than any other rom that i've tried (certainly smoother and probably faster), still has a few bugs but so did all the others. Best of all it's the latest android and can run all the latest apps.
okdewit said:
Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
Click to expand...
Click to collapse
Hmm... That's interesting. I've used USB Mass Storage to do just what you attempted to do without a problem -- good to know as a potential issue.
okdewit said:
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well.
Click to expand...
Click to collapse
Thanks for the tip.