Related
How can I root my HTC EVO 3D with Software number 1.20.401.8 and HBOOT 1.49.0018?
The HTC rooting method does not work since the HBOOT version has to be 1.5 or higher. Also, in order to use the Revolutionary method I'd have to downgrade my HBOOT, which isn't possible right now because the download link from the tutorial I found on XDA is dead.
Is there any other way to root my phone or downgrade the HBOOT? My 3D is an european GSM model.
Hello,
I also own an EVO with 0018 hboot, i folowed htcdev.com to unlock it with succes.
After that i flashed a new recovery and then flashed the Root and SuperUser package found here...
I folowed this thread : http://forum.xda-developers.com/showthread.php?t=1248231
with CWM recovery and changed it to 4ext.
I am still S ON so i can't flash kernels within my phone but it works via fastboot.
When I try to unlock the bootloader following the instructions from htcdev.com I always get the "FAILED (remote: signature verify fail)" error..
i cannot help you more for HTC DEV it worked fine for me without any problem.
the message you got looks like you try to flash a unsigned zip witch can't be possible if you are with a stock phone and try to unlock by the "offcial method..."
here's the ling for revolutionnary method, maybe it can help :
http://revolutionary.io/
I know about the Revolutionary method, but in order to use it I have to downgrade my hboot version, which cannot be done at this moment since the link to the files necessary for downgrading is dead.
You only need RUU or zip, nothing else. I can upload them, if you want.
Odoslané z môjho HTC EVO 3D X515m
I would be thankful if you would reupload PG86IMG.zip, the multiupload file has apparently been deleted.
The first thing you need to do is head over to HTC dev and sign up and also this is where you will unlock you bootloader you must do this first before anything else
Sent from my EVO 3D x515m s off using xda premium
I signed up at htcdev.com and tried to unlock the bootloader using the HTC Method, it didn't work. I already mentioned that a few posts above.
tudorc11 said:
I signed up at htcdev.com and tried to unlock the bootloader using the HTC Method, it didn't work. I already mentioned that a few posts above.
Click to expand...
Click to collapse
Make sure that when you paste the unlock code on the website, there aren't any spaces left. I made the same mistake, whereafter I got the same error message. If you follow the steps exactly, nothing can go wrong. I'm rooted, unlocked and s-on on the same hboot as you.
I retried unlocking the bootloader using the HTC Method from another computer and I get the same error. This is a copy of my cmd window:
Code:
C:\Dokumente und Einstellungen\Administrator>cd c:\root
C:\root>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) A6EA05FD98BC96AF6FA35914CD3F79AA
(bootloader) E243200A6AD29FF21665DCEBEE9E405C
(bootloader) 8B5144B9E1A43EF3A835A7C09C1C9796
(bootloader) B64B64642D25612E884E0C03301B1D43
(bootloader) 8AA2A6735187D3C6AE39DD90A621D62B
(bootloader) BFCF55A26252FA5EE49D1A6695ABAAF6
(bootloader) 51458894BB871934F37594ABED7124CB
(bootloader) 65FC23BB8406A279A7309246A09947DE
(bootloader) BA56EC429CD70D616725045ED4337871
(bootloader) DA7D40190452958CDB4532873BF5C27D
(bootloader) 66275FCF5ED6063BA271CC02B929AEED
(bootloader) 4783DA145877266B0A53BCB7D8C8905A
(bootloader) D397DFAA01DBABABA5FAF0F616F69E02
(bootloader) 4C91A6398A23DA1990150AE70E3326B1
(bootloader) A4DE78A8F3DE3563AFB7DDC0AF965C75
(bootloader) E34C75D5D234AED42223A8B3B45EA0EB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\root>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.141s
Any suggestions?
Manages to root it using the Revolutionary method after finally downgrading my hboot version, problem solved .
Hello there!
I got a HTC Evo 3D some months ago. I unlocked it via htcdev.com, got root, deleted som Apps i dont like and everything was fine.
Today i wanted to revert it to factory settings, but something went wrong.
I used the CWM-Factory-Reset function, everthing was fine except the missing apps i deleted. So I decided to flash a standart Rom and downloaded RUU_Shooter_U_Vodafone_UK_1.21.161.1_Radio_10.53.9020.00_10.13.9020.08_2M_release_203613_signed because it`s the only Vodafone-Rom i found, but it didn`t work.
Maybe the next step was my big mistake:
C:\evo\krams>fastboot flash boot boot_signed.img <-- from the vodafone uk-rom
sending 'boot' (3546 KB)...
OKAY [ 0.811s]
writing 'boot'...
OKAY [ 1.796s]
finished. total time: 2.623s
since then it`s stuck in the bootloop (htc-logo, black, htc-logo ...)
i was happy a when i found RUU_Shooter_U_Vodafone_CH-DE_1.21.166.1_Radio_10.53.9020.00_10.13.9020.08_2M_release_203615_signed a few moments ago but it also didn`t work
What I tried:
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.9020.00_10.15.9020.06_M_release_219793_signed
RUU_Shooter_U_Vodafone_CH-DE_1.21.166.1_Radio_10.53.9020.00_10.13.9020.08_2M_release_203615_signed
RUU_Shooter_U_Vodafone_UK_1.21.161.1_Radio_10.53.9020.00_10.13.9020.08_2M_release_203613_signed
unlocked and relocked
RUU and renamed to PG86IMG.zip
http://forum.xda-developers.com/showpost.php?p=40025870&postcount=5
The Yoda-Installer starts but afaik i need s-off to flash custom roms?
but nothing works
What can i do? Maybe i need only the right RUU / Rom?
Some more Informations:
Vodafone_uk htc evo 3d x515m Smartphone
fastboot works
CWM Recovery seens to work
Locked/Relocked
S-On
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
C:\evo\krams>fastboot getvar version-main
version-main: 3.28.161.3
finished. total time: -0.000s
C:\evo\krams>fastboot oem readcid
...
(bootloader) cid: VODAP102
OKAY [ 0.005s]
finished. total time: 0.007s
"Neuer Tag, Neues Glück" -> New Day, New Luck
Started testig about 5 Minutes ago, flashed "boot.img" rom the Yoda-Rom (yoda_ICS_v8.5.zip\Kernels\stock) and it works
I don`t know why the Vodafone-Kernel didn`t work, but i don`t care anymore
the boot.img from vodafone UK rom was for gingerbread whereas you are probably trying to boot an ics rom so it wont work. yodas kernel is for ics which is why it booted. best thing to do is make a nandroid of your current rom and back it up on your pc. that way you can restore any part of your current rom(boot / system / data etc) when something goes wrong.
I was going through the steps to try to flash the Google Edition ROM onto my T-Mobile HTC One using this guide: http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
I have unlocked the bootloader, rooted, and gotten S-off. I'm on Step 3, changing the model ID if necessary. The guide says the model ID needs to be PN0712000, and mine is PN0713000. So I went to the guide he linked to: http://forum.xda-developers.com/showthread.php?t=2322820
In this guide, I downloaded the PL83IMG.zip and edited the text file to put in my current Model ID, Cell ID, and ROM version. Rezipped, then did the command he gives:
Code:
c:\sdk-tools>fastboot flash zip android-info.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.401s]
finished. total time: 2.653s
Ok, now as he says in the guide, I saw the HTC logo and a progress bar that was sitting at about 3/4 done. He says to reboot the phone, so I did this. The screen remains blank, I don't get the gray spotted screen he describes. I tried the "fastboot oem writemid PN0712000" command, and it just sat on "< waiting for device >" for a long time, until I finally cancelled the command.
I do hear my computer make the noise that a device is connected and disconnected when I plug in and unplug the phone. Also if I hold down the power and volume down button, the phone vibrates and makes a noise after a few seconds. Nothing will appear on the screen though, and any adb or fastboot commands I try don't seem to see the device.
So...is my phone bricked? Is there some way I can recover from this?
OK! I managed to get into the bootloader by holding down power and volume down...I don't know why it didn't do this when I tried it before.
I still can't get the adb and fastboot tools to recognize the device, however. When I go into fastboot in the bootloader, Windows gives a pop up saying that "the last USB device connected to this computer malfunctioned, Windows does not recognize it." It momentarily says FASTBOOT USB on the phone, but then drops back to just FASTBOOT.
So all I can do is get into the bootloader. I can't boot to recovery or normal boot, the screen just stays blank. And I can't get the device to be recognized on my computer, so I can't do anything with adb or fastboot. Should I try a factory reset?
kernco said:
Dammit, I thought I was in the T-Mobile area...how did that happen? Sorry. I'll repost this there.
It says in that tutorial "The command is fastboot getvar modelid. If it model ID doesn't match ours (PN0712000), you'll need to change it"?
Click to expand...
Click to collapse
"
Step 3: Change Your Model ID (if Necessary)
Edit: Changing your MID is actually not necessary, even if you have a different Model ID. I'll leave this here just in case you want to check, and because we still need to connect our phone and open a command prompt."
Seems pretty straight forward that you don't NEED to change the MID, even if it's different.
maybe there was an update in the site?
I would NEVER mess with changing my MID personally changing, CID is no issue.
but, if you really want your phone to be GPE, I guess I would change my MID, it seems quite simple with S-OFF.
Then just flash the RUU and you are as good as a GPE phone.
oh, and PLEASE learn what a brick means...
if your phone turns on in anyway, it isn't bricked...
bricked means no screen, no charging light, nothing, it is literally,.. a brick.
kernco said:
I will try this, but I don't think this is the problem. My bootloader screen is still showing my model as PN0713000, which was my original model ID. And I didn't flash an RUU yet...maybe that was my mistake.
Click to expand...
Click to collapse
why did you flash the old hboot? the tutorial IIRC doesn't say anything about touching the HBOOT for the GPE guide?
It sounds like you haven't done anything harmful, your MID is the same you say.
CID, doesn't really matter, as long as you are on your stock or super cid. for now I would super cid..
Have you tried just going into recovery and doing a full wiping and installing a nandroid you have saved (or so I'd hope)
Try another cable that sometimes helps to get the CPU to see the computer.
you basically need to get adb commands working, superCID, then get a STOCK RUU for your phone, flash that. and you should be good to go.
andybones said:
why did you flash the old hboot? the tutorial IIRC doesn't say anything about touching the HBOOT for the GPE guide?
It sounds like you haven't done anything harmful, your MID is the same you say.
CID, doesn't really matter, as long as you are on your stock or super cid. for now I would super cid..
Have you tried just going into recovery and doing a full wiping and installing a nandroid you have saved (or so I'd hope)
Try another cable that sometimes helps to get the CPU to see the computer.
you basically need to get adb commands working, superCID, then get a STOCK RUU for your phone, flash that. and you should be good to go.
Click to expand...
Click to collapse
Flashing the hboot was in the guide linked to from the GPE guide about changing the mid.
I may be making progress though. I booted into my boot camp partition on my macbook and installed HTC Sync Manager there. Fastboot can see the device now, but adb still can't. I changed the cid with fastboot (won't bother with the mid now) and am currently downloading the GE ROM onto this laptop. Hopefully I can flash it and everything will be good again.
Alright...so my problem now is that when I do the "fastboot oem rebootRUU" command, the phone's screen goes off and stays off. I tried doing the command to flash the ROM anyway, and it just sat on "waiting for device". What is supposed to happen after the "fastboot oem rebootRUU" command?
Alright, so I redid the procedures to unlock the bootloader and root, reflashed the recovery, and now my phone is in a usable state again! I can boot to the Sense ROM and into the recovery no problem.
Maybe the smart person would just settle for being back where I started, but I still would like to get the GE ROM onto this phone, especially since I've changed my CID already. I don't know if that will cause problems if I stay on the stock Sense ROM (I still haven't put my SIM card back into the HTC One from my backup phone). I'm getting this problem when I try to flash the GE rom:
c:\sdk-tools\sdk-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 25.964s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 26.411s
So...do I need to change my model ID after all? As was pointed out to me earlier in this thread, the guide I'm following has an edit indicating it shouldn't be necessary. It does say "S-off" on my bootloader, just to confirm that.
Ok, I got the GE ROM flashed by changing the model ID in the android-info file in the ROM to match my device. Got my sim card in and can make calls and send/receive texts. The OTA update to Android 4.3 (I used the 4.2 GE ROM) downloaded and installed. Everything seems to be working.
Similar issue
Hi All, posting here, cause my problem is very similar.
My phone is verizon.
Here's what happens:
I get success with the whole hboot thing:
Code:
c:\sdk-tools>fastboot flash zip PN0731000.zip
sending 'zip' (474 KB)...
OKAY [ 0.245s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.277s]
finished. total time: 2.527s
My problem is after - when I reboot the phone, I get the grey fuzzy screen, and than I get this:
Code:
Code:
c:\sdk-tools>fastboot oem writemid PN0710000
...
(bootloader) Main MID does not match [PN073] or [PN073]!
OKAY [ 0.018s]
finished. total time: 0.020s
What do I do here? The reason I want to change the mid ofcourse is because I want OTA updates in Google Play Edition. Is there a fix for this? Is there a workaround?
Your thread is now in the AT&T HTC One Q&A
Apologies for the newbie (and probably already answered question), but I cannot find this question asked and answered explicitly:
Does going from an already S-OFF GPe conversion (via the GPe 4.3 RUU) to the T-Mobile 4.3 RUU (to get the 4.4 OTA) reset me back to S-ON?
I want to go back to T-Mobile stock 4.4 (want to give Sense another chance), but still be able to run the GPe 4.4 RUU and get back to where I am right now if I don't like it.
Thanks very much.
FayezZ said:
Apologies for the newbie (and probably already answered question), but I cannot find this question asked and answered explicitly:
Does going from an already S-OFF GPe conversion (via the GPe 4.3 RUU) to the T-Mobile 4.3 RUU (to get the 4.4 OTA) reset me back to S-ON?
I want to go back to T-Mobile stock 4.4 (want to give Sense another chance), but still be able to run the GPe 4.4 RUU and get back to where I am right now if I don't like it.
Thanks very much.
Click to expand...
Click to collapse
Running the 4.3 tmo RUU didnt change my s-off or bootloader state at all. After running RUU, I was able to push TWRP and go back to business as usual.
Is there a TMO stock 4.3 i can flash with twrp that will get me the OTA ? Or do I need stock recovery that came with 4.3?
BurnOne77 said:
Is there a TMO stock 4.3 i can flash with twrp that will get me the OTA ? Or do I need stock recovery that came with 4.3?
Click to expand...
Click to collapse
RUU needs stock recovery. just relock boot loader, RUU, take OTA, unlock/root/flash TWRP & profit
No need to even relock. stock recovery is all you need. My phone was was unlocked and rooted and i got the updates no problem. I was also S-OFF before I updated (from hboot 1.44), still S-OFF after 4.4.2 update.
Appreciate the feedback, everyone - thank you.
So, here's a follow-up question (and I'm still being a newbie here, unfortunately): I've flashed the T-Mobile 4.3 RUU (took a very long time to figure all that out; had to downgrade firmware, flash the rom.zip directly, etc.) and subsequently manually applied the 4.4 OTA via stock recovery. Before doing the RUU, I re-locked bootloader (so it now says "Relocked"). I'm still S-OFF. Now my issue is that I can't flash a custom recovery to get root because my bootloader is locked.
Is there an easy way to unlock bootloader (HBOOT 1.56 now)? I know I can go the "official" HTCDev way, but wanted to check and see if there's something easy/obvious/non-warranty voiding way first.
Thanks!
I've gotten the unlock bin file from HTCDev for two phones with absolutely no issues. You should try to do the same. The process is very simple, just follow their guide...
http://www.htcdev.com/bootloader
Choose 'All other supported models' at the bottom of the list.
shpitz461 said:
I've gotten the unlock bin file from HTCDev for two phones with absolutely no issues. You should try to do the same. The process is very simple, just follow their guide...
http://www.htcdev.com/bootloader
Choose 'All other supported models' at the bottom of the list.
Click to expand...
Click to collapse
Thank you. I ended up doing this because I figured it was a safer way to do what I needed without fumbling my way through non-official methods. Worked great. I'm now on TMo 4.4 and rooted, just like I was hoping to be.
having issues
I'm trying to achieve the same thing, but I'm having trouble flashing the stock recovery. I keep getting, "could not open recovery.img"
My phone is;
s-off
hboot 1.54
android 4.1.2
software # 1.27.531.11
Maybe unrelated, the kernel version is;
3.4.10-g04f3908
[email protected] #1
SMP PREEMPT
I'd be cool if you guys helped w/ fixing that too!
ilikecars212 said:
I'm trying to achieve the same thing, but I'm having trouble flashing the stock recovery. I keep getting, "could not open recovery.img"
My phone is;
s-off
hboot 1.54
android 4.1.2
software # 1.27.531.11
Maybe unrelated, the kernel version is;
3.4.10-g04f3908
[email protected] #1
SMP PREEMPT
I'd be cool if you guys helped w/ fixing that too!
Click to expand...
Click to collapse
You can start by telling us how you went on trying to flash the recovery...
Regardless of recovery, your firmware appear to be very old, I recommend you update that as well.
Are you on stock ROM? Didn't you get OTA notifications about upgrades?
Settings > About > System Updates
shpitz461 said:
You can start by telling us how you went on trying to flash the recovery...
Regardless of recovery, your firmware appear to be very old, I recommend you update that as well.
Are you on stock ROM? Didn't you get OTA notifications about upgrades?
Settings > About > System Updates
Click to expand...
Click to collapse
First off, thanks for helping.
I downloaded the stock recovery img, renamed it recovery, then tried "fastboot flash recovery recovery.img"
The img file is in my fastboot folder.
I am getting OTA notifications about upgrades, but they say the updates can't be installed after they are downloaded.
How do I go about updating my firmware?
I do have TWRP if that makes anything easier.
I'm very new to this if you cant tell. I bought my One used, and seller didn't say it was rooted and s-off in the listing.
Stock OTA will not work with a custom recovery (like TWRP or CWM). You have to flash stock recovery.
Boot into bootloader and do this:
fastboot getvar all
Click to expand...
Click to collapse
Paste the output, make sure you remove IMEI and serialno.
---------- Post added at 08:39 PM ---------- Previous post was at 08:31 PM ----------
You should also follow the guide here: http://forum.xda-developers.com/showthread.php?t=2355814
And flash to latest firmware (which includes stock recovery, which will allow you upgrade via OTA).
shpitz461 said:
Stock OTA will not work with a custom recovery (like TWRP or CWM). You have to flash stock recovery.
Boot into bootloader and do this:
Paste the output, make sure you remove IMEI and serialno.
---------- Post added at 08:39 PM ---------- Previous post was at 08:31 PM ----------
You should also follow the guide here: http://forum.xda-developers.com/showthread.php?t=2355814
And flash to latest firmware (which includes stock recovery, which will allow you upgrade via OTA).
Click to expand...
Click to collapse
Sorry it took me a few days.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.58.1700.5
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0713000
cidnum: t-mob010
battery-status: good
battery-voltage: 3926mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
I followed the guide in the link you posted. I downloaded the 1.27.531.11 firmware file since it matches my software version. Then...
C:\SDK>fastboot flash zip firmware.zip
error: cannot open 'firmware.zip'
ilikecars212 said:
version-main: 3.58.1700.5
I followed the guide in the link you posted. I downloaded the 1.27.531.11 firmware file since it matches my software version. Then...
C:\SDK>fastboot flash zip firmware.zip
error: cannot open 'firmware.zip'
Click to expand...
Click to collapse
The firmware is 3.58.1700.5, not what is shown in Settings>About. What is shown in Settings is the software side of things. getvar in fastboot shows the hardware side of things.
The error you got indicates that firmware.zip is not in the folder you're in (C:\SDK). Either copy the zip over to C:\SDK or just specify a path in the fastboot command.
I think it's better to stick with a recovery image that is closer to your actual hardware firmware version (3.58), but i'm not 100% sure it makes any difference.
shpitz461 said:
The firmware is 3.58.1700.5, not what is shown in Settings>About. What is shown in Settings is the software side of things. getvar in fastboot shows the hardware side of things.
The error you got indicates that firmware.zip is not in the folder you're in (C:\SDK). Either copy the zip over to C:\SDK or just specify a path in the fastboot command.
I think it's better to stick with a recovery image that is closer to your actual hardware firmware version (3.58), but i'm not 100% sure it makes any difference.
Click to expand...
Click to collapse
I definitely had the firmware.zip folder in the same file that has adb and fastboot apps. I've gotten the same error when trying to flash just the stock recovery img. This is why I'm so confused.
NVM. Figured it out for the moment.
I'm officially back to being confused.
C:\SDK>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.111s]
finished. total time: 0.112s
C:\SDK>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (41648 KB)...
OKAY [ 3.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.728s
C:\SDK>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.105s
C:\SDK>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9596 KB)...
OKAY [ 1.234s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.270s
Click to expand...
Click to collapse
ilikecars212 said:
I'm officially back to being confused.
Click to expand...
Click to collapse
Once you switch to RUU mode, I don't think you can flash non-zipped firmware files.
Code:
C:\SDK>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (41648 KB)...
OKAY [ 3.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.728s
Once you had this fail the 1st time, you should've flashed the zip again immediately. You rebooted instead.
So do it again, but flash the same zip twice. That should do it.
Oh, and another thing, The zip you tried to flash doesn't match your model ID. Your getvar reports the phone to be T-Mobile, but you're trying to flash non-T-Mobile firmware.
You need to get the stock TMO firmware that matches your phone:
modelid: PN0713000
cidnum: t-mob010
Click to expand...
Click to collapse
Finally, since you're S-OFF, you can change your CID to the superCID (11111111), this will allow you to flash ANY firmware you'd like.
With your currect CID (t-mob010) you can only flash firmware that matches 't-mob010'.
shpitz461 said:
Once you switch to RUU mode, I don't think you can flash non-zipped firmware files.
Code:
C:\SDK>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (41648 KB)...
OKAY [ 3.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.728s
Once you had this fail the 1st time, you should've flashed the zip again immediately. You rebooted instead.
So do it again, but flash the same zip twice. That should do it.
Click to expand...
Click to collapse
I tried reflashing it 5 times before rebooting, I just went through the steps I took quickly to show what my problem is.
I get the same failure message every time.
Also, I don't understand what you're getting at when you mentioned only being able to flash .zip files in RUU mode. I only tried flashing a .zip file. When I tried flashing the recovery.img I put the phone back into fastboot.
Any more suggestions? Thank you for helping me
shpitz461 said:
Oh, and another thing, The zip you tried to flash doesn't match your model ID. Your getvar reports the phone to be T-Mobile, but you're trying to flash non-T-Mobile firmware.
You need to get the stock TMO firmware that matches your phone:
Finally, since you're S-OFF, you can change your CID to the master CID (11111111), this will allow you to flash ANY firmware you'd like.
With your currect CID (t-mob010) you can only flash firmware that matches 't-mob010'.
Click to expand...
Click to collapse
I unzipped the firmware.zip and checked the android-info.txt and my CID and MID were matching.
I'm not sure how to change to super CID. Is there a chance I'll lose any functionality?
ilikecars212 said:
I unzipped the firmware.zip and checked the android-info.txt and my CID and MID were matching.
I'm not sure how to change to super CID. Is there a chance I'll lose any functionality?
Click to expand...
Click to collapse
You can change to superCID following this: http://forum.xda-developers.com/showthread.php?t=2317536
have you tried following this? http://forum.xda-developers.com/showthread.php?t=2358738
I'm not sure why fastboot complains about a mismatch since the CIDs match. Your current firmware indicates the phone was converted to GPE (the .1700 in the version-main field).
Try to follow the guide above and see how that goes... Make sure you flash a .531 ROM as that is T-Mobile.
What is the model printed at the back-bottom-left of your phone? Is it PN07310?
Or maybe just backup your data and flash this: http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
This is the complete stock 3.24 image for T-Mobile.
Hello,
I have an HTC One M8 (ATT) that is misbehaving. It "crashed" into a lengthy black screen of death before spitting me into the bootloader loop. I can access fastboot and various things occur when I try fastboot commands.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.502.18
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.026s
Click to expand...
Click to collapse
My first strategy was to re-do what I did way back when (I don't know what I'm doing so I follow guides):
Theunlockr root-htc-one-m8-all-in-one-toolkit-method (can't post links)
This did not work. I tried to RUU (htc-one-m8-4-16-401-10-stock-lollipop-ruu-0p6bimg can't post links) but I get error messages when following the instructions:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(118):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(170):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
(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
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
I also tried to just flash TWRP twrp-2.8.7.0-m8.img 16.6M:
C:\adb>fastboot flash img twrp.img
target reported max download size of 1830727680 bytes
sending 'img' (17020 KB)...
OKAY [ 1.592s]
writing 'img'...
FAILED (remote: not allowed)
finished. total time: 1.599s
Click to expand...
Click to collapse
And tried flashing my RUU I downloaded as well:
C:\adb>fastboot flash zip op6.zip
target reported max download size of 1830727680 bytes
error: cannot load 'op6.zip'
Click to expand...
Click to collapse
In short, I have no idea what to do in order to get this thing back up and running. I am also very sad because likely I will be losing my images I took today at the Smithsonian rare books room (The original/actual De Revolutionibus Orbium Coelestium from Copernicus that started the scientific revolution, among others)...hopefully one of you wizards can help me save those if at all possible.
Thanks, and may the forum and cell phone gods have mercy on my soul.
***Edit*** I also just tried doing this, which didn't help (I'm seeing a lot of what look to be read/write failures..could this be a storage hardware failure, maybe?):
C:\adb>fastboot oem writecid CWS__001
...
(bootloader) Start Verify: 0
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) Input CID is not super CID
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 0
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.070s]
finished. total time: 0.071s
Click to expand...
Click to collapse
First of all, delete you IMEI and serial numbers. These are private info, and should never be posted online.
Grahamelot said:
This did not work. I tried to RUU (htc-one-m8-4-16-401-10-stock-lollipop-ruu-0p6bimg can't post links) but I get error messages when following the instructions
Click to expand...
Click to collapse
4.16.401 is the Euro RUU. You can only run RUUs that match the CID and MID of your device; so this is likely why the RUU failed.
You need to run one of the AT&T RUUs, which are linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Also, you CID is already the right one for AT&T (CWS__001), so no need to change it like you tried to near the end of your post. Note sure, but I believe that trying to change the CID to one that it already is, will normally return an error.
Grahamelot said:
I also tried to just flash TWRP twrp-2.8.7.0-m8.img 16.6M:
C:\adb>fastboot flash img twrp.img
Click to expand...
Click to collapse
That syntax is incorrect. It should be: fastboot flash recovery twrp.img
Also, its sometimes helpful to wipe cache before flashing TWRP if you are having issues flashing it: fastboot erase cache
Also, can you confirm your bootloader is still UNLOCKED (which would be my recommendation)?
The RUU is doing its thing now; sad that I will have lost the photos but hopeful that I will have a working phone again. Will update when something happens/doesn't happen.
Grahamelot said:
The RUU is doing its thing now; sad that I will have lost the photos but hopeful that I will have a working phone again. Will update when something happens/doesn't happen.
Click to expand...
Click to collapse
I think the RUU will wipe user data, but leave internal storage intact. Not sure of that, but if I'm right, your photos may still be there after RUU.
Do you use some method to backup your photos and other data? I ask, since many do not; even though its highly recommended to do so. I know you mentioned the photos were taken recently; so its possible that whatever backup method you use hasn't had an opportunity to do its thing. Although there are many cloud backup solutions that work almost in real-time (or at least will backup once you are on a WiFi network, if you have it setup that way).
Changing the default storage location to the removable SD card (which of course requires having one) is also an option. While this is not a backup method (is still volatile, and a single point of failure) it at least avoids the situation of losing access to the photos if the phone crashes, bricks, etc.
Things to consider, to avoid future data loss and disappointment.
redpoint73 said:
I think the RUU will wipe user data, but leave internal storage intact. Not sure of that, but if I'm right, your photos may still be there after RUU.
Do you use some method to backup your photos and other data? I ask, since many do not; even though its highly recommended to do so. I know you mentioned the photos were taken recently; so its possible that whatever backup method you use hasn't had an opportunity to do its thing. Although there are many cloud backup solutions that work almost in real-time (or at least will backup once you are on a WiFi network, if you have it setup that way).
Changing the default storage location to the removable SD card (which of course requires having one) is also an option. While this is not a backup method (is still volatile, and a single point of failure) it at least avoids the situation of losing access to the photos if the phone crashes, bricks, etc.
Things to consider, to avoid future data loss and disappointment.
Click to expand...
Click to collapse
When I last tried the RUU, the phone gave me an ERROR [171] USB connectivity issue and wouldn't proceed. I was hoping this was due to the replacement part that I had used...which ended up being defective in another department.
That company sent me a new part which I've installed. Unfortunately that doesn't seem to be the solution: I still get the ERROR 171. I have uninstalled and reinstalled HTC Sync, I still have access to fastboot (I can issue fastboot commands from the cmd prompt), the phone says "unlocked" at the top, but I can't seem to use the RUU I downloaded nor is the phone showing in windows explorer or in HTC Sync.....any ideas?
Grahamelot said:
When I last tried the RUU, the phone gave me an ERROR [171] USB connectivity issue and wouldn't proceed. I was hoping this was due to the replacement part that I had used...which ended up being defective in another department.
That company sent me a new part which I've installed. Unfortunately that doesn't seem to be the solution: I still get the ERROR 171. I have uninstalled and reinstalled HTC Sync, I still have access to fastboot (I can issue fastboot commands from the cmd prompt), the phone says "unlocked" at the top, but I can't seem to use the RUU I downloaded nor is the phone showing in windows explorer or in HTC Sync.....any ideas?
Click to expand...
Click to collapse
Also I went ahead and got an SD card and have a card reader. Figure if I'm having USB connectivity issues the SD card may allow me to bypass? How do I do something with the SD card and do I want to try to SD card a recovery (TWRP) or can I do the RUU?
Grahamelot said:
When I last tried the RUU, the phone gave me an ERROR [171] USB connectivity issue and wouldn't proceed. I was hoping this was due to the replacement part that I had used...which ended up being defective in another department.
Click to expand...
Click to collapse
What part did you replace?
Are you running the RUU in fastboot mode (which you should)?
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
Grahamelot said:
Also I went ahead and got an SD card and have a card reader. Figure if I'm having USB connectivity issues the SD card may allow me to bypass? How do I do something with the SD card and do I want to try to SD card a recovery (TWRP) or can I do the RUU?
Click to expand...
Click to collapse
You an indeed RUU using the SD Card. Try one of the bootable or zip RUUs listed in my Index thread (under "RUU" section): http://forum.xda-developers.com/showthread.php?t=2751432
Although the USB connectivity issue is often fixable.
redpoint73 said:
What part did you replace?
Are you running the RUU in fastboot mode (which you should)?
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
You an indeed RUU using the SD Card. Try one of the bootable or zip RUUs listed in my Index thread (under "RUU" section): http://forum.xda-developers.com/showthread.php?t=2751432
Although the USB connectivity issue is often fixable.
Click to expand...
Click to collapse
I replaced the small board that has the Aux plug and USB connection on it (and apparently the non-speaker phone microphone on it).
I tried all 3 of the downloadable RUU zip packages from the index; one of them makes decent (what looks to be progress) although most of the updates switch to "Fail-PU" once it attempts to install. I can try to take a photo or something later.
I believe I was running the RUU's in fastboot mode previously. The screen said "Fastboot USB" when it was plugged in. It got to the point where the RUU said "rebooting device". The device rebooted to fastboot again but it took a while and the RUU kept saying "waiting for device" before giving me the USB connectivity error. I still get connection between the PC and the phone though (via fastboot devices in cmd).
Grahamelot said:
I replaced the small board that has the Aux plug and USB connection on it (and apparently the non-speaker phone microphone on it).
Click to expand...
Click to collapse
Is this a laptop of desktop computer?
Any other USB ports besides the board that you replaced?
I think you might be right, in that the board seems to be faulty and causing the USB connection to be lost.
Try one of the bootable or zip RUUs (SD card method) I referred to earlier.
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
Grahamelot said:
I believe I was running the RUU's in fastboot mode previously. The screen said "Fastboot USB" when it was plugged in.
Click to expand...
Click to collapse
Agree, sounds correct. "Fastboot USB" highlighted in red is the proper mode (bootloader-fastboot mode) for RUU. If connected to USB cable, this is the default mode if you boot into bootloader.
redpoint73 said:
Is this a laptop of desktop computer?
Any other USB ports besides the board that you replaced?
I think you might be right, in that the board seems to be faulty and causing the USB connection to be lost.
Try one of the bootable or zip RUUs (SD card method) I referred to earlier.
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
Agree, sounds correct. "Fastboot USB" highlighted in red is the proper mode (bootloader-fastboot mode) for RUU. If connected to USB cable, this is the default mode if you boot into bootloader.
Click to expand...
Click to collapse
I am using a laptop for this process (still installing OS on my desktop). I should clarify that I replaced the USB board with a new one, which had a bad microphone. The original issue occurred with this USB board, as well. The company mailed me a new card to replace the defective replacement. I installed that and saw no change in the behavior of the errors. The board works fine in other respects (can see "Fastboot AC" or "Hboot AC" and "Fastboot USB" with no issues, so seems like connectivity is ok?).
I tried all 3 of the RUUs in your indexed link last night without much luck. I will try again when I get home from work. One froze (the kitcat/lollipop one) during unzipping every one of the 3-4 attempts I made at it (left it on overnight thinking it was just taking a while, too, without success). The other RUU ran but it skipped down most of the list (down to Sensory, or Sources, or something that started with an "s" ) giving Fail-PU on all the previous options. Again, I will re-download all 3 and try them again this evening and report back.
One thing that might be of interest is that I found some sort of recovery.img on the internet. I was able to fastboot boot recovery.img but it seems like everything froze and I lost the ability to type in my cmd prompt (not sure what happened). But at least I could fastboot into a recovery? Sort of? Not sure if that's a good thing or a bad thing.
This is a very frustrating problem and I seem to be making little to no headway despite being able to talk with my phone and have certain things "sort-of" work. Is it possible at this point that I may have had some sort of catastrophic memory/storage failure? Is there a way to re-format/re-partition in case I have some sort of weird corrupted file? Is this all too much to fix (see if I can get a new phone?)?
Grahamelot said:
This is a very frustrating problem and I seem to be making little to no headway despite being able to talk with my phone and have certain things "sort-of" work. Is it possible at this point that I may have had some sort of catastrophic memory/storage failure? Is there a way to re-format/re-partition in case I have some sort of weird corrupted file?
Click to expand...
Click to collapse
AFAIK, the RUUs will re-partition the memory, so I'm not sure why its failing.
The only other thing I can think, is to run a firmware.zip first, then try RUU again. I know some folks who have had issues going back to Sense from GPE (which have different partitions schemes) were able to get the RUU to run by flashing the firmware first.
If we get the firmware to flash, we may be in business; since the firmware includes stock recovery, and might fix whatever is going on with the recovery partition.
ATT firmwares can be found on the following thread. The thread is for a custom ROM, but includes the firmware also; and its the firmware alone that we want:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
I think the RUU will wipe user data, but leave internal storage intact. Not sure of that, but if I'm right, your photos may still be there after RUU.
Click to expand...
Click to collapse
Scratch that, I was remembering wrong. Just happened to see this on another thread:
FLASHING RUU'S WILL WIPE YOUR INTERNAL SD (/DATA/MEDIA)
http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
redpoint73 said:
AFAIK, the RUUs will re-partition the memory, so I'm not sure why its failing.
The only other thing I can think, is to run a firmware.zip first, then try RUU again. I know some folks who have had issues going back to Sense from GPE (which have different partitions schemes) were able to get the RUU to run by flashing the firmware first.
If we get the firmware to flash, we may be in business; since the firmware includes stock recovery, and might fix whatever is going on with the recovery partition.
ATT firmwares can be found on the following thread. The thread is for a custom ROM, but includes the firmware also; and its the firmware alone that we want:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
Ok, so we are on the same page....this is the one I am downloading: ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r(depreciated)
I'm going to unzip whatever this is, extract firmware.zip and put it in my ADB folder. Then I'm going to fastboot flash zip firmware.zip in cmd prompt and pray to the cellular gods that it's successful?
***Edit*** I tried doing the above and got:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1830727680 bytes
sending 'zip' (52096 KB)...
OKAY [ 2.463s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.472s
Click to expand...
Click to collapse
Googling "remote: not allowed" let me to this page: http://forum.cyanogenmod.org/topic/...ll-recovery-from-fastboot-remote-not-allowed/
I tried checking to see if maybe my issue was being locked somehow (I still have my unlock_code.bin file):
C:\adb>fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1830727680 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.128s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.139s
Click to expand...
Click to collapse
I guess I'll try downloading all 3 of those zipped RUUs again from your index page and trying those one at a time. Will post any issues I come across.
Grahamelot said:
Ok, so we are on the same page....this is the one I am downloading: ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r(depreciated)
I'm going to unzip whatever this is, extract firmware.zip and put it in my ADB folder. Then I'm going to fastboot flash zip firmware.zip in cmd prompt and pray to the cellular gods that it's successful?
Click to expand...
Click to collapse
Yes, that is correct. In theory any of the firmwares in that post should work. Lollipop is the most current firmware. 4.16.1540 is Developer's Edition Lollipop. 4.28.502.1 is the latest AT&T firmware. Both have AT&T compatible radios. 4.28 is the "official" AT&T Lollipop firmware.
redpoint73 said:
Yes, that is correct. In theory any of the firmwares in that post should work. Lollipop is the most current firmware. 4.16.1540 is Developer's Edition Lollipop. 4.28.502.1 is the latest AT&T firmware. Both have AT&T compatible radios. 4.28 is the "official" AT&T Lollipop firmware.
Click to expand...
Click to collapse
Downloaded and unzipped the 4.28 firmware. Placed just the firmware.zip file into my ADB folder. Tried: "fastboot flash zip firmware.zip" and got:
c:\adb>fastboot flash zip firmware.zip
target reported max download size of 1830727680 bytes
sending 'zip' (36029 KB)...
OKAY [ 2.221s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.228s
Click to expand...
Click to collapse
Grahamelot said:
Downloaded and unzipped the 4.28 firmware. Placed just the firmware.zip file into my ADB folder. Tried: "fastboot flash zip firmware.zip" and got:
Click to expand...
Click to collapse
Try to flash TWRP version 2.8.1.0 or lower (newer versions won't work with your hboot), per the post here: http://forum.xda-developers.com/showpost.php?p=61886567&postcount=1920
If successful, try to format data in the Wipe section of TWRP. This is the fix I've seen for corrupt data partition.
redpoint73 said:
Try to flash TWRP version 2.8.1.0 or lower (newer versions won't work with your hboot), per the post here: http://forum.xda-developers.com/showpost.php?p=61886567&postcount=1920
If successful, try to format data in the Wipe section of TWRP. This is the fix I've seen for corrupt data partition.
Click to expand...
Click to collapse
Tried flashing the recovery, same thing happened:
c:\adb>fastboot devices
FA44FWM00406 fastboot
c:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.765s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.864s
c:\adb>
Click to expand...
Click to collapse
Grahamelot said:
Tried flashing the recovery, same thing happened:
Click to expand...
Click to collapse
The bootloader is unlocked, correct? It reads UNLOCKED at the top of the bootloader screen?
redpoint73 said:
The bootloader is unlocked, correct? It reads UNLOCKED at the top of the bootloader screen?
Click to expand...
Click to collapse
Yes. For a self-proclaimed unlocked phone it seems to be quite puritan in the zips it wants to entertain accepting.
Grahamelot said:
Yes. For a self-proclaimed unlocked phone it seems to be quite puritan in the zips it wants to entertain accepting.
Click to expand...
Click to collapse
All I can think if is try an even older TWRP version (2.7) as this corresponds more close to your hboot (original hboot from the phones release in May 2014). Although I think the big TWRP change has more to do with the move to Lollipop; and I somewhat expect even TWRP 2.7 to fail.
Running out of ideas. We've tried RUUs, firmwares, and TWRP. I have a feeling you may be right that we have a corrupt storage, fried emmc, or something of the sort.