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.
Related
First, off, awesome NOOB video, and after watching it I can safely say I've done my due diligence. I have scoured our internet and several parallel earth internets with no luck in finding a solution. If any of you can give me a hand, I'd really appreciate it.
Phone Specs:
HTC Rezound
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-V14.6.0.7708.00.0507
eMCC-BOOT
Sep 20 2012,17:40:22
SDK tools: "Pulled from the SDK of February 13, 2013"
PROBLEM: Cannot revert to stock rom by
1) using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
2) or flashing from Amon Ra or TWRP (can't mount eMCC/data)
3) or uploading PH98IMG.zip to SD card and letting Hboot handle the heavy lifting (sticks at HTC boot up screen on reboot)
4) or using "fastboot oem rebootRUU" followed by "fastboot flash zip PH98IMG.zip" gets
sending 'zip' (624366 KB)...
OKAY [ 55.743s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 142.046s
BACKGROUND: I'm obviously a noob, but the only way to learn is by digging in. Here's the progression that's led me to this point:
1) Learned to unlock bootloader
2) Installed cm-10.1-20130629-NIGHTLY-vigor (officially unsupported by available for Rezound from CyanogenMOD's website)
3) Noticed instability so I wiped everything (x3) and tried to revert to stock. Couldn't make any progress, especially since the RUU exe crashes on both Win7 systems I have.
4) To get functionality for work, switched to cm-10.1.0.1-vigor.
5) Still have stability issues, so I'm trying yet again to revert. Current results of attempts are listed above under "PROBLEMS"
Note1: Per Scott's suggestion over either at Phandroid or ScottsRoms (can't remember I've been so many different places), I've modified the android-info.txt in PH98IMG.zip as follows, making sure the version number is higher than the current from CID Getter:
"modelid: PH9810000
cidnum: VZW__001
mainver: 4.09.605.2
hbootpreupdate:12
DelCache:1
DelFat:1
"
Note 2: MD5s check out.
Note 3: Before my first installation of CyanogenMOD's latest nightly, adb worked fine and would list my phone. After CyanogenMOD's latest nightly, adb does succeed in starting daemon and lists what it think is my phone, but instead of listing a phone it lists a blank space and returns to the command prompt. if I try adb reboot, it returns error: device not found. BUT fastboot still works fine.
Appendix 1: fastboot getvar all returns:
C:\Users\Josh\Desktop\Root Project\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (seem odd to anyone else that there's no number there?)
(bootloader) serialno: ******
(bootloader) imei:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.499s
Appendix 2: The sequence I've been following trying to get the thing to accept the stock rom is below...and I've tried small variations variations when what's below fails miserably.
1. Load TWRP or Amon Ra recovery
2. Wipe, wipe, wipe!
3. Reboot bootloader
4. fastboot flash recovery recovery_signed.img (have treated as interchangeable in sequence with step 5)
5. fastboot flash boot boot_signed.img (have treated as interchangeable in sequence with step 4)
6. (used this, also from Scott, before I started manually editing the android-info.txt in the image zip) fastboot flash zip SetMainVersionLOW.zip (to make sure the main version is lower than the stock ROM version--otherwise it'll think you're upgrading to a lower version and won't run)
7. fastboot oem lock
8. This step varies. I've tried
a. fastboot oem rebootRUU then fastboot flash zip PH98IMG.zip
b. fastboot boot TWRP or Amon Ra recovery, then flashing PH98IMG.zip from there
c. dropping PH98IMG.zip on the SD card and letting Hboot handle the heavy lifting
I take it you didn't take a back up of your previous rom before installing CM10.1?
mjones73 said:
I take it you didn't take a back up of your previous rom before installing CM10.1?
Click to expand...
Click to collapse
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
JoshManning said:
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
Click to expand...
Click to collapse
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
mjones73 said:
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
Click to expand...
Click to collapse
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
You already have the latest firmware on your phone, that doesn't get touched when you do a rom install.
Thank you, Matt! I'm downloading the ROM right now. Will post results once it's down.
SOLVED
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
kc6wke said:
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
Click to expand...
Click to collapse
Makes perfect sense. Rocking along now nicely thanks to you. Seriously, can I send you an Amazon card or something?
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
You're welcome, kc6wke covered question 1, for number 2, I knew you couldn't RUU cause you are on the latest firmware and s-on, it's not possible to downgrade firmware unless you're s-off. Your only option really was to install a different rom so I gave you a stock rooted one.
Matt, I've got an additional question if you have time. Any idea why my attempts to root the new ROM aren't taking hold? The phone is running just fine off the ROM you directed me to. After installation, I booted into Amon RA 3.16, installed superuser and su, and rebooted. Nothing. SUChecker returns "su declined / not found"
Actually nevermind. SUChecker is returning a false negative. Apologies, and thanks again!
The one I gave you was already rooted, no need to do that.
mjones73 said:
The one I gave you was already rooted, no need to do that.
Click to expand...
Click to collapse
I now remember your saying that. Thank you so much for your help. I really appreciate it.
Josh,
I may be wrong but I think that the iemi is sensitive info so you might want to delete that from your original post. Maybe delete your serial number as well just in case.
btw... my phone doesn't show a mainver either, never got an answer as to why not, but it works fine.
Thanks! Done and done.
well he was a noob, but then he just became just like the rest of them
how did he uploaded the rom in Amon Ra.
band001 said:
how did he uploaded the rom in Amon Ra.
Click to expand...
Click to collapse
Depends, are you s-on or s-off?
mjones73 said:
Depends, are you s-on or s-off?
Click to expand...
Click to collapse
s-off
---------- Post added at 06:46 PM ---------- Previous post was at 06:31 PM ----------
band001 said:
s-off
Click to expand...
Click to collapse
Sorry but i am s-on not s-off yet. trying to get info on how to also if this does not work.
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
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
y2jdmbfan said:
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
Click to expand...
Click to collapse
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Solarenemy68 said:
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Click to expand...
Click to collapse
Unfortunately I already have the replacement device from HTC...
Just flash an ATT stock rom, then restore the stock recovery. Done.
cschmitt said:
Just flash an ATT stock rom, then restore the stock recovery. Done.
Click to expand...
Click to collapse
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
y2jdmbfan said:
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
Click to expand...
Click to collapse
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
cschmitt said:
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
Click to expand...
Click to collapse
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
y2jdmbfan said:
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
Click to expand...
Click to collapse
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
cschmitt said:
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
Click to expand...
Click to collapse
Now I am getting this error...I am S-On BTW if that makes a difference...
C:\platform-tools>fastboot flash zip firmware_4.18.502.7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47880 KB)...
OKAY [ 3.170s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.415s
Post the output of fastboot getvar all minus IMEI and S/N.
cschmitt said:
Post the output of fastboot getvar all minus IMEI and S/N.
Click to expand...
Click to collapse
C:\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(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
all: Done!
finished. total time: 0.069s
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
cschmitt said:
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
Click to expand...
Click to collapse
Yes it was. I accidentally put back s-on before I flashed the RUU. The phone had s-off and a custom software when I purchased it. The phone was acting up so I called HTC and got an advanced replacement and already have the replacement. I wanted to flash back to a stock firmware and remove s-off and lock the bootloader before I send the old phone back to HTC.
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
cschmitt said:
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
Click to expand...
Click to collapse
Oh I would s-off again no problem, but I can't get rumrunner or firewater to work...Any hints would be great based on the getvar I posted above.
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
C:\platform-tools>
Anyone have any ideas to get firewater working?
I have flashed Android Revolution HD 52.0 and then tried to do firewater, but it kicks me back to the command prompt after the initial chugging...
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.
Hello friends, recently got an M8 Att, its already S-Off, BL Unlocked, Tried CIDs BS_US001, BS_US002 and Super CID 11111111 tried to install UL/DEV Ruu from HTC dev site but alwasys got error 155.
Any suggestion or what am i doing wrong? Thanks in advance.
My getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4xxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Which RUU are you trying to flash? If it's the Sense 7/ Marshmallow RUU then you need to first flash 6.x firmware. I found the same exact version as in the name of the RUU and flashed that first then the RUU flashed without a problem.
Sent from my Nexus 5 using Tapatalk
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
firultd said:
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
Click to expand...
Click to collapse
Search Google for 6.12.1540.4 firmware. I used the one in the first result uploaded by Einwod.
Flash that via fastboot oem rebootRUU.
Twice. It will fail the first time, wait about a minute for the bootloader to reload and flash it again. Don't unplug your phone at all. Once you successfully flash the firmware, do fastboot reboot-bootloader to get back into fastboot, then you should be able to flash the RUU
Sent from my Nexus 5 using Tapatalk
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Which error? Are you familiar with fastboot at all? And HTC oem commands? I take no responsibility for your flashing but what I posted worked fine for me.
Sent from my Nexus 5 using Tapatalk
firultd said:
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Click to expand...
Click to collapse
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Yes i personally do boot loader unlock s -off and all that stuff. Don't worry I know that all responsibility is mine. I mean if after flashing firmware ruu still give an error obviously device will not but isn't it? In that case I still can flash att 5.0 stock ruu?
redpoint73 said:
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Click to expand...
Click to collapse
OK. Very clear explanation that's give me a better look of the situation. Will keep in mind and try. Thank s a lot.
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
psychephylax said:
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
Click to expand...
Click to collapse
Well, lets do it, just give me some hours to backup and will try and post results, again thanks for your time.
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Yeah, it's about 30mb (31626 KB)
Here's the md5 sum from my file: b5add816536334711fb2baa6e8a4d134
HAve no words to describe the happines to see my phone just like a real dev edition, many thanks to all of you for your time. Whole process was right and phone is working awesome.
Glad you got it working.
Sent from my Redmi Note 2 using Tapatalk
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Note that firmware.zip only contains a subset of partitions including hboot, radio, kernel, recovery, WiFi, Bluetooth, Audio and a few others. It doesn't contain the ROM, which is a much larger file (1.5 GB or so); nor is it a full RUU or ROM.zip, etc.
Firmware is important, but not a large file.
Any harm in flashing the 6.12.1540.4 but staying on Lollipop?
I don't know, but why would you want to stay on lollipop?
Sent from my Redmi Note 2 using Tapatalk