Related
I have rooted android devices such as the htc hero and desire so I have a bit of background. However I tried rooting the nexus s and actually didn't even root the phone. After unlocking the nexus bootloader the instructions I followed said to reboot the phone which I did. However when I rebooted the phone it stays on the Google screen with a lock at the bottom of the screen The only upside is that my phone isn't totally bricked because I can access the bootloader by pressing up and power. Someone please help I will donate if you can get my phone up and running. By the way i'm using the tmobile 3g nexus s.
You need to download a recovery image, and, superuser zip file. Put them on the root of your usb storage You, shouldn't, have rebooted the phone after unlocking the bootloader. The phone doesn't have a custom recovery yet, that's why you are seeing the triangle. Put the phone in fastboot open a terminal and type in fastboot devices you should see a line of numbers then fastboot. Then type fastboot flash recovery recovery.img (with the name being the ACTUAL NAME of the recovery image you downloaded) then it should say something like writing recovery and then you can put the phone in recovery mode. As soon as the screen turns off unplug it. When it boots into recovery select flash zip from SD Card (yes we don't, have an SD Card it doesn't matter) then locate the superuser zip and select install. Reboot the phone.
Sent from my NS running NSCollab cuz I lost my tin cans and string....
When you say type fastboot flash recovery recovery.img with the name being the ACTUAL NAME of the recovery image do you mean that i replace the word recovery with the name of the file or just replace recovery.img with the name of the file?
also i can't transfer it to usb storage because it doesn't show up on my pc
You need to turn on USB storage first. Also the name of the recovery image should be something like recovery-clockwork-3.0.0.5-crespo.img (that would be the latest recovery from clockworkmod for our device, (crespo) Nexus S. So you would type fastboot flash recovery recovery-clockwork-3.0.0.5-crespo.img
Also once you move the su zip and recovery img to the USB Storage turn off the phone AFTER SAFELY REMOVING HARDWARE AND TURNING OFF USB STORAGE boot into the bootloader and do the above steps typing fastboot devices first to make sure you are connected All Gamer has a really good guide in either Nexus S general or Q&A
Sent from a bird cage, with a swing!
vintagetonez; I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium app
I should also say that I have tried booting in recovery since and clockwork mod is not there anymore. Its the stock android recovery. Is this a driver issue? I can't imagine so since I was able to unlock the bootloader
Sent from my Nexus S 4G using XDA Premium App
Is it possible to mount the sd card in fastboot or recovery mode if it is what's the command.
vintagetonez said:
I should also say that I have tried booting in recovery since and clockwork mod is not there anymore. Its the stock android recovery. Is this a driver issue? I can't imagine so since I was able to unlock the bootloader
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
With the Nexus S, you MUST REFLASH recovery every time you need it. There is a way to rename the stock recovery so clockwork mod will stick. However, I prefer to reflash it as I never have to worry about bricking my device. If you want to use the renaming method Google it using XDA Developers as a search parameter.
Sent from a bird cage, with a swing!
I figured out what the problem is but I need the system.img file do you no where i can find it in android 2.3.4 i've manually download it to my desktop but can't find the file
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
Hello everyone!
I've used ROM manager to flash clockwork mod recovery and it worked great until I realised that this clockwork doesn't see my SD card! I just wanted to know is there a solution to this without going back to stock etc?
Sent from my Xoom using XDA Premium HD app
Never fear! Fastboot is here!
Fastboot flash recovery recovery.img from the command line of your computer (you must have motorola drivers installed plus adb/fastboot tools)
I recommend Rogue Recovery, it's over in the android development section. Others prefer TWRP and EOS recovery. Take your pick. All support the internal SD card.
Thanks for your reply!
I thought about it initially, wanted to repeat steps used to flash it when original recovery was on. But first command re-booted xoom and took me to clockwork (no s..t, Sherlock? ) and then I thought I better stop before I end up with a brick.
So just to be clear, connect my xoom, go to the right folder on my pc and type:
fastboot flash recovery file-name.img
is that correct? do I need to be in recovery?
xywojtek said:
Thanks for your reply!
I thought about it initially, wanted to repeat steps used to flash it when original recovery was on. But first command re-booted xoom and took me to clockwork (no s..t, Sherlock? ) and then I thought I better stop before I end up with a brick.
So just to be clear, connect my xoom, go to the right folder on my pc and type:
fastboot flash recovery file-name.img
is that correct? do I need to be in recovery?
Click to expand...
Click to collapse
So you need to be in bootloader mode, not recovery. You can either turn the xoom on then press the down button about 2 seconds after you see the splash screen or use 'adb reboot bootloader'. I think it says 'starting fastboot protocol', can't quite remember from memory. then as you said, go to the right folder type fastboot flash recovery file-name.img
then fastboot reboot
then you'll be able to get into your custom recovery
love you man!
Hi together,
I've got a Motorola Photon Q 4g LTE mobile phone and this afternoon I wanted to install CyanogemMod, but whatever I do, I stuck with the following problem:
I can't install any other Custom Recovery. I tried ClockworkMod and OpenRecovery, but I always get the s**t Motorola Bootloader, when I start in Recovery Mode. The Bootloader of my Phone is unlocked via Motorola Website, as told in many other threads.
I know that the users arrrghhh, shabbypenguin and Skrilax_CZ are great experts with firmware and such things, but I'm not allowed to write in developer's forums because I'm new here.
Has anybody got an idea for me, how to geht the Custom Recovery to work?
Btw: I tried to root the phone as well, but that wasn't posible. May be things come together or depend on each other.
Thanks for your help!
When you flash recovery (IE run the fastboot command) is it successful?
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Also, try this.
arrrghhh said:
When you flash recovery (IE run the fastboot command) is it successful?
Click to expand...
Click to collapse
When I flash recovery, I just flash the Motorola given Recovery by Motoroloa Bootloader. The Phone restarts, a logo with the Android Man is shown (stomach opend with some engeniering tools in it) and after about 5-7 Minuten, the system starts normally.
I also managed it to change the "Unlocked Message" into a Motorola Logo by using fastboot flash logo xxxx.bin and I nearly destroyed the flash by flashing an unlikely file. So the phone was shortly out of order because oder "flash failure" (fastboot mode). After that, I managed to flash the "boot.img" file of an CyanogenMod, so the flash was rebuilt and I could use the phone normally.
arrrghhh said:
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Click to expand...
Click to collapse
It shows the connected devices by showing a 8 or 9 ditigt number. It's almost the same view like I connected the phone without fastboot and use "adb devices".
arrrghhh said:
Also, try this.
Click to expand...
Click to collapse
This one I didn't tried yet, because I was so dissappointed of the mismatch with ClockworkMod & Open Recovery. Do you think, that trying this one will help, after two others failed?!
Thanks for you notice and your time. That's very helpful!
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
arrrghhh said:
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
Click to expand...
Click to collapse
Ah ja, now I'm one step closer. I did not know, that the dead Android dude is the sign for stock recovery.
I'll give it this afternoon another try and will report. A bunch of thanks to you at this time!
Hi, it's me again. I managed now the reboot to recovery, by holding the volume up button while doing the "fastboot reboot"-command with the command box. That worked and I could start Photon Q Open Recovery 2.06.
Unfortunately, I did something wrong or so and now the script re-flashed stock recovery again. Nevertheless, I now know how to operate and will do the rest by my own (hopefully).
@arrrghhh: Thank you very much for your help!
So, I finally did everyhting the right way (now with ClockworkMod Recovery), because I now have CyanogenMod running on my Motorola Photon Q
:victory:
@arrrghhh: Thank you very very much!
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?
Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!
I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.
Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)
RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk