I'm coming from a samsung vibrant on tmobile, I never used fastboot with my vibrant. I used adb alot, and this whole fastboot is new to me.
Is this something specific to sprint or specific to the nexus S bootloader?
on my vib I just rooted it and downloaded rom manager, went into the app and told it to flash the recovery and off I go, doesn't seem to be the case here. Here I use fastboot to flash an image, and it doesn't stick around although I heard theres a way to do it, maybe renaming the crespo image file or moving a script on the filesystem. Just trying to figure out the basics as to how they would relate to how I've been doing things for months already on the vibrant, was surprised that it was this different being from the same manufacturer.
-J
jbeez said:
I'm coming from a samsung vibrant on tmobile, I never used fastboot with my vibrant. I used adb alot, and this whole fastboot is new to me.
Is this something specific to sprint or specific to the nexus S bootloader?
on my vib I just rooted it and downloaded rom manager, went into the app and told it to flash the recovery and off I go, doesn't seem to be the case here. Here I use fastboot to flash an image, and it doesn't stick around although I heard theres a way to do it, maybe renaming the crespo image file or moving a script on the filesystem. Just trying to figure out the basics as to how they would relate to how I've been doing things for months already on the vibrant, was surprised that it was this different being from the same manufacturer.
-J
Click to expand...
Click to collapse
Fastboot is an open source utility for flashing. Once rooted you can use rom manager like any other phone. It's not necessary to use an exploit to gain root and then flash a recovery like most phones, you can just unlock the bootloader and flash it directly using fastboot. From there you can flash the such binary and do whatever you please.
There is a script that runs on boot and restores the stock recovery, /etc/install-recovery.sh. After you flash the su binary just rename this or delete it and your recovery will not be overwritten on boot.
Sent from my Nexus S using XDA Premium App
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.
Hi folks,
Been a while since I've rooted. I have a stock evo 4g on 2.3.5, baseband 2.15.00 and kernel 2.6.35. I want to try out CM9 nightlies ROM but I have a few questions about how to get there first.
I see there are 3 main rooting methods for my phone.
1) htcdev
2) taco root
3) captainthrowback
*any others?
Appears I have to downgrade my boot loader version to 2.10. The main question is how do i get amon ra on my phone as the recovery software? From what I recall from the previous rooting i did (using revolutionary) it only came with clockwork orange. With the rooting methods above and using revolutionary, do I get the choice between amon ra or clockwork?
thanks for the time.
JJ
anyone?
what software number is your phone? it should say in the about phone section of settings...
repomanz said:
Hi folks,
Been a while since I've rooted. I have a stock evo 4g on 2.3.5, baseband 2.15.00 and kernel 2.6.35. I want to try out CM9 nightlies ROM but I have a few questions about how to get there first.
I see there are 3 main rooting methods for my phone.
1) htcdev
2) taco root
3) captainthrowback
*any others?
Appears I have to downgrade my boot loader version to 2.10. The main question is how do i get amon ra on my phone as the recovery software? From what I recall from the previous rooting i did (using revolutionary) it only came with clockwork orange. With the rooting methods above and using revolutionary, do I get the choice between amon ra or clockwork?
thanks for the time.
JJ
Click to expand...
Click to collapse
gfunk0311 said:
what software number is your phone? it should say in the about phone section of settings...
Click to expand...
Click to collapse
Hi,
4.67651.3
Here's my way
repomanz said:
Hi folks,
The main question is how do i get amon ra on my phone as the recovery software?
JJ
Click to expand...
Click to collapse
The way I have always done it is:
1. Download and rename the recovery file to PCIMG36.zip and place it in the root directory of the sd-card.
2. Power off the phone.
3. Hold the down (or up) volume key while holding down the power button until you see the screen SUPERSONIC EVT S-OFF at the top -- or something similar.
4. Select Bootloader then select Recovery
4. Let the phone find the PCIMG36.zip file
5. Accept the update when asked
6. DO NOT reboot the phone when asked
7. When you see the recovery menu, go ahead and do a Nandroid then (3 options here) A. Connect phone to computer and choose USB-MS Toggle option, find the PCIMG36.zip file and rename or delete it ... or B. Power off phone, connect to computer and rename or delete PCIMG36.zip file ... or C. Reboot as normal, use a file manager app like Astro or ES File Explorer and find the PCIMG36.zip file ... blah blah blah. Any of those options will keep the phone from asking to update each time you boot into recovery.
Next time you reboot to recovery, you should see Amon RA. As as side note, I would highly suggest using SmelkusMod Amon RA style recovery -- especially for CM9 roms.
I'm running the stable cm10 and I have cwm recovery installed. I was thinking about installing TWRP Recovery because I have hboot 1.14 and I read somewhere that it's easier to flash the fast boot when updating the rom using TWRP. Anyway, I can install it directly through GooManager, but it seems far too easy. Can I really just have GooManager install it for me and that's it?
Yup, it really is that easy
And is it accurate that TWRP makes it easier to flash fast boot files when updating your rom? Coming from Samsung devices, I was a little iffy with having to flash the fast boot files with adb and I actually temporarily bricked my device.
Also, once I update to TWRP through GooManager, that's it, cwm is replaced with TWRP? I feel like I'm missing something.
Also, thanks for answering.
You're not missing anything, it really is that easy.
And when using twrp for hboot > 1.09 you need to use HTC dumlock (it's part of twrp) to flash boot in recovery. Maybe try using flash img GUI, its available in the play store and is all over the cm10 threads.
Also, why flash boot with adb over fastboot? Fast boot seems easier. Or maybe I'm just used to it
Sent from my HTC One S using xda premium
I was going through the thread , [15.11.2012][ICS]PhilZ Touch 3.00 - CWM Based Recovery 6.0.1.5 (Temporary flash) by Phil3759. It talks about flashing a temporary on a stock recovery. I have few queries about this (This is about the concept rather the actual method itself, so though its for S2, posting here)
1. If I understand correctly, stock samsung recovery (3e) looks for signed zips (signed by samsung). So either this is writen for older recovery (2e) which may have allowed unsigned zips OR stock recovery refers to something else (thats not from samsung)
2. If my understanding is correct, there is a separate recovery partition which holds its own recovery kernel separate from the normal boot kernel. In this background, what does flashing insecure kernel means? does this procedure replace the main android kernel? does this insecure kernel also act as recovery kernel when booted in recovery?
3. is there anyway to backup recovery partition (as far as I can think of, this may not be possible. As I have not seen any way to root SGR without installing custom recovery first. and through heimdall, I dont think a dump can be taken of partitions)
That thread is old and doesn't apply to the R in any way.
1) Almost no OEM stock recoveries allow flashing custom signed zips, only those signed by the specific OEM. Sometimes it does work though, if they don't set it up correctly. This is why we could root on JB on the O4X, it allows zips signed with test keys to be flashed.
2) Insecure kernel means you flash a rooted / ADB-enabled kernel on the main boot partition. Yes, it replaces the main kernel. No, it doesn't act, recovery has a totally different kernel. Flashing insecure kernel should only be done from custom recovery, doing so from Odin / Heimdall triggers yellow triangle.
3) It's possible from ADB even if you aren't rooted. You can dump with Heimdall too, Google gives a lot of results.
Thank you Adam77Root
Thank you Adam77Root, that cleared my doubts regarding the recovery.
What I was referring to was like the dump of the partition with dd (or probably tar). On linux, normally if you are not root, you wont have disk access (or unless you are part of disk group). Isn't it the same with android kernel as well?
I have found some info about backup of partiton through heimdall / odin. I am going through that. Will update later on that
( androidforums dot com/exhibit-4g-all-things-root/733167-how-tool-rom-sgh-t759-create-odin-heimdall-backups.html
http://forum.xda-developers.com/showthread.php?t=1372455
)