Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Edit: I GOT IT!!! If you're in the same spot as me, make sure to put the RUU in your ADB directory. It wasn't working for me, moved it, worked like a charm.
detox702 said:
Trying to get an RUU to run to update the HTC One M7 from T-Mobile. I've tried both the 3.24 that the phone has, and the 4.xx new one from the Original Android Dev forum. Both of them fail. 3.xx when trying to verify information, and 4.xx after step 1/5 pushing boot. 4.xx gives error 171 USB issue. I've got the drivers installed, as well as ADB and Fastboot. It connects to the phone and the RUU file reboots it, but instead of going to bootloader it goes to a black screen with HTC in silver, then the RUU on the computer fails.
Any ideas what I might be doing wrong? I have fastboot/bootloader access, but can't boot past the HTC O1ne screen.
Click to expand...
Click to collapse
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
majmoz said:
Are you S-On or S-Off? Do you have stock recovery? Is your MID and CID the same as the RUU? Is your bootloader "Locked"? Do you have the stock hboot for the RUU you are trying to run? The hboot has to be the same or lower than hboot in the RUU!
Click to expand...
Click to collapse
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
detox702 said:
Everything is stock. The co-worker never bothered with rooting/etc. S-On. T-Mo phone using a T-Mo RUU. Locked bootloader. Pretty sure the hboot is the same as well.
Click to expand...
Click to collapse
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
majmoz said:
Reboot to bootloader (FASTBOOT USB), then run the command: fastboot getvar all This will tell you the id information about the phone. There may be some light shed on the status of the phone.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
C:\adb>
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>[/QUOTE]
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.
majmoz said:
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
C:\adb>
Click to expand...
Click to collapse
First of all please remove the serialno and imei from your original post. Nothing looks out of the order. Could the RUU be corrupt? Check the MD5 checksum just to be sure. Or download another RUU from a different site. I have used this site's RUU in the past.[/QUOTE]
I apparently got it. Moved the file from C:\Downloads to C:\adb, ran it, success. Thanks for the pointers, though.
Related
Hi,
I really need help with my bricked Flyer.
I tried to install honeycomb on my Flyer followed the process described in the link below:
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Now, I ended up with a working CM, new and UNLOCKED bootloader, and new radio, S-ON **but** device turns on to white HTC screen and stays on that state.
I tried to revert to genuine GB rom followed the process on this post:
http://forum.xda-developers.com/showthread.php?t=1257909
And now current device state is:
*** RELOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT- 1.11.0006
MICROP- 0850
RADIO- 3821.08.00.26_M
eMMC-boot
I tried to RUU fastboot method using rom.img from RUU_Flyer_HC_S_HTC_WWE_3.10.405
And ended up with error 132 (signature issue)
I also tried to flash PG41IMG.zip (pulled out of RUU_Flyer_HC_S_HTC_WWE_3.10.405) using goldcard without success- same signature issue (wrong product ID)
Curent state- no ADB, no CM, only fast boot works...
I would appreciate any help getting back to a working Flyer.
Thanks!
motman said:
Hi,
I really need help with my bricked Flyer.
I tried to install honeycomb on my Flyer followed the process described in the link below:
http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Now, I ended up with a working CM, new and UNLOCKED bootloader, and new radio, S-ON **but** device turns on to white HTC screen and stays on that state.
I tried to revert to genuine GB rom followed the process on this post:
http://forum.xda-developers.com/showthread.php?t=1257909
And now current device state is:
*** RELOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT- 1.11.0006
MICROP- 0850
RADIO- 3821.08.00.26_M
eMMC-boot
I tried to RUU fastboot method using rom.img from RUU_Flyer_HC_S_HTC_WWE_3.10.405
And ended up with error 132 (signature issue)
I also tried to flash PG41IMG.zip (pulled out of RUU_Flyer_HC_S_HTC_WWE_3.10.405) using goldcard without success- same signature issue (wrong product ID)
Curent state- no ADB, no CM, only fast boot works...
I would appreciate any help getting back to a working Flyer.
Thanks!
Click to expand...
Click to collapse
if you have RELOCKED, You can try your original PG41IMG.zip (GB) with Goldcard
Yeah, I made a goldcard but the problem is that the base version installed on my Fiyer is Wifi_1.36.1540.32 and I can not find this version's RUU file anyware... Am I scr**ed? or is there any way to get this RUU file?
motman said:
Yeah, I made a goldcard but the problem is that the base version installed on my Fiyer is Wifi_1.36.1540.32 and I can not find this version's RUU file anyware... Am I scr**ed? or is there any way to get this RUU file?
Click to expand...
Click to collapse
It seems you made your goldcard incorrect.
I created a new goldcard and confirmed that I made it correctly, copied 41IMG.zip from another WIFI rom but still no go... I'm getting CID incorrect error on HBOOT
motman said:
I created a new goldcard and confirmed that I made it correctly, copied 41IMG.zip from another WIFI rom but still no go... I'm getting CID incorrect error on HBOOT
Click to expand...
Click to collapse
have you branding Version? if yes: it can be image name is different. For example on my Flyer: IMG41DIAG.zip
No, this Flyer was purchased unbranded in BestBuy- US. I guess that the only free solution will be with 1.36.1540.32 RUU version which can not be found anywhere :-(
motman said:
No, this Flyer was purchased unbranded in BestBuy- US. I guess that the only free solution will be with 1.36.1540.32 RUU version which can not be found anywhere :-(
Click to expand...
Click to collapse
You can control your cid with
fastboot getvar cid
viera77 said:
You can control your cid with
fastboot getvar cid
Click to expand...
Click to collapse
Thanks!
I'll try fastboot getvar cid option next week and post my results.
OK, here are the results:
'fastboot getvar all' command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0006
(bootloader) version-baseband: 3821.08.00.26_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0850
(bootloader) version-main: 1.36.1540.32
(bootloader) serialno: HT15JJN00515
(bootloader) imei: 35519**********
(bootloader) product: flyer
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4140000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3674mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 60a0efb2
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Now, running this command:
fastboot oem writecid 11111111
Gives me the following error:
(bootloader) [ERR] Command error !
OKAY [ 0.016s]
finished. total time: 0.016s
What should I do next?
I'm echoing your cry for help. I'm in EXACTLY the same position. SOMEONE PLEASE HELP!
Managed to upgrade to HoneyComb
I managed to unbrick my flyer by redo all HoneyComb process using the link in my first post.
All of this could not happen without using the unlock_code.bin file I originally received from HTC to unlock the bootloader again! I used 'fastboot flash unlocktoken Unlock_code.bin' command then flashed the new CM recovery menu then HC custom rom zip file via CM.
The only step I could not bypass is S-ON due to a newer Hboot version (1.11.0006) which is not supported by Revolutionary yet.
I can live with that although I'm not able to downgrade to stock rom, my CID is still BS_US001. I wish I knew how to revert to the older supported Hboot in order to S-OFF.
I hope that helps.
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
damiancds said:
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
Click to expand...
Click to collapse
cm 11 did'nt update your firmware
what's your results for fastboot getvar all
run it from the bootloader screen / fastboot usb (remove your serial no and iemi)
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
damiancds said:
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
Click to expand...
Click to collapse
this is the last AT&T RUU it will update you to android 4.3 >>
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if that link is slow you can get it directly from HTC here >>
http://www.htc.com/us/support/htc-one-att/news/
you'll have to relock your bootloader
fastboot oem lock
then run the RUU with your phone sitting at the fastboot usb screen
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
damiancds said:
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
Click to expand...
Click to collapse
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
clsA said:
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
Click to expand...
Click to collapse
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
damiancds said:
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
Click to expand...
Click to collapse
after running the RUU your starting from scratch
1.unlock bootloader at HTCDEV.com
2. Flash custom recovery I recommend TWRP 2.6.3.3
How to flash?
1) Download your recovery
2) Put it on your adb/fastboot folder
3) Rename it to recovery.img
4) Open a CMD/Teminal windows on adb folder
5) Put your phone in fastboot
6) Flash the recovery with the command:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. flash custom rom 3.17.502.3 Stock Rooted
That should do it if your Root needs updated
download and flash this same as a rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
i'd installed cm11 via installer but now i wanna go back to sense
i'd installed cm11 via cm installer but now i wanna go back to stock sense,sadly i couldnt find the suitable RUU for my device.Since im really new to this android system i dont have any ideas bout flashing or locking the devices,could u guys please help me out?
i'd tried turning S off with rumrunner but at the end i was struck on an error.
here are my devices details.
m7_U S on
Hboot 1.56
CID : htc__038
version : 4.20.707.7
THANKS.
Okay! SOoooo Im going to apolagize if this is the wrong sport for this! I couldnt quite find a spot that hit everything i was trying to figure out!
SO heres the deal, was looking to upgade my phone! Found an HTC one on ebay SUPER cheap guy selling it tried to root it and got it stuck in a boot cycle..... Easy enough to fix right?! *or so it would have been on a Samsung! thats what im used to working with*
so i get the phone and play a little bit, I load into the bootloader and do a factory reset! the phone restarted and went right to the main set up page! as soon as i get to the end it says Unfortunatly Set up has stopped. *UGH* still im thinking super easy to fix! Just gotta flash Stock rom! so i head in that direction everything im finding says need to S-off the phone. so i start researching! ThinI started with the boot loader, got it unlocked *thats what all the post were saying to do* then went to move on to S-off, heres where it gets messy.... long story short..... the program freaks out gives me some error then starts in to loading CWM and then everything just crashes! Phone, Computer..... everything!
I get the phone back into boot mode, NOW it sats Tampered on the top, I cant get back to the set, Recovery doent work, factory reset doent work..... again long story short after researching it turns out i wiped EVERYTHING.
I can still get to the phone VIA command promts, I can get it to load in to the black HTC screen hell i can even relock and unlock the phone..... But I think where the issue is, the phone is still S-on..... when following all the step to fix this I cant get the ADB to see that my device is connected I can- But i can acces it through other commands..... Hopefully I havent lost everyone!!
Please tell me im not completely screwed....
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
clsA said:
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Sorry, while im not a complete noob with this stuff im still learning. what do you want me to do?
clsA said:
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Never mind! figured it out haha
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(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: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.060s
GNote4Ever said:
Never mind! figured it out haha
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(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: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.060s
Click to expand...
Click to collapse
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
clsA said:
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
The RUU wont work in this case. I did as you said*just to be sure.* But the RUU can cacess the phone in boot mode and because the phone get stuck on the "HTC quietly brilliant" screen its not loaded far enough to engage the USB connection. All I get is USB Connection Error when running the RUU
clsA said:
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
think I got it. Loaded to the Black HTC screen using fastboot oem rebootRUU- then ran the RUU it is "updating boot" as we speak.
GNote4Ever said:
think I got it. Loaded to the Black HTC screen using fastboot oem rebootRUU- then ran the RUU it is "updating boot" as we speak.
Click to expand...
Click to collapse
Next time, an easier method would be to flash a custom recovery (fastboot flash recovery *recovery of your choice*) and then install a new ROM. You put the ROM on an external USB and flash it, or you can ADB push the ROM into the phone.
When running S-Off (rumrunner or firewater) I recommend to always run it from a stock ROM.
So if I get these drivers, and my computer WILL NOT recognize my device, how am I supposed to reapply them to the phone?
I just need to get the drivers back on my phone so I can work on the recovery. I'll probably have more questions about that later.. lol
Hey guys,
My HTC One(ATT) is stuck in the HTC One logo screen. This happened earlier as well but fixed it through RUU. Since then i got upgrade from at&t to the latest 5.12.502.2 with Sense 6.
Tried with the earlier RUU but didnt work. So i am looking for RUU for the latest att update.
Can you please help me with this !!!
Thanks!!!
diganthshah said:
Hey guys,
My HTC One(ATT) is stuck in the HTC One logo screen. This happened earlier as well but fixed it through RUU. Since then i got upgrade from at&t to the latest 5.12.502.2 with Sense 6.
Tried with the earlier RUU but didnt work. So i am looking for RUU for the latest att update.
Can you please help me with this !!!
Thanks!!!
Click to expand...
Click to collapse
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
sharksfan7 said:
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
Click to expand...
Click to collapse
I will give the official one a shot and see if it works.. will update the results soon..
sharksfan7 said:
I haven't seen an RUU for 5.12.502.2 available anywhere yet. The last official RUU from AT&T was 3.17.502.3. The 4.18.502.7 RUU that's floating around apparently wasn't an official release and many people were having problems with it. If you are S-Off, use the 3.14.502.3 RUU then you can OTA up to the latest version.
Click to expand...
Click to collapse
I tried 3.17.502.3 .. doesn't work..
Below is the info of my device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502&2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4226mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am not sure if this doesnt work as it is S-ON.
Original issue was "STUCK AT HTC ONE LOGO SCREEN" .. how can i proceed next ??
Thanks!!
First off. Edit your post above and remove the serial# & imei.
The RUU isn't working b/c you're S-On and on an HBOOT higher than the one in the RUU. You need to be S-OFF to downgrade. Your bootloader is locked as well. Have you ever unlocked the bootloader and flashed a custom recovery? If not, I guess the next thing to try is to do a factory reset from HBOOT. You'll lose all your data but I don't think there is a way around that at this point. But since you were trying to run the RUU I guess you've already resigned yourself to that.
Another route to take is to unlock your bootloader, flash a custom recovery, then a custom ROM.
You might want to wait for other people to chime in. Perhaps they'll have other ideas.
diganthshah said:
I tried 3.17.502.3 .. doesn't work..
Below is the info of my device.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
I am not sure if this doesnt work as it is S-ON.
Original issue was "STUCK AT HTC ONE LOGO SCREEN" .. how can i proceed next ??
Thanks!!
Click to expand...
Click to collapse
I just saw this are you still stuck ?
The easy answer is to unlock the bootloader and flash TWRP 2.6.3.3 and flash my Guru_ reset being your already on the current firmware.
If you don't want to flash the recovery again after the reset just choose no to installing stock recovery and radio and Yes to Root
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload the Rom to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
I had someone inexperienced bring me this phone which they botched. They were able to use htcdev and unlock the bootloader and install TWRP, but that is all. No s-off. They must have wiped it because there is no OS on it and they want it back to stock now. So, I figured I would relock the bootloader and flash the most current ota. Nope. It isn't having it. I tried the 3.28 ota but after the check in hboot, it reads "checking" with "press power to reboot" over the top of the text. I have tried other ruu's and zips only to get checksum errors or signature verification errors. I forgot to mention that when twrp was installed, not a single custom rom would intall. They all failed. The person that brought it to me did mention something about trying to get to the google play edition firmware but they didn't know much about it. Does anyone have any ideas on where I can go from here? Anything would be very helpful. Thank you!
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
redpoint73 said:
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
Click to expand...
Click to collapse
C:\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45FWM10802
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
I have tried all the att ruu's and the unbranded 3.28. In twrp I tried sense and non sense roms, all of which failed.
Delete your IMEI from the post, as this is private info.
Sorry, I should have mentioned to delete the IMEI. Although I did not request to cut and paste all the getvar data.
EDIT: Reported to mods, and they deleted the IMEI.
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
In bootloader, you've verified the bootloader is relocked?
Also, you tried the 2.23 RUU? I know you said you tried "all" the RUUs (it helps to be specific and list everything individually). But I ask because this RUU was released, but now its not listed on HTC's support site (as the OTA was pulled due to battery drain issues) so some people think the RUU itself was also "pulled". Although the direct RUU download still exists and works:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Also, you can try the bootable RUU, which some folks have had better luck with: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Or another approach: What version of TWRP? Some older versions were known to have some flashing issues for some folks. Any specific error messages?
With bootloader unlocked, try to fastboot erase cache, and fastboot flash the latest TWRP. Or try Philz recovery. Then try again to flash a ROM.
whoops, I forgot about the imei. Thanks. Yes, I tried 2.23 and it read no image or wrong image. I will unlock the bootloader again and install the most current twrp and give it a try. anything helps. thanks!
iRootAll said:
I tried 2.23 and it read no image or wrong image.
Click to expand...
Click to collapse
Did you try the bootable version I linked?
Have you tried installing the latest TWRP, wipe the phone and flash a nandroid backup?