Related
I recently flashed Gio's OTA Froyo 1.8.1 and once it had finished flashing, it noted to upgrade my kernel version.
I've flashed at least a hundred rom's onto my phone, but I've never updated or flashed a new kernel. I skimmed the forums and I found a couple threads:
SGS Kernel Flasher I would look into this but 1) it seems it won't work for my MT3G and 2) if it would work, I have no idea if it would be safe to use
ezterry's 2708+ enabled kernel I was looking into using this kernel with the updated radio version, seeing that my radio version is 2.22.23.02, but my issue is with the guide he posted. Generally I can figure stuff out, but thats because I have simple step by step instructions to follow. I'm tech savvy, but not a genius when it comes to hacking my phone.
I just want to figure out the easiest way to learn how to get myself a new kernel, be it a youtube tutorial video, a step by step guide from another forum (or one here on xda that I somehow missed, because I looked...)
Any help is much appreciated, even if you tell me "look at this thread you noob"...lol
I should also note that the reason I'm not following ezterry's guide is because I have that feeling I would miss something (because I tend to do that) and end up bricking my phone.
- Download a kernel (zip file)
- put it on the root of your SD card
- Go in Recovery
- Backup with nandroid
- Flash zip file (your kernel.zip)
- reboot
- if it's not working (boot loop), simply restore your backup or find a other kernel to flask
Always flash kernel after the rom, because lot of rom has a kernel inside, so you need to flash after to have your kernel.
Flashing a kernel is the same as a rom, no more risk!
Edit :
! Kernel is not the same than SPL or Radio !
Ok, because some of the stuff i was reading had a laundry list of stuff to download and follow, it was just too confusing.
PART1: GTAB 3588 Recovery Pack
IMPORTANT NOTE: THESE WILL ONLY WORK WITH 1.1-BASED ROMS!!!!! The new Viewsonic build 4349 does NOT work with these!!!
What this is
A set of tools to flash recovery within a rooted GTablet. This pack includes stock 3588 and bekit's .8 clockworkmod recovery, the flash_img utility, and a Terminal Emulator. This is completely mod-agnostic and should be able to work on most rooted mods. Do NOT use this on 1.2-based stock or mods!!!!
This pack will be built into TNT Lite 4.3.0 and gADAM 1.3.0. I am supplying this pack for all other rooted "legacy" 1.1-based mods out there.
Installation Instructions
This is in an update.zip format. Extract the rar to the root of your internal memory, so that you have a recovery folder and an update.zip. You'll need the apk folder only if you wish to install the Terminal Emulator via a sideload.
Run either standard or clockworkmod recovery and install the same way you would install any ROM. Again, this is only a small set to tools, not a full ROM!
Usage
a) To flash recovery to 3588 stock recovery, using your GTablet
- Download the app "Android Terminal Emulator", by Jack Palevich. Or sideload it (the apk is in the RAR file)
- Run the app, toggle the soft keyboard and change the font settings, if desired (default is very small)
- Type "su" (Superuser should allow su access. If not, you are not rooted and cannot use this!)
- Type "fixrecovery.sh". This should run the flash_image tool and complete in 5-10 seconds
Reboot into recovery to test. 3588 stock has no options, so assuming you have no update.zip in the root of your /sdcard, it should just error out with an "!" error (that's what we want to see).
b) To flash recovery to clockworkmod .8 bekit version recovery, using your GTablet
- Follow steps 1 to 3, above
- Type "cwmrecovery.sh". You should the flash_image tool run and complete
Reboot into recovery to test. You should see the clockworkmod .8 bekit screen, which means the flash was successful.
c) To flash either recovery with adb
Just use an "adb shell" and then run the shell script needed. Again, this requires root access.
Download
3588 Recovery Pack v1.0 Link: http://www.mediafire.com/?1k1zlrsb4f8tkol
md5sum: 34190022d178a9e22494527103de7eac
(update on 3/23/2011)
=====================================
PART2: Clockworkmod .8 bekit (legacy version)
What this is
This is the legacy clockworkmod for 1.0.1-1.1 ROM's (ie. VEGAn, gADAM, TnT Lite 1.x-4.x, etc). It's an update.zip package to flash to clockworkmod, and is OS and hardware agnostic. Do NOT use this on 1.2-based stock or mods!!!!
Installation Instructions
This is in an update.zip format. Extract the main ZIP to the root of your internal memory, so that you have a recovery folder and an update.zip.
Testing
Reboot into recovery. If you see "clockworkmod .8 bekit" in the title, then it is installed.
Download
clockworkmod .8 bekit Link: http://www.mediafire.com/?dvleg4oatkfxm7w
Alternate Link: http://www.megaupload.com/?d=DHOASVPG
md5sum: d34079a1f0e83d8c4e09efe78cda0cc3
(updated on 11/9/2010)
=====================================
PART3: Stock 3588 Recovery Standalone
What this is
This is the stock 3588 recovery for 1.0.1-1.1 ROM's (ie. VEGAn, gADAM, TnT Lite 1.x-4.x, etc). It's an update.zip package to flash to 3588 stock recovery, and is OS and hardware agnostic. Do NOT use this on 1.2-based stock or mods!!!!
Installation Instructions
This is in an update.zip format. Extract the rar to the root of your internal memory, so that you have a recovery folder and an update.zip.
Testing
Reboot into recovery (and ensure you have no update.zip in the root of your device). Standard recovery is very simplistic - if you get an "!" error, you most likely have standard recovery installed.
Download
3588 Stock Recovery Link: http://www.mediafire.com/?97o1jc7ceth8hp7
md5sum: 983ca4efe81ced2604ccdebc5aedfbb9
(Updated on 3/23/2011)
Is this the 'writing on the wall' concerning 3991? Or just another tool?
joe2262 said:
Is this the 'writing on the wall' concerning 3991? Or just another tool?
Click to expand...
Click to collapse
The need for a way to get back to 3588 recovery has been coming up lately - this is a way to address that.
excellent work as always roebeet...if u don't mind just 1 suggestion...when i write my tutorials and such i try to keep things as generic as possible for easier future changes. might i suggest to make your job easier in the future to change the 3588 wording and such to something like latest vs stock or something similar? then all you have to do is update the link and link's descriptor. same thing with cwm i suppose. regardless, this is definitely sticky worthy IMO. great work
flipovich said:
excellent work as always roebeet...if u don't mind just 1 suggestion...when i write my tutorials and such i try to keep things as generic as possible for easier future changes. might i suggest to make your job easier in the future to change the 3588 wording and such to something like latest vs stock or something similar? then all you have to do is update the link and link's descriptor. same thing with cwm i suppose. regardless, this is definitely sticky worthy IMO. great work
Click to expand...
Click to collapse
I actually worded this with future proofing in mind. It will likely always stay 3588.
I have to see if the next VS firmware changes things - if it does, 3588 is a term we will all be using. Or "1.1" or "legacy".
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
roebeet said:
I actually worded this with future proofing in mind. It will likely always stay 3588.
I have to see if the next VS firmware changes things - if it does, 3588 is a term we will all be using. Or "1.1" or "legacy".
Click to expand...
Click to collapse
ahh, gotcha. even better then
Gramps said:
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
Click to expand...
Click to collapse
I amcurious about this too. Assume I flash to a rom with the new recovery, can I get back to 3588 with these tools?
ramerco said:
I amcurious about this too. Assume I flash to a rom with the new recovery, can I get back to 3588 with these tools?
Click to expand...
Click to collapse
I have to revamp my instructions, but the gist of it is this: You just run 3588 stock ROM, against the TNT Lite 5 / TTx standard recovery. That standard recovery will downlevel the bootloader, which the critical part to avoid a brick.
TNT Lite 4.3.0 and gADAM 1.3.0 should also work, but for the sake of my sanity I'm just going to recommend running 3588 stock as a backout.
Gramps said:
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
Click to expand...
Click to collapse
Yeah ... I'm wondering the same too
Also wondering should I follow PART1, PART2 and PART3 for recovery process?
roebeet said:
I have to revamp my instructions, but the gist of it is this: You just run 3588 stock ROM, against the TNT Lite 5 / TTx standard recovery. That standard recovery will downlevel the bootloader, which the critical part to avoid a brick.
TNT Lite 4.3.0 and gADAM 1.3.0 should also work, but for the sake of my sanity I'm just going to recommend running 3588 stock as a backout.
Click to expand...
Click to collapse
Roebeet,
If I have installed clockworkmod for TNT Lite 5, can I just flash update using CWM from image downloaded from PART3 ?
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
butchconner said:
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
Click to expand...
Click to collapse
thank you butch, so i wait for roebeet to post part 4 then
butchconner said:
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
Click to expand...
Click to collapse
There will be, if it's needed. I might update the title and move things around, or create a new thread. It's hard to know until I see what gets released.
"1.0.1" and "1.1" are the stock ROMs we currently have (3588 is actually 1.1-3588, for example). 3991 UAT is "1.2".
So what would the process be to revert from 3991 and TT?
To make sure -- I run the Part I need above using the recovery
in 1.2 (3991 and TTx).
Rev
dony71,
My bad. I said I was trying not to muddy the waters and in asking what
I wanted to know I did just that. My apologies.
Since I didn't see an option for UAT 3991 and TTx (1.2 versions) in the original first post, I was wondering if roebeet was going to add another section explaining in
detail the procedure for them.
Rev
butchconner said:
dony71,
My bad. I said I was trying not to muddy the waters and in asking what
I wanted to know I did just that. My apologies.
Since I didn't see an option for UAT 3991 and TTx (1.2 versions) in the original first post, I was wondering if roebeet was going to add another section explaining in
detail the procedure for them.
Rev
Click to expand...
Click to collapse
It's going to go into the TTx thread, initially (it's my giant list of To Do's). That's because "1.2" isn't released yet.
Thanks for the clarification.
Rev
Roebeet
This should eliminate many questions from new rooters as the original recovery instructions have been modified so many times. Thanks again for making a fairly simple process even simpler
Easy to understand and simple method to recover. Thanks Roebeet.
Will this work to return to stock 1.1 from 1.2.4349 ?
For anyone having issues installing the 4.7.3 Verizon update. Or who lost root after the update and want root back. This is what I did and it worked just fine.
-Reset your phone back to factory settings in the settings -> privacy menu or in recovery mode.
-Get RDS Lite 4.9 or newer and SBF your phone back to 2.3.3 gingerbread so you have a stock verizon 2.3.3 gingerbread install. All the software including the 2.3.3 US Verizon SBF are on XDA in the fourms.
-Root phone with superoneclick
-Install OTARootkeeper from play store. Backup root and then temp unroot in app.
-Take the OTA update from Verizon which will install just fine now
-Restore root with OTARootkeeper
Now you have a stock Verizon Droid Pro running Android 2.3.4 with root. Enjoy!
SBF Files
Where did you get the files? I searched for them and the only thread had a link that I couldnt use.
SBF flash is not necessary.
4.7.3 Put on Sd card and sew through the rekaveri. You'll get an error because of what you can not ask. I did not flash because of build.prop.
Next download 4.6.8 SBF. and parse for the manual
http://forum.xda-developers.com/showpost.php?p=13146095&postcount=3
and cast your files you want to place.
After this update will be in place. And you will not lose
Firmware files can be found here http://forum.motofan.ru/index.php?s=&showtopic=1730230&view=findpost&p=1625509
asf1187 said:
Where did you get the files? I searched for them and the only thread had a link that I couldnt use.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1419303
If you need RDS Lite just google for it. Make sure its 4.9 or up though.
it just seems not success?why,there is something wrong with me,please give me some matters need attention
send from debian for android
This guide is strictly for people who have a Verizon R800x and wants to update to Gingerbread 2.3.4 with root and ClockworkMod recovery, without having to unlock the bootloader nor have a Verizon data plan. Without a data plan you can not update the Verizon Play from 2.3.3 to 2.3.4 because they don't allow updating through WiFi. Also if you flash the 2.3.4 ftf image directly, you will not be able to root it, therefor will not be able to install CWM unless you unlock the bootloader. This guide show you to will get around that.
Note: With this method, although you have CWM, you still will not be able to install custom roms and kernels until you unlock the bootloader. This guide was written before Sony allow the Verizon Play bootloader to be unlocked from their site. Go here to unlock your bootloader, which will allow you to flash custom roms and kernels to your Play: http://unlockbootloader.sonymobile.com. If you choose to do this, you can skip this entire guide.
Instructions:
1. You must be running Gingerbread 2.3.3 on your R800x. If you aren't, download the stock Gingerbread 2.3.3 firmware and use Flashtool to flash it. Drag the ftf firmware file onto the Flashtool screen and follow the onscreen instruction to install. This step will wipe all your phone data except the SDcard.
(You might need to install drivers for your device first, you can find "Flashtool-drivers.exe" in the "drivers" folder in your Flashtool folder.)
2. Enable "USB debugging mode" on your device (Settings -> Applications -> Development).
3. Use SuperOneClick created by CLShortFuse to root your R800x. Then reboot the phone.
(This program might trigger a false positive on your antivirus software, so disable your antivirus while using it. This rooting method only work with Gingerbread 2.3.3 for the Play.)
4. Use specifically the "CWM installer v5" created by pvyParts to install ClockworkMod. That's version 5 btw.
Note: At this point, if you are content with using GB 2.3.3 with root and CWM, stop here. Proceed if you want to update to 2.3.4 with root.
5. Download either the "nandroid backup of stock Gingerbread 2.3.4 w/ root" created by netizenment or this NXT Lite CDMA rom which is already debloated and optimized.
(Put the nandroid backup into the correct directory in your microSD card so ClockworkMod will recognize it, it should be extracted into a folder named "backup" within a folder named "clockworkmod".)
6. Boot the phone into ClockworkMod recovery by: Turning it on, when the Sony logo appear, keep pressing the Volume Down button until you see the blue ClockworkMod menu appear.
7. Restore the stock GB 2.3.4 nandroid backup you just downloaded. Then turn off the phone.
(This will only install the system files, it will not install the 2.3.4 kernel.)
8. Installing the stock 2.3.4 kernel:
a. Download the stock Gingerbread 2.3.4 firmware (this is for Verizon only).
b. Drag and drop the ftf onto the Flashtool window. When you see the "Firmware selection" window appears, look to the right column, under "Exclude" and check to exclude all the items in the list, except the kernel. Then flash it.
(This will install just the 2.3.4 kernel while leaving the rest of your rooted Gingerbread 2.3.4 alone. You need to do this for the Camera and WiFi to work.)
9. In the process of restoring the nandroid backup above, the ClockworkMod recovery might become lost. However, you still have root, so you can install ClockworkMod recovery again using the CWM installer.
Other tips: LBE Security Master have can help lighten the bloatware from your rom. Among its many features, can remove system apps and prevent apps from autostarting, which will leave more free rams.
The end.
does this fix the "gtalk" issue, I went back to 2.3.3 from 2.3.4 cause of that issue.
CamachoDjr said:
does this fix the "gtalk" issue, I went back to 2.3.3 from 2.3.4 cause of that issue.
Click to expand...
Click to collapse
It doesn't fix it. Verizon does this sort of thing on purpose. Pushes out a broken update and then goes, "We are working on a fix."
This phone is about to cause me to start mainlining some serious drugs. I just do not understand what I'm doing wrong.
I have read and read and read and downloaded and downloaded and downloaded. At one point I think I had about 10 Firefox tabs open, madly switching between them trying to figure this beast out. So, I have tried to do the necessary homework before posting here.
I received a Verizon Droid X (MB810 model) and was wanting to install a 2nd-init ROM. It came with .621, which I know has been problematic in the past, but seems not to be a terribly big obstacle anymore. Here are the steps I've taken:
o I rooted the phone via the Slitaz ISO.
o Via adb, I pushed the Droid 2 (D2) reboot recovery and ROM manager (RM) APKs.
o I choose boostrap recovery in the D2 application. Superuser grants the appropriate permission.
o Within RM, I download and flash the latest CWM (5.0.2.0) based on the 2nd-init Droid X option.
o RM says that the flash is successful and Superuser rights are granted.
o From within RM, I choose the reboot into recovery option.
o The phone reboots...right back into the operating system, completely bypassing CWM. Redoing the above steps and holding down the home key just boots into the stock recovery.
Now, I can reboot into CWM from the D2 application, but I'm then confronted with the old version of CWM. I've also read where this method will screw-up the boot process to the point that installing 2nd-init ROMs won't work. I've (somewhat) verified this by trying to install the latest AOKP with the D2 version of CWM, which just endlessly loops the unicorn animation. In fact, in a thread detailing this problem on another forum, it was advised to stay far, far away from the D2 application altogether and just use RM.
I've also had to SBF back to .621 on several occasions using RSDLite 4.9.
This has been nightmarish. I spent almost the entire weekend trying to get this phone to boot into the latest CWM. Do I have to SBF the Milestone ROM in order for this to work? Is that even necessary anymore?
Any help would be GREATLY appreciated, as I'm out of ideas at this point. Thanks a bunch.
- Fred
did you wipe data before/after flashing SBF?
if not, that could cause issues
sd_shadow said:
did you wipe data before/after flashing SBF?
if not, that could cause issues
Click to expand...
Click to collapse
Yes, I forgot to mention I did that in my OP.
I just don't understand what's going on. It's almost as if RM is lying to me about having successfully flashed the newest CWM. I say this because, when I immediately do the flash procedure after booting the phone, nothing shows up in /preinstall/recovery/ using Root Explorer (RE). It's only after I do the D2 bootstrap recovery option that /preinstall/recovery/ is populated with the CWM files. The problem is that these files represent the 2.0.5.8 version, not the 5.0.2.0 update.
To even deepen the mystery, after I did the above, I then went back into RM and reflashed to the latest CWM. I then looked at /preinstall/recovery/ again and all of the original 2.0.5.8 files were still there. There was no evidence that I could determine that RM installed anything anywhere.
I'm at a total loss.
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
sd_shadow said:
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
Click to expand...
Click to collapse
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
i don't think you will get an error
have you tried redownloading D2 bootstrap and rom manager, from market?
have you read this? http://rootzwiki.com/topic/31737-root-droid-x-root-method-for-234-45621-does-not-require-milestone-sbf/page__st__20#entry878745
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
the link was to a post that
someone was having trouble updating cwm to 5.0, and some possible fixes
as for the Slitaz ISO, is just a linux program used to run the magic md5 root method
fleggett said:
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
Click to expand...
Click to collapse
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
test test test
blindmanpb said:
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
Click to expand...
Click to collapse
Slitaz ISO, is just a linux program used to run the magic md5 root method
no it does not install a rom
you only need to update cwm if you want to restore a nandroid backup of a 2nd init rom,
most 2nd init roms come with their own bootstrap, found in the reboot options
you shouldn't install bootstrap or update cwm unless the rom does not install bootstrap
Sorry for the previous "test test test". The forum wasn't letting me post anything until I realized I'm under the ten post threshold and I was trying to quote text that had links.
Thanks, sd_shadow, for the extremely helpful pointers. Unfortunately, I no longer have the phone in my possession, but I might be getting another one to play with soon. I'll let you know if I run into the same problems after applying your potential fixes. Thanks again!
I'm ecstatic to report that the this alternative method by Tomsgt123 worked! Here is what I wound-up doing, from start to 5.0.2.0 finish.
First the facts, all taken from settings -> About phone
System version: 4.5.621.MB810.Verizon.en.US
Model number: DROIDX
Android version: 2.3.4
Baseband version: BP_C_01.09.15P
Kernel version: 2.6.32.9-g1282440 ([email protected] #1)
Build number: 4.5.1_57_DX8-51
ERI version: 5
PRL version: 58012
Bootloader: 30.04
1. Obtain SliTaz GNU/Linux (3.0) root ISO in preparation to root phone. File I used is named Droid2_D2G_DX_DX2-RootCD-2012.iso.
2. Burn SliTaz ISO to bootable media.
3. Enter Windows and boot phone normally.
4. Ensure USB debugging is enabled via the settings -> Application settings -> Development -> USB debugging checkbox.
5. Connect phone to computer via USB cable.
6. Drag from top of phone and select the USB connection -> Charge Only radio button.
7. Boot computer via SliTaz.
8. Choose option 3 (Root Droid X) and follow onscreen directions to the letter, including putting phone in bootloader mode.
9. Boot phone normally and invoke Superuser. Immediately exit Superuser. (This step probably isn't necessary.)
10. Install Droid 2 Bootstrapper (D2B), ROM Manager (RM), and Root Explorer (RE) on phone (I used adb).
11. Invoke D2B and choose Bootstrap Recovery. When done, exit D2B.
12. Make sure phone is connected to internet.
13. Invoke RM and choose Flash ClockworkMod Recovery. Current Recovery should be 5.0.2.0.
14. Choose 3rd option, Motorola Droid X (2nd-init).
15. Tap Flash ClockworkMod Recovery. Wait until recovery files are downloaded and flashed, then exit RM.
16. Invoke RE and navigate to /preinstall/recovery.
17. Rename recovery.zip to recovery.zip.bak.
18. Still within RE, navigate to /sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries.
19. Press and hold on recovery-clockwork-5.0.2.0-shadow.zip and copy the file.
20. Navigate back to /preinstall/recovery and paste the above file.
21. Rename the above pasted file to recovery.zip.
22. Exit out of RE and return to RM. Tap Reboot into Recovery and hit OK at the "Are you sure...?" prompt.
23. Phone should reboot into the 5.0.2.0 version of CWM.
Thanks again, sd_shadow. Without the above "manual" method, I would never have gotten the 5.0.2.0 version of CWM onto this phone. Now, time to play!
- Fred
And guess what? All those previous steps I carefully and deliberately outlined have been rendered obsolete by one, small apk:
http://rootzwiki.com/topic/25017-ro...workmod-flashable-updates-by-ky/page__st__190
(Still can't post links...yet.)
This is the Droid X Bootstrapper 621 MOD (DXB621). Functionally, it is the same as the old D2B except for two huge and critical features:
1. It contains CWM 5.0.2.0 out-of-the-box.
2. It works without having to do the aforementioned file manipulation inside RE.
Because of the above, it negates the need for RM (and D2B) entirely. I immediately installed DXB621 on my freshly SBF'd and rooted Droid X (see previous stats) and it worked flawlessly.
After all this, I'm convinced there is something wrong with RM as it relates to the Droid X with .621 already installed, whether via the OTA update or via SBF.
As a big bonus, after some finagling, I was also able to install HijackedBootMenu 1.1.5 621 1.1, which is a real gift, since it allows booting into CWM (or RZR) without having to first boot the phone to use either D2B, RM, or DXB621 itself.
So, the moral of this long and windy story is to simply use DXB621 for your recovery needs, don't mess with D2B and RM, and don't look back.
- Fred
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
sd_shadow said:
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
Click to expand...
Click to collapse
Yeah, getting any bootstrap to work on a Droid is the first step (after rooting) in doing much of anything, and using the most recent CWM seems to be required for all the latest and greatest ROMs, so it really should be somewhere on page 1 of that monster thread. I only stumbled across it via dumb luck.
I've run into a bizarre issue, though. With the phone connected to a running computer via USB, it won't boot into either CWM or RZR from Hijacked BootMenu (HB). Once you hit either recovery option, it just goes to a (slightly lit) black screen and stays there. The power button doesn't work at that point, so it requires a battery pull.
A clue as to what's going on might be that Windows recognizes the device when HB runs. It's only when I disconnect the cable before booting the phone that either recoveries invoke normally. Very strange.
I currently have CMKang.b3 loaded on the phone. I was pleasantly surprised to see that both the Camera and Torch apps work just fine, as I thought both were inoperable under CM9. This specific build is 9-20130120-UNOFFICIAL-shadow.
- Fred
sd_shadow said:
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
Click to expand...
Click to collapse
THANK YOU! I was having a similar problem as the OP, and this FINALLY fixed it!
also take a look at the modified d2 bootstrap that has been upgraded to cwm 5.0
will save a few steps if you have to reinstall
edit: I have rewritten my instructions here
[HOW TO] Install/Use Droid 2 Bootstrap
The modified Bootstrap is the trick. Straight to CWM 5.0. Took me a long time to figure out that ROM manager appears to update CWM but does not work. I found ROM manager to be of no use or value at all to me and don't install it or delete it.
Got 11 Open
Looking for an answer myself. Currently trying to install using Rom Manager then using button presses to get into Recovery. Will post update shortly.