I've encountered an unpleasantly unique problem (as far as the internet is concerned) with my Nexus 7.
It started when I wanted to upgrade my Nexus from 4.2.1 to 4.2.2. For whatever reason, the upgrade wouldn't install, gave me an error a quarter of the way through and booted me back into 4.2.1 with no repercussions.
Using WugFresh's Nexus Root Toolkit, I managed to get 4.2.2 onto there by flashing it over everything. It seemed fine, but went into a bootloop on the Google splash screen before it could start up and go through the first time setup.
I have tried everything. I tried flashing again with NRT, and got the image attatched, a hither-to unseen error that could not be fixed with a pc reboot or reinstall of NRT. I tried using the old Nexus Toolkit to boot into CWM recovery, but since USB debugging isn't (and can't be) turned on, that could do nothing. I've tried using the SDK command line to unlock it and flash it, but the device can't be found because it hasn't been booted up for that first time startup configuration. I've tried uninstalling all the drivers and trying all of that again, with nothing.
What's left is a nexus 7 with a brand new 4.2.2 that can't boot, no USB debugging, that is locked and unrooted. I can get into the bootloader, but there's no recovery installed.
I'm sorry if this has happened before. I'm sorry if this isn't new. But good christ almighty I just want my tablet to work.
tl:dr help me gods of the Android
If you can boot into the bootloader, can you use the SDK's fastboot tool to flash the stock recovery?
jfmcbrayer said:
If you can boot into the bootloader, can you use the SDK's fastboot tool to flash the stock recovery?
Click to expand...
Click to collapse
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
fudgyhoops said:
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
Click to expand...
Click to collapse
I suppose "fastboot oem unlock" doesn't work, either?
fudgyhoops said:
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
Click to expand...
Click to collapse
As long as you can get into fastboot, you should be able to use fastboot commands, sounds like you have a driver problem. Did you uninstall all the drivers and install the pdanet drivers? If the pdanet drivers don't work try naked drivers. It doesn't matter if debugging is enabled or not or if your device is unlocked and unrooted, you should still be able to do everything via fastboot commands. I recommend wiping everything via fastboot commands and than flashing the stock image. I recommend avoiding rootkits they are more trouble than they're worth, fast boot is a lot easier, faster and safer. You might want to try a different computer if nothing else works. You might have a defective bootloader though. Make sure you check the device manager on your computer to see if there are any errors with the drivers, it should show a yellow triangle if the driver is not working, if that's the case click on update driver and navigate to the SDK drivers.
http://www.androidegis.com/how-to/how-to-unbrick-the-nexus-7/
---------- Post added at 09:01 AM ---------- Previous post was at 08:54 AM ----------
Once you get the stock image flashed, unlocked and rooted, you can use goo manager to install the twrp recovery.
jfmcbrayer said:
I suppose "fastboot oem unlock" doesn't work, either?
Click to expand...
Click to collapse
I was surprised when it did. I had done a full driver reinstall to prestige777's advice, and fastboot started working again. Ran into an error when trying to flash 4.2.2 and bootloader version 4.18 with mismatched signatures, but tried it on another computer (thank you prestige777 again) and it's booting!
Thank you both so much!
fudgyhoops said:
I was surprised when it did. I had done a full driver reinstall to prestige777's advice, and fastboot started working again. Ran into an error when trying to flash 4.2.2 and bootloader version 4.18 with mismatched signatures, but tried it on another computer (thank you prestige777 again) and it's booting!
Thank you both so much!
Click to expand...
Click to collapse
No problem, I'm glad it worked for you.
Related
I was running ParanoidAndroid perfectly until it crashed and not it gets stuck at the loading screen of the ROM (not the Google logo). I'm able to turn it off and get into Bootloader. From there if I choose Recovery mode, it gets stuck at Google logo.
If I plug it into the PC while in booatloader, it gets detected as "Android" but no driver (I'm sure I installed it before with the Toolkit). Toolkit just won't detect the device anymore, keeps getting stuck at the <waiting for device> command.
If I plug it into the PC while stuck at the ParanoidAndroid loading screen, I see MTP and Nexus in Device Manager but w/o drivers.
What can I do now? Any input is appreciated.
Thanks.
Bump.
Itaintrite said:
Bump.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Xentar712 said:
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Click to expand...
Click to collapse
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Itaintrite said:
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Click to expand...
Click to collapse
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Xentar712 said:
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Click to expand...
Click to collapse
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Itaintrite said:
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Click to expand...
Click to collapse
It worked for me only once after reflashing the recovery. Never again after that. Hopefully it gets fixed soon, but until then, I carry my USB cables with me if I'm flashing new roms
Sent from my Nexus 7 using Tapatalk 2
i was stuck in a bootloop after flashing a ROM, and didnt have any backups or other ROMs on the devices storage, so i was attempting to push files to it via ADB, but it wouldnt connect. i went back into the custom recovery image, and accidentally wiped the whole thing, so now i have no OS installed, and not even the seeminly 'faulty' ROM in /sdcard either. i can still get into the bootloader and the custom recovery, but cant seem to get it to connect to ADB. any ideas what i can do?
If you could boot into fastmode, then just flash stock rom.
Leonhan said:
If you could boot into fastmode, then just flash stock rom.
Click to expand...
Click to collapse
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
bmoreyce said:
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
Click to expand...
Click to collapse
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
najaboy said:
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
Click to expand...
Click to collapse
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
bmoreyce said:
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
Click to expand...
Click to collapse
You don't need ADB if you are in the bootloader- you use fastboot.
Hi there
i wiped data to install a new rom. But i wiped the recovery and also the rom so now i only see the bootloader
i see bootloader version 4.18
fastboot mode in red
lock state unlocked
The problem is : my computer won't recognize the n7 though ADB
when i try driver test with nexus root toolkit it says adb device was not found
Si now i'm stuck and i can't install any rom or recovery to boot in
please anybody help
adin59 said:
Hi there
i wiped data to install a new rom. But i wiped the recovery and also the rom so now i only see the bootloader
i see bootloader version 4.18
fastboot mode in red
lock state unlocked
The problem is : my computer won't recognize the n7 though ADB
when i try driver test with nexus root toolkit it says adb device was not found
Si now i'm stuck and i can't install any rom or recovery to boot in
please anybody help
Click to expand...
Click to collapse
Somehow i managed to install a rom. It's Fixed
adin59 said:
Somehow i managed to install a rom. It's Fixed
Click to expand...
Click to collapse
I hate to bring this thread back to life but, how did you manage to do it? I am in the exact same situation but bootloader 4.23. Did you manage to install the ROM through Nexus Root? Or platform tools?
Any help is appreciated.
I am attempting to flash the factory image. Found here. http://forum.xda-developers.com/showthread.php?t=1907796
ADB devices does not list my device and Nexus Root tool says not found. Not sure what else to do at this point.
kktvr4 said:
I hate to bring this thread back to life but, how did you manage to do it? I am in the exact same situation but bootloader 4.23. Did you manage to install the ROM through Nexus Root? Or platform tools?
Any help is appreciated.
I am attempting to flash the factory image. Found here. http://forum.xda-developers.com/showthread.php?t=1907796
ADB devices does not list my device and Nexus Root tool says not found. Not sure what else to do at this point.
Click to expand...
Click to collapse
"
I'm assuming you're in the bootloader while trying to do this. ADB stands for "Android Debug Bridge". The bootloader really has nothing to do with the Android operating system, thus ADB isn't running. You need to use fastboot commands. Try "fastboot devices".
korockinout13 said:
"
I'm assuming you're in the bootloader while trying to do this. ADB stands for "Android Debug Bridge". The bootloader really has nothing to do with the Android operating system, thus ADB isn't running. You need to use fastboot commands. Try "fastboot devices".
Click to expand...
Click to collapse
Thank you very much, that worked for me. :good:
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
matteosaeed said:
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
Click to expand...
Click to collapse
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Also check this out, it might help
matteosaeed said:
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Also check this out, it might help
Click to expand...
Click to collapse
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Why don't you just go to Heisenberg's guide in the general section and flash the latest stock images from Google via Fastboot and start from there? This way you'll at least have a working phone to boot into. From there you can reflash custom recovery and even systemless root. This is what I have always done when the phone wouldn't boot, or I had a backup handy and flashed that. When in trouble just flash latest images.
Asmodic said:
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
Click to expand...
Click to collapse
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sounds like you need to update you drivers if your computer is not recognizing it
Asmodic said:
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Click to expand...
Click to collapse
Any Luck?
it's because you don't have the NEWEST version of TWRP.
Even the simplest of searches would've come up with this answer.
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
pankajste said:
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
Click to expand...
Click to collapse
No it won't, not in this situation.
Heisenberg said:
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Asmodic said:
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Click to expand...
Click to collapse
So this should be marked "Solved?"
It should be marked as "when in trouble revert to Heisenberg's guide."
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.