EDIT: For the solution to this particular issue, head to this post.
Hi, yesterday I successfully did a clean install of OOS 4.0, including Magisk and systemless root. I had everything set up as I wanted it.
Today, I tried the 4.0.1 OTA, after using a Canadian VPN server. It downloaded fine (the full zip), and I launched the OTA.
Phone reboots... into nothing. Now the phone won't boot into recovery mode, or start the system. I thought it was odd, so I flashed stock recovery again (which is what was installed). Still can't boot. Then tried just booting into recovery over fastboot mode. Still no luck.
Then I managed to boot into a modded TWRP. That's something... But tried flashing the OTA from its temp location in TWRP. A couple of "command log" errors, but appeared to patch nonetheless.
Reboot to system though: black screen of nothing, again.
Anyone know what might be the issue, and why it happened after just launching an OTA through the stock dialogue?
Cheers :/
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
abobobilly said:
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
Click to expand...
Click to collapse
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
ememeh said:
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
Click to expand...
Click to collapse
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
abobobilly said:
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
Click to expand...
Click to collapse
I can get to a point of backing up if I want to. Though at the moment, I don't know what I'd backup (maybe just the system partition? I dunno).
I have the same thing: Can get the white 1+ logo, both capacitative button backlights show, the android text logo, but then black screen. Very frustrating. Let me know if you have any luck! I'll update here too.
wierd
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
canceric said:
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
Click to expand...
Click to collapse
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
abobobilly said:
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
Click to expand...
Click to collapse
good thing it worked for you, it bugs me that i cant root the phone since the device doesnt get recognised in fastboot ,reinstalled all the drivers and all, nothing works
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
ememeh said:
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
Click to expand...
Click to collapse
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Shayded said:
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Click to expand...
Click to collapse
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
ememeh said:
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
Click to expand...
Click to collapse
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Shayded said:
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Click to expand...
Click to collapse
Weird. Could be a different problem...
Did you get the install success message?
ememeh said:
Weird. Could be a different problem...
Did you get the install success message?
Click to expand...
Click to collapse
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Shayded said:
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Click to expand...
Click to collapse
Can you still boot back into fastboot and/or recovery?
ememeh said:
Can you still boot back into fastboot and/or recovery?
Click to expand...
Click to collapse
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Shayded said:
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
Click to expand...
Click to collapse
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Shayded said:
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Click to expand...
Click to collapse
Just seen the edit. Okay, makes sense. Good luck :good:
ememeh said:
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Click to expand...
Click to collapse
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Shayded said:
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Click to expand...
Click to collapse
Luckily for you, it doesn't sound like a true hard brick. Sometimes power buttons are just funny like this. In my experience at least (I've come back from near death experiences in a similar way to you before).
In any event, well done! Always such a relief to get things working again.
Related
Hi Guys -
First time android user and attempted rooting using the odin method. I followed the instruction listed here http://forum.xda-developers.com/showthread.php?t=1311194 to the "T" before starting. I was doing alright until after flashing the recovery-cwm-hercules.tar, then it gets weird. It didn't flash to recovery but just rebooted to the main screen (where I could see the background picture with the locker pattern), then it immediately shuts off and the cycle begins again.
The weird thing is that I can't even access recovery mode (hold vol. up+down+power), because I'll see the Clockworkmod logo then it flickers and reboot itself. This happens every time I attempted recovery mode.
My attempts to fix it:
1. I flashed the recovery, http://forum.xda-developers.com/showthread.php?t=1315390, to see if it makes any difference. The same story happens with loading to main screen w/locker then it reboots itself again and again. Sometimes I'll be lucky to input the pattern but before soon it will reboot itself again. Same thing with recovery mode as described above.
2. Flashing the stock kernel provided by http://forum.xda-developers.com/showthread.php?t=1311229 to see if it does anything. Nope, same story for both recovery mode/home screen.
3. The insecure kernel, http://forum.xda-developers.com/showthread.php?t=1320946. Same story. nope, nope.
4. Tried these in all order and permutation. Nada.
5. Tried it both ways using samsung driver/kies.
6. Tried it both ways with/without SIM card.
7. Battery is fully charged when attempting any flashing.
8. All the above in my second computer to no avail.
I'm sorry if this might come across as long winded but I just want you guys to get the full picture. I would really appreciate it if you guys could offer any solutions or advice on how to correct this problem. Please be gentle with this first time android user haha, thanks in advance man.
Manually boot into recovery (vol up/down keys) and make a backup (be sure to do this). Then try wipe data/factory reset through recovery. Sounds like a ROM issue not a hardware issue
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
redlaws said:
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
Click to expand...
Click to collapse
Ok, so if it actually boots into the ROM but reboots, try rebooting to recovery from adb -- "adb reboot recovery"
think it's a no go . i tried using adb recovery method and the same thing would occur, it would restart and seems to load into recovery mode but then I would only see the logo, then it flickers and restart itself.
then the vicious cycle of loading up to the screen-locker and restarting itself begins. guess this is the smartphone version of being friend-zoned.
Have you tried taking battery out then back in and while holding volume up/down plug it back into computer? That has never failed to get me into d/l mode. Man I hope you get it working.
Yeah I tried that and getting to download mode is not the problem. just that recovery mode doesn't boot properly in that it would restarts itself. and when i boot normally to screen, i would see the locker and background picture then within 3 secs, it would restart itself.
Guess last resort is to go to t-mobile store, play dumb, and get samsung on it. only problem is that i worry about the flash rom counter # since mine is like 10 already (my attempts to address this problem). Let's hope those tmobile reps aren't that tech savvy.
Thanks for all the help fellas, great early posting experiences so far.
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
kt0ce said:
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I'm going to give it another try. I've been trying it with different files for a good 2 days now though.
AllGamer said:
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
Click to expand...
Click to collapse
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
redlaws said:
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
Click to expand...
Click to collapse
did you let go of holding the vol+ & vol- buttons as soon as you see the blue text in CWR ?
it can easily reboot by accident when holding those buttons and hitting power, but the buttons are so responsive it selected the first option to reboot the phone by accident a couple of times on me
I'm positive that I held it properly and long enough. I never got to the blue text, just the CWR logo showing then turns off (like you shutting off a tv) and reboots itself. Trying to flash it again with Odin didn't work either and I tried the recoveries from different sources as well.
I went to the Tmobile store today and seems like they'll mail me a replacement then I'll return my current one to them. Only thing is stocking/processing fee but it's a small price to pay if it resolves everything.
glad they will give you another one..
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
reocej said:
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
Click to expand...
Click to collapse
Dude, I understand that it should but it's not. I've flashed the stock recovery for more than 10 times and I still can't past the home screen. It would just reboot itself in less than 3 sec. And I'm positive I flashed it properly. Believe me I don't want to spend extra money if I don't have too.
hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
same prob
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
Same problem as OP, and I can not get into download mode either. If I do as above, it still goes on booting .
saeidzzz said:
hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could write them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
you are a life saver!
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
I thought I was going to have to factory reset my phone like other forums suggested and lose everything. Thanks to your suggestion I was able to get out of recovery reboot loop. Thank you!
Thanks for your help, you are a lifesaver lol! I saved so much money and time because of you. Have a great day
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
But how to enter recovery it still says set warranty bit recovery
i am facing problem with set warranty bit: recovery in samsung J5 model...
samsung j5 500f
i have the same problem when i flash twrp recovery..any solution ????
Ghats normal
Sent from my SM-N900T using XDA-Developers mobile app
My Fix
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
ulop3z said:
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
Click to expand...
Click to collapse
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Tmobilefan906 said:
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Click to expand...
Click to collapse
The phone is fine now, it was just stuck on the loop and spamming home was the only way out, its fine now I've had no problems and it boots up fine
This happens...
This happens to almost everyone at some point of time. There is no need to worry as you just need to flash recovery like TWRP or CWM. To shed some light on this issue... boot loops mainly happen when you uses the incorrect version of software with your ROM or stock firmware. By using youtube you can look at the videos of your phone model and find the recovery version number needed.
For anyone who has a Note 3 T-Mobile phone who is still stuck! I am willing to make a video to show how to fix this and provide all the firmware/version numbers + links in one bundled location to make it easier.
ALL PHONES ARE VERY specific... ONLY USE THE CORRECT FIRMWARE FOR YOUR MODEL PHONE
Again, if you have a Samsung Note 3 T-Mobile, model number SM-N900T and are still lost. Let me know so I can shot a video and bundle files needed.
---------- Post added at 08:44 AM ---------- Previous post was at 08:38 AM ----------
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could write them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
Don't be scared by this... just choose the correct versions before blindly trying to install a ROM. Also, only use links from main sources if you dont fell like auditing the code!
Hi guys, sorry for might be late about helping you now years later... But recently I've found something interesting about fixing this issue.
*****
Fix: (100% working in Galaxy Grand Prime SM-G530H)
UPDATED: More detailed info!
# Before flashed Recovery or Root:
1. Root device using Odin or any other rooting known workaround.
2. Backup Recovery (optional), and Kernel using Rashr (available on PlayStore).
3. Flash Custom Recovery (TWRP), using Odin PC software or TWRP android app.
4. Flash backed-up Kernel.img file to Boot partition using TWRP install section.
5. Reboot system (It may take a few time to boot)
# After flashed Recovery or Root: (accidentally or without knowing)
1. Search online and download your exact Phone Stock Kernel.
2. Follow *before flashed* above ↑ from 3rd.
Bonus info:
Even after flashing TWRP, you might be able to Boot device yet, by going to TWRP → Advanced → Reboot system. (It bypass bootlooping to Recovery, while: “Set Warranty Bit : Recovery”).
That's all! Try at your own, then share it!
I was at work the night before, and my capacitive buttons stopped responding, so I went for a restart in hopes they would kick back on, this just caused my phone to enter a boot loop. Soft resetting and hard resetting both continue the loop, trying to enter recovery mode throws me back into the loop, entering download mode locks the phone on the small HTC screen. I tried to flash the current RUU onto the phone, but it won't proceed with the install due to a low main battery error despite the fact I've had it charging for 6 hours. The only thing I can think of doing now is sending it back in hopes they fix it, but theres a lot of information I ignorantly haven't backed up, and now can't access before sending it back.
If anyone has any helpful tips or ways to move forward I would be grateful.
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
silegeek said:
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
Click to expand...
Click to collapse
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Snickie12 said:
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Click to expand...
Click to collapse
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
Holding Volume up just continued the loop, I can get into the bootloader like you said, but theres not very many options, download locks the phone onto the HTC logo and doesn't proceed, the recovery option just restarts the phone into the loop.
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
silegeek said:
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
Click to expand...
Click to collapse
Whenever I plug it in while off, it shows the low battery icon and tries to turn itself on.
I had exactly the same problem...were you able to sort it out?
same problem except I can charge mine will I be able to ruu even if it is locked ?
isaac1993 said:
same problem except I can charge mine will I be able to ruu even if it is locked ?
Click to expand...
Click to collapse
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
No,it's not. I'm bl ul,s-off,and I can ruu anytime.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
I thought it was charging but now fount out it wont charge
isaac1993 said:
I thought it was charging but now fount out it wont charge
Click to expand...
Click to collapse
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
singlemalt said:
I had exactly the same problem...were you able to sort it out?
Click to expand...
Click to collapse
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Snickie12 said:
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Click to expand...
Click to collapse
Did they tell you what they did to fix it by chance? Thanks.
singlemalt said:
Did they tell you what they did to fix it by chance? Thanks.
Click to expand...
Click to collapse
No they didn't sorry.
singlemalt said:
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
Click to expand...
Click to collapse
My friends s7 completly bricked doing the N update. If you havnt done anything to your phone just take it back and get a new one.
Same exact issue here after the Verizon OTA update.
Failed after the first reboot after the update.
The storage was pretty maxed, wonder if that has something to do with it.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
I have very similar htc 10 issue : (
https://www.reddit.com/r/HTC10/comments/9j8nyk/htc_10_oreo_stuck_in_boot_loop_i_can_only_access/
how do you do fastboot commands when only at bootloader screen when you cant access download mode or recovery : ( also my htc 10 was low on stoage space I must have corrupted the htc 10 oreo : (
Hi! So I have been rolling with the marshmellow version of RR for quite some time and figured I was due for an upgrade. I went to update to the Nougat version, and did everything correctly, firmware, wipe, rom, then gapps. Much to my dismay I was greeted with a screen prompting me for my pattern to start android, I thought this a bit odd but went with it and my pattern did not work. I tried again thinking I may have done it wrong but nothing worked. I didnt think much of it and went to flash again to make sure I did it right, but my recovery never booted. Afterwards I got an error that was very quick and I was not able to read. It came just after the "your phones bootlader has been unlocked" etc. It was a very similar screen as well. After this, I was not able to boot up the phone at all. Once I was able to power up the phone but it simply gave me the same error and now its not starting at all. Any help would be much appriciated and thank you if you made it through this post.
First of all, you need to flash the very latest version of TWRP. If you are suffering from encryption issues and cannot decrypt TWRP, you will need to press back on the TWRP screen, and press wipe -> Format data
You will lose all your data and will be unencrypted. Make sure you have the latest TWRP, as this is vital for Nougat.
FriendWithin said:
First of all, you need to flash the very latest version of TWRP. If you are suffering from encryption issues and cannot decrypt TWRP, you will need to press back on the TWRP screen, and press wipe -> Format data
You will lose all your data and will be unencrypted. Make sure you have the latest TWRP, as this is vital for Nougat.
Click to expand...
Click to collapse
Thank you for the help, but I cannot even get into my device to update TWRP.
Try holding the power button for a minute, or try volume down + power to get into the bootloader.
FriendWithin said:
Try holding the power button for a minute, or try volume down + power to get into the bootloader.
Click to expand...
Click to collapse
Already did, it doesnt work. Black screen.
Im facing the same problem too. Cant even get adb to work ?
If you can still get into your bootloader, use fastboot commands to flash the latest TWRP.
Either hold Vol Up + Power when you phone is off, or turn it on normally and click any volume button during the "bootloader unlocked" warning screen to access the boot menu.
If you can't access the bootloader at all, then I believe the unbrick guide is your only option.
I can get to the bootloader, but when i flash recovery, it just restarts again and again.
Wipe the recovery partition first before you flash the new one.
Also, what version of TWRP are you using?
Yeah I will look into brick guides. Also going to try and let my phone charge to see if that may help. As far as I can tell it isnt charging but I might as well try.
Thank you for all the help guys, eventually what worked for me was indeed an unbrick guide. I will now be sure to read up entirely on what exactly I need to upgrade to fix this issue. For any wondering https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ This was the guide I used to fix my phone.
So, I was on /e/ os, and I wanted to switch to lineageos, so I downloaded the zip, flashed TWRP (as recovery) went into it, flashed los, rebooted, got to boot screen, and right as it was about to go into setup, it turned off. I tried again, same thing, etc etc. I tried to go into fastboot and recovery, nothing. It's stuck at the Recovery mode... loading... then it has purple led at the top. it is the canadian h812 version.
myphoneisweirdlol said:
So, I was on /e/ os, and I wanted to switch to lineageos, so I downloaded the zip, flashed TWRP (as recovery) went into it, flashed los, rebooted, got to boot screen, and right as it was about to go into setup, it turned off. I tried again, same thing, etc etc. I tried to go into fastboot and recovery, nothing. It's stuck at the Recovery mode... loading... then it has purple led at the top. it is the canadian h812 version.
Click to expand...
Click to collapse
please, someone respond
myphoneisweirdlol said:
So, I was on /e/ os, and I wanted to switch to lineageos, so I downloaded the zip, flashed TWRP (as recovery) went into it, flashed los, rebooted, got to boot screen, and right as it was about to go into setup, it turned off. I tried again, same thing, etc etc. I tried to go into fastboot and recovery, nothing. It's stuck at the Recovery mode... loading... then it has purple led at the top. it is the canadian h812 version.
Click to expand...
Click to collapse
Hi. I don't know exactly what the problem is and how to solve it. I would wait for an answer steadfasterX, or someone who knows the exact answer.
I would try to do this, but as I wrote above, I do not know if it will help or not:
Factory reset hardware key combo (https://forum.xda-developers.com/t/unlock-unofficial-g4-unlock-any-lg-g4-device-with-usu.3760451/)
As written above the regular key combo to get into the LG factory reset screen changes a bit:
power off device
disconnect any usb cable from the device
press volume UP + power button and KEEP THEM BOTH pressed until you see the LG logo the first time! THEN you have to immediately release the power button (ONLY that) and press and keep holding the power button directly again! Keep them pressed until you see the white LG factory reset screen
After that, I would try to go into the recovery, to format and restore or reflash.
Hope this helps. But it is better to wait for the answer of the knowledgeable. Good luck!
xDev91 said:
Hi. I don't know exactly what the problem is and how to solve it. I would wait for an answer steadfasterX, or someone who knows the exact answer.
I would try to do this, but as I wrote above, I do not know if it will help or not:
Factory reset hardware key combo (https://forum.xda-developers.com/t/unlock-unofficial-g4-unlock-any-lg-g4-device-with-usu.3760451/)
As written above the regular key combo to get into the LG factory reset screen changes a bit:
power off device
disconnect any usb cable from the device
press volume UP + power button and KEEP THEM BOTH pressed until you see the LG logo the first time! THEN you have to immediately release the power button (ONLY that) and press and keep holding the power button directly again! Keep them pressed until you see the white LG factory reset screen
After that, I would try to go into the recovery, to format and restore or reflash.
Hope this helps. But it is better to wait for the answer of the knowledgeable. Good luck!
Click to expand...
Click to collapse
It worked... I hope the factory reset actually fixes it. (by it worked I mean I got into it)
Nope. Didn't work. It freezes up and says 'Secure booting error :1003' MODIFIED!' with a purpleish pinkish led.
Boot in fastboot and execute:
fastboot format userdata
(this will erase all internal data, pics, apps etc)
Then let it boot.
steadfasterX said:
Boot in fastboot and execute:
fastboot format userdata
(this will erase all internal data, pics, apps etc)
Then let it boot.
Click to expand...
Click to collapse
I forgot, how do i boot in fastboot again?
I GOT IT INTO DOWNLOAD MODE! I REPEAT, I GOT IT INTO DOWNLOAD MODE!
myphoneisweirdlol said:
I GOT IT INTO DOWNLOAD MODE! I REPEAT, I GOT IT INTO DOWNLOAD MODE!
Click to expand...
Click to collapse
Nevermind, nothing worked
myphoneisweirdlol said:
Nevermind, nothing worked
Click to expand...
Click to collapse
I said fastboot mode not download mode. Read the UsU thread first post how to boot into it.
WOOOO BABY LETS GO I GOT INTO FASTBOOT (Edit: I fixed it!)