Related
Hi
I followed this tutorial (http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/) to root my Nexus S (GTi-9023). Like a bunch of other people on this site my phone got stuck on the "Google with a pad lock" boot screen (I should have come to xda first). So to get past this i downloaded the stock rom (from here: http://forum.xda-developers.com/showthread.php?t=1056062) and extracted boot.img and then flashed the stock boot image and booted with it as below.
>fastboot flash boot boot.img
>fastboot boot boot.img
This fixed fixed my booting problem and i then used rom manager to install clockwork recovery. I can boot into clockwork recovery from rom manager but not from fastboot. i get an android with an exclamation mark. Any idea why and/or how to fix this?
Thanks in advance.
boozelclark said:
Hi
I followed this tutorial (http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/) to root my Nexus S (GTi-9023). Like a bunch of other people on this site my phone got stuck on the "Google with a pad lock" boot screen (I should have come to xda first). So to get past this i downloaded the stock rom (from here: http://forum.xda-developers.com/showthread.php?t=1056062) and extracted boot.img and then flashed the stock boot image and booted with it as below.
>fastboot flash boot boot.img
>fastboot boot boot.img
This fixed fixed my booting problem and i then used rom manager to install clockwork recovery. I can boot into clockwork recovery from rom manager but not from fastboot. i get an android with an exclamation mark. Any idea why and/or how to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Rename /etc/install-recovery.sh to install-recovery.sh.bak, then reflash the recovery.
DONT use rom manager to flash the recovery it hardly ever works [for me],
If you have 'Android SDK' and 'ADB' then,Download a decent recovery file and place it in your 'Android-SDK/tools" directory, then go to your 'cmd' [command prompt] and navigate to your android-sdk/tools directory ,,example below.
''cd C:/android-sdk/tools'' [cd meaning 'change directory']
Then type, "adb devices" it should list your devices ith a load of numbers and letters, if it does then proceed, if not re-plug your device into the USB [in the bootloader]
Then type,
"fastboot flash recovery recovery.img" and let it do its thing. [if it does not work , make sure you renamed you recovery file to 'recovery.img'
Hope this helps!!
XDA_Badman said:
DONT use rom manager to flash the recovery it hardly ever works [for me],
...
Click to expand...
Click to collapse
The problem is that with the stock rom the stock recovery gets flashed after boot up (by /etc/install-recovery.sh). Search for install-recovery.sh in the nexus s forums.
I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.
You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!
Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!
N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!
Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4
ddb540 said:
N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!
Click to expand...
Click to collapse
Hey you might want to look at the Google Nexus Toolkit. You can sideload a file if you already have a custom recovery installed.
http://forum.xda-developers.com/showthread.php?t=1995688
Good luck!
Lord Yurij said:
Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.
abaaaabbbb63 said:
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.
Click to expand...
Click to collapse
Sorry, I typed incorrectly. Yes, I did fastboot flash system system.img, etc.
ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.
Convert a tar.md5 file to .img
gee2012 said:
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.
Click to expand...
Click to collapse
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
Odin? That's for samsung mate. Won't work here. You need to download the factory images and extract it to get stock recovery. Or just head over to general section and there are thread for flashable stock recovery/modem/kernel. There is also a guide on how to use adb, a very detailed one at that. I'm sure you won't have trouble following it. Just read carefully and do it. All the things you need are given in that thread.
Edit: Guide - http://forum.xda-developers.com/showthread.php?t=2010312
AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
1. Make sure you have Android SDK installed. if not download here.
2. Download Nexus 4 factory rom from here.
3. Unzip the factory rom [occam-kot49h-factory]. If you dont know how to unzip. Download and install Winrar. Open the file with Winrar and Extract it somewhere in your computer.
4. Turn off your phone
3. Hold Volume up + Power; once it loads up to bootloader; connect it to your computer
5. The file [occam-kot49h-factory] you extract it early; in there you should see a file flash-all-bat. Open it [run it as admin if you are running Vista/7/8] and let it do its magic. Your phone will factory reset.
http://www.wugfresh.com/nrt/
go to this website, download the toolkit, and connect your nexus to computer on fastboot mode, do some few clicks, and boom, done
Hi,
I made this post/thread because i couldn't find a solution to my problem through this forum and google.
Here is my trouble:
I was trying to install a twrp recovery and was following the instructions of a tutorial.
-So first i installed flashify and proceeded to a back up of the current kernel and current recovery
-Then downloaded a custom recovery image through TWRP release for my nexus 4
-After this i accidentally flashed the recovery image to boot instead of recovery
Now as you can guess the trouble is that my phone only boots to TWRP recovery instead of usual boot.
I tried to find aswers on this forum and google and yet i didn't find a solution.
I tried this post but without results:
http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
I would be grateful for any help and wish to recover this mistake without using a factory reset if possible.
Thank you, as you can see i am pretty new to this environment.
Can you get into fastboot mode? If yes, try flashing a stock Google rom and perform a factory wipe after installing the stock rom.
audit13 said:
Can you get into fastboot mode? If yes, try flashing a stock Google rom and perform a factory wipe after installing the stock rom.
Click to expand...
Click to collapse
Thank you for your answer, yes i can get into fastboost mode. As i am pretty new can you explain me how i can flash the stock Google rom (i guess it is the factory rom provided ?). Will this operation erase my data on the phone ?
Boot into fastboot and flash boot.img and recovery.img file from stock rom. Make sure you use the stock rom that matches the rom currently installed on your phone.
Ilovkos said:
Thank you for your answer, yes i can get into fastboost mode. As i am pretty new can you explain me how i can flash the stock Google rom (i guess it is the factory rom provided ?). Will this operation erase my data on the phone ?
Click to expand...
Click to collapse
Once in fastboot, extract the downloaded zip you got from Google. There you will find flash-all.bat Execute it as admin and wait. If it doesn't work, then extract the zip within the first zip and you should get loads of .img files. You will manually have to flash them. The commands are a bit different for each partition. They go like this:
Code:
fastboot flash system system.img
fastboot flash recovery recovery. img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash data userdata.img
Note that if your cmd/terminal isn't open from the directory where the files are you will have to input it's location, for example
Code:
fastboot flash recovery C:\Users\YOURUSER\Desktop\recovery.img
Also note that there must be no spaces neither in the file name or the directories where the file is located, otherwise it probably won't flash.
Also yes, doing this will completely revert you to stock, and you WILL loose all your data. You could try just reflashing recovery.img and then flashing TWRP over it. If you can get to TWRP after this, then connect the USB cable to your PC and transfer all the data you need, after which I recommend flashing to stock. You can root and/or flash custom ROMs after this.
However in your case I think you don't have to completely go back to stock. Just try flashing the proper boot and recovery images over fastboot like I explained above and try booting then.
nerotNS said:
Once in fastboot, extract the downloaded zip you got from Google. There you will find flash-all.bat Execute it as admin and wait. If it doesn't work, then extract the zip within the first zip and you should get loads of .img files. You will manually have to flash them. The commands are a bit different for each partition. They go like this:
Code:
fastboot flash system system.img
fastboot flash recovery recovery. img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash data userdata.img
Note that if your cmd/terminal isn't open from the directory where the files are you will have to input it's location, for example
Code:
fastboot flash recovery C:\Users\YOURUSER\Desktop\recovery.img
Also note that there must be no spaces neither in the file name or the directories where the file is located, otherwise it probably won't flash.
Also yes, doing this will completely revert you to stock, and you WILL loose all your data. You could try just reflashing recovery.img and then flashing TWRP over it. If you can get to TWRP after this, then connect the USB cable to your PC and transfer all the data you need, after which I recommend flashing to stock. You can root and/or flash custom ROMs after this.
However in your case I think you don't have to completely go back to stock. Just try flashing the proper boot and recovery images over fastboot like I explained above and try booting then.
Click to expand...
Click to collapse
Thanks to both of you I managed to fix this just by flashing the boot.img of the Google factory img. It didn't erase my data except my messages which is nice.
Hello, I tried to install an os image on the Nexus 6P Android. In addition I downloaded the Angler Image where the flash-all batch is. I'm afraid that the files will not be transferred to the phone at all. For example, if I try to install TWRP in the bootloader and then reboot the phone, I am stuck with the Google logo and with the warning "Your device software can not be checked for corruption cant open bootloader" (Which is quite normal if you have unlocked the bootloader).
I'm not so good with it and hope someone can help me with it.
Please don't blame me if it is obvious. I'm a ****ing noobie
shoXy-. said:
Hello, I tried to install an os image on the Nexus 6P Android. In addition I downloaded the Angler Image where the flash-all batch is. I'm afraid that the files will not be transferred to the phone at all. For example, if I try to install TWRP in the bootloader and then reboot the phone, I am stuck with the Google logo and with the warning "Your device software can not be checked for corruption cant open bootloader" (Which is quite normal if you have unlocked the bootloader).
I'm not so good with it and hope someone can help me with it.
Please don't blame me if it is obvious. I'm a ****ing noobie
Click to expand...
Click to collapse
From your description I'm not sure exactly what you did. Did you fastboot flash the factory image? Did you fastboot flash TWRP? You need to do it that way if you didn't. See this guide...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So im using flashboot flash recovery twrp.img and after that i reboot the phone and im getting the same problem that im stuck on the warning message.
shoXy-. said:
So im using flashboot flash recovery twrp.img and after that i reboot the phone and im getting the same problem that im stuck on the warning message.
Click to expand...
Click to collapse
after flashing the factory image
let phone boot up into system for a minute
boot into your bootloader
boot into your bootloader using fastboot the twrp.img
once in twrp, flash the TWRP.ZIP file on you sdcard
then you can install cust kernel or magisk, or just reboot to system