Looking for Clear directions on how to restore a Streak 7 to Stock 3.2
I got my Streak for christmas and I ran Superuser7.zip on it. I need to fully unroot and restore back to stock for some testing. I can't seem to figure out exactly how to do that. I have the Lg7_WiFi_506_19534_30.pkg but can't seem to figure out how to flash it since ive installed CWM on it for superuser7.
And is that the correct flash? I've seen 506 and 507 talked about, don't know how to tell the difference.
Any help Greatly appreciated!!
Thank You!
Thanks, I'm also interested in seeing a straightforward guide on getting back to stock on the Streak 7.
Sent from my Galaxy Nexus using Tapatalk
Really?
No one? Come on. Im not a complete Noob and not looking for a diaper change guide. But I can't find any direct info on this.
First time working with Streak, usually work with samsungs.. Those are much easier to restore to stock.
I have the LG7-WiFi_506_19534_30.pkg that I found online but am not completely positive this is the package I need.. Goes back to what the heck does the 506 and 507 represent and I don't find any reference to those numbers in my about android tab.
Also... If i wanted use the built in restore function to load a .pkg,, well.. CWM4 killed that. So how do i flash a pkg now?
Anyhelp! if I can get enough direction, I will write a noob guide to this.
Thanks!
OK. Got some of my own homework done.. And figured out what it is I am really looking for.
I know how to restore technically.. but heres the issue. I need to remove CWM5.0.2.7
I need to restore the stock recovery, Then i can just flash a factory.pkg file and its back to stock.
So .. Can anyone refer me to the Stock Recovery .img file I can flash with Fastboot to restore the ability to flash a .pkg file?
Thanks!!
As you're trying i'll throw you a bone:
Dell Streak 7 - xda wiki
Download whatever rec matches the pkg you're going to install, as you've already had a stock 5xx rom installed at one point (the clue is that you had CWM 5.0 installed and working) just install the matching 5xx rec.
You seem to be attempting to install the 506-wifi one.
There's 2 entries on the wiki for 506, one has a modem baseband and the other doesnt, one of them is the wifi version. I'll let you try and figure out this last step.
Then i was reading those as recovery.. FILE NOT FOUND on that site.
got a copy of them? I'm currently running 512 software from Dell according to the build # on streak.. 20031
Appreciate your help.
I was moving files around earlier today on the server, you might have been trying to download them in the short window then when they wernt available.
If there's still any files that arnt working i'll fix them as I find them.
If you're on 512 could you make a nandroid first? 512 is one I dont have and you have it.
obviously i've nuked the Recovery.. but yes I will reset the tablet, and nandroid a copy of it.
Then What is the best next set to set it to stock at that point?
Thanks!
Install the 506 wifi recovery and you can flash the pkg you downloaded if that is the one you wish to flash.
If you're already rooted I believe gingerbreak also has a feature to unroot your rom. If you downgrade to 506 it's techincally a different rom but so far there's very little difference between the various 5xx roms
As promised. NooB Guide for returning back to completely Stock 3.2
Thanks to TheManii for helping me get on the right track and understanding what exactly is needed.
OK. So you've installed CWM 5.0.2.7 and rooted your streak 7 and for what ever reason you want to revert back to Stock, Day 1.
Heres your guide.
DISCLAIMER.. This worked for me. Not my fault if your bork your device for following this guide, however it should work.
Things that are needed.
Fastboot (found here with info on how to get into various modes http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide )
The Correct PKG file for your device See http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak_7#Official and get the 506 or 507 PKG and Recovery file(repeated below). Read the page and see if you need 506 or 507 and pick the right one, WiFi or 4g.
And the Same recovery.img file from same package (if you using 506, then 506's)
(you got rooted, so I assume I don't need to get your pampers changed.. You should have a pretty good idea about this so far)
Make a directory and unzip the fastboot+ADB.zip files
copy the recovery.img file downloaded above to same extracted folder so that fastboot and recovery.img are in the same directory.
On the streak. you need to have in a SD Card in the slot, the .pkg file you downloaded and have it named update.pkg in the root level (top) of the sdcard.
Power off your Streak
Put into Fast Boot Mode (see above if you don't know how)
drop to dos (CMD) cd to that directory.
fastboot -i 0x413C flash recovery recovery.img
fastboot -i 0x413C reboot
Streak should Reboot.
OK you have just copied over the 506 or 507 recovery image.. Congrats. your part way there.
Now I did this using my modified Streak 5 Dock that works just find for my Streak 7. That part worked perfect. The next part, if you were using it in the dock. After copying files to the SD card.. Remove from dock.. i believe it interfered. worked perfect out of the dock.
Boot to recovery VOL UP & Power at same time.
use arrows to move to option 2. Software upgrade via update.pkg on SD card. and press power button to enter.
Wait.
Recovery will load.
Read the screen. Its telling you to press the power button to use the emergency flash to recover your device. This will erase your device. (if you didn't already know this, or have this as your intention... Well... I'll leave it at that)
It will verify the pkg. then it will install. Took between 4-8 min.. Then it rebooted.
That took even longer of-course.. Just like day 1 when you turned it on after getting it from Dell.
If all went well. It will have returned you to the welcome screen where you are initially setting up your Streak 7.
Congrats. Your back to stock 506 or 507.
Now There is a 514 pkg file if your looking to upgrade to the latest as of 1/7/12. I am actually installing that as I type this.
If you decide to do the upgrade to 514.. Delete the existing update.pkg (if the streak didn't, it wasn't there when I went to copy the newer one over) and rename LG7-WiFi_514_21700_30.pkg or what ever applies to your device to update.zip and move to the sdcard.
Make sure SDCard is in Streak.
Power off the device.
Vol up and power. Select option 2 again. It will boot to recovery.
Power button to accept.
Sit back and watch.
Wait for reboot. as mine is right now
Tada.. Stock 514. Hope this helps some of you as it has helped me greatly.
Make sure to Thank TheManii and I would appreciate some Thanks if this helped you too
I will be putting up a Mirror for all the files tomorrow 1/7/12.
MobileMedic
That is a very nice guide I used it to un-root and remove CWM from my tab, if you or I could make this more clear, and why do you type "fastboot -i 0x413C" isn't it like this example: fastboot flash recovery C:/ADB/Win32/recovery.img
?
"-i 0xAAAA" is an optional value, it tells fastboot to explicitly target a specific connected device.
0x413c is the USB pid assigned to dell, if you only have a single device connected in fastboot mode it will simply assume you mean that one device.
Thanks for Defining that TheManii.
I used that info by borrowing from the Rooting Post.
[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
MobileMedic
Enter your password?
Followed this guide to the T pretty much with the latest version from Dell. Now I get Enter your password. No password *I* know works!
Any ideas? Thanks in advance.
You need to install clockwork mod 5.0 and do a fac reset.
this doesnt work for me when i try to flash the update.pkg tru option it takes me back to cwm. Anyway to go back to stock, no cwm no root?
antrax360 said:
this doesnt work for me when i try to flash the update.pkg tru option it takes me back to cwm. Anyway to go back to stock, no cwm no root?
Click to expand...
Click to collapse
Have you cleared all caches? reflash it again once you have and hopefully your password issues will be removed if all other methods have failed
Success and a request for OP
I just flashed 506 over my HC Dell Streak (T-Mo) and it worked like a charm. After first boot it went right to the setup screen. This was in prep for a sale.
I would request that the OP please update the first post to reflect the steps outlined in post 10(?) - it would be helpful to have steps listed in the very first post of this thread.
Also, using the Fastboot + ADB download did not help with fastboot for me. I use a laptop for development, and that has SDK/JDK installed on it, but had originally used my desktop to nvflash back to Froyo after trying StreakDroid. The download package did not include the right support files to make fastboot work correctly on my desktop. Had to do the fastboot commands on my laptop.
I would suggest this is the best way to avoid the read-only mode when you want to clean out your Streak 7 for future sale.
mobilemedic said:
Thanks to TheManii for helping me get on the right track and understanding what exactly is needed.
Wait.
Recovery will load.
Click to expand...
Click to collapse
How long should it take for recovery to load? I nvflashed back to 2.2, then flashed 506-30's recovery using fastboot. It's hanging when I tell it to upgrade via update.pkg (which is the 506-30 branch pkg).
EDIT: I re-nvflashed to 2.2 and stopped it from rebooting. Went to 2.2's stock recovery and flashed update.pkg (which was 506-30). No password anymore and it seems to have worked. Going to try 514-30 next.
Hi I need help, my Dell Streak 7 T-Mobile is stuck on boot loop n when I try to flash stock Rom it starts installation but right before it's seems to be completed it says "Install modem error.. installation will restart " & it reboot to tht boot loop.
Plz help
Sent from my HTC_Amaze_4G using Tapatalk 2
Related
I'm mobile right now... But.... The root and recovery guide are posted on rootzwiki.com... This is the LTE version... Ill pretty this up when I am gone from work....
Sent from my SCH-I510 using XDA App
poitee said:
I'm mobile right now... But.... The root and recovery guide are posted on rootzwiki.com... This is the LTE version... Ill pretty this up when I am gone from work....
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Can you make a recovery file that we can flash with Odin? A few of us have lost stock recovery snd the CWM recovery file we have available won't work.
jimh1999 said:
Can you make a recovery file that we can flash with Odin? A few of us have lost stock recovery snd the CWM recovery file we have available won't work.
Click to expand...
Click to collapse
I'm one of those few...
[HOWTO] Flash provided recovery without ODIN with broken main recovery [HOWTO]
So after 20 minutes of fiddling with things, I figured out how to get the recovery flashed without having to have recovery installed or without ODIN.
You will need
(1) Rooted LTE device
(2) ROM Manager installed *get at App market*
(3) This file from poitee's post: http://www.mediafire.com/?w45j8i0fcj0wck0
(4) ES File Explorer (or any other file explorer, I just use ES) or USB connection.
(5) Patience
=---------=-------=
Start with a rooted tab. Download the Rom manager.
1) In the ROM Manager, click on Flash ClockworkMod recovery. It will ask you what device etc, select Galaxy Tab. Wait for it to flash so it says "Current recovery: ClockworkMod 4.0.0.4".
2) After it's done, scroll down and hit All Clockwork Mod recoveries. Select 4.0.03. Let it download it and flash it.
3) Unzip the recovery.zip and take the recovery.img file and place it on the tablet.
4) Either using ES File Explorer, or just using Windows Explorer with tablet plugged in, find folder called "clockworkmod" in the SDCard root.
5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
6) Delete recovery-clockwork-4.0.0.3-p7100.img from that folder
7) Copy the recovery.img file from the ZIP above into this folder and rename it recovery-clockwork-4.0.0.3-p7100.img
8) Go back to ROM Manager, and select Flash ClockworkMod recovery, select the tab and hit OK. It will flash 4.0.0.4.
9) Place your tablet into Airplane Mode (turn off Wifi/4G/3G)
10) Scroll down again, select All Clockwork Mod Recoveries, select 4.0.0.3, and hit OK. That will now flash the recovery we just replaced.
11) Exit out of the ROM manager.
12) Push power button, hit Reboot.
13) As soon the screen goes blank, hold power button+volume rocker up till you see the box or downloading.
14) Hit UP once so the box is selected.
15) Hit DOWN once so that it boots into CWM.
*updated* Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
You are done
Success....Thank You for this, I was about to give up.
Notes,
~I had to put Tab in airplane mode after step 9
~I didn't leave Tab plugged in
~nand backup will work but no progress bars in CWM
~Rom Manager will alert of recovery update, just dont update recovery
~edit per Scott's post, name of file should be recovery-clockwork to match filename structure in the folder
Finally we have recovery on LTE Tab.
THANK YOU!
My notes:
- I also had to put it into airplane mode after step 9
- I tried to flash the new recovery.img and it failed so I rebooted the tablet at this point.
- I noticed the the first recovery was named recovery-clockwork-4.0.0.4-p7100.img so I changed recovery-clockworkmod-4.0.0.3-p7100.img to recovery-clockwork-4.0.0.3-p7100.img and flashed it with no issues.
Then I booted into CWM and noticed the progress bar issue during the backup.... but.... I BOOTED INTO RECOVERY!!
Thanks again!
~Scott~ said:
THANK YOU!
My notes:
- I also had to put it into airplane mode after step 9
- I tried to flash the new recovery.img and it failed so I rebooted the tablet at this point.
- I noticed the the first recovery was named recovery-clockwork-4.0.0.4-p7100.img so I changed recovery-clockworkmod-4.0.0.3-p7100.img to recovery-clockwork-4.0.0.3-p7100.img and flashed it with no issues.
Then I booted into CWM and noticed the progress bar issue during the backup.... but.... I BOOTED INTO RECOVERY!!
Thanks again!
Click to expand...
Click to collapse
You are right about the name, same for me.
Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
Updated the guide with the names and airplane steps.
tijayz said:
Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
Updated the guide with the names and airplane steps.
Click to expand...
Click to collapse
Thanks to you and poitee for finding the solution. If you find any roms or kernals that work, please report back. Also can we flash the stock recovery back on this Tab?
I would still like to know why the CWM recovery would,nt work on the LTE version
First of all, let me say thanks for the effort and risk for eveyone involved. Now, please excuse my noobiness here, but is there a way in here to back up the stock rom before flashing/rooting? In other words, can I reverse this process to stock for returns/service?
I've seen how to reverse to stock the WiFi version, but this LTE is uncharted territory. Thanks!
My Galaxy LTE is bricked... Is there any way to just install the plain stock image back?
Mine was never rooted, so i'm kind of stuck, anyone have the stock recovery image?
Yep, I think what we need is the stock recovery image right? Anyone?
www.jamezelle.com/myfiles/stockrec.zip
DD the image inside to mmcblk0p2. At your own risk. Its the stock lte recovery.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk
jamezelle said:
www.jamezelle.com/myfiles/stockrec.zip
DD the image inside to mmcblk0p2. At your own risk. Its the stock lte recovery.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk
Click to expand...
Click to collapse
Can you elaborate on your instructions? I have done my fair share of ROM flashing and have used CWM for quite a while, but not sure about going back to stock on the recovery.
I accidentally used Rom Manager to flash "recovery" 4.004 to my LTE Tab and then it would no longer boot up (keeps going back to Samsung screen).
Can get to the screen to choose recovery or Odin. Then, I made it worse by flashing (with ODIN) what I thought was the correct stock image, and wound up putting the Wifi model on to it.
After quite a bit of reading (and kicking myself) ...
I have created a ODIN capable stock recovery image, and now I can get into stock recovery, but I need the rest of the LTE image to restore my unit. Can anyone make a dump of the factory stuff (other than the data) ? Heck even if I can get it working on just Wifi for now, that would be ok until the LTE image surfaces.
I really don't want to try to return it since I have only had it for 2 days and it would be pretty obvious that I had messed with it.
Thanks. I can make
Not sure if it will help but I'll wipe data and pull a nandroid if you want but I'm on cwm stock lte since I still can't figure out how tonsetup my PC for rom dev on hc
Sent from my Incredible 2 using XDA Premium App
mattj949 said:
I accidentally used Rom Manager to flash "recovery" 4.004 to my LTE Tab and then it would no longer boot up (keeps going back to Samsung screen).
Can get to the screen to choose recovery or Odin. Then, I made it worse by flashing (with ODIN) what I thought was the correct stock image, and wound up putting the Wifi model on to it.
After quite a bit of reading (and kicking myself) ...
I have created a ODIN capable stock recovery image, and now I can get into stock recovery, but I need the rest of the LTE image to restore my unit. Can anyone make a dump of the factory stuff (other than the data) ? Heck even if I can get it working on just Wifi for now, that would be ok until the LTE image surfaces.
I really don't want to try to return it since I have only had it for 2 days and it would be pretty obvious that I had messed with it.
Thanks. I can make
Click to expand...
Click to collapse
Don't worry man we'll get you going.
~Scott~ said:
Can you elaborate on your instructions? I have done my fair share of ROM flashing and have used CWM for quite a while, but not sure about going back to stock on the recovery.
Click to expand...
Click to collapse
Can you boot into android? If so I can give you the instructions to get the stock recovery back on via command line or mattj949 can post his Odin file.
I wound up returning and exchanging, but I still want to back it up in case it happens again....
However, I did make a fully working CWM ODIN flashable (for LTE Tab), however, not sure how to post it here. I left it on my office PC, will figure out how to post tomorrow.
Bricked?
Im having the same problem with rooting then using clockwork to flash recovery 4.0.0.4. Now Im stuck with the Galaxy Tab boot screen then to black then the boot screen and to black continuously.
I can access Odin but my computer doesn't recognize the Tab and never has. When I plug it in I hear the computer recognize it but gives a different sound doesn't see it. ???
Can anyone help me get this thing booted again.
Thanks
Ok, I'm a noob and I tried to root my phone. However, I messed it up and I'm not sure how.
I successfully unlocked the bootloader.
I then flashed the recovery with Amon_RA's image. All is still good.
I attempted to root installing from zip using this step "Use trackball -> "Flash zip from from sdcard" -> nexus-addon-0.1-signed.zip"
I then rebooted and now I'm stuck at X. It won't boot past that.
I can access the bootloader and all that other crap. I'm a noob so type slow and in small words to I can fix this. Until I see a reply, i'll play around with it to see if I can return the image to stock.
dieselfiend said:
Ok, I'm a noob and I tried to root my phone. However, I messed it up and I'm not sure how.
I successfully unlocked the bootloader.
I then flashed the recovery with Amon_RA's image. All is still good.
I attempted to root installing from zip using this step "Use trackball -> "Flash zip from from sdcard" -> nexus-addon-0.1-signed.zip"
I then rebooted and now I'm stuck at X. It won't boot past that.
I can access the bootloader and all that other crap. I'm a noob so type slow and in small words to I can fix this. Until I see a reply, i'll play around with it to see if I can return the image to stock.
Click to expand...
Click to collapse
Where did you get that ROM from and did you check md5sum before flashing?
I got the ROM from the link at the top of this page.
http://forum.xda-developers.com/showthread.php?t=636795
It's nexus-addon-0.1-signed.zip is the file.
Also, how do I check md5sum before flashing?
dieselfiend said:
I got the ROM from the link at the top of this page.
http://forum.xda-developers.com/showthread.php?t=636795
It's nexus-addon-0.1-signed.zip is the file.
Click to expand...
Click to collapse
oh that's not even a rom.
if you have successfully install Amon Ra, just put the ROM of your liking on the sd card and flash.
Sent from my Transformer TF101 using Tapatalk
All I'm trying to do is root the phone using these instructions
http://forum.xda-developers.com/showthread.php?t=636795
I don't really want or need a new ROM. Stock is fine for me. Just want root access. Any clue how I get out of this mess?
Ok, I might have just found my problem. The instructions say to use that addon if I don't have superboot installed. I do have superboot installed. How do I reverse it?
Maybe passimage method back to stock than try again
I can only access bootloader and recovery at this point. How do I push a file to the sdcard so I can install from ZIP?
dieselfiend said:
I can only access bootloader and recovery at this point. How do I push a file to the sdcard so I can install from ZIP?
Click to expand...
Click to collapse
just take the sd card out and use card reader or use custom recovery then mount sdcard
what file do I put on the sdcard?
dieselfiend said:
what file do I put on the sdcard?
Click to expand...
Click to collapse
If you want to go back to stock search for passimg.zip or you can use any ROM you like.
my adb isn't recognizing my device. Fastboot is but not adb. This is why I can't push anything to the phone at the moment. This is getting frustrating.
take the sd card out and put the passimg.zip file on it
I did that and nothing happened. Is there something special I need to do in order for it to take?
It was working just fine until I installed the google addon zip described above from the sdcard. Is there any way to uninstall the addon from recovery?
The PASSIMG.zip method doesn't work for me. It briefly says it can't find image or something like that. It flashes on the screen very fast so I can't get the details. Any other suggestions for me to try? Like I said, I can boot to recovery just fine. I can even install from zip through recovery. I should have backed up that image before I started messing around with it. I'm learning as I go though.
Phew!!! Back in business with the passimg method. My mistake was adding another .zip when I renamed the file. so to the phone it looked like PASSIMG.zip.zip and wasn't recognizing it. Once I got that fixed it updated just fine. I'm booted now. I'll update then try and root once again.
Good to hear.
Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!
Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.
already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now
Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.
Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!
well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?
Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium
Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC
Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.
for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.
Just put your new recovery in the superguide and gave you credit. Keep up the good work!
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100
Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks
Ok guys, for all of you who are STILL waiting for the official update to roll out to our tabs, wait no longer. Thanks to PCPIMP over on android forums who pulled the update file from /cache in his tab before installing, we now have it and can flash it ourselves. However, there are a few quirks to getting this thing to flash properly. First: It must be flashed from stock recovery, NOT cwm recovery. Also, once you download the file from the multiupload link, you must rename it to update.zip Be careful here. When I renamed it to update.zip, somehow it would automatically add "bin" on to the end of the file. So without being able to see it, the file ended up with the name update.zip.bin and it was not showing up in stock recovery to flash. Use a file manager like 7zip to change the name or open up the properties on your PC to do it properly. Once it's renamed properly, put it on the the SD card. Here is something I am not completely sure of......but I *think* it doesn't matter what build you're on when you flash this file. It appears to me to be very insecure. You can even open up the update.zip with 7zip and debloat the stuff you don't want. I did. I only see one "patch" file in the update.zip and that was the LTE modem. What that means I'm prettty sure is that it will only require one file to be present on your tab to flash properly. This *may* even be able to be flashed directly from the Leak I posted of this build, for those of you who are on it. As long as you are on the correct radio because that's what it looks for. When you flash this file, it even wipes your data for you, But it does NOT wipe the SD card. I actually flashed it twice to see how secure it was. I flashed it from EH04 and EH04 radios and then I reflashed it directly over itself (EL01 and the EL01 radios) and it worked fine. So, I hope everyone understands all of that long winded babble I just spewed.
Step 1. Download update http://goo.gl/6XtFD (<--Huge thanks to PCPimp for hosting this) and rename it PROPERLY with 7zip or something to update.zip and place it on the root of your SD card. Make sure you don't have any other files named update.zip already on your SD, as that could get confusing, lol.
Step 2. Odin flash this recovery: http://dl.dropbox.com/u/20070269/lterec.tar.md5
Step 3. Boot into the stock recovery you just flashed and select apply update from SD card. Then scroll until you find update.zip. If it is not there, that means you didn't properly rename it. It most likely added the letters bin to the end of the name and can't be recognized by the recovery. So reboot and fix that and then start step 3 back over.
Step 4. When it is named properly and you flash it, most likely you are immediately going to see the dreaded Yellow exclamation point on the android signifying that there is an error or that you did something wrong.......Just wait. Keep watching it. It will eventually flash and your tab will reboot and you will be on EL01 and updated. Now, if you want root, see step 5
Step 5. Download both of these files: Kernel - http://droidbasement.com/galaxy/ker...36.4_lte_hc32-oc-xtra-vfpv3-d16_fp-010912.zip SU.zip - http://dl.dropbox.com/u/20070269/Superuser-3.0.7-efgh-signed.zip and put them both on your SD card.
Step 6. Open up odin program on your PC and click PDA and you will need to quene up this file in PDA: http://dl.dropbox.com/u/20070269/recovery.tar.md5 also, uncheck Auto Reboot in odin. YOU DO NOT WANT AUTO REBOOT TO HAVE A CHECK IN IT IN ODIN. REMOVE IT. Then power off tab and then boot into download mode by holding the power button until you see the samsung galaxy tab screen, then quickly let go of the power button but then immediately after and at the same time, hold power button and volume up until you are given two choices: A white box or the android. Careful, volume down at this point will choose for you. You will already be on the one you want to choose, which is the full sized android. BUT, make sure that odin is completely ready to go first. Make sure the recovery.tar that you just downloaded is quened up in PDA. On your tab push the volume down button and then follow the screen instructions. When the "Downloading" screen comes on, you need to move kinda quickly but you can relax. Just plug it in and hit start in odin. When you see the green pass in odin, unplug the tab and use the volume and power buttons again to boot into the other option, the white box and the little android. THIS IS VERY IMPORTANT! Once you have flashed the recovery.tar file, you must NOT let the tablet boot up fully and normally. You must directly into recovery. If it fully boots first, then the stock kernel will overwrite the cwm recovery with the stock recovery.
Step 7. So once you boot into to the turquoise cwm recovery, flash the 2 files you downloaded in step 5 in this order: The awesome kernel first, credit to Pershoot. Then flash the SU.zip file credit to ChainsDD: <------sometimes this SU.zip file will give you an error in CWM recovery when flashing it, just try it again and it will work.
Step 8. Reboot your tablet and enjoy a rooted EL01 updated tab with an AWESOME OC kernel from Pershoot.
Credit
Pershoot for the sweet kernel and recovery used in my guide
PCPIMP for pulling the update file from his tab and uploading it for us all
ChainsDD for root in general and the Superuser.zip used in my guide
Minor bloat removed...pretty darn fast without deodexing or kernel changes. I may just keep it stock with SU access.
Thanks for the files and the guide, everything is working great. I didn't wipe and am really surprised how well it's working, but still wish I could get rid of the TouchWiz stuff.
If I might make a suggestion, it'd be good to know to copy SU and the kernel to the device before flashing the CWM Recovery via ODIN. After flashing CWM, I had to let the tablet start up, copy the files, re-flash with ODIN, then load CWM and flash the kernel and SU. Not a big deal, just could have saved a step for me (although, I also could have read ahead...).
So i odin'd back to factory stock to use this, and it did push this update to me at the end of it, so it wound up not being necessary, thanks though!
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Is the ota update radios the same as in the leak?
sent from my 4g galaxy tab
inline6power said:
Is the ota update radios the same as in the leak?
sent from my 4g galaxy tab
Click to expand...
Click to collapse
No they are not.
Sent from my SCH-I905 using Tapatalk
ifiweresolucky said:
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Click to expand...
Click to collapse
Hmmm......interesting. What build and radio were you on when you flashed the update zip?
Sent from my SCH-I905 using Tapatalk
ifiweresolucky said:
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Click to expand...
Click to collapse
Had the exact same results using leaked 3.2 Baseband i905.02V.EIO2 Build HT85B.EIO3.SCH-I905.EI03 pershoot Kernal
Psean said:
Had the exact same results using leaked 3.2 Baseband i905.02V.EIO2 Build HT85B.EIO3.SCH-I905.EI03 pershoot Kernal
Click to expand...
Click to collapse
Yea, it seems that we do in fact have to be on at least the EH04 radios to flash the update. I noted in the OP that the update.zip contains an LTE modem patch, meaning it first has to detect the prior official radio so that it can patch the update to the modem. If it doesn't detect the correct modem, it errors out.
Sent from my SCH-I905 using Tapatalk
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
muzzy996 said:
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
Click to expand...
Click to collapse
Way better. Radios are ten times better and the nice thing is now ypi can view the market in portorit and not just landscape
sent from my 4g galaxy tab
muzzy996 said:
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
Click to expand...
Click to collapse
I have to agree that the radios are better. And, to me, it actually seems a little more snappy. And I don't think it's placebo either because at first, the update seemed a little buggier. But now that a few days has passed, I guess it's settled and it appears the bugs are gone. I would suggest updating.
Sent from my SCH-I905 using Tapatalk
kidserious said:
Step 5. Download both of these files: Kernel - http://droidbasement.com/galaxy/ker...36.4_lte_hc32-oc-xtra-vfpv3-d16_fp-010912.zip SU.zip - http://dl.dropbox.com/u/20070269/Superuser-3.0.7-efgh-signed.zip and put them both on your SD card.
Step 6. Open up odin program on your PC and click PDA and you will need to quene up this file in PDA: http://dl.dropbox.com/u/20070269/recovery.tar.md5
Click to expand...
Click to collapse
Question for you. I was already updated before this was posted, but if I odin in the recovery file in step 6, then flash in the 2 files from step 5, the end result will still be the same right? Rooted, with CWM and Pershoot's kernel installed, on the official update?
EDIT: NVM. I followed step 6 to the letter, then flashed in files from step 5. Of course next stop was SetCPU... Everything working fine.
eXiled Killah said:
Question for you. I was already updated before this was posted, but if I odin in the recovery file in step 6, then flash in the 2 files from step 5, the end result will still be the same right? Rooted, with CWM and Pershoot's kernel installed, on the official update?
EDIT: NVM. I followed step 6 to the letter, then flashed in files from step 5. Of course next stop was SetCPU... Everything working fine.
Click to expand...
Click to collapse
Yep, that works, lol. Cool deal
Sent from my SCH-I905 using Tapatalk
Bah . . stuck at bone stock 3.2 with stock recovery.
Tried flashing CWM 5.0.2.7 both from the dropbox link and from pershoot's site but when I try to boot into it I just get a blank screen. Rebooting into 3.2 gets me back the stock recovery but I'm unable to get CWM to work.
Open to ideas.
Odin flash of the CWM recovery file goes perfectly smoothly. I reboot and pick it and immediately get a blank screen (can see the bleed through of the backlight) and it sits there for as long as I let it (left it for 5 minutes waiting).
Long story short, I didnt realize the issue with the modems before trying the procedure coming from the leaked 3.2 which forced me to do a full wipe and reset using stock 3.1 and doing OTA updates normally to get to 3.2. That all went okay after spending an hour figuring out what was wrong . .
muzzy996 said:
Bah . . stuck at bone stock 3.2 with stock recovery.
Tried flashing CWM 5.0.2.7 both from the dropbox link and from pershoot's site but when I try to boot into it I just get a blank screen. Rebooting into 3.2 gets me back the stock recovery but I'm unable to get CWM to work.
Open to ideas.
Odin flash of the CWM recovery file goes perfectly smoothly. I reboot and pick it and immediately get a blank screen (can see the bleed through of the backlight) and it sits there for as long as I let it (left it for 5 minutes waiting).
Long story short, I didnt realize the issue with the modems before trying the procedure coming from the leaked 3.2 which forced me to do a full wipe and reset using stock 3.1 and doing OTA updates normally to get to 3.2. That all went okay after spending an hour figuring out what was wrong . .
Click to expand...
Click to collapse
Apply rooted kernel, because stock kernel keeps on flashing stock recovery. then flash custom recovery. sounds like recovery is being stupid/corrupted. Or odin back to stock then reroot etc.
magneticzero said:
Apply rooted kernel, because stock kernel keeps on flashing stock recovery. then flash custom recovery. sounds like recovery is being stupid/corrupted. Or odin back to stock then reroot etc.
Click to expand...
Click to collapse
Not sure why I had to but I rebooted my PC and tried again. What I noted is after updating to 3.2 via OTA my pc stopped recognizing the tablet on the USB port I normally used to flash. Other ports worked so I switched but as you suggested the recovery being flashed by Odin was going in corrupted.
muzzy996 said:
Not sure why I had to but I rebooted my PC and tried again. What I noted is after updating to 3.2 via OTA my pc stopped recognizing the tablet on the USB port I normally used to flash. Other ports worked so I switched but as you suggested the recovery being flashed by Odin was going in corrupted.
Click to expand...
Click to collapse
So you got cwm flashed eventually?
Sent from my SCH-I905 using Tapatalk
kidserious said:
So you got cwm flashed eventually?
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
Yep, all back to normal. We'll see how it goes. Out of the box it was noticably better than the leak, like perhaps it was zipaligned or something. Leaked rom with zipalign and v6 supercharger was pretty sweet already though.
Running fine right now.
Most irritating thing for me is the wifi toggle is gone from notification menu, replaced instead with mobile data toggle. Why someone would do this is beyond me. Leaked version had both a wifi toggle and an airport mode one. Now, I have to add a toggle onto a home screen, run extended controls or dive into settings manually to toggle it.
Also I'm not 100% sure if I hit it by mistake but I could have sworn I turned off auto brightness this morning and yet it was back on during lunch today.
All in all I'll agree its worthwhile to move from leaked to this but only marginally so, for stability sake and getting the latest modem drivers. If it puts you closer to the next OTA then its worth it.
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?