Stuck boot loop and Volume Up broken (can't access recovery) - Galaxy S III Q&A, Help & Troubleshooting

Just like the title says stuck on boot loop (stock rom) and my volume up button broken so i cant access recovery at all , And adb shows no devices however odin can see the phone So i cant use (adb reboot recovery)
Any way to access recovery ? Or i'm just trapped there?

Flash recovery through Odin. It may boot directly into recovery. Did your button break after you flashed the phone? Are you 100% sure it's broken? I've cracked open an S3 and it's not an easy thing to break.
Use the latest tar from: https://dl.twrp.me/i9300/
Worst comes to worst, reflash stock - root/flash recovery, and then make sure you follow through with the process correctly. I managed to mod an unmodded i9300 4.1.3 to rooted/MM/recovery/F2fs in under an hr.

Turbine1991 said:
Flash recovery through Odin. It may boot directly into recovery. Did your button break after you flashed the phone? Are you 100% sure it's broken? I've cracked open an S3 and it's not an easy thing to break.
Use the latest tar from: https://dl.twrp.me/i9300/
Worst comes to worst, reflash stock - root/flash recovery, and then make sure you follow through with the process correctly. I managed to mod an unmodded i9300 4.1.3 to rooted/MM/recovery/F2fs in under an hr.
Click to expand...
Click to collapse
It boots to system , And Any stock i flash from odin boot loop too as it needs factory reset from recovery (which i can't do)

Related

[Q] Can't install TWRP Recovery on my phone..

I have the Galaxy Note SGH-I717R (Rogers version), with the stock android 4.0.4 installed. I want to install a custom ROM but I cannot get TWRP Recovery to work on this phone. I have followed all the guides but it will not work, even though it appears to install correctly. I put my phone into download mode, start odin in admin mode, attach my phone, it is recognized by odin, then I choose PDA and select the TWRP Recovery tar file (which is the correct one for my device). After I click Start on Odin it goes through these messages as it installs and reboots my device:
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
and the box in the upper left corner turns green and says "Pass!".
After this, I have my phone usb disconnected and I reboot into recovery mode.. Only when it starts in recovery, it is the same stock recovery mode that comes with stock android! With this, I cannot flash the custom ROM because it gives the error that verification failed.
I have tried installing TWRP through goo manager as well, but when I choose the openrecoveryscript option, it says that nothing was found for my device.
What am I missing here? How can I install this custom recovery to allow me to flash a custom ROM?
I also tried this with 2 different versions of TWRP - 2.5.0.0-quincyatt.img and the latest 2.6.3.0-quincyatt.img
This may seem like a silly question but does the TWRP package include root in it? I have had to root with Clockwork mod tar first and then I have installed TWRP after that.
There are free utilities on Google Play that can tell you if you are rooted or not.
Download the 2.6.1.0.IMG.tar file and flash it. Also change the USB port you are using, and reinstall the Samsung USB drivers before attempting it again.
fraughtsigewulf said:
This may seem like a silly question but does the TWRP package include root in it? I have had to root with Clockwork mod tar first and then I have installed TWRP after that.
There are free utilities on Google Play that can tell you if you are rooted or not.
Click to expand...
Click to collapse
according to others, you do not need to be rooted to flash a rom.
I flashed a zip file for TWRP, just like a normal rom. once you flash, it replaces your cwm.
the error????????? if it is status 7, your recovery needs to be updated
OK, I've solved the problem. I followed another video that said to uncheck auto reboot on odin when installing TWRP, then remove the battery and unplug once it loads it on. I did this, and ended up bricking my phone, it wouldn't start saying need to fix bad firmware in kies recovery. Kies wouldn't even detect my phone at this point, so I started Odin again and was able to run a recovery from there by pressing start, it said it removed something, and was successfully recovered. I tried rebooting into recovery mode again on my phone, and magically it loaded into TWRP! From there I was able to flash the custom Revolt ROM and now my phone is running fine.
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
ok, i've flashed via odin, pulled the battery and started it up but it still goes to stock recovery.
I've also flashed, shut it down, pulled the battery, rebooted and then selected reboot in recovery with no luck either.
Am I missing something?
Thanks
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
Thanks! I was trying to instal ClockworkMod Recovery with no luck, I have an Australian Version of GT-I9506, and your tip worked for me! Solved... :victory::victory:
can't get it done
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
I just can't get recovery to work after pulling the battery, it keeps on saying firmware error. What I am doing wrong?
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
mayoni said:
I just can't get recovery to work after pulling the battery, it keeps on saying firmware error. What I am doing wrong?
Click to expand...
Click to collapse
I'm having the same problem with an SGH-I717R. I flash TWRP with ODIN, pull the battery and disconnect the USB cable so the phone powers off. Then I hold Vol Up+Vol Down+Power until the phone vibrates, I see the "Samsung Note" logo on the screen for a fraction of a second, then it goes into "ODIN MODE", tells me how many custom binaries I've flashed, etc, and says "Firmware upgrade encountered and issue" and tells me to run recovery from Kies. If I restart the device normally, it goes into this mode as well. I can return the phone to a usable state by booting into download mode, flashing TWRP again with ODIN, then letting the phone reboot without holding any buttons down, but then recovery is back to stock 3e.
I've also tried this using CWM and Heimdall, as per the instructions on the CM wiki, with the same results. I've uninstalled and reinstalled the USB drivers and also enabled USB debugging on the device, since I read somewhere that might be an issue. I realize I'm replying to a 2-year old comment from rangercaptain, but do you have any more suggestions?
mdm_ said:
I'm having the same problem with an SGH-I717R. I flash TWRP with ODIN, pull the battery and disconnect the USB cable so the phone powers off. Then I hold Vol Up+Vol Down+Power until the phone vibrates, I see the "Samsung Note" logo on the screen for a fraction of a second, then it goes into "ODIN MODE", tells me how many custom binaries I've flashed, etc, and says "Firmware upgrade encountered and issue" and tells me to run recovery from Kies. If I restart the device normally, it goes into this mode as well. I can return the phone to a usable state by booting into download mode, flashing TWRP again with ODIN, then letting the phone reboot without holding any buttons down, but then recovery is back to stock 3e.
I've also tried this using CWM and Heimdall, as per the instructions on the CM wiki, with the same results. I've uninstalled and reinstalled the USB drivers and also enabled USB debugging on the device, since I read somewhere that might be an issue. I realize I'm replying to a 2-year old comment from rangercaptain, but do you have any more suggestions?
Click to expand...
Click to collapse
There is an Odin flashable cwm at rootgalaxynote. Once that is flashed you can load a su zip to your phone and flash or change to twrp by flashing it with cwm..not Odin. You then just reboot to recovery and you will be in twrp. You should probably use one from gimmeitorilltell version 2.8.0.0 or higher. I use 2.8.0.0 as it supports theming still. If you need more detail hit me up for the links. Searching the forum or googling should get you there though.
Sent from my SAMSUNG-SGH-I717
developweb said:
There is an Odin flashable cwm at rootgalaxynote. Once that is flashed you can load a su zip to your phone and flash or change to twrp by flashing it with cwm..not Odin. You then just reboot to recovery and you will be in twrp. You should probably use one from gimmeitorilltell version 2.8.0.0 or higher. I use 2.8.0.0 as it supports theming still. If you need more detail hit me up for the links. Searching the forum or googling should get you there though.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Thanks for the pointers! Would you say this tutorial[1] is more or less what you're suggesting I try? And then from there, flash TWRP 2.8.0.0 from CWM recovery?
[1] XDA won't let me embed a link because my account is too new, but it's a page on rootgalaxynote that ends with /galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
EDIT: Ugh, scratch that idea. I followed the instructions on that site and exactly the same thing happened. Flashing CWM through ODIN appears to work fine, but if I reboot immediately after flashing I end up with stock 3e recovery again, and if I hold Vol Up+Vol Down+Power to reboot immediately after flashing, I get the ODIN mode "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message and can't get past it until I flash CWM with ODIN again and let the stock recovery overwrite on reboot.
EDIT #2: So I finally got it to boot CWM by holding Vol Up+Vol Down as ODIN reboots the device, but trying to flash the Superuser zip from that site results in an error and the instant you boot system, it overwrites recovery with stock again. Am I correct to assume that if I can get into CWM and flash a custom ROM, recovery will stop being reset to stock on every boot?
mdm_ said:
Thanks for the pointers! Would you say this tutorial[1] is more or less what you're suggesting I try? And then from there, flash TWRP 2.8.0.0 from CWM recovery?
[1] XDA won't let me embed a link because my account is too new, but it's a page on rootgalaxynote that ends with /galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
EDIT: Ugh, scratch that idea. I followed the instructions on that site and exactly the same thing happened. Flashing CWM through ODIN appears to work fine, but if I reboot immediately after flashing I end up with stock 3e recovery again, and if I hold Vol Up+Vol Down+Power to reboot immediately after flashing, I get the ODIN mode "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message and can't get past it until I flash CWM with ODIN again and let the stock recovery overwrite on reboot.
EDIT #2: So I finally got it to boot CWM by holding Vol Up+Vol Down as ODIN reboots the device, but trying to flash the Superuser zip from that site results in an error and the instant you boot system, it overwrites recovery with stock again. Am I correct to assume that if I can get into CWM and flash a custom ROM, recovery will stop being reset to stock on every boot?
Click to expand...
Click to collapse
Did you repeat steps as instructed at this point?
If you get any errors at this point, don’t worry about it and repeat Steps 13 to Step 16 twice more and reboot. You will still get root.
Sent from my SAMSUNG-SGH-I717
developweb said:
Did you repeat steps as instructed at this point?
If you get any errors at this point, don’t worry about it and repeat Steps 13 to Step 16 twice more and reboot. You will still get root.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Yep, I was finally able to root the device doing that, but I still can't get CWM recovery to persist. I can flash it with ODIN, then hold down Vol Up+Vol Down as ODIN resets the device, which gets me into CWM recovery. From there I can do the usual CWM recovery stuff, and if I reboot, then hold down Vol Up+Vol Down immediately, I can get back into CWM recovery. I can do this as many times as I like and it always brings up CWM recovery. As soon as I let the phone boot the stock OS, CWM recovery is gone and I'm back to stock 3e. My end goal is to flash a custom ROM to this device; I assume if I do that, the stock recovery will stop being restored on every boot?
mdm_ said:
Yep, I was finally able to root the device doing that, but I still can't get CWM recovery to persist. I can flash it with ODIN, then hold down Vol Up+Vol Down as ODIN resets the device, which gets me into CWM recovery. From there I can do the usual CWM recovery stuff, and if I reboot, then hold down Vol Up+Vol Down immediately, I can get back into CWM recovery. I can do this as many times as I like and it always brings up CWM recovery. As soon as I let the phone boot the stock OS, CWM recovery is gone and I'm back to stock 3e. My end goal is to flash a custom ROM to this device; I assume if I do that, the stock recovery will stop being restored on every boot?
Click to expand...
Click to collapse
Sorry this didn't work for you, but I'll throw in the last bit anyway.
" With Android 4.0.4 update, your phone might overwrite the ClockworkMod Recovery you flashed in ODIN. To get around the problem, simply flash ClockworkMod Recovery again in ODIN, then when you see “PASS!”, immediately hold down Volume Up and Volume Down buttons, you should be in ClockworkMod Recovery instead of the Belly-up Andy Android figure."
Sent from my SAMSUNG-SGH-I717
Same Problem
Huge problem

[Q] Trouble Flashing CWM Recovery [YP-G70]

Hey guys -
I'm having trouble getting CWM Recovery to work with my YP-G70. I've rooted, installed ROM Manager, wiped data and partitions, installed Odin, Used Odin to (supposedly) flash the DD_01142012.tar recovery to the device. Everything looks successful, but when booting back up ROM manager only gives me the option to go to "recovery setup" instead of the normal flash option. Even when I reboot it in recovery, it just goes to the standard android recovery screen. Any ideas on how to fix this? It may be painfully obvious, this is my first root.
Hydraulix_93 said:
Hey guys -
I'm having trouble getting CWM Recovery to work with my YP-G70. I've rooted, installed ROM Manager, wiped data and partitions, installed Odin, Used Odin to (supposedly) flash the DD_01142012.tar recovery to the device. Everything looks successful, but when booting back up ROM manager only gives me the option to go to "recovery setup" instead of the normal flash option. Even when I reboot it in recovery, it just goes to the standard android recovery screen. Any ideas on how to fix this? It may be painfully obvious, this is my first root.
Click to expand...
Click to collapse
Rom Manager does not work for this device ( I think ) and you should not use it. "DD_01142012.tar" is not just a recovery, it's the kernel too. They are integrated. Flash it again and hold power and vol-up during boot up to get to recovery then flash your rom...

[Q] Soft brick, stuck on Samsung screen, no recovery mode

Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
Did you hold the button combinations when your phone is off for more than 4 seconds? If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom. Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
gsstudios said:
Did you hold the button combinations when your phone is off for more than 4 seconds?
Click to expand...
Click to collapse
Yes, I almost got blisters on my fingers, thats how often (and long) I tried it. Also released the power button but continued to hold vol-up+menu as soon as the boot screen showed up.
If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom.
Click to expand...
Click to collapse
Does sound a little crazy indeed, but it also makes sense to add such a feature (i.e. boot into recovery if rom isn't present). Any particular suggestion for a KitKat kernel or should I just pick one of those mentioned here?
Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
Click to expand...
Click to collapse
Nope, no recovery, ergo no factory reset (or is there another way with a softbricked phone?)
Anyway, that would delete the userdata from the phone as well (e.g. photos), correct? Or are they already gone due to my rom flashing etc.? Oh wait, there is this difference between internal memory and internal usb storage, right?
Update
So I could not decide which one of Kitkat Kernels mentioned here to take. But I tried flashing the CWM recovery files, both GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar and CWM-KitKatCompatible-i9100.tar, with Odin. Flashing went fine, but on boot I only see the bootlogo and then the screen went black.
Any suggestion on what other kernel I could try would be welcome.
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
summerchild said:
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
Click to expand...
Click to collapse
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash CM11 from the CWM, not through Odin).
dapperdanman said:
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash km from the CWM, not through Odin).
Click to expand...
Click to collapse
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
summerchild said:
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
Click to expand...
Click to collapse
I don't have a backup of the original ROM, but I can flash a stock ROM and that still gets stuck on the animated Samsung logo.
Anybody else with an idea?

[Q] Custom Recovery problem (Rom manager-cwm)

im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
scarface195894 said:
im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
Click to expand...
Click to collapse
Pull battery let it sit for two minutes. Push menu button, volume down button, and power button at the same time boot into download mode. once there flash a fresh copy of your OS which ever version of KitKat your running. You lose all your personal data, but your beyond that now. Then here is link to my thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 enjoy !!!
uknow said:
Yeah ive said it a few times this should not be used
If youve bricked your phone you can get back into your phone by holding volume down menu botton and power botton at the same time when it pops up the warning screen to enter download mode hit cancel your phone will then boot up after your phone is on if you do not have a computer the way you fix the phone so you dont have to do this every time your phone is off you need mobile odin and a kitkat cwm.img.tar for our phone flash it and problem solved you can now boot into cwm recovery then if you want you can flash a twrp img zip through cwm or just keep cwm hope this helps
Ps if you Google mobile odin the dev gives it away on his xda mobile odin page
Click to expand...
Click to collapse
.............^^^^^^...........
stuck in recovery loop also
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
update-- i found an updated version of the philz tar file and installed it with odin and that got me out of the loop..just havent tried to get back into recovery yet...lol
Cat1970 said:
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
Click to expand...
Click to collapse
First, pull the battery for a minute then reinstall hold the power, menu, and volume down buttons at the same time and boot into download mode. The version of Phil'z CWM you flashed is to old for 4.4.4 NK4. Now download to your desktop the right Philz CWM recovery file (Phil'z_Touch_6.48.4-hlte.tar.md5 ) here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ there are two listed use the second one. Flash with odin and you should be good to go. Go to my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 for more info.
done exactly as you said and the same screen came up saying recovery is not seandroid enforcing and then it jumps to Philz Touch 6 so im assuming everything is right now...i really appreciate the help! tyvm
different rom
ok..i installed cyanogen rom..i also used titanium backup..i want to go back to where i was but i dont see titanium backup on there anymore..how do i revert back?
i guess i need to update my phone n900p (help)
my rooted note 3 was running 5.0 L so i tried flashing a custom recovery both TWR and CWM now its stuck in boot loop. i read all the post showing you how to get out the bootloop. how ever i still need to put a recovery on my phone are there any updated links for this with odin because i was using the odin 3.0 sorry odin 307

