Related
I was trying to install one of drewgarens touchwiz roms. touchwiz milestone 5 firefly i believe. not the most recent one because i was too lazy . boy was that a mistake. everything was going smoothly until it booted and it got stuck on boot. I thought no big deal just go into recovery and use a backup. until i did so and recovery was gone and there was only download mode. I have spent the whole afternoon trying to fix it and none of it has worked. I tried flashing the stock rom and it as well got stuck on boot. I looked at all the AT&t relevant ones and also the international versions. so all in all is there anyway to fix this and has anyone had the same issue? i was flashing from cyanogenmod 10 m1 to the drewgaren rom btw. I can also go to download mode. I tried to flash stock but it still gets stuck on boot. log. I flashed the ATT boot logo and it did not work. all of which were flashed through odin.
any thanks in advance is greatly appreciated.
I think you can flash back to stock with just download mode + odin
Randomacts said:
I think you can flash back to stock with just download mode + odin
Click to expand...
Click to collapse
I already tried that. It still get stuck on the Boot logo
stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
I can't help you but I wish you luck.
stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
Unplug your device. Hold the power button to turn it off. Hold volume up, home, and power. It should go to recovery. If you do the same thing with volume down instead of up, you can get into download mode.
Sent from my SAMSUNG-SGH-I747 using xda premium
Sounds like you need a recovery...try this
http://forum.xda-developers.com/showthread.php?t=1746665
[SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]
Follow the instructions and you should be able to flash the recovery and continue on with what you were doing. Remember to wipe really good when going from aosp back to any stock based ROM. They are completely different and will cause boot loops if you don't wipe.
jethro650 said:
Sounds like you need a recovery...try this
http://forum.xda-developers.com/showthread.php?t=1746665
[SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]
Follow the instructions and you should be able to flash the recovery and continue on with what you were doing. Remember to wipe really good when going from aosp back to any stock based ROM. They are completely different and will cause boot loops if you don't wipe.
Click to expand...
Click to collapse
I cannot enable usb debugging
Crap...there are Odin flashable versions of cwm floating around you'll need to find one of those. If you haven't found one I'll post one up when I get home.
jethro650 said:
Crap...there are Odin flashable versions of cwm floating around you'll need to find one of those. If you haven't found one I'll post one up when I get home.
Click to expand...
Click to collapse
K I made it home lol. I'll attach a Odin flashable cwm, it's an older one but it'll get you a recovery, I hope. I just tried it on my phone with Odin, 3.07 both with usb debugging enabled and disabled on my phone and it worked both times. Crap keep getting errors uploading right to xda servers, I'll drop box it in a minute.
Ok here we go Odin cwm--> https://dl.dropbox.com/u/28590257/Odin recovery/CWM-Recovery-LTE-SGS3-v4.tar.md5
Newest twrp --> https://dl.dropbox.com/u/28590257/Odin recovery/twrp2.3.1install.zip
I'll add the newest twrp for you lol. Flash the cwm with odin, should work and then the twrp is a zip you can flash in cwm.
Hope this helps get you a recovery.
Remember in Odin use only PDA and only have auto reboot checked.
jethro650 said:
K I made it home lol. I'll attach a Odin flashable cwm, it's an older one but it'll get you a recovery, I hope. I just tried it on my phone with Odin, 3.07 both with usb debugging enabled and disabled on my phone and it worked both times. Crap keep getting errors uploading right to xda servers, I'll drop box it in a minute.
I'll add the newest twrp for you lol. Flash the cwm with odin, should work and then the twrp is a zip you can flash in cwm.
Hope this helps get you a recovery.
Remember in Odin use only PDA and only have auto reboot checked.
Click to expand...
Click to collapse
This may sound like a stupid question but what boxes do i tick in odin?
After your hooked up and Odin is open under the options on the left side check only Auto Reboot. On the right under files check PDA and use that button to browse your computer and find the cwm you downloaded from my dropbox. Then just hit start on the bottom of the Odin window and let it finish, your phone should reboot when its done. It will get stuck again like you described in your first post but pull the battery, put it back in and boot into recovery using vol up,home and power buttons. That should (if everything flashed OK) put you into cwm 5.5.0.4. Once there wipe data/factory reset then restore the back up you mentioned in your original post, that should get you running again.
---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------
If something has happened to your backup then you could try the stock rooted stuff here , just pick the one for your carrier and follow the instructions. :highfive:
jethro650 said:
After your hooked up and Odin is open under the options on the left side check only Auto Reboot. On the right under files check PDA and use that button to browse your computer and find the cwm you downloaded from my dropbox. Then just hit start on the bottom of the Odin window and let it finish, your phone should reboot when its done. It will get stuck again like you described in your first post but pull the battery, put it back in and boot into recovery using vol up,home and power buttons. That should (if everything flashed OK) put you into cwm 5.5.0.4. Once there wipe data/factory reset then restore the back up you mentioned in your original post, that should get you running again.
---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------
If something has happened to your backup then you could try the stock rooted stuff here , just pick the one for your carrier and follow the instructions. :highfive:
Click to expand...
Click to collapse
I was able to get it into recovery but i realized i did not have my sd card in so i turned it off and put my sd card in. unfortunately i was not able to get it back into recovery i tried flashing it again with the sd card in and no luck
That's odd. Couple of stupid questions on my part just to make sure, you had the right button combo, and, you released the buttons soon as the splash screen came on? Can you still get into download mode? Oh and did you do the wipes while in recovery?
jethro650 said:
That's odd. Couple of stupid questions on my part just to make sure, you had the right button combo, and, you released the buttons soon as the splash screen came on? Can you still get into download mode? Oh and did you do the wipes while in recovery?
Click to expand...
Click to collapse
oh my gosh THANK YOU SOOOMUCH. I was worried i would have to take it to at&t ill be sure to press the thanks button.
I take it you got your phone working lol. Glad I could help a little. Little advice, anytime you switch to a different type of ROM (aosp to stock based or the other way around) make sure you wipe data/factory reset before flashing anything. It will save you problems in the long run.
Oh and could you go back and edit your original post and just add solved in brackets to the title for people in trouble looking for info.
stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
Depending on which stock ROM you flashed with odin you should now have a recovery, if not then something isn't right. The full bone stock ROM should have the factory 3e recovery, and the root injected stock ROM should have some version of CWM recovery. A factory reset will most likely fix your boot loop, if there is no recovery flash the rooted stock ROM that matches your device from this guide.
Edit - Didn't see there was a second page 0_o
situation...
-flashed the phone using odin pc
-installed clockwork recovery using rom manager pro app on phone
-flashed 'cleanrom' onto phone didn't like it so flash another rom 'jedi x'
-didn't clean/wipe data before flashing it
-flashed 'jedi x' then the phone restarted
-didn't finish restart, stuck in bootloop...
tried to reflash CWM6 onto my phone using download mode and pc odin didn't get pass bootscreen 'samsung' logo
tried to enter recovery mode by holding vol up + home + power... can't get access to recovery mode....
desperately need help... please help!!!
try wiping... 2 different roms won't pay nice if you don't wipe
Sent from my SPH-L900 using xda app-developers app
I'm actually in the exact same situation. I was simply transferring music to my phone when it went into this boot loop. I've tried using ODIN to flash every possible ROM I've been able to find.
Desperately in need of help.
How exactly do I perform a "wipe"?
1. Can you guys get into Download and or Recovery mode?
2. If recovery is available, did you back up? If so, restore or flash back to original Rom.
3. If you can get into Download mode, flash back to a stock Rom, and start fresh.
Might sound obvious, just trying to help. I've learned that often I thought the phone was "done", but after refusing to give up on it, it came back to life...
Just keep trying , sounds recoverable for both.
---------- Post added at 10:07 PM ---------- Previous post was at 10:01 PM ----------
QuantumPSI said:
I'm actually in the exact same situation. I was simply transferring music to my phone when it went into this boot loop. I've tried using ODIN to flash every possible ROM I've been able to find.
Desperately in need of help.
How exactly do I perform a "wipe"?
Click to expand...
Click to collapse
You can wipe by getting into recovery. Wipe Data, cache, dalvik cache.
I can only get into download mode and I've tried to flash to stock ROM SEVERAL times now to no avail.
I've noticed that the binary counter isn't going up after each attempt though...
QuantumPSI said:
I can only get into download mode and I've tried to flash to stock ROM SEVERAL times now to no avail.
I've noticed that the binary counter isn't going up after each attempt though...
Click to expand...
Click to collapse
So, does odin say- succeeded or failed or do nothing when you flash?
Says succeeded every single time.
QuantumPSI said:
Says succeeded every single time.
Click to expand...
Click to collapse
Were you on LK8 or LJC ? No recovery?
LJC, and no, no recovery
QuantumPSI said:
LJC, and no, no recovery
Click to expand...
Click to collapse
Not even stock recovery? - power + home key + vol up ?
never gets to that menu... just reboots
QuantumPSI said:
never gets to that menu... just reboots
Click to expand...
Click to collapse
Well, all I can say is keep trying or a hammer. It's bound to work once... Sorry but I dont know what else to tell ya.
Good luck with it!
Hmm, there really doesn't seem to be a solution to this. Any possible way to "fastboot" it?
Anyone know where I can find a PIT file?
Install latest TWRP once rooted, I have a separate thread about how to root your device.
1. Download latest twrp from here http://techerrata.com/browse/twrp2/d851
2. Download Flashify (for root users) from play store
3. Open flashify select recovery file you downloaded then flash it to your device. Done
(Boot into recovery menu when device is powered off)
1. Hold volume down and power button simultaneously
2. Soon as LG logo appears immediately let go of both volume down and home button
3. Repeat step one right after step 2
You will be asked to factory reset your device SELECT YES BOTH TIMES and you should boot right into recovery menu.
Done
Thanks for the guide bit it does not work.
I did as you have explained, flashed the twrp image but it does not go to recovery mode after pressing volume down plus power butto. It turns on normally..??
How do i know if the twrp is properly installed??
Omarley01 said:
Install latest TWRP once rooted, I have a separate thread about how to root your device.
(Boot into recovery menu when device is powered off)
1. Hold volume down and power button simultaneously
2. Soon as LG logo appears immediately let go of both volume down and home button
3. Repeat step one right after step 2
You will be asked to factory reset your device SELECT YES BOTH TIMES and you should boot right into recovery menu.
Done
Click to expand...
Click to collapse
askfriends said:
Thanks for the guide bit it does not work.
I did as you have explained, flashed the twrp image but it does not go to recovery mode after pressing volume down plus power butto. It turns on normally..??
How do i know if the twrp is properly installed??
Click to expand...
Click to collapse
If at first you don't succeed, try ... try again. You are probably not timing the second press correctly.
mitbit2k3 said:
If at first you don't succeed, try ... try again. You are probably not timing the second press correctly.
Click to expand...
Click to collapse
i tried but to no success.
when i see lg logo i let go both buttons, then immedietely i pressed both buttons, but it boots normally...??:silly:
Edit: after i press yes, all my data will be lost??
askfriends said:
i tried but to no success.
when i see lg logo i let go both buttons, then immedietely i pressed both buttons, but it boots normally...??:silly:
Edit: after i press yes, all my data will be lost??
Click to expand...
Click to collapse
No data will be lost. "Yes" twice and you should be in TWRP.
mitbit2k3 said:
No data will be lost. "Yes" twice and you should be in TWRP.
Click to expand...
Click to collapse
YES I MADE IT.. THANK YOU SO MUCH.:good:
PLEASE MENTION THIS IN YOUR GUIDE THAN ONE HAVE TO PRESS THE SAME BUTTONS AGAIN "IMMEDIETELY" AFTER SEEING LG LOGO.
This only works if you have the play store (and thus GAPPS) installed. I however do not.
You should modify the title to reflect that.
Will this work on lollipop?
Sent from my LG-D851 using XDA Free mobile app
Regnuf said:
Will this work on lollipop?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Great work on this TWRP. Works great on LP also after using a bumped boot.img and kk aboot also. Anyway to speed up backup's? Seems like over 10 minutes+ to backup to SD Card.
---------- Post added at 12:29 PM ---------- Previous post was at 11:46 AM ----------
Ok, tried my first backup restore on TWRP from SD Card and it failed! Hmm. Anybody else have a successful restore? Just got my G3 so this is the first TWRP I've tried. Send you a PM OP.
---------- Post added at 12:48 PM ---------- Previous post was at 12:29 PM ----------
Tried TEAMWin's TWRP and backup restore failed also. Must have been a bad backup. Gonna try backup again with TeamWin's and restore and see what happens.
this link from the stock rom thread points to a version 2.8.6.1 which is newer than everything in the OP link
https://docs.google.com/file/d/0BxgcaWaR5dRTZExOQnZGWV91U3M/edit?pli=1
is this the right one to use?
what are the steps to go back to no twerp and no root and back to oem phone?
on my g2 I would go to factory reset in the setting and it would only boot into recovery mode..
I just searched for TeamWin TWRP and D851. Got a link to here: http://teamw.in/project/twrp2/249/ Seems twrp-2.8.7.0-d851.img is latest.
Update: I was trying to find a safe way to update TWRP and went back to the below site. The instructions now say to update with TWRP Manager. It worked flawlessly.
http://teamw.in/project/twrp2/249/
Install TWRP Manager. Tap on Install TWRP. Select your device from the device list (d851) and then tap on Install Recovery. The file will download and be installed automatically.
Hi guys,
could anyone please help, I've been playing around quite a lot with rooting and flashing, but now I'm stuck with a problem I can't solve...
Device
Galaxy Tab S 8.4 WIFI (SM-T700 klimtwifi)
Starting point
Flashed CM12 , with CF root and TWRP
Everything ok, but had some trouble with wifi and root, so I wanted to flash a new rom.
Problem
Tried flashing another rom (can't remember if it was AROMA or BlissPop...), but the flashing got stuck.
Now I can only access Download-mode, not Recovery and normal boot gets stuck in the white Samsung-logo, I get past first screen and some other Samsung-animation.
What I've tried
Access to Recovery, not working (I have a stock-backup on internal SD)
Flashed stock image via Odin (T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5). Should be on right now, but no change in working.
Re-flash TWRP via Odin (tar-file)
Have I missed something? Any problem with going back and forth between Android 4 and 5?
F-B said:
Hi guys,
could anyone please help, I've been playing around quite a lot with rooting and flashing, but now I'm stuck with a problem I can't solve...
Device
Galaxy Tab S 8.4 WIFI (SM-T700 klimtwifi)
Starting point
Flashed CM12 , with CF root and TWRP
Everything ok, but had some trouble with wifi and root, so I wanted to flash a new rom.
Problem
Tried flashing another rom (can't remember if it was AROMA or BlissPop...), but the flashing got stuck.
Now I can only access Download-mode, not Recovery and normal boot gets stuck in the white Samsung-logo, I get past first screen and some other Samsung-animation.
What I've tried
Access to Recovery, not working (I have a stock-backup on internal SD)
Flashed stock image via Odin (T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5). Should be on right now, but no change in working.
Re-flash TWRP via Odin (tar-file)
Have I missed something? Any problem with going back and forth between Android 4 and 5?
Click to expand...
Click to collapse
After flashing the stock image, factory reset in recovery again.
But I can't get into recovery, even after flashing stock...
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
F-B said:
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
Click to expand...
Click to collapse
Sounds like one of the partitions is damaged, its strange because when you flash the stock firmware it relays all the partitions, just to verify you downloaded one of the big factory images from sammobile.com that's 1.6gb big, then flashed with Odin the extracted tar file...also you might not have a custom recovery installed if you have so vol up and home n power wouldn't work......
Maybe your way out of this is going the other way, flash a custom recovery through Odin, then get into that and use it to install ironrom which is like stock but cleaner.
F-B said:
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
Click to expand...
Click to collapse
Try pressing power +vol down and up together+home and then as soon as screen goes dark/black press power+vol up+home hopefully that will get you into recovery.
Have you edited to vold.fstab file
---------- Post added at 01:15 PM ---------- Previous post was at 01:07 PM ----------
If you have edited the vold.fstab file then try to flash a stock rom via odin with the pit file of your device.
F-B said:
But I can't get into recovery, even after flashing stock...
Click to expand...
Click to collapse
Just to elaborate when flashing stock through Odin it wipes your custom recovery and root...hence why you need to use auto root again through Odin.
Cheers guys for your inputs! I'll only get my hands on the tab this evening, so I'll test your solutions then and report back-
maxal said:
Try pressing power +vol down+home and then as soon as screen goes dark/black (just before you enter download mode) press power+vol up+home hopefully that will get you into recovery.
Click to expand...
Click to collapse
Thanks, have to try this!
pdolton2000 said:
Sounds like one of the partitions is damaged, its strange because when you flash the stock firmware it relays all the partitions, just to verify you downloaded one of the big factory images from sammobile.com that's 1.6gb big, then flashed with Odin the extracted tar file...also you might not have a custom recovery installed if you have so vol up and home n power wouldn't work......
Maybe your way out of this is going the other way, flash a custom recovery through Odin, then get into that and use it to install ironrom which is like stock but cleaner.
Click to expand...
Click to collapse
Yeah, flashed T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5 2,4gb
Tried flasing TWRP, no difference. Maybe here's the timing as well...
max86533 said:
Have you edited to vold.fstab file
---------- Post added at 01:15 PM ---------- Previous post was at 01:07 PM ----------
If you have edited the vold.fstab file then try to flash a stock rom via odin with the pit file of your device.
Click to expand...
Click to collapse
No clue about vold.fstab, so I seriously hope I haven't edited it
pdolton2000 said:
Just to elaborate when flashing stock through Odin it wipes your custom recovery and root...hence why you need to use auto root again through Odin.
Click to expand...
Click to collapse
Yeah, have to make sure I have done it in right order, Stock -> Root -> Custom Recovery... I've tried so many solutions that I'm starting to doubt myself.
Unfortunately, I find myself in the same situation, I do not know what to do.
Have you flash pit file via odin because maybe your device partitions corrupt during rooting.
F-B said:
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
Click to expand...
Click to collapse
F-B said:
Cheers guys for your inputs! I'll only get my hands on the tab this evening, so I'll test your solutions then and report back-
Thanks, have to try this!
Yeah, flashed T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5 2,4gb
Tried flasing TWRP, no difference. Maybe here's the timing as well...
No clue about vold.fstab, so I seriously hope I haven't edited it
Yeah, have to make sure I have done it in right order, Stock -> Root -> Custom Recovery... I've tried so many solutions that I'm starting to doubt myself.
Click to expand...
Click to collapse
Hi just to add I have just edited the instructions I gave you please read again.
F-B said:
Cheers guys for your inputs! I'll only get my hands on the tab this evening, so I'll test your solutions then and report back-
Thanks, have to try this!
Yeah, flashed T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5 2,4gb
Tried flasing TWRP, no difference. Maybe here's the timing as well...
No clue about vold.fstab, so I seriously hope I haven't edited it
Yeah, have to make sure I have done it in right order, Stock -> Root -> Custom Recovery... I've tried so many solutions that I'm starting to doubt myself.
Click to expand...
Click to collapse
Okay sounds like you've hit a dead end but don't panic your not the first to hit this point with t700.
Okay here's what I want you to do,
1. Open up device manager and completely remove your adb driver making sure to check the "also delete driver " box if shown
2. Download this http://developer.android.com/sdk/win-usb.html the latest Google adb drivers ..DL this ready actually.
3. Completely disable anti virus..remove if you have to, along with windows defender .
4. Restart
5. Download "i know it seems mad" the austrailian firmware http://www.sammobile.com/firmwares/download/43233/T700XXU1ANL1_T700XSA1AOA1_XSA/ and extract the file inside the archieve
6. Right click Odin and run as administrator to be safe.
7. Go for gold and try this...if it works your laughing and can change the firmware or ROM to any local area.
8. If...this doesn't work...restart one last time n try again, if still no then try using another laptop or PC if you can
Good luck keep me updated...I am trying to find you another solution too, got an idea with something called heimdall but not sure as never used it, supposed to be an alternative to Odin.
Hi All, finally had the time to sit down and test your solutions. As it happens, the first (easiest) thing I tried was the timing in pushing recovery boot, according to great help of Maxal. Worked on first attempt, booted into stock recovery, wiped everything and stock rom booted. I was prepared to do it all, so it was funny that a few well-timed presses of buttons solved it .
Now I'm rooted with TWRP and BlissPop again. Thanks everyone for great suggestions and assistance!
I also solved, it was enough to wait for the battery becomes exhausted, recharge the tablet and once off from entering recovery and do a factory reset.
The system is restarted.
maxal said:
Try pressing power +vol down and up together+home and then as soon as screen goes dark/black press power+vol up+home hopefully that will get you into recovery.
Click to expand...
Click to collapse
Man, you're genius! Thanks!
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Wrong section
Hacker101 said:
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Click to expand...
Click to collapse
So you have tried booting into the bootloader and entered "fastboot boot twrp.img" in adb?
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Alcolawl said:
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Click to expand...
Click to collapse
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Hacker101 said:
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Click to expand...
Click to collapse
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
TheBobMiller said:
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
Click to expand...
Click to collapse
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Hacker101 said:
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Click to expand...
Click to collapse
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
TheBobMiller said:
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
Click to expand...
Click to collapse
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
Don't worry about the Thanks, cause I'm sure others have contributed more. Sorry I'm not more familiar with the Linux instructions!
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
TheBobMiller said:
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
Click to expand...
Click to collapse
Yes I was on May.. Do you have link to Verified Signer?
jkashuba07 said:
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Yes I was on May.. Do you have link to Verified Signer?
Click to expand...
Click to collapse
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
Thank you, and will do.. yes chainfire has done a lot of good work, definitely have appreciated him over the years
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Hacker101 said:
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Click to expand...
Click to collapse
Correct. Only the may bootloader requires the extra zip file to be flashed. I am still on April but I have heard people not having any problems and some having nothing but problems from May. I think I'm going to give it a try tomorrow and see how it goes.
Edit: Tried the May bootloader and couldn't get it to boot a custom rom or TWRP, so I went back to April after flashing the Android O Beta and playing with it for a couple of hours. I feel that the Beta is still too early for a daily driver, but it was nice to mess around with some of the features we will have once this OS is released.