[Q] fastboot error 99 thread - One (M7) Q&A, Help & Troubleshooting

I thought I would start a thread to address a problem that I am having, but I would imagine others are having. Here's my specifics and all that I have done to help with it. I have a T-Mo HTC ONE with baseband 4A.17.3250.20_10.40.1150.04L and the following
bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35PW905086
(bootloader) imei: 355972050436865
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3913mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Fastboot writecid returns
E0902910 E0902E20
FAILED (status read failed (Too many links))
Working on a Windows 8.1 laptop wiht intel drivers for fastboot.
Here's what I have tried to get it back to stock:
The T-Mo roll back returns an error and fails to flash. The latest firmware flashing http://forum.xda-developers.com/showthread.php?p=46513625 also returns an error 99.
I appear to be unable to roll back or forward. I would like to get it to stock so that I can warranty exchange but I am stuck. All firmware work seems to return errors. Can I try something else?

According to the info you posted, you are S-ON... As it says at the top of the firmware thread:
Requirements for flashing: S-OFF
Have you ever flashed any firmware/radios before? If you haven't, then your firmware is already stock and there's no need to touch it. All you need to do is flash the stock ROM and recovery.

gpmartinson said:
I thought I would start a thread to address a problem that I am having, but I would imagine others are having. Here's my specifics and all that I have done to help with it. I have a T-Mo HTC ONE with baseband 4A.17.3250.20_10.40.1150.04L and the following
bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35PW905086
(bootloader) imei: 355972050436865
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3913mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Fastboot writecid returns
E0902910 E0902E20
FAILED (status read failed (Too many links))
Working on a Windows 8.1 laptop wiht intel drivers for fastboot.
Here's what I have tried to get it back to stock:
The T-Mo roll back returns an error and fails to flash. The latest firmware flashing http://forum.xda-developers.com/showthread.php?p=46513625 also returns an error 99.
I appear to be unable to roll back or forward. I would like to get it to stock so that I can warranty exchange but I am stuck. All firmware work seems to return errors. Can I try something else?
Click to expand...
Click to collapse
You won't be able to downgrade or upgrade on S-On
you cannot flash or run a rom/ruu higher or lower than your current firmware
you can install rom zips using a customer recovery of higher versions without changing anything on your current firmware.
you can gain S-Off using rumrunner

Related

s-on hboot 1.54, no access to OS

I think I messed up big time:
c:\droid\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was trying to factory reset to remove device encryption and I am just dumb, really really dumb...
I typed in: fastboot oem writesecureflag 3
So now my device is on 1.54 with S-ON. I can't run rumrunner as it wants access to ADB, my ATT HTC One was the latest GPE and encrypted and now for some reason will not boot into the OS. I've tried unlocking via htcdev and I get a success message in fastboot but nothing changes. Factory reset does nothing, and I can't install the RUU.zip or use the RUU.exe, I get an error stating the signature verification failed. I get that sig verification failed with an insertcoin ROM as well. Can anyone help me?
badgcoupe said:
I think I messed up big time:
c:\droid\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was trying to factory reset to remove device encryption and I am just dumb, really really dumb...
I typed in: fastboot oem writesecureflag 3
So now my device is on 1.54 with S-ON. I can't run rumrunner as it wants access to ADB, my ATT HTC One was the latest GPE and encrypted and now for some reason will not boot into the OS. I've tried unlocking via htcdev and I get a success message in fastboot but nothing changes. Factory reset does nothing, and I can't install the RUU.zip or use the RUU.exe, I get an error stating the signature verification failed. I get that sig verification failed with an insertcoin ROM as well. Can anyone help me?
Click to expand...
Click to collapse
Do you have stock or custom recovery installed?
I had TWRP installed but now it will not boot to it via the recovery option in hboot, it just goes back into the loading google boot loop. I just tried to repush TWRP to the device but got FAILED (remote: signature verify fail)
Brought the phone to ATT and they actually gave me another one. Lesson learned.

[Q] Looking for some help S-ON, Unlocked, CWM Can't Install ROM

