Hey. I dont understand I flash the custom recovery with odin but when i go into recovery I have stock recovery. I have tried twrp and Clockwork. Non works, The flash process is passed and complete. I wait for the phone to reboot and let it start up shut it down. Then go into recovery mode. I have taken out the battery before it starts up and go into recovery straight away but still stock... what is going wrong? I have heard about bootloader But all say its no bootloader on for s2 plus. Any help is appreciated! Thank you. If something is unclear please ask. :good:I have tried 6 custom recovery's non works. but will flash
wackyleaks said:
Hey. I dont understand I flash the custom recovery with odin but when i go into recovery I have stock recovery. I have tried twrp and Clockwork. Non works, The flash process is passed and complete. I wait for the phone to reboot and let it start up shut it down. Then go into recovery mode. I have taken out the battery before it starts up and go into recovery straight away but still stock... what is going wrong? I have heard about bootloader But all say its no bootloader on for s2 plus. Any help is appreciated! Thank you. If something is unclear please ask. :good:I have tried 6 custom recovery's non works. but will flash
Click to expand...
Click to collapse
Your mistake is you are letting it boot into system before you boot into recovery. It doesn't work like that, you obviously haven't carefully and completely read the instructions to install custom recovery via Odin.
You have to flash the recovery and then boot immediately into recovery BEFORE allowing the device to boot into any other mode, otherwise, it reverts back to stock recovery.
Here is the simplest way to do this without screwing it up.
When you flash the recovery in Odin, make sure the "autoreboot" option in Odin is UNCHECKED, then flash the recovery. When it is done flashing, disconnect the device from PC, then, you have two options, either remove the battery then immediately reinsert the battery then boot into recovery using the button combination or disconnect device from PC then power the device off then boot into recovery using the button combination.
Sent from my SM-S767VL using Tapatalk
Related
I tried to follow the thread by open1your1eyes0 on how to install custom recovery, root and unlock after taking the OTA.
I followed the instructions down to the part where I install a custom recovery. I tried CWM since I am most familiar with that, but the MD5 didn't check out after downloading 2 different instances of it. So I ventured out with TWRP. Flash was successful through Odin, but I couldn't get into recovery mode. So i tried to flash CWM over it. Either way, I don't think the custom recovery flash worked and now my boot screen says "Recovery booting", shows a Samsung logo, a lock picture, and says Lock. i cna get into what looks like stock recovery and it looks like my Android robot got shot and a triangle with a ! is coming out of his torso. He doesn't appear well.
Can anyone help me out here and explain what happened and how to fix it?
If you let your phone boot up then it did re write the stock recovery. Re flash your recovery making sure auto reboot is unchecked when it says passed unplug your cable pull the battery, put it back in then try to boot into recovery
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
If you let your phone boot up then it did re write the stock recovery. Re flash your recovery making sure auto reboot is unchecked when it says passed unplug your cable pull the battery, put it back in then try to boot into recovery
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Hmm... won't let me get to Odin mode. I do the 3 button method, then once the disclaimer appears, I try to hit Volume Up before it automatically reboots. It briefly shows the Odin download screen then just reboots anyway to the Samsung Custom lock boot screen.
Well that's strange! Try pulling your battery, letting it sit for a couple then trying to go into Odin mode again
If I helped you in some way.... pass on the favor and help the next person!
Yes, as stated in the subject, I've reverted to stock firmware for my specific device (Photon Q C Spire) from trying a few different custom roms, and have this issue now. It will load properly if I don't install custom recoveries. I've tried different CWM and TWRP versions, and none will load Android as the stock recovery does.... Any suggestions?
p.s. I was looking into possibly using something called an SBF file...
Reverting to the stock firmware, you use RSD Lite to flash a FXZ file - you have already done this or not?
Yes, I that's how I got back to factory settings. I lost my root and custom recovery in the process of course. But after booting Android, and doing the initial setup and activation, I decided to install a custom recovery to root it that way. Well, couldn't boot past recovery, so, had to revert back to stock recovery and root via the exploit with Android running in developer mode... sucks. But I'm currently rooted on a fully functional 4.1.2 C Spire FXZ.
So what's you end goal? Stock ROM with custom recovery?
You fastboot flash the custom recovery of your choice, boot said recovery, take a backup.. and then when you try to 'Reboot System' to boot Android, it fails to boot? How long did you let it boot? Do you get a boot animation?
No boot animation, because it boots straight into recovery no matter if I hard reset, soft reset, power/down power up or any means of trying to load Android. Also, the bootloader/fastboot screen wouldn't even load, it goes straight into the custom recovery every time. The only way I could get into bootloader/fastboot was by holding the Vol+Pwr keys. So, what I did was install stock recovery, and it then booted normally.
sulken2000 said:
No boot animation, because it boots straight into recovery no matter if I hard reset, soft reset, power/down power up or any means of trying to load Android. Also, the bootloader/fastboot screen wouldn't even load, it goes straight into the custom recovery every time. The only way I could get into bootloader/fastboot was by holding the Vol+Pwr keys. So, what I did was install stock recovery, and it then booted normally.
Click to expand...
Click to collapse
Well it seems like you're good then...?
When I was on stock, I installed TWRP and immediately took a backup of my stock configuration. I still have that backup, and it still works fine.
Trying to install CyanogenMod for my razr maxx HD. Recently used RSDlite to install 183.46.10 after OTA KK update kept failing. Then used towelroot to root and motopocalype to unlock bootloader. Fastboot screen shows bootloader is unlocked with status code: 3.
I then followed the instructions on the CyanogenMod site to flash CWM 6.0.4.4 recovery using fastboot, and all appeared to work fine.
However, when I try to reboot into recovery, nothing happens. I get hung up on the motorola dual core flashscreen for about a minute or two, then the screen goes black, then the phone reboots normally.
I tried flashing a different copy of CWM, tried TRWP, and tried several third party apps from Google Play store to boot directly into recovery using software reboot instead of hardware keys - all with the same results. I even tried flashing custom CWM recovery using ROM Manager and Rashr, same result.
Do I have a corrupt recovery partition? Any suggestions for how to fix?
You need to install a recovery for that phone specifically.
http://androidhosting.org/Devs/Dhacker29/
Use the recovery files found here.
Edit: on the site I posted, browse to the msm8690 folder. There you will find the recovery files.
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Thanks, guys, total noob mistake. I knew the recovery needed to be specific for the phone, but didn't realize it varied depending on the bootloader. Will try again with the right recovery!
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
TheGman125 said:
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
iBolski said:
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
Click to expand...
Click to collapse
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
TheGman125 said:
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
iBolski said:
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. Have code 3 on the devices.
try and unplug from USB when you reboot
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Poursinet said:
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Click to expand...
Click to collapse
Are you saying you are trying to flash a recovery or are you trying to GET to the stock recovery? If you are trying to get to the stock recovery, the key presses to get to it have changed.
Your best bet is to power off your phone. Then, press and hold power+vol up for a few seconds until you see the menu come up. Then, press vol down to highlight Recovery and then press the vol up button.
Eventually, you'll see the "Dead Andy". From there, press and hold vol down+vol up+power. You might have to do it a couple of times. Eventually, you'll be in the recovery but for the XT926, it's kind of hard to read because for some reason, they decided to make it dim.
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Poursinet said:
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Click to expand...
Click to collapse
Variable not supported comes up under some Windows, but it usually still works.
You never go straight to the bootloader when you reboot. You have to reboot the phone (or turn it off first) and then press and hold vol up+power. Then, from there, you use vol down to select recovery and then press vol up.
It never boots directly into the recovery unless you tell it to via an ADB command or from within a custom ROM that allows it.
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Caliburno said:
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Click to expand...
Click to collapse
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I think this may be the problem I am having. I cant get my 926 to boot to recovery from fastboot after I load CWM recovery. Is there some trick?
Hey guys... i've been trying to put a custom rom on this old p5113.... i've tried flashing latest TWRP on it with odin which odin claims its successful, but when i reboot the device and try to go into recovery i get back the original samsung recovery.... it's almost like it overwrites recovery at boot... i've read number of guides on this but i seem to be following the same steps they're suggesting.... am i missing anything obvious? from my understanding it's a straight up odin flash on custom recovery and then just use that to wipe/format and install rom + gapps.
Any ideas?
MartinCA1980 said:
Hey guys... i've been trying to put a custom rom on this old p5113.... i've tried flashing latest TWRP on it with odin which odin claims its successful, but when i reboot the device and try to go into recovery i get back the original samsung recovery.... it's almost like it overwrites recovery at boot... i've read number of guides on this but i seem to be following the same steps they're suggesting.... am i missing anything obvious? from my understanding it's a straight up odin flash on custom recovery and then just use that to wipe/format and install rom + gapps. Any ideas?
Click to expand...
Click to collapse
how are you doing it exactly, do you unplug the usb cable just as you see its "passed" with green status? or let it reboot itself? or are you rebooting it yourself? usually it will reboot itself into the recovery after it is successful, sometimes it goes to the system directly, generally the idea is to get into the recovery mode as soon as you flash it through odin. you should not let it boot and go to system( means don't let it start your rom, no samsung logo instead go to recovery first by pressing your volume up with power button. (if it's not going directly into recovery)