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.
Related
Hi all!
I'm sure many of you are confident on doing this, but some are not. This quick how-to is for the scenario when you have Froyo installed with Recovery3e which is the default recovery and you're trying to make a backup of your firmware in Rom Manager without flashing another kernel via Odin.
You click on "backup", the phone reboots to ClockWorkMod Recovery. Or not. You will see Recovery3e popping up with an error message telling you that the package is not signed. Fear not, here's the solution:
Pre-requisites:
Phone must be rooted
Rom Manager installed
ClockWorkMod Recovery installed from within Rom Manager
After getting the error message, just take the battery out and simply apply volume UP + Home button + Power button to get to recovery and CWM will come up, doing what you've asked it for!
Just installing CF-Root with Odin is the simplest solution for me which roots your device and installs ClockworkMod
http://forum.xda-developers.com/showthread.php?t=788108
Is there any useful advantage to loading the latest version of CWM using the market app?
I originally flashed mine with CF-Root, but since have flashed the speedmod kernel and that seems to have changed it again.
alexhull24 said:
Is there any useful advantage to loading the latest version of CWM using the market app?
I originally flashed mine with CF-Root, but since have flashed the speedmod kernel and that seems to have changed it again.
Click to expand...
Click to collapse
I have just updated my rom manager and the change is a new layout with icons and it looks much nicer
The guide is for those, who don't want to change the factory kernel in the rom. Flashing CF-Root/SpeedMod/Voodoo or whatever you sympathize with is the best solution I agree, as it comes with several benefits aside rooting, but not everyone wants to do it that way.
I would add, just to be sure, after backup copy the backup file to external SD card..
myrddral said:
Hi all!
I'm sure many of you are confident on doing this, but some are not. This quick how-to is for the scenario when you have Froyo installed with Recovery3e which is the default recovery and you're trying to make a backup of your firmware in Rom Manager without flashing another kernel via Odin.
You click on "backup", the phone reboots to ClockWorkMod Recovery. Or not. You will see Recovery3e popping up with an error message telling you that the package is not signed. Fear not, here's the solution:
Pre-requisites:
Phone must be rooted
Rom Manager installed
ClockWorkMod Recovery installed from within Rom Manager
After getting the error message, just take the battery out and simply apply volume UP + Home button + Power button to get to recovery and CWM will come up, doing what you've asked it for!
Click to expand...
Click to collapse
hi, i did the same and got the update.zip in my phone but when i try to apply it during 3e recovery, i always get the <E:failed to verify whole-file signature xxxxx Installation abort>
can anyone help me with this issue?
many thanks in advance.
p/s: the phone is already rooted and rom manager installed with the latest CWM recovery 2.5.1.2
current firmware 2.2, kernel version 2.6.32.9, build number froyo.DXJPE
same issue as last post, I have successfully rooted the phone with oneclick, I have installed rom manager, I have flashed CWR (v2.5.1.2) phone is GT-I9000, Firmware is 2.2.1, kernel 2.6.32.9, build FROYO.BOJS5 and baseband is I9000XXJPY
I checked, root is working and rom manager got the proper root access
if I access "backup your current ROM" it takes me to the recovery v3 mode, where there is no backup options. if I try to apply the update.zip, I got the error signature not verify. I remove the battery, I reinsert it and the phone reboot to the recovery3, I apply the update.zip again and get the same messages, again and again.
I could probably install CF-ROOT but I would like to do a nandroid backup first and this is never presented in the options
reup
dereut said:
same issue as last post, I have successfully rooted the phone with oneclick, I have installed rom manager, I have flashed CWR (v2.5.1.2) phone is GT-I9000, Firmware is 2.2.1, kernel 2.6.32.9, build FROYO.BOJS5 and baseband is I9000XXJPY
I checked, root is working and rom manager got the proper root access
if I access "backup your current ROM" it takes me to the recovery v3 mode, where there is no backup options. if I try to apply the update.zip, I got the error signature not verify. I remove the battery, I reinsert it and the phone reboot to the recovery3, I apply the update.zip again and get the same messages, again and again.
I could probably install CF-ROOT but I would like to do a nandroid backup first and this is never presented in the options
reup
Click to expand...
Click to collapse
Same here!
On same ROM...
There is an excellent guide on this forum, and on another one that specify that galaxy s with froyo 2.2.1 and recovery3 needs to install CF-ROOT :
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000
and
http://forum.xda-developers.com/showthread.php?t=1035995
what this thread here is about is how NOT to need CF-ROOT
this is a bit like biting your own tail. I think the most important part for me is: if you flash another kernel, can you revert to your previous one as it is not possible to do a nandroid backup before flashing the kernel
for warranty sake, it would be important to be able to revert to a nandroid backed-up ROM, then revert to recovery3 than unroot the phone before bringing it back in case of need of repair
I found an app, sgs kernel flasher, it might be possible to backup the original kernel this way
so it would go like this :
root the phone (onclick root worked well with my phone)
install rom manager
install sgs kernel flasher
backup the kernel
flash CF-ROOT as describe in http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000 (the clearest guide I found so far)
flash CWR (or is it not necessary with CF-ROOT)
do a nandroid backup
save preciously the backup and the previously backed up kernel
play with the new toys .....
when warranty is needed:
restore the nandroid backed-up ROM
revert to original kernel with sgs kernel flasher
unroot with oneclick
can someone with experience revue this list and tells us if it sound correct ?
thanks
reup
I went a bit further, following my own post just above :
my phone is already rooted and has ROM MANAGER installed
I used the first option of ROM manager and flash the last CWR. that has created a update.zip on my sdcard, but I cannot use it as I am still on recoveryv3
I backed up my kernel using "sgs kernel flash" (found on market)
I flashed a new kernel : CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip. this is because my phone build is build FROYO.BOJS5 (noticed the 2 JS5)
rebooted the phone, I open ROM Manager and went to "reboot into recovery"
there I was on recoveryv2, with very little options but I "apply update.zip" twice (first one failed)
I rebooted and suddenly I had access to the new flashed recovery, CWR with backup options
I did a nandroid backup
one trick, the OK button became the right most button, and not the center one anymore
one think left to do, revert to stock samsung with recovery v3. to test the complete process
another trick, the CF-ROOT kernel came package into a zip files and when trying to flash it with sgs kernel flash it fails. you need to unzip the file first, it will gives you a .tar file, this one can be flash successfully
so all together, we can flash a new kernel all from the phone, without ODIN and without a PC (windows, Linux or other)
reup
dereut said:
I went a bit further, following my own post just above :
my phone is already rooted and has ROM MANAGER installed
I used the first option of ROM manager and flash the last CWR. that has created a update.zip on my sdcard, but I cannot use it as I am still on recoveryv3
I backed up my kernel using "sgs kernel flash" (found on market)
I flashed a new kernel : CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip. this is because my phone build is build FROYO.BOJS5 (noticed the 2 JS5)
rebooted the phone, I open ROM Manager and went to "reboot into recovery"
there I was on recoveryv2, with very little options but I "apply update.zip" twice (first one failed)
I rebooted and suddenly I had access to the new flashed recovery, CWR with backup options
I did a nandroid backup
one trick, the OK button became the right most button, and not the center one anymore
one think left to do, revert to stock samsung with recovery v3. to test the complete process
another trick, the CF-ROOT kernel came package into a zip files and when trying to flash it with sgs kernel flash it fails. you need to unzip the file first, it will gives you a .tar file, this one can be flash successfully
so all together, we can flash a new kernel all from the phone, without ODIN and without a PC (windows, Linux or other)
reup
Click to expand...
Click to collapse
You and me are in exactly the same situation. To do nandroid backup for warranty reason we have to brake that same warranty.
Only I didnt use cf-root, I went for hardcore speedmod...
Original Article
Since the Nexus One has been updated to 2.3.4, most root applications have been patched, superoneclick root and gingerbreak dont work. However, this does (Roots to 2.3.3) without unlocking the bootloader.
First of all, huge thanks to danger-rat and Phoenix84118 on the N1 Forums and XDA for walking me through this (and holding my hand I might add)
Disclaimer: I will not be held responsible for your phone. If your phone explodes/bricks or even releases the plague, it is your fault, and your fault alone. You take all responsibility for going through with this tutorial.
Downloads you need:
You can download these before hand or just download them as you read the guide.
[step 01] http://goo.gl/fWoS6
[step 08] http://goo.gl/ajTCV (get the latest version)
(edit: the link seems to be down, you will have to regester on xda and download it from the bottom of the post, v1.9.5 should work, http://goo.gl/lFTio )
[step 12] http://goo.gl/ZN5ON , http://goo.gl/4ULk and http://db.tt/ooDaCnU
1) Download http://goo.gl/fWoS6 (UNZIP THIS, then move on)
2) Rename it to PASSIMG.zip (NOT PASSIMG.zip.zip) If you can't see the '.zip', don't type it (the download already is a .zip).
3) Plug your Nexus One into the computer and mount it (or put the SD card into a card reader). Place the zip above into the root directory of the SD card.
4) Boot your phone into bootloader mode(Power + Vol-), Hold them down until you get a white screen.
5) If PASSIMG is correctly recognized, you'll see a prompt to install it (Vol+). Follow the directions. THIS WILL ERASE ALL THE DATA ON THE PHONE (will NOT erase the SD card).
6) When it's done, the phone will reboot. (Vol+)
7) Remove/rename the PASSIMG.zip file, so it won't check for it again (delays recovery mode by minutes).
8) Now to root your N1, go here http://goo.gl/ajTCV and download the latest version.
[before you continue, ensure you have the android sdk and drivers upto date]
(edit: the link seems to be down, you will have to regester on xda and download it from the bottom of the post, v1.9.5 should work, http://goo.gl/lFTio )
9) Unzip it , hook up you N1 to a pc and open up the superoneclick root program.
10) Click root, When it says: Waiting for Device, Turn USB Debugging ON
11) Install ROM Manager, open it, and click Flash ClockworkMod Recovery.
[Note if it failed, download the Superuser app from the market to update it, then reboot and su should not work, in ROM Manager, click repair]
[Before you do this step, download these and place it on your sd card: http://goo.gl/ZN5ON , http://goo.gl/4ULk and http://db.tt/ooDaCnU ]
12) Now click reboot into clockwork recovery.
-Install .zip from sdcard
-Choose .zip from your sd card
-Yes, and let the update install
13) During this process the phone will reboot twice
The first time will show you the solid X, then go back to recovery, the second time, it will show you the solid X, here, you must pull the battery before it moves onto the animation.
Failure to do this in time means youwill have to restart the entire process, as CWM and the root is lost.
14) Now boot up the phone into recovery (power + vol-) then select recovery
15) CWM should still be on there, now install a zip from sdcard and pick su-2.3.4.1-ef-signed.zip
16) Install the Recovery-Fix.zip
17) Once complete, hit back and reboot the system!
You now have root on android 2.3.3! Congratulations!
Nice. I just ran into the page by accident looking up CWM 5.x for the Nexus One.
My only suggestion would be to indicate what those links are. I personally don't like clicking on shortened links, as I can't tell what it is. Plus, this isn't twitter.
I suggest everyone wanting to do this, read all the steps carefully BEFORE proceeding. There's some stuff that's timing specific, so you have to be quick (specifically, step 13).
Nice guide though. I'm glad my help was made into a guide. I would have done it myself but.... well no I wouldn't have. I would LIKE to have done it, but I'm lazy. I'm glad you took the initiative (and thanks for the nod!).
EDIT: The guide title says 2.3.4, but end with "You now have root on android 2.3.3". One of the downloads is indeed 2.3.4. So just FYI, this IS 2.3.4 (GRJ22).
Thank you Lt.Fury, great tutorial!!!
This did not work for me.
When running SuperOneClick I get an error on Step #4
Parameter name: startIndexFAILED
Any ideas?
unfortunately i could root my n1 with superoneclick
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
i used above to unlock my n1 and it worked successfully.
I used the latest version of superoneclick and works fine!
Make sure you have all drivers updated and net framework!
Just get one error, when try install the SU from sdcard, on recovery, i couldn't install it, but no problem, CM7 have SU pre installed!
I tried through super one click but it didn't work for me..though I had all prequisitives.
Nvm the method given by cm worked for me
Sent from my sexy nexy
thanks! Nice Guide!
Okay First of all download the following files
a)http://android.clients.google.com/packages/ota/google_crespo/VQ8PQk_V.zip (4.0.3 OTA)
b)http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip (2.3.6 Official I9020T Build)
c)http://bit.ly/su2361ef (SU flashable)
d)http://forum.xda-developers.com/showthread.php?t=988686 (Grab recovery form this thread)
e)http://developer.android.com/sdk/index.html (Grab the android SDK installer)
f)http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429 (Radio file only required for I9020A)
Okay so when done with all that proceed as follows
1) Backup your current apps using Titanium Backup (Optional/Recommended)
2) Backup(Nandroid) your rom using backup option in CWM (Optional/Recommended)
3) Do a full wipe, wipe sdcard, system, data, cache Transfer a,b,c,f to your phone.
4) Flash the 2.3.6 Official I9020T Build you had downloaded using the install zip option in CWM (IMP-DO NOT REBOOT RIGHT NOW)
5) Flash the flashable SU file you had downloaded and then reboot.
6) Once your phone is on, continue to set up your account or skip it as you wish. (Optional)
7) Open up market, download the latest SU app, Voodoo OTARootKeeper, Titanium Backup and any other app you use that requires root.
8) Open the updated SU app, hit menu button and click preferences, go all the way down, click on su binary(tap to check for updates) , and make sure it updates to v3.0.3
9) After that is done, open and allow root permissions to all your root apps. (This is important)
9.5) Run Voodoo OTARootKeeper and click on protect root, make sure all options get checked.
10) Turn off phone, keep volume up and power pressed to boot into fastboot.
11) Select recovery with volume buttons and use power to launch.
12) Once you see a android bot image and an arrow image, keep volume up pressed and press power once, then you'll see some options appear.
13) Select apply update option and find the official 4.0.3 OTA file you had downloaded and flash. Reboot.
14) Once you have booted into ICS, go to Voodoo OTARootKeeper and select resture Root, all options should now be ticked, if not something went wrong.
15) Voila, you have root. Now to get back CWM recovery you can follow this -
i) Place the recovery img file in the android sdk platform-tools folder
ii) Switch to the directory where you unzipped the Android SDK & go to "tools"
iii) Then type "fastboot flash recovery yourfilename.img" & hit enter
iv) That should do it.
v) Optionally you may do it form Rom Manager too, if it works.
16) (ONLY FOR I9020A) Reboot phone, turn it off, boot into fastboot, select recovery, CWM should launch, flash the radio file you had downloaded to get radio working on I9020A (ONLY FOR I9020A)
Root only works for the apps that were installed while on 2.3.6
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip , use this root file, flash it in cwm, everything works, permissions etc.
This might work for other variants, tested on I9020A and I9020T, I take no responsibility for anything that might go wrong with your device. I take no credit for any links or procedures provided in this guide, I just tested and compiled.
Thanks and best of luck.
..........
Good guide but first two links are broken.
bajansurfer said:
Good guide but first two links are broken.
Click to expand...
Click to collapse
Thanks, fixed.
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
poging22 said:
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
Click to expand...
Click to collapse
Might not work, though you can try, if it fails, do it my way, also its impossible to get any kind of root that way.
Link for the ATT Radio doesnt seem to be working
Great work!
wipe SD card?
Is this necessary?
I don't think it's necessary to wipe the SD card, I followed the procedure in http://forum.xda-developers.com/showthread.php?t=1396913 and although it said my SD card would be wiped, everything was still there after I was done!
Anyone on a i9023 tried this?
Hmm...does "any version" includes M200(Korean Nexus S)?
Sent from my Nexus S using Tapatalk
http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429
I think he meant that for the 9020A radio
Link fixed, sorry for that, SD wiping might not be necessary, but I suggest as it makes it cleaner. Might work for I9023 and M200, I have no clue, maybe some experienced developer can answer that better.
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
little hiccup at step 12. im getting the android bot with exclamation mark but i press volume up with power and nothing happens. menu doesnt show up....
Edit: NVM... i pressed it 3 or 4 times and it finally worked
Michie23 said:
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
Click to expand...
Click to collapse
You should post it in questions, I cannot answer this.
fromthestars said:
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Click to expand...
Click to collapse
Many ways of doing it, I just am suggesting one, the flashable zip for ics isn't available as yet, what did you flash?
i9020 keeps getting status 7 aborted and my padlock is still unlocked on t-mobile 2.3.6
Has any tried this on an i9023? Thank u
Sent from my Nexus S using xda premium
1. Place the superuser.zip file attached at the end of the post on your sd card.
2. Flash recovery in bootloader with "fastboot flash recovery <filename>.img". I recommend CWM 5.0.2.3 found in this thread - http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
3. Go to recovery, in "mounts and storage" select "mount system" and then flash su-install.zip (EDIT : Mounting system not necessary, the script does it automatically while flashing the zip, but just in case)
4. Fix Permissions and reboot system.
5. Use any root explorer (i recommend ROM Toolbox, free in market) and go to /etc and either rename "installrecovery.sh" to "installrecovery.sh.old" or just delete it (its not needed).
6. There it is - Rooted ICS with a recovery that sticks.
EDIT -- IF, by any chance, after following the above steps, you find that you're stuck without a recovery (android exclamation screen), just flash a recovery via fastboot and you'll be fine. This time the recovery WILL stick. I think its something to do with the su-install.zip. I dont know for sure because I found it off the internet, its not mine.
Also, I did the superuser market update and I DID NOT lose root. I have an I9020T. So others with the same can safely update, imo.
Thanks to ab.grafix for being a part of the team.
IMPORTANT -- The su-install.zip posted previously is NOT mine. I didnt know who made it but just found out. All credit to dzo binary and Chamb'. I just made a guide coz it worked for me and I thought it might help others too.
Tested on I9020T and I9023
Don't forget to click on that thanks button if this helped.
UPDATE -- Superuser was updated by ChainsDD to support ICS 4.0.3. Thank you ChainsDD! Updated zip is now attached.
So now that we have root we need a overclocked kernel...
Sent from my Nexus S using XDA App
works great but very old cwm
Worked as described. Thanks !
Old cwm? Wich version? Is it possible to flash the latest one with rom manager?
So I am on ICS alpha13.
I9023
- wipe everything and Flash Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader via clockworkmod
- Reboot in stock recovery and flash stock ICS
- Boot in ICS enable debug mode
- Run the bat follow instruction?
Is it ok?
Thanks
Hi will it work on the rogers i9023a? Can someone tell me which stock ICS to flash?
Thanks
Thanks, it worked and nothing was wiped since I was already unlocked. With apps that require root you no longer get asked for root permission nor do they show in app list in superuser but it seems to have root for now
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
when in BL i dont have Unlock option :|
Thanks for your effort.
But I'm curious about the flashable zip file.
What's the difference of the zip file between the orignal superuser ?
And did the recovery do some magic which CWM can't do?
After reading the script , I just see the zip is important ,maybe the recovery is doing some magic too.
I'll just flash the zip and see what happen.
ro_explorer said:
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
Click to expand...
Click to collapse
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
I've done it, thanks a lot. I've also replaced the recovery.img file with the last cmw and all went well.
Now the rom doesn't show the root permission request toast but it works however.
I'd ask if its possible to manually update the superuser.apk or its better to mantain this one?
sakisds said:
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
Click to expand...
Click to collapse
Great .. I'll do that because I miss my "old" cwm
EDIT: it worked, thanks!
thanks, working here on 9023. warning for other users - do not update superuser from the app itself, or it'll stop working. at least it did for me, when i updated it to 3.0.3
confirmed working I9020a...
[INFO] Working root for ICS 4.0.3
Credits to Chamb'.
Flash via CWM and you're done.
Tested working for ICS 4.0.3 I9020T.
Enjoy!
Source: http://forum.xda-developers.com/showpost.php?p=20394635&postcount=4
It seems to have worked like a charm, thank you!
I was even able to flash the latest CWM Recovery using ROM Manager
can I flash stock 2.3.6 with cwm?
Im on ics alpha13
Anyone got a download link for the stock 2.3.6?
bratfink said:
Anyone got a download link for the stock 2.3.6?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664
Flash recovery with odin
Copy SU file to Root of device and flash from recovery
Files and method found at link below;
http://galaxytabhacks.com/galaxy-tab-10-1-root/how-to-root-ics-on-galaxy-tab-10-1/
Hi guys,
I have a problem.
I used this guide as well as others, and always appeared to me to superuser icon but root checker and other apk me reported that the tablet does not have root.
sorry for my english I'm slovak
winco206 said:
Hi guys,
I have a problem.
I used this guide as well as others, and always appeared to me to superuser icon but root checker and other apk me reported that the tablet does not have root.
sorry for my english I'm slovak
Click to expand...
Click to collapse
Nazdar
Actually I have the same issue as winco, I had root before upgrade to ICS.
I used this guide, everything looked fine. I have installed CWM, I have Superuser app, but tablet does not seem to be rooted. Even when I press in CWM. "fix root" it does not help at all.
Does anyone know if there is an easy way to root it without connecting the PC method?
Many thanks
Hi all, some time has passed, does anyone know? To help 2 noobs. Many thanks
Sent from my GT-P7500 using Tapatalk HD
doktorko said:
Hi all, some time has passed, does anyone know? To help 2 noobs. Many thanks
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Make it 3............same problem here
doktorko said:
Nazdar
Actually I have the same issue as winco, I had root before upgrade to ICS.
I used this guide, everything looked fine. I have installed CWM, I have Superuser app, but tablet does not seem to be rooted. Even when I press in CWM. "fix root" it does not help at all.
Does anyone know if there is an easy way to root it without connecting the PC method?
Many thanks
Click to expand...
Click to collapse
If you have CWM installed, then you need to get the superuser.zip onto the internal sdcard partition. You can download it using the tablet's browser, then use an file manager application to copy the downloaded zip into /sdcard.
Then boot into recovery and install it with "install zip from sdcard".
Defaults browser of Android 4.0.4 stock rom errors
when i turn internet in stock rom 4.0.4. it not work and put out.
who can explain to help me?
u know how to root SGT WIFI only with update 4.0.4 ?
root twrp not working
I'm a newbee with android so please appologize for stupid remakrs or questions.
I wanted to root my Samsung Galaxy Tab 10.1 with android 4.04 (Icecream I think) because I can't use my WD-elements external 2TB disk, not even with an external power supply. The disk is not recognized by the tablet, I only get a message 'High power device connected".
After some googling I saw that the S3C driver is missing. It seems that the tablet has to be rooted to be able to innstall such a driver.
I followed instructions from this thread, used Odin en then tried to reset my gt_p7500 by pressing start and volume down and then volume up.
The TWRP windows shows up but the screen is running like hell. So I cannot reach twrp to backup my old image and install the new image.
So my tablet is still not rooted.
Pleas advise me what to do.
Working method for me
scherpbierje said:
I'm a newbee with android so please appologize for stupid remakrs or questions.
I wanted to root my Samsung Galaxy Tab 10.1 with android 4.04 (Icecream I think) because I can't use my WD-elements external 2TB disk, not even with an external power supply. The disk is not recognized by the tablet, I only get a message 'High power device connected".
After some googling I saw that the S3C driver is missing. It seems that the tablet has to be rooted to be able to innstall such a driver.
I followed instructions from this thread, used Odin en then tried to reset my gt_p7500 by pressing start and volume down and then volume up.
The TWRP windows shows up but the screen is running like hell. So I cannot reach twrp to backup my old image and install the new image.
So my tablet is still not rooted.
Pleas advise me what to do.
Click to expand...
Click to collapse
I'm new to this too. Will try to help as much as I can since I've been able to successfully flash new ROM, TWRP etc., The process is as follows:
1. I found that the only TWRP recovery + ODIN combo that worked for me was the one packaged in this thread. Booted my tab into Download mode -> flashed TWRP with the ODIN (both from the package in the mentioned thread) -> Rebooted into recovery TWRP.
1a. From TWRP -> Wipe -> Cache, Dalvik Cache, Data.
2. Did 'adb push <rom_image.zip> /sdcard' (without quotes. need to have Android SDK installed in your PC with version 1.0.29 or above. Reason for version is to have 'sideload' functionality which I'll show how to use later).
3. Did 'adb push <gapps.zip> /sdcard' (same notes as in above bullet).
4. Selected "Install" option in TWRP -> Selected rom_image.zip from /sdcard location -> swiped to flash/installed the ROM (I used this ROM and find it to be the best so far and suits my liking).
5. Installed gapps in the same process as above for ROM.
6. Rebooted system.
Additionally, you could download TWRP flashable .zip file of TWRP 2.6.3.0 in order to get 'adb sideload' functionality. I found this to be a savior for me many a time.
:highfive:
Let me know how it goes. all the best flashing...
twrp is the problem!
baystallion said:
I'm new to this too. Will try to help as much as I can since I've been able to successfully flash new ROM, TWRP etc., The process is as follows:
1. I found that the only TWRP recovery + ODIN combo that worked for me was the one packaged in this thread. Booted my tab into Download mode -> flashed TWRP with the ODIN (both from the package in the mentioned thread) -> Rebooted into recovery TWRP.
1a. From TWRP -> Wipe -> Cache, Dalvik Cache, Data.
2. Did 'adb push <rom_image.zip> /sdcard' (without quotes. need to have Android SDK installed in your PC with version 1.0.29 or above. Reason for version is to have 'sideload' functionality which I'll show how to use later).
3. Did 'adb push <gapps.zip> /sdcard' (same notes as in above bullet).
4. Selected "Install" option in TWRP -> Selected rom_image.zip from /sdcard location -> swiped to flash/installed the ROM (I used this ROM and find it to be the best so far and suits my liking).
5. Installed gapps in the same process as above for ROM.
6. Rebooted system.
Additionally, you could download TWRP flashable .zip file of TWRP 2.6.3.0 in order to get 'adb sideload' functionality. I found this to be a savior for me many a time.
:highfive:
Let me know how it goes. all the best flashing...
Click to expand...
Click to collapse
The problem lies within TWRP. As I wrote: TWRP shows up but the screen is scrolling like hell. So I am not able to reach TWRP to wipe or anything at all.
so still no root I am sorry to say.
scherpbierje said:
The problem lies within TWRP. As I wrote: TWRP shows up but the screen is scrolling like hell. So I am not able to reach TWRP to wipe or anything at all.
so still no root I am sorry to say.
Click to expand...
Click to collapse
Oh ok . The version I had mentioned in my reply did not help?