A couple days ago, my volume buttons were not working so I thought a quick restart would fix it. But when I restarted it, it went into bootloader. Its stuck on the 'Restart bootloader' option and I can't select it with my power button nor can I select other options with my volume keys. I try and hold down the power button and it restarts into bootloader again. I booted into recovery and tried to restore it with a nandroid I made that had everything stock but that didn't work. I also did a factory reset, but every time I try to boot into system it goes to bootloader instead. The only problem I can think of was that I held my phone when my hands were wet so maybe water went inside? I'm tempted to get rice to get the water out but I want to be certain that this is the result of water damage. If it helps, I had TWRP and a very early version of Lineage OS on the device before it happened.
TheGentleShark said:
A couple days ago, my volume buttons were not working so I thought a quick restart would fix it. But when I restarted it, it went into bootloader. Its stuck on the 'Restart bootloader' option and I can't select it with my power button nor can I select other options with my volume keys. I try and hold down the power button and it restarts into bootloader again. I booted into recovery and tried to restore it with a nandroid I made that had everything stock but that didn't work. I also did a factory reset, but every time I try to boot into system it goes to bootloader instead. The only problem I can think of was that I held my phone when my hands were wet so maybe water went inside? I'm tempted to get rice to get the water out but I want to be certain that this is the result of water damage. If it helps, I had TWRP and a very early version of Lineage OS on the device before it happened.
Click to expand...
Click to collapse
Hi... How did you manage to boot into recovery without the volume rocker?
Have you tried a simple:
fastboot format cache
fastboot format userdata
fastboot reboot
From bootloader?
Is your bootloader unlocked? If yes, try loading a factory image from Google if none of the above work.
5.1 said:
Hi... How did you manage to boot into recovery without the volume rocker?
Have you tried a simple:
fastboot format cache
fastboot format userdata
fastboot reboot
From bootloader?
Is your bootloader unlocked? If yes, try loading a factory image from Google if none of the above work.
Click to expand...
Click to collapse
I used 'fastboot boot recovery.img' to get to recovery. I tried to format the cache and userdata again, but still didn't normally boot. I also tried flashing the stock images from Google's website but still it won't boot.
TheGentleShark said:
I used 'fastboot boot recovery.img' to get to recovery. I tried to format the cache and userdata again, but still didn't normally boot. I also tried flashing the stock images from Google's website but still it won't boot.
Click to expand...
Click to collapse
I never seen this before. If you type fastboot reboot, it reboots directly into bootloader, right? I first thought avout the bootloop issue many currently report. But if you can boot a recovery.img or if your phone only reboot into bootloader, I think this scenario can be excluded.
Hmm you said you touched you phone with your hand wet?!
Could it be the moisture that oxidized the volume down contact inside of the phone? I don't have another idea. Wait for other people to chime in. Hopefully it's another (easy to solve) issue which I am unaware of.
Good luck.
5.1 said:
I never seen this before. If you type fastboot reboot, it reboots directly into bootloader, right? I first thought avout the bootloop issue many currently report. But if you can boot a recovery.img or if your phone only reboot into bootloader, I think this scenario can be excluded.
Hmm you said you touched you phone with your hand wet?!
Could it be the moisture that oxidized the volume down contact inside of the phone? I don't have another idea. Wait for other people to chime in. Hopefully it's another (easy to solve) issue which I am unaware of.
Good luck.
Click to expand...
Click to collapse
Ah well. Thanks anyways.
TheGentleShark said:
Ah well. Thanks anyways.
Click to expand...
Click to collapse
Did factory image flash without error?
Last try: did you try pressing power button till it reboots?
Good luck...
5.1 said:
Did factory image flash without error?
Last try: did you try pressing power button till it reboots?
Good luck...
Click to expand...
Click to collapse
No error came up when I flashed it and holding power button at bootloader restarts the phone back into bootloader. I might just stick it into some rice and use my old Nexus for now unless another solution presents itself.
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
WRDD said:
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
Click to expand...
Click to collapse
Hi. In order to get the attention of @TheGentleShark you should either reply directly to one of his posts, or put an ampersand in front of his name so he gets a notification. Otherwise he will never know (or see) your question. Hopefully he has some useful feedback for you.
WRDD said:
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
Click to expand...
Click to collapse
Sorry for late reply, but I did manage to get if fixed. I sent it back to my phone company to get fixed since it was still under warranty (even though its rooted with unlocked bootloader). Though, they didn't really tell me what went wrong. I assumed it was a hardware problem (a piece of rice was stuck in the speaker hole and was impossible to remove but was gone when I got the phone back).
Related
Hi Everyone,
I have some experience of unlocking, rooting , flashing custom roms etc. but this issue has me really stumped and searching for the past couple of hours only led me to 1thread with a similar issue and no solutions. So here it is:
stock (4.3) N4 stuck in boot loop.
Fastboot oem unlock will not survive reboots, so I am unable to flash stock image back on my device.
Please Help with a solution to get this phone working again!
History:
Last night I turned on my wife's N4 (Android 4.3 stock) and put it on charge and walked away. This morning I found it is stuck on the "X" boot screen and red hot. I powered down, let it cool for 1/2 hour and then fully charged it (while off).
It will no longer boot, sticking on the "X" screen.
Booting into fastboot and choosing recovery leads me to android with red "!".
This phone has never been rooted, unlocked, custom recovery or custom ROM. ( I have however done all of this to my other N4)
Attempts:
Decided to wipe it and reisntall stock 4.3, lots of errors because it is locked.
So 1st step is to unlock, however whenever I do fastboot oem unlock I get the prompt about unlock and YES/ NO. I select YES and it successful erases and report LOCK STATE - UNLOCKED in red.
I reboot the phone into fastboot and LOCK STATE - ENABLED in green. Now stuck on what to do next.
(Secure boot - enabled).
Many thanks in advance.
Go into the stock recovery and do a factory reset. Go into the bootloader, choose Recovery Mode. When the dead android/red triangle comes up, hold power and tap volume up. Then select wipe data/factory reset.
Chromium_ said:
Go into the stock recovery and do a factory reset. Go into the bootloader, choose Recovery Mode. When the dead android/red triangle comes up, hold power and tap volume up. Then select wipe data/factory reset.
Click to expand...
Click to collapse
Please see 1st post:
Booting into fastboot and choosing recovery leads me to android with red "!".
Click to expand...
Click to collapse
htcsens2 said:
Please 1st post:
Click to expand...
Click to collapse
Please read my post:
Go into the stock recovery and do a factory reset. Go into the bootloader, choose Recovery Mode. When the dead android/red triangle comes up, hold power and tap volume up. Then select wipe data/factory reset.
Click to expand...
Click to collapse
Chromium_ said:
Please read my post:
Click to expand...
Click to collapse
Sorry, I re-read and followed your instructions :good:. I went pass the red "!" and did the wipe data / factory reset.
I rebooted into fastboot and issued
Code:
fastboot oem unlock
LOCK STATE- unlocked
I then rebooted again into fastboot
LOCK STATE- enabled :crying:
update:
I see errors after the wipe cache (successful)
E:failed to mount / cache (Invalid argument)
then lots of errors of failure to mount other cache sub directories and flies.
htcsens2 said:
Please see 1st post:
Click to expand...
Click to collapse
the android with the red "!" IS the stock recovery.
Summary so far:
N4 (stock) stuck at "X" screen.
booting into recovery and doing factory wipe + reset formats ok (but results in errors mounting cache)
"fastboot oem unlock" will unlock the phone for next reboot (google logo + unlock symbol) where it will then hang.
Subsequent reboots the device is locked (hang at Google screen withOUT unlock symbol).
Booting into Fastboot the device is locked again.
More help gratefully received.
dupe
it sounds like you might have an issue with the storage. at least when the storage goes bad, it follows the same symptoms. usually when the storage goes, people just find their device on X. if unlocking the device results to going back to locked after a reboot, it sounds like its actually not clearing the storage of the device, which would happen if the storage went back.
simms22 said:
it sounds like you might have an issue with the storage. at least when the storage goes bad, it follows the same symptoms. usually when the storage goes, people just find their device on X. if unlocking the device results to going back to locked after a reboot, it sounds like its actually not clearing the storage of the device, which would happen if the storage went back.
Click to expand...
Click to collapse
Thank you. I was reaching the same conclusion of a hardware issue. I'll arrange a warranty repair. I have 3 days left on the Warranty....
htcsens2 said:
Thank you. I was reaching the same conclusion of a hardware issue. I'll arrange a warranty repair. I have 3 days left on the Warranty....
Click to expand...
Click to collapse
cutting it close!
simms22 said:
cutting it close!
Click to expand...
Click to collapse
Yes, 3 days the other side and I would be mad.
oh well. Thank you everyone for the sanity check. :good:
Let m know if there is anything else I can try before it goes back.....:fingers-crossed:
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
Good evening XDA,
I've got a Nexus 6p (obviously), and can't get it to boot. Unfortunately, I don't know the exact history as to how it's in this state.
I've tried everything I can think of and read every guide/steps/forums I can find that relates to my situation.
I can get to the bootloader and issue Fastboot commands. I've got adb/fastoot/drivers installed via the sdk/platform tools, and drivers are up to date as far as I can tell.
-I'm using the OEM cable attached to my computer (Surface Pro3, Windows 10)
-I can unlock/re-lock the bootloader as I wish.
-I've tried WugFresh toolkit, flash factory + unroot. All completes, but phones continues to loop even after leaving it for an hour+.
-I've tried Heisenbergs guide for manually flashing stock google images via fastboot to no avail. Tried several different google images. Everything completes, but it still just loops.
-I can get all fastboot commands to complete with no errors, but the phone just simply bootloops at the google logo, or if I leave bootloader unlocked it loops with the orange triangle & google logo. I have left it looping for at least an hour+, but it doesn't finish:crying:
-Stock recovery or a fastboot flashed trwp recovery simply won't boot, it just goes to the google logo and loops, I don't get the dead android w/triangle. "Recovery" in the bootloader selections is RED, if that means anything. Tried fastboot commands to boot recovery, but just sends it to the google logo and loops.
-Adb commands don't work, only fastboot commands.
-During flashing a google stock image with fastboot, the only thing that stands out is "max download of ####### reached", or something similar, but it still completes.....?
Seems to me that I've got a true brick (first ), and just need to send it in for repair.
Any help would be greatly appreciated. TIA.
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
TnT_ said:
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
Click to expand...
Click to collapse
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Dhickory said:
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Click to expand...
Click to collapse
Does all the data in the bootloader look fine? The storage size etc?
TnT_ said:
Does all the data in the bootloader look fine? The storage size etc?
Click to expand...
Click to collapse
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Dhickory said:
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Click to expand...
Click to collapse
Usually with board failure - that I saw in other threads - there are missing fields. My phone had a little glitchyness after I accidentally flashed the userdata.img - which caused my 128gb to become 32gb, which I found amusing - Other than that, I don't know. I'm sure others would reply.
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Dhickory said:
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Click to expand...
Click to collapse
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Jammol said:
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, and I've been reading the "Let's figure out this brick together" thread. The link you posted requires ADB commands to work to fix the EFS partition, but I can only run fastboot commands. ADB nor Recovery work on my device. Still reading...
Woohoo! Huawei replaced the phone, no questions asked. I think the saving grace was being able to flash stock images, and relock the bootloader. May be helpful to anyone else in this situation that can only run fastboot commands, and no recovery.
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
alijaved154 said:
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
Click to expand...
Click to collapse
Tried factory reset and reboot?
tropical cactus said:
Tried factory reset and reboot?
Click to expand...
Click to collapse
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
alijaved154 said:
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
Click to expand...
Click to collapse
You can select factory reset by pressing the volume button . Factory reset will come up. Select by pressing power button and press again to wipe.
tropical cactus said:
You can select factory reset by pressing the volume button . Factory reset will come up. Select and wipe.
Click to expand...
Click to collapse
in fastboot only the options are:
start
barcodes
recovery
bootloader
alijaved154 said:
in fastboot only the options are:
start
barcodes
recovery
bootloader
Click to expand...
Click to collapse
I have factory reset as an option. Not sure why you don't.
tropical cactus said:
I have factory reset as an option. Not sure why you don't.
Click to expand...
Click to collapse
in fastboot? i dont have it i dont know what hapoened to it
alijaved154 said:
in fastboot? i dont have it i dont know what hapoened to it
Click to expand...
Click to collapse
Try reboot bootloader and scroll through options again.
tropical cactus said:
Try reboot bootloader and scroll through options again.
Click to expand...
Click to collapse
comes back to the same screen but will still try today
alijaved154 said:
comes back to the same screen but will still try today
Click to expand...
Click to collapse
Very strange, unless it only shows up if you enable developer options before.
Same problem after update
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Erroras said:
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Click to expand...
Click to collapse
you are not alone...?
Same issue on one I have my hands on. This could get interesting.
From fastboot can anything be pushed/flashed like a previous actually functional firmware? Is there other specific software to do so? Only got my hands on the defective non functional device today but I'm planning and scheming a fix if possible.
One thing is really interesting. Why only after this update???? Why not after update from 6 to 7 then 7 to 7.1 and after 7.1 to 8.0. I think Google or Huawei is cheating us and forcing us to buy Google pixel.
I also have this issue (I'm using a nexus 5x, but this thread is the closest to my issue I've found), but it came incrementally. First, I started getting reboots every 20m or so, while doing normal phone things (reading, mostly). Then it started getting into bootloops that were 2-3 boots long, and would then work normally for the 20m mentioned above. I tried a factory reset, but it just got worse, and now either reboots on the Google logo or during the Android animation. My fastboot menu only has the regular "Start" as green. The only other options are Restart Bootloader, in red, and Recovery mode, also in red. Power off is there, obviously, but that's it. It started happening yesterday, and worsened to its current point within only a few hours.
Well. I have just joined the club. What is going on with that?
Happened to me today and I was using the latest build of SuperXE 6P.
Guys! lol
1. Dev options in ROM is same old. Settings/about and tap build 10 times to see count down to developer. Back to settings. In there for OEM unlock
2. Factory reset can be done any number of ways.
a. In ROM. Settings/backup and reset/factory reset.
b. From anywhere, hold power+volume down until you see the bootloader. There are 2 possible screens in there. One of them has factory reset. Beware! From here it will likely wipe your sdcard!
c. From recovery. You can get there from bootloader. You can also flash an up to date recovery image from bootloader.
The rest of your recovery process should be provided by the ROM thread by which you will get your choice of ROM.
Make sure you have access to a PC with adb. You will likely need to flash a vendor image
My device is only recognized in fastboot mode. No ADB, no recovery. Tried to uninstall and manually install latest USB drivers, it didn't work. My Nexus is now just stucked in a bootloop. I even tried to flash factory images to no avail. Really don't know what to do...
FYI I have no screen in bootloader allowing me to factory reset: only Start/Reboot/Reboot bootloader/Barcodes, as others stated above.
My HTC U Ultra suddenly froze past nigth, then it rebooted... and never came back, it won't go past the HTC logo over and over. I am not able to enter in recovery mode either, the only thing I can do is, by pressing both volume buttons and power, entering in what seems to be fastboot menu. In that state I can send the phone fastboot commands (no adb commands though) but If i try to wipe it it says "unable to do in s-on" or similar. I was pretty happy with this phone, and spent a few bucks in a new battery not two months ago.... anything I can do?
Thanks.
PS: I failed to state that the phone is stock, not unlocked or rooted.
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
spikey001 said:
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
Click to expand...
Click to collapse
Reset doesn't work, and the other procedure didn't work either.
If I leave it plugged to the charger, it will fall into an endless reboot loop. Sometimes (few) it will end up booting, but If i try to do something with the phone it doesn't respond and reboots again.
Thanks.
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
spikey001 said:
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
Click to expand...
Click to collapse
I tried that, too, but didn't work. If I do a fastboot devices it detects the phone, but if I do a fastboot getvar all it doesn't give me any information, it doesn't admit adb commands, when I try to flash a rom or a recovery, it fails, I suspect it needs to have the USB debugging enabled, but I can't enable it in this state.
As I said before, if I leave it plugged to the charger, It will randomly end up booting (it can happen in the third loop or in the 50th), but it will freeze or reboot again in few seconds.
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
spikey001 said:
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
Click to expand...
Click to collapse
The data is not a problem, every important file has been backed up.
Regarding factory reset, since the device won't go to recovery, I can't see how can I do it.
-- Edit --
I noticed that when the phone is cold, those few times it boots, it lasts a little bit more (a matter of seconds) until it freezes again, so I tried to leave it in the freezer for a few minutes, and tried to boot it, and had enough time to do a factory reset. The factory reset worked, because now, when it boots, it goes straight to the intial setup, but keeps hanging after a few seconds. I suspect that the internal memory was somehow damaged, I don't think there is much left to do...
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
spikey001 said:
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
Click to expand...
Click to collapse
I can't see how to skip initial setup... and I don't have time enough to go through it, the phone will hang in 30 seconds or less. At this point, I really needed a working phone, so I bite the bullet and bought a new one... I will deal with the old one later, or I might sell it for parts.
Thanks everybody for the help.
No worries, enjoy your new phone