Develop Bugs

Can't boot into recovery/OS, only hboot/fastboot works

So..
The patient:
A completely stock HTC Desire Z.
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
What happened?
Got home, and connected the phone to my computer via USB cable to charge, as I do every time.
However this time I have also launched and forgot to exit Blizzard Authenticator app (I'm a Diablo 3 fan )), which, as I have previously noticed, causes a garbage collection extremely often (only by displaying a progress bar which is constantly moving).
There were two times previously where I left this app open and after an hour or so the phone automatically rebooted itself.
So.. it happened again: I noticed a brief vibration from the phone, as it does when it starts to boot and shows the HTC logo. So I took it in the hand to see what's happening and it was extremely hot, and after a few seconds of showing the HTC logo it rebooted, then showed HTC logo again, rebooted, and looped until I pulled the battery out.
I thought it must have some thermal protection which tries to save the phone from overheating and is constantly shutting it off. So I pulled the battery out and left it to cool-down.
After that - same thing, when you put in the battery and push the power button (or connect a USB cable), it displays the HTC logo for a few seconds and then reboots, starting a boot loop.
So, the summary:
The phone will only boot to hboot while holding down the VOLUME DOWN button.
It won't boot into recovery if I select it from the hboot/fastboot menu. It does exactly the same (boot-looping).
hboot/fasboot works perfectly fine, I am able to interact with the phone while in fastboot USB mode.
I was able to use stock RUU, it flashed everything fine, not a single error, but the result was the same - still boot-looping.
I was able to upgrade hboot and unlock the bootloader via htcdev.com and successfully flash the ClockWorkMod recovery, but still I am not able to boot to it because of boot-loop.
I tried flashing official ROM from RUU by using fastboot oem rebootRUU so that I could see what's actually happening, expecting that I ran into the same issue as a few other people on this forum (the "re-flush image immediately" issue, where the zip must have been flashed multiple times before succeeding), but no, the ROM flashed perfectly fine. And still the same result: boot loop.
So, after two days of browsing, reading, searching and trying I finally ran out of ideas.
Here goes some additional info, if it could prove useful while diagnosing the problem:
Code:
FROST:~ frost$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.2
(bootloader) serialno: SH0*********
(bootloader) imei: ***************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: low
(bootloader) battery-voltage: 3570mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.003s
Code:
FROST:Downloads frost$ fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__Y13
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: SH0*********
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=HTC__Y13 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-Nor androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0********* androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:15618 msec
* the phone reboots at this point, so naturally, USB connection is lost, causing the output below: *
Code:
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 8.358s
Any ideas of what's causing this? And/or how to fix this?
Thanks in advance.

* bump *

same problem here i just rebooted my phone and now im stuck. ive tried to flash a stock rom and it flashed successfully but wont boot to it.

Do you know if you had the bad nand ship
Sent from my Xoom using xda app-developers app

Warbuff said:
Do you know if you had the bad nand ship
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
Bad NAND chip? How could I determine that? By serial number? If so, how can I get the serial number via fastboot?
Is there any methods/logs to actually check the NAND chip for faults? Because as I said, I didn't get a single read/write error while flashing recovery/rom or booting, other than automatic reboot.

Unfortunately you don't seem to be able to use adb. Here's more info on the nand corruption problem http://forum.xda-developers.com/showthread.php?t=1051995
Also I suspect that you weren't able to fastboot flash the recovery because you don't have true s-off. Hopefully somebody with more info chimes in
Sent from my HTC Vision using xda app-developers app

Warbuff said:
Unfortunately you don't seem to be able to use adb. Here's more info on the nand corruption problem http://forum.xda-developers.com/showthread.php?t=1051995
Also I suspect that you weren't able to fastboot flash the recovery because you don't have true s-off. Hopefully somebody with more info chimes in
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info, I will follow their progress on this issue.
Yes, I am not able to use adb since I cannot boot to recovery, so all I have is fastboot.
And.. well, I was In fact able to flash the recovery, it didn't throw any errors at all, while flashing, and returned "OK".
Also I cannot boot into recovery, it keeps doing exactly the same as booting into the OS - boot looping. And it does not matter if I flash the stock recovery via RUU or try ClockWorksMod, they both flash fine, but the end result is the same - boot looping.

Just send it to HTC its makes it easier

Since it's not rooted, send it to HTC, they will fix it/ send you a new one free of charge.
Sent from my HTC Vision using xda app-developers app

Ditto
Exactly the same problem here, thought it was just me and now I find loads of people talking about it. Unfortunately being well over a year out of the 1 yr warranty I think there is effectively 0% chance HTC will do anything about it unless they have a pile of the phones laying around in a warehouse they want to get rid of. I should be so lucky.
As more and more people go to buying phone direct rather than through their carrier I think this is an opportunity for manufacturers to distinguish themselves by offering longer warranties. Yeah I know they are a volume based business so it is not in their interests for people to be holding onto phones for years and years, but I think people might actually pay attention, and there is always the resale market who might appreciate a longer warranty. Again manufacturers would probably rather you bought a new one rather than a used phone - however the ability to resell your phone does encourage people to upgrade sooner than they might otherwise have done.

I've sent mine to the HTC, they did not tell, what's exactly wrong with the phone, but they have replace the logic board.
With the warranty void/expired, I can see a couple of options:
1) Find a logic board on the net (eBay, for example) and replace it yourself (not that big of a deal, really)
2) Leave a job to some phone service shop, in case you really want to keep the phone. This could be costly, though.
After my phone was repaired, I've realized that every single HTC phone I have previously owned was flawed in one way or the other.
HTC Tornado - Windows Mobile: the joystick controller started malfunctioning and the windows mobile OS was giving me brain cancer.
HTC Magic - Android: Logic board failed after half a year of ownership. The phone won't turn on.
HTC Hero - Android: Touch screen digitizers were flawed, after some time, lower part of the screen won't register touches. Had to change two of the damn things myself.
HTC Desire Z - Android: logic board failed on 100% stock device, never been flashed, never was dropped, never got wet.
After selling Desire Z I've bought a Samsung Galaxy Nexus and I'm a happy owner of it ever since. Not a single issue with it. Very satisfied. Will try to avoid HTC, even though HTC One might look like a quality phone, I'll stick to Samsung in the future.

