This guide is intended for the Samsung Galaxy Core Prime, but it may work on other devices if you have the same issue.
The problem: You can only boot into recovery, and bootloader/download mode.
What you need: Stock Recovery, Odin v3.10.6 (This is what I used at least), TWRP Recovery and TrapKernel.
Download those and when you are done boot your device into Bootloader/Download mode.
Guide for 'beginners'
Connect it to your computer.
You should already have TrapKernel flashed then good, if not then flash if by clicking BL(It doesn't make a difference from what I have noticed, if you choice BL or AP but in my case I choice BL) and selecting it TrapKernel. Hit start.
Your device will start normally. This Doesn't fix your problem yet. Turn your device off and boot back into Bootloader/Download mode.
Click BL again and select the stock recovery you downloaded.
Click start.
Your device is now booted normally, but yet again this is expected and doesn't fix the problem.
Turn your phone off. It will boot into recovery again, scroll down and click "Reboot into Bootloader"
Now hold your power, vol down, and home button until your device turns off and turns on.
It will prompt you, hit vol up.
Now go back into Odin and hit BL again, and find TWRP recovery.
Hit start and it will, once again start your device normally.
Your device is now fixed. Don't believe me? Power off and power it back on. It will boot normally.
For more experienced people that just want the basics of what to do:
Flash TrapKernel if you haven't already.
Flash Stock Recovery (By itself), then flash TWRP Recovery(By itself).
Your problem should be solved.
Have any problems or think I didn't explain this good enough? Tell me. I am open to constructive criticism.
Very important root necessity
very important root necessity before you try to root your phone you must go to the developers options and check the "device to allow OEM bootloader unlock"this way it can allow the bootloader to be unlocked and you can then gain root. Sincerely Bricked for days.
Your sir are a savior
I'm sorry if I come off as crazy. BUT THANK YOU SO FREAKING MUCH. I just got done typing out a lengthy reply in the rom's forum about the "Device reboots into recovery" issue. I wish I had read around for your reply. Jesus man, you saved my bacon. I will like your post. Both of them.
Related
I'm not sure if this is a "brick". I'm abel to get into recovery but anytime I try to boot, it just stays in the 4GLTE flash screen forever. I had successfully rooted it and loaded CM10, but then it failed the last nightly I loaded and told me I had unauthorized software, and now this...
I just tried going back to stock, but it doesn't help. The flash seems to work, but I get the same problem.
I'm seriously sad right now
mariod505 said:
I'm not sure if this is a "brick". I'm abel to get into recovery but anytime I try to boot, it just stays in the 4GLTE flash screen forever. I had successfully rooted it and loaded CM10, but then it failed the last nightly I loaded and told me I had unauthorized software, and now this...
I'm seriously sad right now
Click to expand...
Click to collapse
Click link in sig...start with section 2 going back to stock , then root, then UNLOCK BOOTLOADER! Now you can flash cm10.
droidstyle said:
Click link in sig...start with section 2 going back to stock , then root, then UNLOCK BOOTLOADER! Now you can flash cm10.
Click to expand...
Click to collapse
When I reboot into recovery (which is actually becoming tricky now - as I need to quickly hit up-volume before it normal boots), I don't see any options for wipe/factory reset. I do see the green 2D android though... but there are no options. I'm just in ODIN mode.
mariod505 said:
When I reboot into recovery (which is actually becoming tricky now - as I need to quickly hit up-volume before it normal boots), I don't see any options for wipe/factory reset. I do see the green 2D android though... but there are no options. I'm just in ODIN mode.
Click to expand...
Click to collapse
"ODIN mode" is download mode (with the 2D android background), not "recovery mode" (with a different, 3D android). In step 3, you held home+vol down+power to enter download mode, then pressed vol up to confirm. In step 8, you're going into recovery by holding home+vol up+power.
You don't have to be fast; just press the power button last and hold it until you get into recovery or download.
---
The reason you got the "unauthorized software" error was that you didn't unlock your bootloader. You should do more reading to prevent soft bricks like this in the future. Next time, root your phone, unlock the bootloader, flash a custom recovery, reboot into recovery, and make a backup(!) before trying to install a ROM. :good:
lazarus2405 said:
"ODIN mode" is download mode (with the 2D android background), not "recovery mode" (with a different, 3D android). In step 3, you held home+vol down+power to enter download mode, then pressed vol up to confirm. In step 8, you're going into recovery by holding home+vol up+power.
You don't have to be fast; just press the power button last and hold it until you get into recovery or download.
---
The reason you got the "unauthorized software" error was that you didn't unlock your bootloader. You should do more reading to prevent soft bricks like this in the future. Next time, root your phone, unlock the bootloader, flash a custom recovery, reboot into recovery, and make a backup(!) before trying to install a ROM. :good:
Click to expand...
Click to collapse
When I try that, it starts to go into recovery mode (and I see the 3D android), but then it boots up normally and hangs at the 4G LTE screen.
The background to this issue is that I used the Guide you linked to root (prior to bootloader being avail), and had CM10 installed. Everything was great and functional until I tried installing This issue has materialized after installed the privacy app (forget the name) which needed root and started cycle rebooting the phone. So I went to flash the latest CM10 nightly, only to hit this issue.
I never flashed the kernel - figured rooting through the initial work around the community had, would have been sufficient in perpetuity... oops
mariod505 said:
When I try that, it starts to go into recovery mode (and I see the 3D android), but then it boots up normally and hangs at the 4G LTE screen.
The background to this issue is that I used the Guide you linked to root (prior to bootloader being avail), and had CM10 installed. Everything was great and functional until I tried installing This issue has materialized after installed the privacy app (forget the name) which needed root and started cycle rebooting the phone. So I went to flash the latest CM10 nightly, only to hit this issue.
I never flashed the kernel - figured rooting through the initial work around the community had, would have been sufficient in perpetuity... oops
Click to expand...
Click to collapse
UPDATE: I was able to get into recovery (the combo button timing is definitely more sensitive than before. ...and now it's booted up normally. THANK YOU!
I have a Xoom WiFi on Android 4.1.2
I was trying to Unlock, Flash Recovery, Root and then Flash a Rom. I have Flashed on my phone a couple of times so I am a little familiar with the process.
I did the following:
1.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
2.
adb reboot bootloader
fastboot flash recovery "name of file".img. (the file i used was "recovery-clockwork-touch-6.0.3.1-wingray.img").
3.
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
This is where things go wrong.
Upon reboot,
I press down volume upon seeing the logo.
It then says Android Recovery.
I then press up volume.
then it says entering Android Recovery Mode
reading ODM Fuse:1
Then the Green Android man shows up with the red triangle.
It sits there for a while then boots into Android normally.
I have been searching for a solution since this morning. Everything I found about this has not helped.
Earlier in the day I did Flash a different Recovery so I think I have two. I installed the ROM manger app. It shows two installed.
ClockworkMod Recovery
Team Win Recovery Project (TWRP)
I am stuck as to what to do... Please help.
Thanks
Jim
jbfoster said:
I have a Xoom WiFi on Android 4.1.2
I was trying to Unlock, Flash Recovery, Root and then Flash a Rom. I have Flashed on my phone a couple of times so I am a little familiar with the process.
I did the following:
1.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
2.
adb reboot bootloader
fastboot flash recovery "name of file".img. (the file i used was "recovery-clockwork-touch-6.0.3.1-wingray.img").
3.
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
This is where things go wrong.
Upon reboot,
I press down volume upon seeing the logo.
It then says Android Recovery.
I then press up volume.
then it says entering Android Recovery Mode
reading ODM Fuse:1
Then the Green Android man shows up with the red triangle.
It sits there for a while then boots into Android normally.
I have been searching for a solution since this morning. Everything I found about this has not helped.
Earlier in the day I did Flash a different Recovery so I think I have two. I installed the ROM manger app. It shows two installed.
ClockworkMod Recovery
Team Win Recovery Project (TWRP)
I am stuck as to what to do... Please help.
Thanks
Jim
Click to expand...
Click to collapse
Please follow the Root Method mentioned in the 2nd Post of LAIOT thread . You can easily find it within the Development Forum , or my signature.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
One of the files link is broken.
The requested URL /atftas/OEM/Motorola/XOOM/Xoom-Universal-Root.zip2 was not found on this server.
I have another problem.
Now I have two devices. If I unplug the Xoom it still finds emulator 5554. What is emulator 5554?
Thanks
Jim
I got around the emulator 5554 problem by using the -d option. I followed everything and all went fine. I installed the app Root Checker Basic but it says Sorry! this device does not have proper root access.
All steps completed with no errors.
I guess I'm stuck again.
Jim
I flashed back to stock. Did all the steps again and the same thing.
I tried several more times and it still would not work.
I went to another site and downloaded the root.zip and it worked this time. The root file on this site would not work for for some reason.
The Android man with the red triangle problem is also gone. Not sure what fixed it. I assume that it was because I flashed back to stock and used a different root.zip file.
Thanks for all the help
Jim
Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.
rspilot1 said:
Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.
Click to expand...
Click to collapse
Hi. What recovery are you using?
If you haven't installed a custom recovery, then that explains your issue. Basically, the app scheduled a custom recovery script which kept failing in the stock recovery. You should normally be able to reboot into the system holding the power button, thus skipping going to recovery. This also resets the recovery script so everything is back to normal.
Nandroid is normally only possible using a custom recovery like TWRP or CWM.
I saw that you might be able to perform a Nandroid without restarting the phone (so without a custom recovery) using this app: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en
I have never tried it. Looks promising though.
But please note that you won't be able to restore the backup without a custom recovery.
EDIT: If you do have a custom recovery, why not boot in recovery mode and make the backup from there?
Cheers
Recovery Boot Loop Problem
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.
rspilot1 said:
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.
Click to expand...
Click to collapse
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505
Recovery Boot Loop Problem
andreiav said:
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505
Click to expand...
Click to collapse
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks
rspilot1 said:
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks
Click to expand...
Click to collapse
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505
Recovery Boot Loop Problem
andreiav said:
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505
Click to expand...
Click to collapse
Thank you, that answered some questions.
you've been a great help.
Recovery Boot Loop Problem
rspilot1 said:
Thank you, that answered some questions.
you've been a great help.
Click to expand...
Click to collapse
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.
rspilot1 said:
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.
Click to expand...
Click to collapse
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers
Recovery Boot Loop Problem
andreiav said:
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers
Click to expand...
Click to collapse
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.
Recovery Boot Loop Problem
rspilot1 said:
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.
Click to expand...
Click to collapse
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?
rspilot1 said:
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?
Click to expand...
Click to collapse
Yep. 5 minutes process at most
Sent from my GT-I9505
Recovery Boot Loop Problem
andreiav said:
Yep. 5 minutes process at most
Sent from my GT-I9505
Click to expand...
Click to collapse
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.
rspilot1 said:
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.
Click to expand...
Click to collapse
Awesome! Really glad it worked.
Cheers!
Sent from my GT-I9505
Hello, I bought a OnePlus one (came with CM11 - 4.4.4) and followed the standard steps to root it
1) unlock bootloader - successful, phone got factory reset, checked the status using fastboot
2) Flash custom recovery (TWRP) using fastboot - always "okay" message
3) The phone DOES NOT boot to recovery after this - it gets stuck at the 1+ logo, or remains stuck for a few seconds and goes to normal reboot. -I've tried using fastboot to reboot phone while holding down volume button
Please help! i've look this problem up and haven't found a solution.
I tried 2.7.0.0, and the latest 2.8.5.1, along with 2.8.6.0, along with trying to use the one plus tool kit. Using the toolkit, even flashing the stock recovery, then booting it didn't work.
after you flash recovery in fastboot, do not issue the fastboot reboot command. you need to manually power off the phone by keeping the power button pressed till it powers off
kenboyles72 said:
after you flash recovery in fastboot, do not issue the fastboot reboot command. you need to manually power off the phone by keeping the power button pressed till it powers off
Click to expand...
Click to collapse
I tried this, same result
ak14523 said:
I tried this, same result
Click to expand...
Click to collapse
As the other posted mentioned you have to fastboot flash twrp (2.8.6.0) then power off phone and use volume down + power button combo to get to recovery. Its flashing but if you boot to OS it will be overwritten by CM recovery hence booting directly will alleviate that
Boot into os, enable dev options by tapping the build number a bunch of times in settings-about phone section, go back and go into settings-developer options, make sure "update cyanogen recovery" is unchecked. Flash recovery again, and like people have said, power off the phone and use volume down and power buttons together to boot into recovery.
Thanks for the quick replies guys. I have tried all the above s and none of them have worked
Should I try unlocking the bootloader again?
I recommend going to this guide and following it closely: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
As for which version of TWRP to use, I recommend this version: https://www.androidfilehost.com/?fid=24391638059059048
I've been trying to flash TWRP onto my Galaxy S3 and my Galaxy S9 for a few days now, and every time I try to do so, it flashes successfully, but then boots into stock Samsung recovery when entering recovery mode. I've used Odin on Windows and Heimdall on Linux, but both have the same issue. I tried different versions of TWRP as well.
If it helps, I'm pretty sure both phones are OEM unlocked. The S9 has the option in developer options, and says it it unlocked in download mode. The S3 doesn't have any option for this, and doesn't say anything in download mode about it.
Even though the S3 might not be OEM unlocked, it still doesn't explain the issue with the S9.
I'm also dual booting, so all attempts were from the same computer. It might be some issue with my computer, but I really don't have access to another one right now, so I was wondering if anyone had any other ideas or thoughts on the issue. Any help would be appreciated.
Did you check this?
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
https://twrp.me/samsung/samsunggalaxys3internationalexynos.html
I think for S3 it's
Vol up + Home + Power
Basically:
1. Flashing
2. Reboot into Recovery by keep pressing Vol up + Home + Power
3. Allow TWRP to become permanent
Perhaps you want to check/re-ask here as well:
https://forum.xda-developers.com/c/samsung-galaxy-s-iii-i9300-i9305.1563/
SigmundDroid said:
Did you check this?
https://twrp.me/samsung/samsunggalaxys3internationalexynos.html
I think for S3 it's
Vol up + Home + Power
Basically:
1. Flashing
2. Reboot into Recovery by keep pressing Vol up + Home + Power
3. Allow TWRP to become permanent
Perhaps you want to check/re-ask here as well:
https://forum.xda-developers.com/c/samsung-galaxy-s-iii-i9300-i9305.1563/
Click to expand...
Click to collapse
Holding the given buttons just brings me to default recovery, so I'm not sure what the proper recovery is. I've also tried Volume Up + Down + Home + Power.
Hmm, didn't flash an S3 for quite some time but I vaguely remember that I had similar problems during
"After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted"
and often missed or was too clumsy, too late or both
Would in fastboot the command
fastboot reboot recovery
work for you? Or does it still end up in stock recovery?
Perhaps it's really time to check in the s3 threads for further advice?
SigmundDroid said:
Hmm, didn't flash an S3 for quite some time but I vaguely remember that I had similar problems during
"After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted"
and often missed or was too clumsy, too late or both
Would in fastboot the command
fastboot reboot recovery
work for you? Or does it still end up in stock recovery?
Perhaps it's really time to check in the s3 threads for further advice?
Click to expand...
Click to collapse
Okay so turns out I needed to boot into recovery immediately after flashing TWRP on both phones because when booting into the system, the recovery is replaced. After doing this, everything worked fine and I was able to get custom ROMs working! I appreciate your help though