Related
I used Root Checker to make sure I have root and that I'm good to go but CWM isn't working when flashing ROMs. I also tried booting into recovery but flashing anything just makes the phone reboot.
I'm running Steel Droid v.2 but I can't flash any new roms.
I'm in the same boat, for some reason when I try flashing anything, I get a "E:Can't open (bad)"
I can restore backups of my debloated stock, and SD2, but can't flash anything now for some reason (SD3, narcotICS, etc)
Even just tried to SBF back to stock, wiped everything out, re-rooted, installed the Bootstrap, installed CWR, and still nada.
lordgodgeneral said:
I'm in the same boat, for some reason when I try flashing anything, I get a "E:Can't open (bad)"
I can restore backups of my debloated stock, and SD2, but can't flash anything now for some reason (SD3, narcotICS, etc)
Even just tried to SBF back to stock, wiped everything out, re-rooted, installed the Bootstrap, installed CWR, and still nada.
Click to expand...
Click to collapse
Thats werid ive never heard of that problem hmm.. after you installed bootstrap click on it and click install recovery. Also try installing the cwm on rom manger. If that doesnt work try scrolling all the way to the bottom in rom manager and downgrading a cwm version to see if that works. Otherwise im not sure :/
Sent from my STEEL DROID3 using XDA App
Are you guys using the latest version?
Sent from my DROID3 using XDA App
Yeah I'm using the latest version of CWM.
I can't even flash ROMs from Recovery though. No idea what's going on.
Found out what my problem was. For some reason, was getting a bad download, had to redownload all the roms again. Weird thing is the MD5 sum was correct on them, but even trying to open the zip files on the computer was throwing errors.
Never ran into this problem before, so really weird, but all is working now.
Fixed the problem by reinstalling Droid 3 bootstrap. Woot!
Sent from my DROID3 using Tapatalk
Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.
Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.
Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..
Still reboots to cwm... it won't flash stock recovery. Any ideas?
xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
OP updated for the new packages from mtmichaelson
xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.
Just reinstalled busybox... got it!
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?
How can I install two ROMS (MavROM and ICS) on my D3? one in SAFE MODE and one without.
what programs to use?
I already have MAVROM installed with SAFESTRAP from hashcode, but if i disable it, i get the stock rom.
thank you.
You have to use a bootstrap to flash your nonsafe before you install safestrap
Sent from my XT860 using xda premium
can you direct me to a link to that application? all I can find is safestrap from hashcode.
i have this one: "Droid3CWBootstrap"
http://www.appbrain.com/app/droid-x-recovery-bootstrap/com.koushikdutta.droidx.bootstrap
but how can I install zip with it?
I'm sorry I didn't see your last PMs
Anyway.
1) Start in stock ROM http://forum.xda-developers.com/showthread.php?t=1336980
(Or your non-safe ROM in safestrap and then remove safestrap)
2) After root, download bootstrap (I uploaded it) http://www.mediafire.com/?3u8xhmsp3lg5yfx
3) Install the APK and open the bootstrap app. Press install recovery then reboot recovery. You're now in bootstrap, not from using vol -+ etc (from your PM)
4) Flash mavrom using their CWM Recovery instructions
5) Once you got it setup, remove bootstrap app and install safestrap http://goo.gl/1pr5T
6) Reboot into safestrap and switch to safe system. Make a backup if you want before swithing. The switch will backup your current ROM (data), which is mavrom. Once in safe-system you can now flash ICS using the instructions. This will flash ICS in a different place. When you go back to non-safe system your mavrom will be restored.
Hope it's clear now
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
bogdan_wrc said:
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
Click to expand...
Click to collapse
Np aside from the fact that I'm not on XDA all day the notification is very small - most of the time I don't see it until the next day
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
zzandrewst said:
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Endoroid said:
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
zzandrewst said:
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
you can't flash nonsafe with safestrap. Gotta use a bootstrap to flash your nonsafe, then install safestrap for flash safesystem. But yes, i have liberty as my nonsafe and ics as my safe
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
what to do?
I dont have the INSTALL from zip option, just UPDATE from zip.
that why i used safestrap.
but if I want to install the boot animation from RAZR, now in which location shall I do that? it used to be in /system/media folder. still there?
thank you, i managed to install both one successfully.
bogdan_wrc said:
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
Click to expand...
Click to collapse
I think thats because you tried to flash using original recovery, you said something with -+ volume buttons?
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Really a fastboot flash isn't such a big deal. I've done it more times than I can count. Takes 10 minutes. Id rather have my fav rom in nonsafe so I can use safe to testing new roms and new ics builds
Sent from my XT860 using xda premium
Is this dual boot system possible for my phone ? I would like to switch froyo and cynaogenmod !
Sent from my Optimus Me using XDA App
DoubleYouPee said:
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
Click to expand...
Click to collapse
I think you miss a key point. When you boot safestrap it starts in the non-safe system no matter what you do. Depending on your mode it then moves you to a totally separate partition on the device, preventing you from doing any harm to the boot rom.
The non-safe is key for the entire system to work. Yes it can be any rom, but you do put yourself at risk of losing two installs, including all the data.
Easy unbrick may be as fast to get to stock, but to rebuild back to where you were is going to take a lot longer.
In the end I am just advising caution, not telling people what to do. It does go against what the system was designed for and people should be aware of that before jumping off the ledge.
I understand, but now I have to go back to bootstrap to do essentially the same thing
Not sure if I follow you..
If you are only working in Safe-mode Rom the worst you can do is blow that rom up. Fixing it is just a matter of restoring your last backup via Safestrap recovery.
The problem with working in non-safe rom is that you can blow up both and lose your recovery. From that point you have to do Fastboot, install bootstrap, restore non-safe backup, install SafeStrap, restore Safemode backup.
Unless I am not understanding you correctly.
I've been struggling installing custom roms on my phone so I figured I'd document the process to help out anyone else starting out. I'd like to thank everyone for helping me figure this out and for the hard work of the community for making this possible.
Edit: My goal was to come up with a way to install CM9 while leaving the original system it came with and all my settings and apps. I understand how to do TitaniumBackup and how to save specific apps/files to but I wanted an exact backup of my original system alongside any custom rom so I just wrote down the steps I used to make it happen.
Root the system
1.First apply one click root using this tool
Further instructions here: http://forum.xda-developers.com/showthread.php?t=1319653
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
Droid 3 CWM (ClockWorkMod)
2. Install this apk onto the phone and click the first button then the second button
http://forum.xda-developers.com/attachment.php?attachmentid=882933&d=1328117678
3. Boot into recovery and make a backup of your system
4.Apply Fastboot package for UMTS XT860 Iusacell Mexico using RSD Lite 5.5
Further instructions here:
http://rootzwiki.com/topic/4370-sbf...959-and-56890/page__view__findpost__p__100987
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
RSD Lite: http://www.multiupload.com/T6NOEBKKLO
5. Reroot using 2.3.6 Zerg tool
Basically after flashing with RSD Lite then re-root using this tool:
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
6.Re-install CWM (Droid 3 Bootstrapper from step 2) and then apply the Bell rar file as a nandroid restore.
Further instructions here: http://forum.xda-developers.com/showpost.php?p=21446640&postcount=112
https://rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar
7. Reboot into the system and let the OS load again then re-install cwm (no need to reroot) and reboot back into recovery.
the trick to booting into recovery the second time is to turn the phone off, hold the m key while pressing the power button, plug in the phone to usb, choose bp tools
source: http://forum.xda-developers.com/showpost.php?p=21474818&postcount=120
restore your original backup from step 3 using advanced restore and restore the Data only and then wipe cache and dalvik cache
8. Remove CWM and install safestrap instead it involves using adb shell and removing certain files instructions found here:
http://www.droidforums.net/forum/dr...d-help-removing-clockworkmod.html#post1801072
9. Install SafeStrap once CWM is removed just install it, reboot and press the menu key while booting
http://dl.xda-developers.com/attach...5/7/9/2/5/Droid3_Safestrap_Tweaked_v1.08d.apk
10. ICS Install, at this point you have prepped your system so you can install CM9 otherwise it won't boot on the stock Bell 2.3.4
Instructions here: http://forum.xda-developers.com/showpost.php?p=22254669&postcount=61 (start at step 8 or 9 in those instructions)
-Apply CM9 Alpha 6 Zip
http://www.hash-of-codes.com/files/cm9-droid3-20120130-1730.zip
-Apply XT860 Sub-Patch (by Rick#2) for ICS Zip
http://bit.ly/Ah5b6d
Further instructions here: http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Great tutorial
As a note, in step 6, you could flash any custom rom to /system. You might not be able to restore /data though. Can try and if no go do a data wipe. If you backup apps with titanium backup and call logs/sms/mms with mybackroot its not such a big deal. Just redownload those 2 apps and restore everything(honestly I rarely nandroid, only if im doing something im confident will end in a fastboot flash, I just use those 2 apps). Im running liberty in /systemorig and eclipse in /system
Sent from my XT860 using xda premium
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Endoroid said:
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks for the tip I wouldn't have been able to get this far without your help Endoroid. I'll edit the How-To to use the same root twice, I wish mods would sticky more useful posts like zerg's root instead of pete's root and How-To such as this one.
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
ncho2233 said:
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
Click to expand...
Click to collapse
First, you may wish to just go with safestrap and try flashing g rom in safe mode. If it bootloops no harm done because your bell /system is intact
If that fails you can try using motofastboot instead of rsdlite to just flash /system. You can restore your /system with your nandroid.
As far as I know roms should work with bell 2.3.6.
If you do end up flashing the whole fastboot package with rsdlite you can make your phone appear to be bell stock. You can restore your nandroid and then mod the build.prop so about phone shows bell info. The warranty guys would have to look deep to see its been changed.
Its up to you ultimately but as I said I don't think you would have to flash the fastboot. Safestrap should work as is on bell 2.3.6. As long as you don't mess with /systemorig (nonsafe mode) its easy to remove the evidence. Uninstall safestrap recovery and remove su/superuser
If I recall correctly dasilva had his issue due to being on 2.3.4 and unable to update.
Sent from my XT860 using xda premium
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
ncho2233 said:
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
Click to expand...
Click to collapse
Correct
Safestrap was built with the idea of keeping your phone intact. You can still easily receive OTA updates and can return your phone to stock if you need to get warranty repair done
Sent from my XT860 using xda premium
dasilva333 said:
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
Click to expand...
Click to collapse
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
白い熊 said:
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
Click to expand...
Click to collapse
+1
1of16 said:
+1
Click to expand...
Click to collapse
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
danifunker said:
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
Click to expand...
Click to collapse
Thanks, and I can use it on my XT862 too?
is it possible to install the latest OTA (5.7.906), which I want to use as stock rom?
Hello everyone!
Iv recently acquired a new milestone 3, and after gettint out of the box only did the one click root service to root it up, and installed bootstrap / rom manger and so on. But when I power off the phone holding X I get into a ! triangle screen, which I cant even power down the phone via button.
Also booting with M, or both vol buttons I can get into a list of options, but recovery, bt tools or any other wont get into the recovery mode.
is there any other way? clockwork mod is already installed says the app, and the normal boot goes ok.
Iv downloaded from another post the CM7 which I wanna install, but impossible without the recovery mode.
any help appreciated, all Iv found in the forums was how to get into recovery, but none worked for me.
... never mind
If you are using cwm, make sure you are using the DROID 3 bootstrapper. There is no way to enter recovery without it.
Imo, you should use safestrap (the official version) . It's way better. Because the only way to get to recovery when you have cwm is the bootstrap app, if you bootloop your phone, the only solution is an sbf. Safestrap retains access to the custom recovery.
EDIT: I saw you installed the bootstrap. To get to recovery, open the app and click the reboot recovery option, then reboot your phone.
Sent from my DROID3 using xda premium
both options: bootstrap recovery and reboot recovery goes to normal boot into the OS.
since its a payd up app, already sent email to the devs so I can help troubleshoot whats going up on my device, but got no answer.
Odd. Make sure you hit bootstrap recovery, wait for it to say success, then hit reboot recovery.
Sent from my DROID3 using xda premium
I've had that.problem before with the bootstrap before. I could not get it to work no matter what. Rerooted, made sure I had su, busybox etc. Sbf'd and did it all again. Just use safestrap, it works. Just uninstall your bootstrap first
Sent from my XT860 using xda premium
http://db.tt/XzRiaG55
This is the modded version. Its supposed to be able to flash both safe and non safe modes but it doesn't. You can only flash in safe mode. But it does have a console included which can be handy. Its still cwm but redesigned ui. Note that if a rom isn't specifically meant for the xt860 you will need a patch for it. So far only eclipse 3.0 and mavrom 4.0 have xt860 version. I'll also find you the sbf for you. Always handy to have
Sent from my XT860 using xda premium
http://sbf.droid-developers.org/umts_solana/list.php
Choose the one for your carrier. If you are running windows you'll need rsdlite to use it. Just unzip the sbf somewhere on your comp and point rsdlite to the xml file in the unzipped folder. Make sure your battery is charged before doing this. And before flashing anything too. Just in case.
Sent from my XT860 using xda premium