[Q] Fastboot isn't working, neither is recovery...

[cojomojo]

I want to return my at&t m8 back to stock (currently on stock rooted with one bad mod installed) so I can give the phone to my father. I dont have S-OFF and dont care about resetting the tamper flag. I have tried many methods to do so, the first being fastboot flashing the stock recovery, then fastboot oem lock, rebooting bootloader, then running the AT&T RUU. After i tried this several times, i noticed that the stock recovery never gets flashed even though it reports 'okay':

fastboot flash recovery recovery.img
target reported max download size of 1830723584 bytes
sending 'recovery' (24576 KB)...
OKAY [  1.789s]
writing 'recovery'...
OKAY [  0.896s]

Fastboot reboot-bootloader (both the cli command and if you go select reboot fastboot on the phone) also doesn't work, it reboots the phone normally.

Seems weird that the flash doesn't happen and that reboot-bootloader doesnt work, but nonetheless i try another method restoring a stock nandroid from http://forum.xda-developers.com/showthread.php?t=2701376 . I followed the steps, fastboot erase cache --> fastboot flash boot boot.emmc.win --> fastboot erase cache --> reboot to recovery and restore nandroid --> reboot phone. ANNDDD.... somehow I'm still on the same System/ROM as I was before all this. Also worth noting, any files I push with adb are gone after a reboot. Not sure what is going on but any help would be appreciated.

 

[jball]

So you have root permission right ?

Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]

 

[cojomojo]

So you have root permission right ?

Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]

Yes I have root.

Unfortunately anything that has to be done from the phone that isn't in the boot loader or recovery, is not an option at this point because it's in a boot loop (makes it to lock screen and then reboots). Sometimes it stops the loops and works for awhile, so if it does I'll give this a shot. However, is there any other method via adb/Fastboot over USB or TWRP?

 

[redpoint73]

Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices

If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.

You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.

You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'

But again, you need to relock the bootloader first.

 

[cojomojo]

Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices

If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.

You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.

You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'

But again, you need to relock the bootloader first.

Device id shows when i run fastboot devices . I am Positive the fastboot connectivity is not the issue here. So i am attempting to use the bootalble RUU. Since I am S-On though, I have to relock the bootloader first. When I run fastboot oem lock I get this:

(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: 			cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: 			cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.126s

And then it reboots the phone normally, it goes into its loop, I go back to bootloader, and it still shows unlocked.

Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?

 

[redpoint73]

Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?

This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.

Its odd that fastboot devices works, but fastboot oem lock fails.

Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.

 

[cojomojo]

This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.

Its odd that fastboot devices works, but fastboot oem lock fails.

Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.

Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?

EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.

 

[jball]

Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?

Try flashing the boot.img for your device from fastboot

https://www.androidfilehost.com/?fid=23329332407584494

 

[cojomojo]

Try flashing the boot.img for your device from fastboot

https://www.androidfilehost.com/?fid=23329332407584494

fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [  1.868s]
writing 'boot'...
OKAY [  0.547s]
finished. total time: 2.416s

Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.

 

[jball]

fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [  1.868s]
writing 'boot'...
OKAY [  0.547s]
finished. total time: 2.416s

Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.

After each flash "reboot bootloader"

fastboot flash boot boot.img
fastboot reboot-bootloader

fastboot flash recovery recovery.img
fastboot reboot-bootloader

Than try booting to recovery from hboot

I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.

 

[cojomojo]

After each flash "reboot bootloader"

fastboot flash boot boot.img
fastboot reboot-bootloader

fastboot flash recovery recovery.img
fastboot reboot-bootloader

Than try booting to recovery from hboot

I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.

Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:

Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [  1.855s]
writing 'boot'...
OKAY [  0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [  1.621s]
writing 'recovery'...
OKAY [  0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.010s]
finished. total time: 0.010s

Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.

Oh, and I have tried multiple USB cables for the hell of it.

 

[jball]

Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:

Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [  1.855s]
writing 'boot'...
OKAY [  0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [  1.621s]
writing 'recovery'...
OKAY [  0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.010s]
finished. total time: 0.010s

Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.

Oh, and I have tried multiple USB cables for the hell of it.

K you said you use a type of virtual machine right.

Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome

 

[cojomojo]

K you said you use a type of virtual machine right.

Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome

No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.

 

[jball]

No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.

One more ridiculous question I need to ask

Do you have fastboot unchecked through your battery/power settings

---------- Post added at 10:19 AM ---------- Previous post was at 09:54 AM ----------

@cojomojo

If nothing else works maybe try what I have over in here

http://forum.xda-developers.com/showthread.php?t=2586472

 

[redpoint73]

Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?

EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.

Strange, fastboot problems are most often a driver issue. But I agree, if you've tried it natively on Mac and PC, it would seem that drivers is not the cause.

Out of curiosity, what ROM is running on the phone currently?

 

[cojomojo]

One more ridiculous question I need to ask

Do you have fastboot unchecked through your battery/power settings

I am trying to check to see if maybe fast boot is on. I suppose it is a possibility, now I just need the phone to stay on long enough to check.

Out of curiosity, what ROM is running on the phone currently?

Running stock rooted, with one mod installed (wifi tethering). It is the 50% of the problem because it is causing the reboot loop i mentioned earlier.

******* Update **********
"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick. Thanks to all sticking with helping me out here, even as we approach 3 pages

 

[jball]

@cojomojo

Post an update if and when you fix it and what you did to fix it so others might pass in and learn.

I'm still racking my brain thinking of any possibilities it could still be

 

[cojomojo]

@cojomojo

Post an update if and when you fix it and what you did to fix it so others might pass in and learn.

I'm still racking my brain thinking of any possibilities it could still be

Will do for sure. Thanks for your help! I'm thinking I might try and get the phone on long enough to try flashify or something. Maybe try and get s-off???

 

[ashyx]

Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it, does it state so in the bootloader screen?
If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.

 

[cojomojo]

Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it? If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.

Bootloader says unlocked... so I assume it is unlocked. I suppose I could go through the unlock process again, but it definitely says "unlocked". Also TWRP flashing/restoring/anything does absolutely nothing. And I have tried 3 cables and 2 computers.

*** CLARIFICATION ****
I can get into TWRP fine, and I can restore, flash ROMS, whatever... BUT even though they report okay with 0 errors, everything stays the same, i.e. nothing in TWRP actually works. Same with Fastboot.