I'll do my best to put everything here:
I tried to root/s-off/custom rom from memory, and that is probably why I'm here.
1. I started by unlocking the phone, that was successful, installed a recovery. Started with TWRP, right now I'm on CWM.
2. Tried to install firmware to get that updated, failed, so I installed some random boot.img in my downloads dir.------I think this is where it went bad
3. Coudn't get it to SU, or to install a rom, errors ranged from:
Can't cd into sdcard (only after I copy a zip file into it)
Couldn't use firewater, revone, or rumrunner
Can't install SU​4. Tried to flash an RUU but I couldn't find the appropriate one, of course. That failed with sig failures. (followed all the right steps relocked, rebootRUU...etc)
5. tried sideloading, dont know how, looked it up and not super comfortable.
And here I am, stuck. I consider myself pretty seasoned in rooting/romming but I'm stuck.
Here is what I hope is relevant:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT355W900951
(bootloader) imei: XXXXXXXXXXXX <------------------Masked
(bootloader) meid: 00000000000000 <------------------"actual"
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OS: OSX, do have access to a PC, not at my house though. Did I break it good, is there hope?
Thanks in advance!
theomajigga said:
I'll do my best to put everything here:
I tried to root/s-off/custom rom from memory, and that is probably why I'm here.
And here I am, stuck. I consider myself pretty seasoned in rooting/romming but I'm stuck.
Here is what I hope is relevant:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT355W900951
(bootloader) imei: XXXXXXXXXXXX <------------------Masked
(bootloader) meid: 00000000000000 <------------------"actual"
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OS: OSX, do have access to a PC, not at my house though. Did I break it good, is there hope?
Thanks in advance!
Click to expand...
Click to collapse
Try this link to 4.19 RUU. Follow @Mike1986 guide for returning to stock. The guide is also a great help in flashing, rooting and installing custom ROMs. You have to correct MID & CID to run the RUU. This will put you back at stock with an unlocked bootloader.

[SOLVED] HTC One M7 unable to update to lollipop

First of all I would like to explain myself for starting another topic with this title but my problem is pretty specific and I searched the web for this and haven't found a solution yet.
So this is how it goes. I have stock telstra rom on my device and seeing as telstra isn't so keen on updating it I converted my cid and mid to europe international (HTC__001), OS- *.**.401.11, flashed firmware and changed my build.prop to match. Once I did that I got a notification of an OTA for lollipop but once it starts, in recovery it says "/system/app/DocumentsUI.apk has unexpected contents" and red triangle with exclamation point shows so the installation is aborted. My question is how do I get OTA to work on my phone without losing all the data on it? Phone is s-off, rooted and unlocked but other then that I didn't change a thing, specially not that apk.
D:\OTA M7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) meid: *
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3809mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
Click to expand...
Click to collapse
Edit: flashed stock odexed 6.09.401.12 rom and firmware and it's all good, updating right now.
-. typewrited .-

Help - Multiple Issues (No Baseband No Imei and cannot flash stock roms)

