Last week I rooted my Galaxy S3 using Odin and today I went as far as to unlock the boot and flash the phone to use a custom boot image. Unlocking the boot was fine and flashing it with Flashify using a TWRP IMG file until it asked to reboot. When it turned off it didn't boot back and I have tried removing the battery. the SD card and putting it back and it did nothing.
I honestly didn't check if this has happened to someone else in the forums because most of the times I come here its a hassle to find the right thread so if someone has already posted a solution please link me or if not any other kind of help will be welcomed.
What do you mean unlock the boot? And a boot image is not the image you see at boot if that's what you thought. A boot.img is part of the kernel. What were you trying to do? What file did you use?
Do you mean you unlocked the bootloader? The sprint s3 isn't locked. I can't figure what you're talking about.
madbat99 said:
What do you mean unlock the boot? And a boot image is not the image you see at boot if that's what you thought. A boot.img is part of the kernel. What were you trying to do? What file did you use?
Do you mean you unlocked the bootloader? The sprint s3 isn't locked. I can't figure what you're talking about.
Click to expand...
Click to collapse
sorry for the late reply...
I was trying to install a custom boot animation and the instructions I found where to install an app called Quickboot to make a TWRP recovery back up of the ROM to be modified in case an error happened and I had to go back to the previous setting. After I did that the app required the phone to restart to apply the changes, it turned off it never turned on after that up to this day.
QUARAN7INE said:
sorry for the late reply...
I was trying to install a custom boot animation and the instructions I found where to install an app called Quickboot to make a TWRP recovery back up of the ROM to be modified in case an error happened and I had to go back to the previous setting. After I did that the app required the phone to restart to apply the changes, it turned off it never turned on after that up to this day.
Click to expand...
Click to collapse
If you want boot animation change, DO NOT install a boot image. Not the same thing. Boot image is part of the kernel (boot.img and ramdisk). For a boot animation, you need either a custom binary, or be using a rom that supports custom boot animations.
Did you make a full backup in twrp first? You can restore your backup.
madbat99 said:
If you want boot animation change, DO NOT install a boot image. Not the same thing. Boot image is part of the kernel (boot.img and ramdisk). For a boot animation, you need either a custom binary, or be using a rom that supports custom boot animations.
Did you make a full backup in twrp first? You can restore your backup.
Click to expand...
Click to collapse
I did but the phone won't turn back on
QUARAN7INE said:
I did but the phone won't turn back on
Click to expand...
Click to collapse
What s3 variant do you have ?
Sent from my SPH-L710T using XDA Free mobile app
hilla_killa said:
What s3 variant do you have ?
Sent from my SPH-L710T using XDA Free mobile app
Click to expand...
Click to collapse
The one from Sprint, SPH-L710 / Kit-Kat 4.4.2
Related
I'm curious if it's possible to just boot into cwm to do a backup and install a ROM. I would like to do something like this
fastboot boot recovery-clockwork-5.5.0.2-maguro.img
Then create a nandroid backup and flash a custom rom. The purpose of doing this would allow me to retain my stock recovery. Is this possible, are there any negatives to doing it this way, if I need to get back into CWM to restore my backup or flash a different ROM couldn't I just rerun fastboot without wiping out my stock recovery?
Flashing CWM does not modify your bootloader. The recovery and bootloader are two different things. Without unlocking the bootloader you won't be able to fastboot CWM anyway.
Sent from my Galaxy Nexus using XDA App
Sorry, I mistyped I intended to say recovery not bootloader, I have already unlocked my boot loader
You cannot Fastboot boot a recovery since this method is intended to boot a boot image.
There are no downsides to flashing CWM since it is trivial to flash the stock recovery back.
Temporarily loading CWM makes is more complicated, especially if something goes wrong flashing ROMs you have more steps to perform to recover.
Sent from my Galaxy Nexus using XDA App
silow said:
You cannot Fastboot boot a recovery since this method is intended to boot a boot image.
There are no downsides to flashing CWM since it is trivial to flash the stock recovery back.
Temporarily loading CWM makes is more complicated, especially if something goes wrong flashing ROMs you have more steps to perform to recover.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
What are you talking about?? Of course you can boot a recovery using fastboot. And it doesn't make anything more complicated.
Sent from my Galaxy Nexus using Tapatalk
moltenbobcat said:
I'm curious if it's possible to just boot into cwm to do a backup and install a ROM. I would like to do something like this
fastboot boot recovery-clockwork-5.5.0.2-maguro.img
Then create a nandroid backup and flash a custom rom. The purpose of doing this would allow me to retain my stock recovery. Is this possible, are there any negatives to doing it this way, if I need to get back into CWM to restore my backup or flash a different ROM couldn't I just rerun fastboot without wiping out my stock recovery?
Click to expand...
Click to collapse
Yes, you can do everything you stated. Although it is almost as much effort as flashing CWM and flashing the stock recovery after.
Sent from my Galaxy Nexus using Tapatalk
Yeah I was kind of thinking I was over complicating it I think I will just go with flashing it permanently. I did read somewhere in a cwm thread that there are a few issues with having cwm flashed to recovery like not being able to charge with the phone off.
Sent from my Galaxy Nexus using Tapatalk
moltenbobcat said:
Yeah I was kind of thinking I was over complicating it I think I will just go with flashing it permanently. I did read somewhere in a cwm thread that there are a few issues with having cwm flashed to recovery like not being able to charge with the phone off.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That doesn't apply to us. That was an issue that came up with the early builds of CWM for the HTC Sensation. The problem with what you wanted to do is more of a recovery issue. What happens if you flash or modify the wrong file and you get stuck in a boot loop? Now you have to wait to get to a computer to re-boot into the recovery to get a restore going. As long as your boot loader is unlocked and you can turn the phone on you'll have no issues with getting it back to stock for a warranty exchange if that's what you're worried about.
Sent from my Galaxy Nexus using Tapatalk
I flashed CM10 onto my phone a couple weeks ago, everything went smoothly. Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update. Well I download the update, reboot phone into fastboot, attempt to go into recovery and I get the red triangle !. I know this is an issue with the phone apparently not finding a recovery boot but why didn't my reverting to stock reinstall the stock recovery? Does anyone have any guides they suggest to get stock recovery back? (I've found a few but thought I would ask).
Now, this is understandable that my phone can't boot into recovery since I flashed CM recovery onto it and whatnot, but I attempted to boot into recovery on my girlfriends phone (same phone, NEVER BEEN UNLOCKED OR FLASHED) and it can't boot into recovery either... Is something going on here or am I just missing a huge piece of the puzzle? I don't really want to have to flash anything on my girlfriends phone to fix it, she's not into the tinkering and would rather not have her data reset. Any help would be appreciated.
And for the record, I did a search to figure this out but at the very least I can only find solutions for people who have flashed CM or similar and nothing pertaining to the problem my girlfriend's phone has.
Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app
nktje said:
Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Used this method:
http://forum.xda-developers.com/showthread.php?t=1848566
It worked, I'm on stock ICS, but I didn't do ANYTHING after booting into ICS again and attempting to install JB and booting into recovery. Did I miss something? How do I "flash recovery"?
Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app
I think you are confusing a few things here. First off, the Android with the red triangle IS the stock recovery main screen. (If you want to flash the update manually, you need CWM -- go into fastboot mode and type: fastboot flash name-of-recovery.img, where name-of-recovery is the recovery that you downloaded and want to flash.) Second, you need the stock recovery for an update to install over-the-air, but you need a custom recovery if you want to flash it manually.
Muffinabus said:
Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update.
Click to expand...
Click to collapse
this happened. you installed stock recovery when you reverted, whats the surprise?
and you dont need to relock bootloader to successfully update through ota. seems to me know the op needs to refine his searching skills.
nktje said:
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Click to expand...
Click to collapse
just press vol up+power to bring up the stock recovery menu.
edit: damn efrant, i got this man
sent from my i9250
nktje said:
Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.
Muffinabus said:
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.
Click to expand...
Click to collapse
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250
bk201doesntexist said:
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250
Click to expand...
Click to collapse
Alright, I think I got it... so the android with the red ! triangle IS stock recovery? I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then? So what does the stock recovery DO other than sit there and reboot after a minute?
Muffinabus said:
Alright, I think I got it... so the android with the red ! triangle IS stock recovery?
Click to expand...
Click to collapse
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
Muffinabus said:
I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then?
Click to expand...
Click to collapse
No, that does not work on the GNex.
Muffinabus said:
So what does the stock recovery DO other than sit there and reboot after a minute?
Click to expand...
Click to collapse
Have a look at the menu, and you can see the options.
efrant said:
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
No, that does not work on the GNex.
Have a look at the menu, and you can see the options.
Click to expand...
Click to collapse
Thank you! I feel like an idiot now. I honestly thought it'd be the same as the Nexus S where you were able to do this...
Yeah, I'm an idiot...
I was trying to root my 2013 N7 and I thought I had the factory image for it (it was actually the factory image for the 2012 N7). Anyhow, I ran through the "flash-all" script which proceeded to erase everything, including "boot". Now I can't boot anything even after installing the makeshift system.img here:
http://forum.xda-developers.com/showthread.php?t=2380913
Because my situation is a little different, I'm guessing it's because I hosed the boot on my machine.
Right now I can still get into the bootloader and go into recovery using TWRP, but when I try to boot into system I just get stuck at the Google logo .
Is there any way to fix this before google releases the factory image?
I do not believe so since the architecture of the old and new devices are differwnt that when you flashalled the old image something got messed up. You could try locking the bootloadewr and exchanging your nexus or wait for official image which should be soon
Sent from my Nexus 7 using xda app-developers app
Fastboot flash boot boot.IMG
Boot.IMG is your kernel
Sent from my Nexus 7 using xda premium
jporter396 said:
I do not believe so since the architecture of the old and new devices are differwnt that when you flashalled the old image something got messed up. You could try locking the bootloadewr and exchanging your nexus or wait for official image which should be soon
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I should mention that I didn't actually get to flash the old image because there was a signature mismatch. So I didn't actually install the old image...now I'm just left in a state where everything was deleted (including boot).
smirkis said:
Fastboot flash boot boot.IMG
Boot.IMG is your kernel
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I don't have boot.IMG for a 2013 Nexus 7, where can I get it?
petersellers said:
Sorry, I should mention that I didn't actually get to flash the old image because there was a signature mismatch. So I didn't actually install the old image...now I'm just left in a state where everything was deleted (including boot).
Click to expand...
Click to collapse
I would try doing what I did again, maybe on the off chance it works. Try downloading the image again. Good luck !
Sent from my Nexus 7 using xda app-developers app
stock image needed
Since you fully flashed an old factory image, the best option is to wait for Google to post the Factory image for Nexus 7 - Razor (maybe by Tuesday?). I had flashed an old recovery.img and my new nexus wouldn't boot. I got someone to pull it from their nexus and give it to me. It worked for me, but that was only one partition. All yours are messed.
treoo0_1 said:
Since you fully flashed an old factory image, the best option is to wait for Google to post the Factory image for Nexus 7 - Razor (maybe by Tuesday?). I had flashed an old recovery.img and my new nexus wouldn't boot. I got someone to pull it from their nexus and give it to me. It worked for me, but that was only one partition. All yours are messed.
Click to expand...
Click to collapse
I didn't actually flash the old image, there was a version mismatch.
I have the system partition thanks to the link in my post, I have the TWRP recovery partition, I think all I need is a boot partition. I'm guessing here since I'm new at android stuff.
petersellers said:
I didn't actually flash the old image, there was a version mismatch.
I have the system partition thanks to the link in my post, I have the TWRP recovery partition, I think all I need is a boot partition. I'm guessing here since I'm new at android stuff.
Click to expand...
Click to collapse
I can try help you.Just tell me one thing when you try starting the device what do you see?
And don't worry there is a way for this
decianV West
nsnarayan10 said:
I can try help you.Just tell me one thing when you try starting the device what do you see?
And don't worry there is a way for this
Click to expand...
Click to collapse
I see the google logo in the middle of the screen, with an unlocked lock logo at the bottom "since I have unlocked the bootloader".
If I press the volume rockers I get the choice to power off, start, restart bootloader, or recovery mode. Restart bootloader takes me to the standard android bootloader with the robot on its side, recovery takes me to TWRP.
I'm uploading boot.img for you.
BOOT.IMG HERE
petersellers said:
I see the google logo in the middle of the screen, with an unlocked lock logo at the bottom "since I have unlocked the bootloader".
If I press the volume rockers I get the choice to power off, start, restart bootloader, or recovery mode. Restart bootloader takes me to the standard android bootloader with the robot on its side, recovery takes me to TWRP.
Click to expand...
Click to collapse
Probably u got two choice.
1- find stock ROM for the device and flash it.
2- find someone with the exact same device, ask he/she to create backup of his/her device and flash it to yours.
And did you try flashing your device with proper factory image anyhow?
Boot.IMG was pulled by me here.
http://forum.xda-developers.com/showthread.php?t=2380380
Nburnes said:
Boot.IMG was pulled by me here.
http://forum.xda-developers.com/showthread.php?t=2380380
Click to expand...
Click to collapse
You're my messiah. I had unlocked, installed twrp, and booted into twrp. It asks if you want to root, I said yes then no boot. Fastbooted the system.img, but after the bootloader the screen would stay black but if plugged into my computer it would show the MTP device and I could access it. Flashed the stock boot.img you posted, and tada I get boot animation and actualy boot.
Thanks guys! I tried nburnes' boot.img and it worked great!
This was an educational experience, for sure
petersellers said:
Thanks guys! I tried nburnes' boot.img and it worked great!
This was an educational experience, for sure
Click to expand...
Click to collapse
Good and next time make sure not to repeat this mistake and how did u install it?
jporter396 said:
"exchanging your nexus"
Click to expand...
Click to collapse
Lets not promote this since it's fixable even if it means waiting for Google to release the official image. Don't screw over the store and others in queue waiting to buy because of self induced error.
nsnarayan10 said:
Good and next time make sure not to repeat this mistake and how did u install it?
Click to expand...
Click to collapse
/fastboot flash boot boot-flo-JSS15J-stock.img
I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.
ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
ovimunt said:
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
Click to expand...
Click to collapse
May I ask what variant you are using? GT-i9195?
Then please boot your phone into download mode, this can be done by first switching of your phone completely then holding the power button, home button and volume down button until the download screen appears where you press continue. Once you have done that connect your phone using the usb cable and make sure all drivers have been installed! Once the drivers are installed start up Odin uncheck the f.rest time box and click the AP section and then select the recovery file provided by Sir Arco in the root thread.
If you need more help please ask, If it worked then still reply
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Whosat said:
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Click to expand...
Click to collapse
Thanks for the response. Yeah, I kind of realized that's what's happening. I've managed to boot into the custom recovery right after the flash and did what I had to do in there, but then after I reboot the phone again, the custom recovery is gone. Is there a way to stop stock recovery being reflashed automatically?
Also, if I want to install a custom kernel, how can I backup the current one so that I can restore it at a later date if I need to? I know how to do this on HTC phones but it all seems to be a bit different on Samsung and I don't want to mess up anything.
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Whosat said:
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Click to expand...
Click to collapse
Umm... yeah, I think it did ask but I just accidentally pressed no before reading what it said... So I guess I'll just have to flash the recovery again and then answer yes to that question.
Thanks
Yes that would be the correct way to do it.
Hope all goes well!