[Q] Can't enter Recovery Mode, have to wipe phone

Hi
A friend of mine asked me to help with his old phone. He wanted to hand his phone to his children, but he can't remember the passwort he entered once.
It is a complete stock phone. No ADB activated.
But the main problem is, that I can't enter recovery mode. I am very familiar with flashing phones and so on and know what to do, but I really can't enter the recovery mode. At least I can enter download mode (not as good as normaly, it often doesn't work, but I can).
Has somebody an idea how I can reset the phone with Heimdall or Odin? I also tried to flash a new recovery (CWM, CWM touch, stock) and the Stock ROM, but I still can't enter recovery mode (volume rockers seem to work, also home button) .
@Pflunz thats odd. So even flashing siyah kernel out of my head still doesnt allow you to boot into recoverymode? Because the S2 has recovery and kernel for system builtin.
Try to maybe flash gingerbread for the s2 first and it will probably work.
After you have flashed gingerbread and try to boot into system. If that works then you can root it and flash recovery. And boot into recovery from your rom.
You can do the same with jellybean stock instead of gingerbread. Read odin guide cause you can reflash stock with odin and it should be okay. Are you also flashing it for the right model?
I dont own anymore the S2 so I cant talk out of direct experience anymore.
I hope also for you that someone who is current in the s2 community can help you with this problem goodluck :good:

Categories

Resources