Update on my exchange with HTC
I reported my problem to HTC and after a couple of messages each way I got this:
I'm sorry to hear that your G2 is still not powering on properly. Where this is the case, I have to be the bearer of bad news. This phone is classified as an End of Life device. This means that we no longer have the means to repair this phone.
I apologize that I am unable to help you further with this Simon. There may be a local repair shop in your area that may be able to help you with this.
Thank you again for being a valued part of the HTC family. Have a great day!
Click to expand...
Click to collapse

Eureka
I'm pleased to report that today I grabbed my G2 as I was clearing off my desk where it has been languishing for 18 months now. I'd had the exact same problem detailed in this report and failed in all attempts to get it going again. Emails with HTC also drew a blank since they told me the G2 was end-of-life and could do nothing to help me.
On a whim instead of throwing it in the trash along with the two Li-ion batteries I decided to try booting it. Too my surprise it did boot and I was able to recover the device, update all the apps and it is now fully functional. Unbelievable! Maybe there was some capacitor that needed to drain completely, or maybe something weird happened in the last 18 months. Either way I don't care, it's good to have my G2 bac and it is still a great phone. I love that keyboard even if I loved the G1 keyboard even more!
So I'm not keeping it for use without a SIM as the remote for my TV, DVR and a Chromecast client. All the apps I need for Chromecast work perfectly on it - NetFlix, YouTube, Google Music, etc. etc.

[Q] PB31IMG Not Progressing....

Was gifted a Dinc that was stuck on boot screen, reset did nothing.
DL'd the GB PB31IMG.zip (from Doug's site), ran in HBOOT .... Update is now stuck on step 2, updating the radio.
It reads like this:
Parsing...[SD ZIP]
[1] BOOTLOADER - FAIL-PU
[2} RADIO_VZ - Updating
The progress bar on the right hand side looks to be 95% full, but nothing has changed in, oh, maybe 30 mins.
Don't want to power down quite yet and risk junking it. Maybe should have tried the Froyo stock image??

Tried the Froyo image... same result, except it passed boot loader.
Could HW issues prevent radio updating?
Sent from my ThunderBolt using Tapatalk 2

What I'm looking at.... another 30 min in. May try some older stock images.
Sent from my ThunderBolt using Tapatalk 2

Each time you power down the device during a critical update like this you have a chance of bricking. I hate to say you may have gotten a defective phone.

Yeah it's looking that way. I'm curious as to just what is defective though. It's a freebie so I'm not torn over it. I'll keep playing and see if something works.
Sent from my cm_tenderloin using xda app-developers app

Have you tried a newer ruu that will update hboot? Then you could unlock your bootloader flash a recovery, do a full wipe, and try to flash a rom. Or unlock,fastboot flash misc partition, and try to downgrade to froyo again (hopefully the radio takes), then flash recovery and then the s-off patch. However the radio not updating dosent seem like a good sign.

I think it's officially a paperweight. It won't communicate with the RUU. It will list as a fastboot device but will not pull the identifier token (just says waiting for device). Maybe that is because of the HBOOT version, though. What is the oldest version that will work with the htcdev unlock? This one is on .92.

