Related
Howdy guys,
First off, I've Google'd everything and searched everywhere. I've gone through 5 generations of Android phones, rooting every one of them. Got a Nexus 4 now. This problem is with my N10 (obviously).
I tried using mskip's toolkit (v2.0.0, option 8) to do a full unlock, root, etc. I get to the part where it's trying to boot into recovery, and fastboot just hangs on my laptop. On the tablet it says (highlighted in cyan) "FASTBOOT STATUS - DATA00625800"
Above that, is all of the usual info, which I'll post here in case it helps:
PRODUCT NAME: manta
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION: MANTALJ12
CARRIER INFO: NONE
SERIAL NUMBER: A3201042***
LOCK STATE: UNLOCKED
REBOOT MODE FLAG: NONE
The device is unlocked. I've tried relocking and unlocking again.
I tried manually flashing the recovery (both CM & TWRP), and also tried booting to both of those (fastboot boot recovery.img).
Each combination gives a slightly different STATUS code.
Oh, I can get into the stock recovery. I also tried sideloading a rooted ROM. Gets to 31% and hangs.
I think I got everything written here, might have missed something obvious.
Ideas/help?
downloader123 said:
Howdy guys,
First off, I've Google'd everything and searched everywhere. I've gone through 5 generations of Android phones, rooting every one of them. Got a Nexus 4 now. This problem is with my N10 (obviously).
I tried using mskip's toolkit (v2.0.0, option 8) to do a full unlock, root, etc. I get to the part where it's trying to boot into recovery, and fastboot just hangs on my laptop. On the tablet it says (highlighted in cyan) "FASTBOOT STATUS - DATA00625800"
Above that, is all of the usual info, which I'll post here in case it helps:
PRODUCT NAME: manta
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION: MANTALJ12
CARRIER INFO: NONE
SERIAL NUMBER: A3201042***
LOCK STATE: UNLOCKED
REBOOT MODE FLAG: NONE
The device is unlocked. I've tried relocking and unlocking again.
I tried manually flashing the recovery (both CM & TWRP), and also tried booting to both of those (fastboot boot recovery.img).
Each combination gives a slightly different STATUS code.
Oh, I can get into the stock recovery. I also tried sideloading a rooted ROM. Gets to 31% and hangs.
I think I got everything written here, might have missed something obvious.
Ideas/help?
Click to expand...
Click to collapse
It's obvious, and you may have tried it, but have you issued adb reboot recovery while you're booted into the operating system?
Yep, I can get into recovery... I just can't flash or boot to a non-stock recovery.
downloader123 said:
Yep, I can get into recovery... I just can't flash or boot to a non-stock recovery.
Click to expand...
Click to collapse
And in-OS solutions like ROM Manager's recovery flash aren't working either for you?
I don't have root because I can't flash any zips (stock recovery doesn't let you do anything except Google .zips right?)
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
GedBlake said:
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi guys, I actually encountered this problem a minute ago when I attempt to flash a new version of TWRP recovery on my grouper. Whenever I go to the recovery, it just shows 'No command' with a red alert of Android on it (I started to panic when I found that there's an unusual error that prevents me from entering the recovery and this is the first time that I saw this error on my flashaholic experience *btw my previous recovery was CWM) I'm currently on stock 4.4.2 with an unlocked bootloader. I have no idea what problem is causing to display that issue when attempting to enter recovery but then I left it for like 5-10mins while it's displaying that error and after that the device reboots then it just quickly enter TWRP recovery normally as is :silly: sick of that haha, silly ol grouper jesus -_-
EDIT
After entering recovery, I got stuck forever on bootloader and recovery! whenever I reboot, I always get directly enter to the recovery and it forces me to not to enter the ROM oh my god at least I can still configure the recovery so I can backup and flash another ROM :|
My wife's Nexus 7 is on the 4.13 bootloader. I've tried to change it before to no avail. I tried to use Wug's kit to flash the latest 4.4.2(coming from the 66Y build) but I got the error on the bootloader flash. So everything got wiped but the bootloader and left an empty device. All attempts to flash after that failed to get past the first line(erasing boot), I guess 'cause it was already erased? I flashed the individual img' s(boot, system, etc) and got the Nexus to boot up into kit Kat 4.4.2, but there is this little glitch in between the "google" splash screen and the boot animation where I can see recovery flash for a split second. I want to flash the proper bootloader and redo the process clean, but for the life of me I can't get the bootloader to take. I flash in Wug's, the same way I flashed the other img's, but fastboot screen still shows 4.13. Adb shows connected but says "offline" next to device, which is making the adb reboot command fail(unless I'm done now something else wrong there). Can anyone help? My wife is not pleased.
Sent from my SCH-I535 using Tapatalk
Your wife is displeased because of a momentary flash of the screen while booting? **
Or maybe she's displeased with the idea of you fooling with her tablet and that's the only straw to grasp at?
You need to say exactly what the error is, not "an error occurred". You can cut-n-paste right here into your posts.
Also, you should verify the checksum (e.g. MD5) of the bootloader image file you are attempting to flash to make sure you are really using a valid bootloader file.
(In particular, the one shipped in the KOT49H = 4.4.2 factory image is corrupted)
Note [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Honestly, I would avoid flashing your bootloader unless it was absolutely, positively necessary. It's the riskiest flashing operation that you could possibly perform on your tablet. Unless I missed something, you didn't really indicate anything else was particularly wrong with the tablet.
good luck
** I think I saw a bug report about fleeting screen flashes in KitKat 4.4.2 (you see an "old" screen briefly appear when you are on your way to doing something else; they are quite noticeable because they are "out of sequence"). For instance I've seen my settings screen appear momentarily when I am moving between two running apps. I think I saw this reported as a KitKat bug - not something due to the bootloader.
.
Well, bootloader now says 4.23, but I still get the invalid state error when flashing the latest kit kat img. Is there a way to force request an OTA? The 4.4.2 OTA failed because I was on a custom rom/recovery, but now it seems to say I am up-to-date even if I downgrade. Is there a way to clear the memory or get the OTA to attempt?
How do you flash? Using a toolkit? Fastboot? ADB? On what operating system? What is the error message and at what step does occur?
It's a bit difficult to give suggestions how to solve a problem when one has only little information.
If you have a 4.23 bootloader installed, flashing boot.img and system.img is sufficient to get a running system, I.e.
Fastboot flash boot boot.img
Fastboot flash system system.img
While boot.img and system.img are extracted from the factory image, but without having detailed information ...
Sent from my Nexus 7 using xda app-developers app
I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk
jackdubl said:
I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It may be that the file is corrupt, but it could also mean that your usb port is faulty. Try plugging it in on a different usb port.
First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I thought I mentioned that I couldn't get adb to reboot into the bootloader because device said "offline" so I couldn't run in fastboot. The toolkit lets you flash in fastboot without using adb so that's how I flashed the system and boot. I'll just leave it the way it is. Seems to run fine and no slow charging issue.
Sent from my SCH-I535 using Tapatalk
Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I know that part. But how do you enter the commands after that?
Sent from my SCH-I535 using Tapatalk
So I was running cynogenmod on my nexus 7 2012, and now that lollipop is out, I wanted to do a complete restore of my device and install stock. I first tried a few one click methods, but none of those worked, so I tried using the android sdk to install it through the command prompt. After a long struggle, I gave up and tried to turn my device back on, but it says "booting failed" in the upper right corner, and it doesnt get past the google screen. I can get to fastboot no problem, but I cant get into my recovery(which I am guessing got wiped). When I tried to reinstall stock again, every method i tried got stuck on trying to flash the bootloader. Is my device permanently bricked? If its not how can I fix it? thanks
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
bftb0 said:
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
Click to expand...
Click to collapse
Yea in fastboot it says that the bootloader version is 4.23. Ill try flashing it without the bootloader and see if that works
ok so I tried running the flash-all.bat, and it says archive does not contain boot.sig, and archive.sig. Then, it continues flashing, but after it gets to sending boot, I get an error that says FAILED(data transfer failure (unknown error)). then When I try to do something on the nexus it is frozen, and I have to hold power and volume down to get back into fastboot. Am I missing the boot and archive files?
ok so I reinstalled the android sdk and then flashed the image and it worked. There must have been some files missing or something. Thanks for your help!
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Methods tried - 1-21
*TWRP #IRC*
Boot phone into TWRP, run these commands. You may have to flash factory images one more time if you get stuck at the splash screen (rather than looping)
Enter adb shell then copy and paste these two lines, separately.
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix bootloops for most. TWRP 3.2.1-1 causes a fatal error. The above shell commands should get 'most' running.
-----------------------------------------------------------------------
All methods below are MTC20F unless otherwise stated.
If you notice a method that worked, that I haven't listed please share with me with the source so I can have a full list.
Method 1
Followed instructions on flashing full firmware, found on g.co/ABH
Method 2
Followed instructions for OTA, found on g.co/ABH
Method 3
Followed @Heisenberg instructions in the HOWTO for manually flashing firmware via fastboot
Method 4
Flashed stock firmware, then wiped data/cache in stock recovery
Method 5
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-0
Method 6
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-1
Method 7
Flashed firmware via fastboot, then flashed full stock firmware through twrp (specify which version)
Method 8
Flashed firmware via fastboot, then flashed OTA firmware through twrp (specify which version)
Method 9
Utilized Wugs tool to flash full firmware
Method 10
Flashed firmware via fastboot, then sideload OTA via adb
Method 11
Flashed firmware, then flash your own TWRP backup
Method 12
@Eric214 says
Advanced wipe - System, Data, Cache and Dalvik.
Flash vendor image MTC20F.
Flash PureNexus, Gapps, SuperSu 2.76.
Reboot.
Method 13
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via fastboot
Method 14
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via update.zip
Method 15
@shiftr182 method
Fastboot firmware, flash twrp, repair and resize, flash nougat bootloader, flash nougat update from HERE
Method 16
@neaznc021 method
"I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked"
Method 17
Fastboot stock, flash backup, flash MM ROM
Method 18
@rbouza1 method
"Fastboot format user data partition
Run factory image
Fastboot bootloader radio vendor
Flash twrp
Try and boot if not flash stock rom /any mm rom boot into twrp and try a restore. Those were my steps and it worked"
Method 19
@FragmentsOfLife method
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Method 20 @avivasaf
"Got backup from my friend, you need this!
Format userdata
Flash twrp
Make any backup
Move the good backup to the file backup
Restore it
Flash any Mm rom(i flashed cm13)
Fastboot flash mm bootloader, radio, vendor
And you got it!!!!"
Method 21 @Azhar05 method
flash developer preview 5 and flash latest twrp and then copy mtc 20f vendor image to twrp folder and then in twrp install image mtc 20f
Method 22
Let me know if you have more!
reserve 2
tr4nqui1i7y said:
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Click to expand...
Click to collapse
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
sixgunmojo said:
[/HIDE]
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
Click to expand...
Click to collapse
Thanks, that would be useful. I'm thinking of how to incorporate that in a simple enough way that people don't accidentally provide incorrect information.
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
busbeepbeep said:
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
Click to expand...
Click to collapse
Your device isn't recognized by adb/fastboot?
tr4nqui1i7y said:
Your device isn't recognized by adb/fastboot?
Click to expand...
Click to collapse
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
busbeepbeep said:
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
Click to expand...
Click to collapse
Try this tool to make things a little easier, and more automated for now. Wugs
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
busbeepbeep said:
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
Click to expand...
Click to collapse
Boot into bootloader manually then try to run something
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Eric214 said:
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Click to expand...
Click to collapse
What eMMC is your device using, if you don't mind?
tr4nqui1i7y said:
What eMMC is your device using, if you don't mind?
Click to expand...
Click to collapse
64GB Toshiba
Eric214 said:
64GB Toshiba
Click to expand...
Click to collapse
Just to clarify, you were able to get your device to boot?
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Jammol said:
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Click to expand...
Click to collapse
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
tr4nqui1i7y said:
Just to clarify, you were able to get your device to boot?
Click to expand...
Click to collapse
Originally i had no issues I flashed factory images from Pure Nexus June build Via Fastboot. Rebooted the phone and took the OTA through the phone and then flashed TWRP 3.0.2-1 (the Newest one) and through TWRP flashed SuperSU 2.76 then FDR the phone before setting it up. All was fine and perfect. I made a backup and then factory data reset my phone Saturday and then restrored the backup. No go, Bootloop city. Got home did most of what was mentioned and nothing happened. Flashed PN through TWRP 3.0.2-1 and flashed my stock rom that came with the phone in Feb (29Q) and restored my EFS (I backup my EFS after any Android version change). The phone booted perfectly. no issues since. Took me about 2 hours total once i got home and was able to start using ADB and Fastboot commands.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
Also i forgot to add my info....
BL: 03.58
Baseband: 3.72
Varient: Angler-VN2
CPU: 0x20001
eMMC: 64GB Toshiba
DRAM: 3072MB Samsung LDDR4
UNLOCKED
Qfuse status: ENABLED
Off-mode-charge: Enabled
Download Mode: DISABLED
I also forgot, I was enrolled in the beta program obviously since i took the OTA through the phone.
tr4nqui1i7y said:
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
Click to expand...
Click to collapse
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Jammol said:
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Click to expand...
Click to collapse
Alright, thanks for clarifying. Didn't want to accidentally add something to the second post haha.