Related
Hi,
I recently rooted my phone through VISIONary+ r14 and today downloaded ROM Manager. I flashed ClockworkMod Recovery, but I can't back up my current ROM (stock/branded). I want to make a complete 100% backup of my current phone to be able to restore later if I need to.
However, I don't know how to do it. There is a 'Backup current ROM' option on ROM Manager, but whenever I do it my phone restarts showing the black screen with the phone and the red Caution exclamation mark + triangle, so I have to hold Volume Up and the Power button to restart my phone.
What do I do?
Also, it may be worth mentioning my Desire HD is a Vodafone Australia branded phone which hasn't been updated at all.
Well, the triangle image thingy means you dont have recovery flashed...
So, you have to choose 'Flash ClockworkMod Recovery' first. - That wil download a file from the internet and install it for you, so make sure you have internet connection
That will flash/install a recovery for you, in which you can create a backup.
Oh and i think you need to S-OFF your phone before installing recovery (im not sure about that but thats what i've heard)
click here for S-OFF http://forum.xda-developers.com/showthread.php?t=855403 --the last process says that after S-OFF you can install CWM recovery
noodlesfordaddy said:
I flashed ClockworkMod Recovery,
Click to expand...
Click to collapse
Can you confirm if you did this separately to ROM Manager or as per above, used the Flash Recovery option in ROM Manager?
Have you confirmed you do have root?
If you reboot into recovery do you get to the clockworkmod recovery screen? What version is it?
If root can't be confirmed, re-do the visionary method. If root is confirmed but can't get to CWM-R do as per above and flash recovery from RM console.
Yes, I can confirm it is rooted.
I just ENG S-OFFed, so I'm going to try flashing recovery once again, although I'm still pretty sure it worked before that since Clockworkmod says "Current Recovery: ClockworkMod 3.0.2.6, Latest Recovery: ClockworkMod 3.0.2.6"
Will I do damage flashing it again?
EDIT: I pressed Flash ClockworkMod Recovery again and it waited for a little and then said that it was successful.
EDIT 2: Attempting another backup... And it's working!
No, you won't damage the it.
As I fly through different ROM's and do lot's of restores and backups I often have times where I need to reflash recovery.
look uot the link in my signature and try to do what it explanes......
Do all fases of rooting and you will have a perfectly rooted phone.
Also follow suggestions of CodeNameUnknown1.
Try man....Try
noodlesfordaddy said:
EDIT: I pressed Flash ClockworkMod Recovery again and it waited for a little and then said that it was successful.
EDIT 2: Attempting another backup... And it's working!
Click to expand...
Click to collapse
Great news!! Glad you got it sorted so far.
So, I have a problem.
I pressed the Backup option in ROM Manager, and the phone restarted, I'm now in Recovery mode... But I have a very strange problem. I can't make any selections.
I can scroll through the menu options fine, but can't select anything. If I press the power/lock button, the menu goes away and the clockworkmod logo in the middle just brightens up. If I press the home or menu buttons, the same thing happens, and if I press them again the menu just reappears. The return and search buttons do nothing except vibrate. What the hell?
That's an odd one.
Can you boot into recovery by turning phone off then holding vol- press power button and go to recovery from there? Does this do the same thing?
If same then I would uninstall ROM Manager and flash the recovery again via fastboot (in which case you can download the 3.0.2.8 version (page 3 ish of the development forum). Then try again.
Then re-install ROM Manager (which will show wrong version but ignore it).
At the moment I'm having trouble trying to turn off the phone at all :S looks like I'm actually going to have to open this horrible battery cover.
EDIT: After a battery pull I tried holding the Vol+ button and power button but it has just booted normally.
I can't actually try the vol- and power because my volume down button simply doesn't work...
EDIT 2: Uninstalled ROM Manager, reinstalled, booted into Recovery Mode, now it's backing up right next to me! Yay!
So I assume that, once it's done, I just take one big file it makes and put it on my laptop or something?
EDIT 3: Okay, one more step and I should be completely rooted with no hassles.
Will this method (http://forum.xda-developers.com/showthread.php?t=857537) work for a branded phone? It says it requires a stock kernel. My phone meets all other requirements, but is the kernel of a Vodafone AU branded Desire HD 'stock' enough to work with this S-OFF tool? I would attempt it but I'm a little worried I might screw something up.
noodlesfordaddy said:
EDIT: After a battery pull I tried holding the Vol+ button and power button but it has just booted normally.
I can't actually try the vol- and power because my volume down button simply doesn't work...
Click to expand...
Click to collapse
Is this still an issue? If so you really need to get that fixed!!
noodlesfordaddy said:
EDIT 2: Uninstalled ROM Manager, reinstalled, booted into Recovery Mode, now it's backing up right next to me! Yay!
So I assume that, once it's done, I just take one big file it makes and put it on my laptop or something?
Click to expand...
Click to collapse
Yep.
noodlesfordaddy said:
EDIT 3: Okay, one more step and I should be completely rooted with no hassles.
Will this method (http://forum.xda-developers.com/showthread.php?t=857537) work for a branded phone? It says it requires a stock kernel. My phone meets all other requirements, but is the kernel of a Vodafone AU branded Desire HD 'stock' enough to work with this S-OFF tool? I would attempt it but I'm a little worried I might screw something up.
Click to expand...
Click to collapse
You are good to go.
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.
So a friend of mine was updating ClockWorkMod and within about two reboots his phone would only flash the Samsung logo that pops up when the phone first turns on then nothing would happen (black screen). He reflashed the last version of CM stable (CM 10.1.2 for d2att) and nothing changed.
So I figure, we can just flash back to stock via ODIN but the device will only enter Download Mode for about a split second; it shows the green Android then flashes away to a black screen just like bootup. There was a video taken of the text in the corner, the flash counter was incremented and it said something like "QUALCOMM SECUREBOOT: ENABLED"
To be clear, we can enter CWM recovery just fine with no hiccups but we can't enter Download Mode or boot the device. I've tried booting into each mode with the device plugged into a computer and ADB will only recognize it in recovery mode, not in Download or normal bootup.
Is this a hardware failure? I can't tell and I'm not sure how to proceed. Would a Jig help?
Any help would be appreciated.
EDIT: It has now been discovered and confirmed that a loose power button is the culprit here.
Do you have access to a USB jig to force the phone into download mode?
audit13 said:
Do you have access to a USB jig to force the phone into download mode?
Click to expand...
Click to collapse
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
hakoda said:
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
Click to expand...
Click to collapse
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Larry2999 said:
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Click to expand...
Click to collapse
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
hakoda said:
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
Click to expand...
Click to collapse
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
audit13 said:
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
Click to expand...
Click to collapse
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
hakoda said:
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
Click to expand...
Click to collapse
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Larry2999 said:
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Click to expand...
Click to collapse
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
hakoda said:
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
Click to expand...
Click to collapse
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Larry2999 said:
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Click to expand...
Click to collapse
Can confirm that it's a stuck power button; tapping it continuously with an end of a chapstick tube while the phone booted got us all the way into Cyanogenmod; we confirmed that TWRP flashed successfully as well. However, we as soon as we stop tapping it, it goes back to the previous behavior.
We're now looking for some guides online to fix it, seems mechanical if tapping it continuously will keep it unstuck for short amount of time.
Thanks again guys
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.
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.