manhatton said:
I think it's officially a paperweight. It won't communicate with the RUU. It will list as a fastboot device but will not pull the identifier token (just says waiting for device). Maybe that is because of the HBOOT version, though. What is the oldest version that will work with the htcdev unlock? This one is on .92.
Click to expand...
Click to collapse
You need at least 1.02 for the identifier token stuff to work. You should be able to flash just the HBOOT through the bootloader with the PB31IMG.zip from dinc.does-it.net (the link in cmlusco's sig).

Just attempted that and may have found the problem, although I have no clue what it means. On my way to flashing the HBOOT here's where it failed:
c:\Android>fastboot oem rebootRUU
...
(bootloader) msm_nand_erase: failed, block 4091, status 0xC001A0
(bootloader) [ERR] Bad block found: 4091
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60800 2048 0 failed (-5)
(bootloader) Mark bad block 4091 failed (-5)
(bootloader) msm_nand_erase: failed, block 4092, status 0xC001A0
(bootloader) [ERR] Bad block found: 4092
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80800 2048 0 failed (-5)
(bootloader) Mark bad block 4092 failed (-5)
(bootloader) msm_nand_erase: failed, block 4093, status 0xC001A0
(bootloader) [ERR] Bad block found: 4093
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0800 2048 0 failed (-5)
(bootloader) Mark bad block 4093 failed (-5)
(bootloader) msm_nand_erase: failed, block 4094, status 0xC001A0
(bootloader) [ERR] Bad block found: 4094
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0800 2048 0 failed (-5)
(bootloader) Mark bad block 4094 failed (-5)
(bootloader) msm_nand_erase: failed, block 4095, status 0xC001A0
(bootloader) [ERR] Bad block found: 4095
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0800 2048 0 failed (-5)
(bootloader) Mark bad block 4095 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261824): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261824
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4091
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60800 2048 0 failed (-5)
(bootloader) Mark bad block 4091 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261888): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261888
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4092
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80800 2048 0 failed (-5)
(bootloader) Mark bad block 4092 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261952): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261952
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4093
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0800 2048 0 failed (-5)
(bootloader) Mark bad block 4093 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 262016): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 262016
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4094
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0800 2048 0 failed (-5)
(bootloader) Mark bad block 4094 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 262080): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 262080
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4095
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0800 2048 0 failed (-5)
(bootloader) Mark bad block 4095 failed (-5)
(bootloader) [ERR] <Error>partition_write::Too many bad blocks(out of ran
(bootloader) ge)
OKAY [ 0.275s]
finished. total time: 0.277s
After that it shutoff. Any clue what this indicates?

Now, I don't what this is.... Tried rebooting into RUU again and had a different result:
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF6A800 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 45
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF6B000 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 46
......40 some odd iterations of this later.....
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF7F000 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 86
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF7F800 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 87
There was more, but wouldn't show in the window. It also did not shutoff this time, however the command prompt is hung and I cannot navigate the menu with the rocker. ODD

Did you try to flash the bootloader or the ruu? You can only flash a seperate bootloader if you are s-off.

I tried running the RUU executable from the htcdev site first, when that didn't communicate with the phone I tried the 'oem rebootRUU' command to try and flash the 1.07 HBOOT from there. I was thinking of trying to use the 'flash bootloader' command, but figured it wouldn't work s-on.

To use the ruu exe the phone must be booted. And as i said before you cant flash an hboot only update unless you are s-off. You need to flash this http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot. Place the file on your sdcard in no folders, named eaxctly PB31IMG.zip. Boot to hboot. It should automaticly find the file and prompt you to press vol up to install. Or you can do the fastboot oem rebootRUU way.

Right, right, right....
The thread was started because flashing the stock image PB31IMG wasn't working, a subsequent step was attempting oem rebootRUU which failed, and I acknowledged the s-on problem.
I'll try the stock image you provided to see if it takes.

Ugggh, this phone....
Well, that image progressed a little further than the first two. Passed bootloader, then...
1 RADIO_VZ - FAIL-PU
2 BOOT - OK
3 RECOVERY - OK
4 SYSTEM - Updating....
Stuck like this for 15 minutes. Seeings how the HBOOT was successfully updated to 1.07, I'm sorely tempted to pull the batt and try to unlock now. Guess I can't make it worse! Here it goes....

Correction. I made it worse. No booting of any sort now.

Not even hboot? Did the rest of the ruu complete or did you stop it?