I've searched and tried everything before posting, I must be missing something.
A brief background is a while back I tried flashing CM12.1 and when I did I lost my baseband(baseband unknown) and IMEI unknown, therefore I tried to flash back to stock using an official RUU.exe, but wound up in a bootloop (wiped dalvik). I was unable to boot into recovery because my volume down button did not work.
Recently I replaced the Flex board for the volume button and tried to get the phone operational again thinking that if I flash a stock rom it would give me back my baseband and imei, but I cannot flash anything stock. If I flash anything stock I wind up in a bootloop, I've tried RUU.exe's, RUU.zip's, Nandroid Backups, etc. sometimes I get "System Process not responding" message, not sure of the exact message but it gives me a choice to "wait" or "ok", but just shuts down after making either selection. I recently was able to get a little further with a development rom, in which I made it to the android unlock screen, but as soon as went to unlock it the phone rebooted.
I've tried all of this with the bootloader locked and locked, cleaning the dalvik and other caches. I've performed complete wipes with SuperWipe, but the problem still persists, I cannot flash anything Stock. I am able to flash Android Revolution HD 93.0, but still no baseband or IMEI.
The phone is S-Off
Any Ideas what I am doing wrong?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **EDITED OUT**
(bootloader) imei: **EDITED OUT**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4071mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s
Thanks
I don't know if anyone can help me or if there is much support here anymore, but here is an update.
After I posted my original message I noticed that there was something wrong with the bootloader variables, I've fixed by flashing an FUU and matching RUU. I still have the Unknown Baseband and Unknown IMEI in Revolution HD. With the stock RUU I flashed along with the FUU I still get a bootloop. I am able to get past it by holding the volume up or volume down for Safe Mode during the boot process, but as soon as I unlock the screen I am brought back to white HTC boot screen.
Here are the updated bootloader vars:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.1540.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Edited
(bootloader) imei: Edited
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.102s
isnt ARHD 93.0 require lollipop firmware, so your bootloader must be 1.61?
Thanks I will try and flash tomorrow and report back.
Sent from my SAMSUNG-SGH-I337 using XDA-Developers mobile app
I flashed the FUU that contained Hboot 1.61 and ARHD93, but still have the same issues with the Unknown Baseband and IMEI.
The thing is that I am really not sure which FUU to use, for this flash I used 7.19.401.51_WWE_TWRP2870.
Here is new boot loader dump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *Edited*
(bootloader) imei: *Edited*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4048mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
spillb said:
I flashed the FUU that contained Hboot 1.61 and ARHD93, but still have the same issues with the Unknown Baseband and IMEI.
The thing is that I am really not sure which FUU to use, for this flash I used 7.19.401.51_WWE_TWRP2870.
Here is new boot loader dump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *Edited*
(bootloader) imei: *Edited*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4048mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Click to expand...
Click to collapse
it seems like you are having the same problem as mine. I havent found any fix yet. You can try Cyanogenmod roms, it works for me
Do you have baseband and imei?
Which CM are you using
Sent from my SAMSUNG-SGH-I337 using XDA-Developers mobile app
spillb said:
Do you have baseband and imei?
Which CM are you using
Sent from my SAMSUNG-SGH-I337 using XDA-Developers mobile app
Click to expand...
Click to collapse
i dont have imei and baseband on sense and GPE rom, but i have them on CM roms
Currently im using CrDroid
kyeljnk said:
i dont have imei and baseband on sense and GPE rom, but i have them on CM roms
Currently im using CrDroid
Click to expand...
Click to collapse
Thanks, I am going to flash it an see if I get the same
I tried it but still same problem. Can you tell which hboot and rom versions you are using?
Sent from my SAMSUNG-SGH-I337 using XDA-Developers mobile app

Phone bootloops, tried installing roms, all bootloop, errors when trying RUUs.. help

A friend gave me his HTC ONE M7 to fix, he had a bootloop problem.
I tried unlocking bootloader, getting a custom recovery and installing a rom (with flashing boot.img in fastboot), but they all bootloop.
I tried to install RUUs, exe's give me error 170/171/155 or crash and zip files give me "FAILED (remote: 02 data length is too large)" or they just freeze Command Prompt and close.
Phone is now relocked and S-ON, on Windows 7 (cause fastboot didnt find device on win10 for some reason) and I use a USB Port 2.0 just in case.
I have to mention that its my first time working on a HTC device, and I might not know what RUU to take or I miss something, the last one I tried was:
i.imgur.com/lkUR356.png
also getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
XRED1 said:
A friend gave me his HTC ONE M7 to fix, he had a bootloop problem.
I tried unlocking bootloader, getting a custom recovery and installing a rom (with flashing boot.img in fastboot), but they all bootloop.
I tried to install RUUs, exe's give me error 170/171/155 or crash and zip files give me "FAILED (remote: 02 data length is too large)" or they just freeze Command Prompt and close.
Phone is now relocked and S-ON, on Windows 7 (cause fastboot didnt find device on win10 for some reason) and I use a USB Port 2.0 just in case.
I have to mention that its my first time working on a HTC device, and I might not know what RUU to take or I miss something, the last one I tried was:
i.imgur.com/lkUR356.png
also getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Use the 7.19.401.51 ruu, the same from your screenshot. You must use the fastboot version linked at post #1 of that thread otherwise you'll get the data length error.
alray said:
Use the 7.19.401.51 ruu, the same from your screenshot. You must use the fastboot version linked at post #1 of that thread otherwise you'll get the data length error.
Click to expand...
Click to collapse
Thank you for your time, I spent a lot of time on it and I was too tired to see that I need that fastboot version.
Phone works now. Thanks again.

Categories

Resources