Hi all,
I'm a bit stuck. Went to sleep last night with a working phone. Woke up this morning with the device turned off, and trying to turn it on always bumps me into Fastboot. I'm guessing my custom ROM tried and failed to update overnight...?
I can run fastboot commands, but trying to boot using a boot.img from a downloaded ROM (fastboot boot boot.img) still kicks me into Fastboot. Tried installing a Stock ROM, and the full install goes through, but still reboots to Fastboot.
I've downloaded the MSM tool and EDL package to see if I can get that to work, but you guessed it, I can't get into EDF mode (holding both vol buttons and connectting the phone sends me to Fastboot).
Anyone any ideas
Arran
In my case I fixed it by swapping to the other slot...
getvar current-slot to see the active partition
fastboot --set-active=a to set partition a instead.
Rebooted - all OK
Related
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.
Hello everyone,
i think my OP3 is bricked, cuz after i wanted to install new custom ROM with TWRP it went south. When I swiped to install the ROM it showed, it´s corrupt so i wanted so i wanted to push some other .zip to the phone through adb, but no device showed after adb devices or fastboot devices in fastboot. So I tried restore phone from backup i had via TWRP and the phone just wouldnt boot. Oneplus logo showed for a few seconds then it disappears and phone goes dark. Have to hold start button for 10 sec for hard restart phone and then i can go only to fastboot (now it will show fastboot devices in command line). Recovery won´t boot. Tried flashing stock recovery, some versions of TWRP and still just OP logo and dark.
Thanks for every help.
I think for:
fastboot -w
fastboot flash recovery recovery_of_ur_choice.img
on flashboot mode obviously ^^
With that, u must have access to twrp
Hi,
A few days ago I woke up with battery at 1% asking to enter extreme mode and after I did some charging I noticed my battery is draining fast. Then I decided to restart my phone and it went into a bootloop.
I restarted this phone previously without any problems.
Now I can't enter download or recovery mode. I can only use fastboot on bootloader menu but not adb cause I can't enter download mode (adb shows no devices but fastboot shows).
My phone bootloader is locked, S-oFF production. Everything is stock, never changed anything.
Tried fastboot oem rebootRUU didnt work.
Tried fastboot boot recovery.img and failed as I need unlocked bootloader
fastboot oem unlock/lock shows unknown command
fastboot flash hosp hosp.img also didn't work
fastboot flash boot recovery.img didn't work.
All of them lead to a small HTC logo in the middle but then return to the bootloop.
I also tried removing SD card and rebooting but didn't work.
Is there any solution to this problem? Thanks.
A wild shot..
ttimt96 said:
Hi,
A few days ago I woke up with battery at 1% asking to enter extreme mode and after I did some charging I noticed my battery is draining fast. Then I decided to restart my phone and it went into a bootloop.
I restarted this phone previously without any problems.
Now I can't enter download or recovery mode. I can only use fastboot on bootloader menu but not adb cause I can't enter download mode (adb shows no devices but fastboot shows).
My phone bootloader is locked, S-oFF production. Everything is stock, never changed anything.
Tried fastboot oem rebootRUU didnt work.
Tried fastboot boot recovery.img and failed as I need unlocked bootloader
fastboot oem unlock/lock shows unknown command
fastboot flash hosp hosp.img also didn't work
fastboot flash boot recovery.img didn't work.
All of them lead to a small HTC logo in the middle but then return to the bootloop.
I also tried removing SD card and rebooting but didn't work.
Is there any solution to this problem? Thanks.
Click to expand...
Click to collapse
Have you tried a "Power Off" ... wait 10 to 20 secs ... then hold "vol down" and "power" at same time. See the little "HTC" twice before you release the buttons. That should put you in boot loader mode. Then we can go from there. If it doesn't then I don't know what to do. It is how I have recovered from my catastrophes... and I have had similar instances like yours.
Hi. When i turn the phone on, it goes automatically to fastboot mode. Since I flashed something wrong in TWRP, i can not get out from fastboot. Also i can not flash any fastboot roms with miFlash, it ends always with a failure, no such file or directory.... I downloaded the fastboot rom, i extracted it, selected it, refresh+flash but nothing helps. What now?
Adb fastboot current slot is ‘b’, but after restart comes fastboot mode again.
what happens when you boot the other?
fastboot --set-active=a
And restarting can't exit fatsboot mode, it seems that bl detects that your phone has a bootloop, and then enters fastboot mode, usually this requires me to use fastboot to flash the boot partition.
I am using crDroid v7.15 system with InfiniR Alioth v2.06 kernel.
Reflash kernel, you probably switched partition ...
boot tempory recovery and flash kernel
snx413 said:
Reflash kernel, you probably switched partition ...
boot tempory recovery and flash kernel
Click to expand...
Click to collapse
I rebooted 7 times in a row and the 8th reboot seems to go into fastboot mode.
Usually everything works fine after I write to the boot partition in fastboot mode.
It seems to enter fastboot mode in this state, long pressing the power key does not bring the phone back to normal, the device must be rebooted using fastboot reboot in the command line.