Not even hboot. I let it sit for 20-25 minutes after I noticed it stuck "updating" then pulled the battery.
I shouldn't have flashed that image without asking for radio info (or md5 for that matter) as I think I remember reading somewhere that there is a particular radio that bricks the phone if it's flashed over itself.
Sent from my ThunderBolt using Tapatalk 2

More likely the batttery pull did it. Sadly we won't know. I hope that you can figure out something.
Sent from my Galaxy Nexus using Tapatalk 2

manhatton said:
Not even hboot. I let it sit for 20-25 minutes after I noticed it stuck "updating" then pulled the battery.
I shouldn't have flashed that image without asking for radio info (or md5 for that matter) as I think I remember reading somewhere that there is a particular radio that bricks the phone if it's flashed over itself.
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
It was radio 2.15.10.12.20 and it can be flashed over it self without issue, i have done it several times my self. The md5 is just the file url with .md5 on the end ( http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.md5 ).
All files on dinc.does-it.net have an md5.

Htc one M8 No recovery No Os

Hi
My friend some how managed messing up both the OS and recovery of the phone, he said he was using it and all of a sudden it turned off battery was about 50% and booted in bootloader so he tried every option on the screen LOL . Now it is stuck in bootloader mode whenever i try to select the recovery it comes back to the HBOOT. i have already tried unlocking the bootloader but its not working as well. I am all out of ideas as i do have an samsung and lg phone and i know a great deal about them but for htc i have limited knowledge.
i have also tried to use this RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
but every time it ends up with Error 171 Usb connection error ( i have used different usb cables and tried other usb slots as well still no luck )
i am all out of ideas now.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: INVALID_VER_INFO
version-cpld: None
version-microp: None
version-main: 4.19.61.3
version-misc: PVT SHIP S-ON
serialno: SH4AR*******
imei: 3578**********
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: ORANG001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: a7a99c85
hbootpreupdate: 11
gencheckpt: 0
any help will be greatly appreciated.

anyone????????

Look here at post #28 and #30. http://forum.xda-developers.com/show...2717928&page=3 . Download that .zip template
You can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed (change the .txt file with your CID and MID), put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM

Is the bootloader LOCKED or RELOCKED ?
Is it rooted ?
It seems that baseband is corrupted, if it is not a hardware failure, flashing a signed firmware may helps as there is no RUU available for the device version.
You need signed firmware 4.19.61.3, try to search for it.
I may have the firmware.zip in my hardisk .. will look for it later. But I do have a higher version firmware 6.12.61.4 available in my thread linked in my signature.
For S-On device, only firmware of same or higher version can be installed.
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/show...2717928&page=3 . Download that .zip template
You can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed (change the .txt file with your CID and MID), put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM
Click to expand...
Click to collapse
His device is S-On, he won't be able to do that and your link is not reachable.

ckpv5 said:
His device is S-On, he won't be able to do that and your link is not reachable.
Click to expand...
Click to collapse
You are indeed correct. My bad. Missed that bit. The link should be reachable though as I have used it this morning. Anyway, doesn't matter now.

ckpv5 said:
Is the bootloader LOCKED or RELOCKED ?
Is it rooted ?
It seems that baseband is corrupted, if it is not a hardware failure, flashing a signed firmware may helps as there is no RUU available for the device version.
You need signed firmware 4.19.61.3, try to search for it.
I may have the firmware.zip in my hardisk .. will look for it later. But I do have a higher version firmware 6.12.61.4 available in my thread linked in my signature.
For S-On device, only firmware of same or higher version can be installed.
His device is S-On, he won't be able to do that and your link is not reachable.
Click to expand...
Click to collapse
thanks for the reply, no its not rooted and its the stock S-on not unlocked or re-locked.
i am trying the 6.12.61.4 RUU i will report back if i have any success with it ,

nevermind . i think there is a hardware problem.
C:\Users\******\Downloads\Compressed\mini-sdk>fastboot oem rebootRUU
... (bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY
C:\Users\********\Downloads\Compressed\mini-sdk>fastboot flash zip firmw
are.zip
sending 'zip'... (53849 KB) [isLargeZip: 0 fileCount: 1 / 1]
Sending... 10240 KB / 53849 KB
Sending... 20480 KB / 53849 KB
Sending... 30720 KB / 53849 KB
Sending... 40960 KB / 53849 KB
Sending... 51200 KB / 53849 KB
Sending... 53849 KB / 53849 KB
FAILED (status read failed (Unknown error))

mossesmos said:
nevermind . i think there is a hardware problem.
Click to expand...
Click to collapse
It looks like it is a hardware problem. It's best to send to HTC Service Centre if it is still under warranty.

HTC M8 eye with official rom stuck in fastboot

Hey guys
Last night my phone(HTC m8 eye 5.07.401.1) slowed down badly, after a while it restarted automatically and fastboot screen showed up.
Things I've tried:
1-Restarting the phone after fully charging it for 1 billion times (worked once but the phone was frozen and restarted automatically again)
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
3-Trying to flash the official rom , didn't work
4-removing the SIM and SD card and restarting the phone, didn't work
by the way, usb debugging was not active last time the phone was working normally, Also the phone have not experienced any unusual activity like rooting or flashing custom roms or...
What can I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA00000000000
(bootloader) imei: 3580000000000000
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
------------------------------------------------------------------------------------------- fastboot results----------------------
C:\fastboot>fastboot devices
FA57LY901038 fastboot
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.041s]
finished. total time: 10.041s
C:\fastboot>fastboot flash zip update.zip
target reported max download size of 1826332672 bytes
sending 'zip' (1687274 KB)...
OKAY [ 57.179s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 118.969s
---------------------------------------------------------------------------------------

I don't have the "eye", only the "standard" M8, but I'll try to help as much as I can, as far as anything that I believe is common between the two M8 versions (unlocking bootloader, flash RUU, etc.).
bahmaniq said:
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
Click to expand...
Click to collapse
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
bahmaniq said:
3-Trying to flash the official rom , didn't work
Click to expand...
Click to collapse
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.

redpoint73 said:
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
Click to expand...
Click to collapse
Yes, *****LOCKED***** it says, I guess it is very serious on this one. Based on knowledge I gathered in these 2 days, I think it should show a black confirmation screen after I try to unlock it (using *.bin file), but it simply does not.
redpoint73 said:
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
Click to expand...
Click to collapse
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
redpoint73 said:
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
Click to expand...
Click to collapse
So, that's it, I'm gonna play "One last goodbye" and let the history judge. 2 years of EMERGENCY CALLS ONLY, 2 years of zero antenna...
After a silent peaceful night
You took my heart away
oh I wish, I wish you could have stayed

bahmaniq said:
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.

redpoint73 said:
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
Click to expand...
Click to collapse
It has been a long time since the last time I was here but the problem is not solved. Sorry for the delay, and No the black screen with HTC logo does not appear.
Is there anything I can do to get rid of this fastboot screen? or the phone is useless

Bootloop fix for Nexus 7 2013 when flashing doesn't help

This practical solution I wanted to share here after i couldn't find a solution online is for Nexus 7 devices that can boot into Fastboot. If your device can't boot into fast boot anymore try this solution by K23m from here. And if your device have instead a faulty eMMC that might need replacement or else check here instead.
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop two days ago. I used twrp recovery to wipe it all, refresh lineage os or stock ota, yet i couldn't get past the boot loop. Ill spill the beans early here, It fixed and it needed me to zero out all the free space of the eMMC. as soon as i did that i got back to a 100% reliability and fast speeds like the first time i bought it.
But first was how to boot into a working android image to download and run the zeroing utility. The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz" you can google it but ill provide this mirror link just in case it disappears.
I believe that my problem was that i had little space left and it got corrupted in some way maybe because of bad Trim process. in any case the following old factory image is small and have the highest (only?) chance to boot once and allow to reset the empty space values int he eMMC.
I started by following the process under fast boot:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15j.zip
Try booting 4 times if it doesn't work add this step before:
Download the great restore script and files from "[TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)" here at XDA and download the "Nexus7_2013_KTU84P_Restore.zip WIFI Flo" if you're like me or the other corresponding image for your Nexus 7 version.
First copy the files of the razor-jss15j-factory from the compressed archive inside the same folder as the restore archive and
Run these fast boot commands from within:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash recovery twrp-3.2.1-0-flo.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot -w
fastboot -w update image-razor-jss15j.zip
fastboot flash boot boot.img
fastboot reboot
Try booting 4 times with at least one switched off period of 20mn in between till you boot in. ( it is random and its not guaranteed it will work for you like i did for me)
I know some command are redundant and might make you think its stupid to do so but believe me when i say i spent 2 days non stop trying everything i can short of opening the device to heat gun the eMMC chip
These are the last steps i took to finally boot in and i repeated the process as i tried the first time to flash newer images in the hope they will boot too but to no avail.
Now that you booted in the old android version first go to the App Store and download a free zeroing app like" Secure Eraser " by Giuseppe Romano from the app store. after you run it twice, you can reinstall lineage os or your favourite stock version and be relieved.
I hope this amateurish post help you not discard too early your beloved Nexus 7 tablet. its only worth for me is manga reading and youtube sometimes, and for that its a wonder.

jackkill said:
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop... The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz"
Click to expand...
Click to collapse
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers

k23m said:
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers
Click to expand...
Click to collapse
Thank you k23m,
Ill add the Fresh persist solution link for those who can’t boot into Fastboot
and the link to the Hardware Nand bricks fix too
As for my experience, I did try google’s recovery firmware and steps, however it proved ineffective. At some point even the recovery partition stopped working and forced me to only use Fastboot afterward. As i looked everywhere on how to fix the stuck boot and tried the proposed software solutions with no avail, i decided to share my practical experience of what worked for me, in hope it helps someone else facing the same problem.
my Nexus 7 device is already around 4 years old and it was a discounted demo unit form a retail store, It is a fact that the amount of read write have already reached a high level that must have wore the Nand quite a bit already. However, as the secure eraser method solved the problem, I don’t believe that doing so once in the 4 years span is much of a risk in comparison. My device was on post Stock Android 4.3 most of the time and was on Lineage OS Android 7 since last year, Trim clearly failed to perform. And many sources online believe that the way Google implemented Trim isn’t complete and think that the decreasing device performance on android devices must be linked to it.
I am convinced that the problem was software, related to Trim somehow, and as the Land chip i own is a Toshiba, it can be ruled out from the known faulty Nand brand some Nexus 7 have. Moreover, no error message was displayed when performing Fastboot operations. everything was executed with success all the time.
Cheers

jackkill said:
However, as the secure eraser method solved the problem...
Click to expand...
Click to collapse
Many things happened during the repair session and I'd not credit "secure eraser" for the speed improvement.
The "secure eraser" app does not require root (to run fstrim) nor trigger TRIM ever! It just fills up empty storage space. Read the reviews - slow, horrible , inefficient. Let me propose an alternative - boot TWRP and run/install my TRIM script - it will optimize the storage space in seconds, without excessive NAND wear out - see the attachments. Run it whenever you feel that Google's TRIM algo is deficient and it's time for manual override...
:highfive:

About to give up on old Nexus 7 2013 (last ditch)
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years. The last months, I pretty only used it for podcasts via the PocketCast (best Podcast app and runs on both the major mobile OS's.)
Anyways, it had been getting caught in these bootloops off and on. The last time it successfully booted was on Sunday (4/29). That session lasted until this past Sunday until it decided to reboot on its on and hasn't been usable since.
I tried the ADB tools on a Windows 10 but the only way Windows would talk to the device was when I set it to Recovery mode with the "Install from ADB". I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.
I should add that I never installed any custom ROMs ,TWRP, or what have you. In fact, I never really paid much attention to the Android Development scene at all until the past couple of days.
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out. I got my money's from it though.
If anyone has any advice on other things to try, I'd be all ears. I'm probably going to move on try my hand with one of the Odroids.

Burgin said:
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years......
Anyways, it had been getting caught in these bootloops off and on........
I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.........
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out.
Click to expand...
Click to collapse
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Please post the output of the following commands:
turn off the Nexus
connect it to your PC
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache​
Next...
go to your folder with fastboot.exe and adb.exe
download twrp-3.2.1-0-flo.img to the folder
also unzip and copy the attached "twrp-log.bat" to the folder
in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
when TWRP is up and running (may ask for ADB driver) and you see the menu, double-click on twrp-log.bat
Note, the above steps must be done withn 3 minutes to ensure complete dmesg log
then you will find a new file twrp.txt in the folder
zip up twrp.txt and attach it to your next post
Actually, as a new XDA user you may not be able to attach files or post links, so upload twrp.txt to http://pastebin.com and post only the subpage part, eg. from https://pastebin.com/9cat4t4X7 post only this 9cat4t4X7
Cheers :good:

First, thank you for the quick reply
Moving on. My problem is I can't get anything from the fastboot command. It just says "Waiting for device".
I assume that my USB drivers are totally wrong and I need to start all over in that regard.
When I read from this page, "developer.android.com/studio/run/oem-usb#InstallingDriver", I gather that there are actually two drivers to install, one for the Google USB driver and another specifically for the Nexus 7. Am I reading this correctly? What is this second driver?
(Oh and I did manage to find what I think to be a better quality USB cable.)
k23m said:
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Cheers :good:
Click to expand...
Click to collapse

Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
fastboot getvar all
Code:
(bootloader) version-bootloader: FLO-04.08
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 32G
(bootloader) serialno: 07d98df8
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: locked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006b7ffbe00
all:
finished. total time: 0.043s
fastboot oem gpt-info
Code:
(bootloader) partition[1].name = radio
(bootloader) partition[1].first_lba = 131072
(bootloader) partition[1].last_lba = 306143
(bootloader) partition[1].size 87536 KB
(bootloader) partition[2].name = modemst1
(bootloader) partition[2].first_lba = 393216
(bootloader) partition[2].last_lba = 399359
(bootloader) partition[2].size 3072 KB
(bootloader) partition[3].name = modemst2
(bootloader) partition[3].first_lba = 399360
(bootloader) partition[3].last_lba = 405503
(bootloader) partition[3].size 3072 KB
(bootloader) partition[4].name = persist
(bootloader) partition[4].first_lba = 524288
(bootloader) partition[4].last_lba = 554287
(bootloader) partition[4].size 15000 KB
(bootloader) partition[5].name = m9kefs1
(bootloader) partition[5].first_lba = 655360
(bootloader) partition[5].last_lba = 656919
(bootloader) partition[5].size 780 KB
(bootloader) partition[6].name = m9kefs2
(bootloader) partition[6].first_lba = 656920
(bootloader) partition[6].last_lba = 658479
(bootloader) partition[6].size 780 KB
(bootloader) partition[7].name = m9kefs3
(bootloader) partition[7].first_lba = 786432
(bootloader) partition[7].last_lba = 787991
(bootloader) partition[7].size 780 KB
(bootloader) partition[8].name = fsg
(bootloader) partition[8].first_lba = 787992
(bootloader) partition[8].last_lba = 794135
(bootloader) partition[8].size 3072 KB
(bootloader) partition[9].name = sbl1
(bootloader) partition[9].first_lba = 917504
(bootloader) partition[9].last_lba = 920503
(bootloader) partition[9].size 1500 KB
(bootloader) partition[10].name = sbl2
(bootloader) partition[10].first_lba = 920504
(bootloader) partition[10].last_lba = 923503
(bootloader) partition[10].size 1500 KB
(bootloader) partition[11].name = sbl3
(bootloader) partition[11].first_lba = 923504
(bootloader) partition[11].last_lba = 927599
(bootloader) partition[11].size 2048 KB
(bootloader) partition[12].name = aboot
(bootloader) partition[12].first_lba = 927600
(bootloader) partition[12].last_lba = 937839
(bootloader) partition[12].size 5120 KB
(bootloader) partition[13].name = rpm
(bootloader) partition[13].first_lba = 937840
(bootloader) partition[13].last_lba = 938863
(bootloader) partition[13].size 512 KB
(bootloader) partition[14].name = boot
(bootloader) partition[14].first_lba = 1048576
(bootloader) partition[14].last_lba = 1081343
(bootloader) partition[14].size 16384 KB
(bootloader) partition[15].name = tz
(bootloader) partition[15].first_lba = 1179648
(bootloader) partition[15].last_lba = 1180671
(bootloader) partition[15].size 512 KB
(bootloader) partition[16].name = pad
(bootloader) partition[16].first_lba = 1180672
(bootloader) partition[16].last_lba = 1180673
(bootloader) partition[16].size 1 KB
(bootloader) partition[17].name = sbl2b
(bootloader) partition[17].first_lba = 1180674
(bootloader) partition[17].last_lba = 1183673
(bootloader) partition[17].size 1500 KB
(bootloader) partition[18].name = sbl3b
(bootloader) partition[18].first_lba = 1183674
(bootloader) partition[18].last_lba = 1187769
(bootloader) partition[18].size 2048 KB
(bootloader) partition[19].name = abootb
(bootloader) partition[19].first_lba = 1187770
(bootloader) partition[19].last_lba = 1198009
(bootloader) partition[19].size 5120 KB
(bootloader) partition[20].name = rpmb
(bootloader) partition[20].first_lba = 1198010
(bootloader) partition[20].last_lba = 1199033
(bootloader) partition[20].size 512 KB
(bootloader) partition[21].name = tzb
(bootloader) partition[21].first_lba = 1199034
(bootloader) partition[21].last_lba = 1200057
(bootloader) partition[21].size 512 KB
(bootloader) partition[22].name = system
(bootloader) partition[22].first_lba = 1310720
(bootloader) partition[22].last_lba = 3031039
(bootloader) partition[22].size 860160 KB
(bootloader) partition[23].name = cache
(bootloader) partition[23].first_lba = 3031040
(bootloader) partition[23].last_lba = 4177919
(bootloader) partition[23].size 573440 KB
(bootloader) partition[24].name = misc
(bootloader) partition[24].first_lba = 4194304
(bootloader) partition[24].last_lba = 4196351
(bootloader) partition[24].size 1024 KB
(bootloader) partition[25].name = recovery
(bootloader) partition[25].first_lba = 4325376
(bootloader) partition[25].last_lba = 4345855
(bootloader) partition[25].size 10240 KB
(bootloader) partition[26].name = DDR
(bootloader) partition[26].first_lba = 4456448
(bootloader) partition[26].last_lba = 4456463
(bootloader) partition[26].size 8 KB
(bootloader) partition[27].name = ssd
(bootloader) partition[27].first_lba = 4456464
(bootloader) partition[27].last_lba = 4456479
(bootloader) partition[27].size 8 KB
(bootloader) partition[28].name = m9kefsc
(bootloader) partition[28].first_lba = 4456480
(bootloader) partition[28].last_lba = 4456481
(bootloader) partition[28].size 1 KB
(bootloader) partition[29].name = metadata
(bootloader) partition[29].first_lba = 4587520
(bootloader) partition[29].last_lba = 4587583
(bootloader) partition[29].size 32 KB
(bootloader) partition[30].name = userdata
(bootloader) partition[30].first_lba = 4718592
(bootloader) partition[30].last_lba = 61079518
(bootloader) partition[30].size 28180463 KB
(bootloader) partition[31].name =
(bootloader) partition[31].first_lba = 0
(bootloader) partition[31].last_lba = 0
(bootloader) partition[31].size 0 KB
(bootloader) partition[32].name =
(bootloader) partition[32].first_lba = 0
(bootloader) partition[32].last_lba = 0
(bootloader) partition[32].size 0 KB
(bootloader) partition[33].name =
(bootloader) partition[33].first_lba = 0
(bootloader) partition[33].last_lba = 0
(bootloader) partition[33].size 0 KB
(bootloader) partition[34].name =
(bootloader) partition[34].first_lba = 0
(bootloader) partition[34].last_lba = 0
(bootloader) partition[34].size 0 KB
(bootloader) partition[35].name =
(bootloader) partition[35].first_lba = 0
(bootloader) partition[35].last_lba = 0
(bootloader) partition[35].size 0 KB
(bootloader) partition[36].name =
(bootloader) partition[36].first_lba = 0
(bootloader) partition[36].last_lba = 0
(bootloader) partition[36].size 0 KB
(bootloader) partition[37].name =
(bootloader) partition[37].first_lba = 0
(bootloader) partition[37].last_lba = 0
(bootloader) partition[37].size 0 KB
OKAY [ 0.289s]
finished. total time: 0.290s
fastboot format cache
Code:
fastboot format cache
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 143360 4k blocks and 35840 inodes
Filesystem UUID: 582c2894-53a4-11e8-8bf9-f98baf2837a1
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.510s]
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.522s
---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.

Burgin said:
Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
.....
fastboot format cache
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
....
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.
Click to expand...
Click to collapse
Thank you. It looks like you had to unlock it before running TWRP. I see some errors which should go away after you flash the latest factory image from fastboot. Then before you boot the fresh system, please make sure it is still connected to USB3 or a 2 Amp charger. If or when Android is up and running start an app like StabilityTest or some other heavy load benchmark tool. If there are no problems, disconnect the charger and see how it goes without it.
Your battery's stats:
Code:
<5>[ 3.908325] bq27541_get_psp voltage_now= 4040000 uV
<5>[ 3.909149] bq27541_get_capacity = 70% ret= 71
<5>[ 3.909973] bq27541_get_psp temperature= 287 (0.1¢XC)
<5>[ 3.910980] bq27541_get_psp current_now = 356 mA
<5>[ 3.911804] bq27541_get_psp charge_now (compensated) = 2235000 uAh
<5>[ 3.912811] bq27541_get_psp charge_avg (uncompensated) = 2365000 uAh
<5>[ 3.913635] bq27541_get_psp charge_full = 3161000 uAh
<5>[ 3.914611] bq27541_get_psp charge_design = 4090000 uAh
<5>[ 3.915466] bq27541_get_psp energy_now = 8067000 uWh
<5>[ 3.916442] bq27541_get_psp charge_counter = -51000 uWh
<5>[ 3.917266] bq27541_get_psp power_now = 1438000 uW
<5>[ 3.918243] bq27541_get_psp cycle count = 600
There is a huge drop of "charge_full" and very high "cycle count". I'd say the battery is definitely finished. I bet there are no problems or bootloops when it is connected to a good external power source via a short USB cable.
:highfive:

k23m said:
....
[*]in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
....
Cheers :good:
Click to expand...
Click to collapse
I am a newbie to using TWRP and this is the first time I have attempted to try a Custom ROM for my Nexus 7 2013 (flo).
The above command saved me. I was able to go into TWRP, Wipe, Advanced Wipe, and perform a Wipe of everything except the internal storage.
I then did the adb flash recovery <latest TWRP.img> and now I get the most welcome sight of the TWRP GUI.
Many many thanks.