I'm in a pickle, and have been working at it all night to try to get my phone back to at least working order.
Here's what happened so far:
Phone is an ATT model HTC One m8 converted to GPe via RUU. CID was changed to GOOGLE's to received ota updates.
OTA update installed, and I noticed it said something about the firmware. When it finally booted, I didn't have any cellular signal.
Fast forward to 5 hours of trying to recover from it and even flashing the original GPE RUU, I still don't have a baseband.
Here's what I have tried:
RUU of 5.0.1. No signal.
RUU of Sense rom. (Wouldn't boot, so hard to use nandroid backup). No signal.
Flashing radios. Tried ATT and GPE. No luck.
All of these report Baseband is unknown. Worked fine @ 4.4.4. before the update today.
Here's what fastboot shows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.16.213319
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx3014 (It does show a full IMEI just hiding some of it)
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help would be greatly appreciated. Ive searched all over and haven't found a solution.
EDIT: Forgot to mention that I am currently at stock sense rom (4.4.2) and it doesn't report a baseband. Fastboot shows an IMEI though.
lordpelvis said:
RUU of Sense rom. (Wouldn't boot, so hard to use nandroid backup). No signal.
Click to expand...
Click to collapse
The RUU completes properly, but phone doesn't boot? Or are there any errors?
Not sure how nandroid figures in here. RUU will re-install stock recovery, so a nandroid will do you no good; unless you install custom recovery again.
If in fact the RUU and radio flashes are running to completion (but still no signal), that would not bode well. You might have a radio brick, or something like that.
What Sense RUU did you run, and what GPE RUU did you run (please link it).
And to confirm, you are trying to use this device on AT&T's network?
redpoint73 said:
The RUU completes properly, but phone doesn't boot? Or are there any errors?
Not sure how nandroid figures in here. RUU will re-install stock recovery, so a nandroid will do you no good; unless you install custom recovery again.
If in fact the RUU and radio flashes are running to completion (but still no signal), that would not bode well. You might have a radio brick, or something like that.
What Sense RUU did you run, and what GPE RUU did you run (please link it).
And to confirm, you are trying to use this device on AT&T's network?
Click to expand...
Click to collapse
Yes. Trying to use on ATT network. It doesn't even detect whether a sim is in it or not.
GPE Thread I followed: http://forum.xda-developers.com/showthread.php?t=2708651
I ran the Sense RUU from here: http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
Phone does boot, wifi works but there is no baseband or IMEI in the software on either GPE or Sense. I flashed the RUU then flashed custom recovery to do the restore. Sense booted fine but still didn't have any cellular connection. Fastboot shows a baseband and IMEI though.
lordpelvis said:
I ran the Sense RUU from here: http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
Click to expand...
Click to collapse
Try these also:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
So its still not clear, the Sense RUU ran to completion, with no errors? If so, again it doesn't sound good.
Yes no errors. It was fine on 4.4.4 GPE. Could the OTA update have burned up the radio? Going to try 4.4.3 now.
lordpelvis said:
It was fine on 4.4.4 GPE. Could the OTA update have burned up the radio? Going to try 4.4.3 now.
Click to expand...
Click to collapse
OTA typically updates radio, so its possible.
redpoint73 said:
OTA typically updates radio, so its possible.
Click to expand...
Click to collapse
Still no dice on the 4.4.3 RUU. No errors. Phone boots but sticks at the HTC green logo. I can swipe down from the top and see there's no service but nothing else is happening. It will randomly reboot as well.
EDIT: Phone finally finished welcome wizard. Still random reboots and no baseband.
Looks like a trip to ATT is looking more and more likely.
Any other suggestions? Ideas?
Try WNC's Dev Edition 3.28 firmware package: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
At this point, I'm just thinking of anything that will flash the radio, that hasn't already been tried.
redpoint73 said:
Try WNC's Dev Edition 3.28 firmware package: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
At this point, I'm just thinking of anything that will flash the radio, that hasn't already been tried.
Click to expand...
Click to collapse
What's weird is fastboot getvar all reports an IMEI but the roms don't see it.
Still no lock. All roms don't see the IMEI.
lordpelvis said:
Still no lock. All roms don't see the IMEI.
Click to expand...
Click to collapse
how do you fix your phone after all?
I didnt. Warranty replaced.
Related
LOOKS LIKE S-OFF FOR 1.54 HAS HAPPENED. NO NEED TO DOWNGRADE CHECK THE POST HERE
MODS Lock This One Up!!!
I was about to give up on s-off since I got the OTA update but there is hope.
I got s-off doing the following:
1.) Unlock your device via HTCDev
2.) Download and flash CWM Recovery
3.) Flash the stock nandroid for your phone...
a. TWRP Nandroid AT&T Thanks JEANRIVERA
b. TWRP Nandroid AT&T Thanks JEANRIVERA
c. TWRP Nandroid AT&T Thanks cschmittIf any one has other links to other devices let me know... I think this will work on all of the variants.:laugh:
Please note that this nandroid was made with TWRP and may need to be restored with TWRP.
On a side note... The original nandroid that I had linked was also created with TWRP and as I was unable to locate the restore function in my TWRP I did restore with CWM.
4.) then relock your device
Code:
fastboot oem lock
5.) grab 1847-ruu-m7-ul-jb-50-cingular-12650212.exe here and run it... Thanks cschmitt
6.) goto the tutorial here... and follow the directions...
This has worked for me... and I hope this will help someone else. All the information came from other people, I just happened to put it in the right order.
If this did not work for you there are New instructions here... Thanks domohan
IT IS IMPORTANT TO DO ALL THE STEPS IN ORDER...
I take no responsibility for anything you do with this information.
If I forgot to mention your name specifically... I'm Sorry and Thanks!
If I helped you hit the thank you button.
I see, new hboot. Downgrading it is then. Interesting that they haven't forced htc to shut off the unlocking service.
worked as advertised
Thanks a lot. A process for sure but worked for me following the ATT OTA update to .15. Although, I went on to follow the guide at wonderhowto dot com for installing the ASOP Google Edition. Thanks again.
Yeah that was the update that got me ... I am really glad that it worked for someone else... :laugh:
I am having trouble flashing the nandroid. I have tried to both flash the zip as well as unpack it and try to do a restore. Any thoughts?
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
Ok, I actually flashed this one http://forum.xda-developers.com/showthread.php?t=2252959
Then ran the .12 RUU and am now S-OFF. Thanks for this!
well i am glad you got that working... The way i did the nandroid was by extracting the zip to clockworkmod\backups ... then choosing restore... I had TWRP but could not find the restore Nandroid option.
The only way I see this actually working is that the RUU just checks the HBOOT version, and not the build date. Otherwise, the .12 RUU would fail to install because the OTA HBOOT has a newer build date.
If this is true, then all AT&T users better get S-OFF now (if they know what S-OFF does). I have a feeling the 4.2.2 update will come out with a newer HBOOT with a higher number. Then surely, any 4.1.2 RUU will not work.
In any case, it seems to be working for those of us who weren't paying attention and downloaded the OTA... But the message is still S-OFF now while you can, 'cause they will patch the thing eventually.
I was getting Error = -6 codes and this method worked perfectly for me! Thanks so much!
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
i used this and it worked flawlessly for me, great looking out man. im now s-off with tampered removed
TabascoJoe said:
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
Click to expand...
Click to collapse
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
INeFFeCTiVE said:
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
Click to expand...
Click to collapse
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Here are the steps I did to unlock bootloader, root and acquire s-off:
I went back to fully stock unrooted s-on to get the OTA just to b on the safe side. This is where I knew the update screwed up the current s-off method so I unlocked the bootloader using HTCDev. Then proceed to root and pushed the revone file to the appropriate folder location. I followed all the commands from revone up to where u Chmod 755 revone. After that since I already had root, I simply type su then proceeded with the s-off and unlock command. Removed tampered label and voila!!! Back in business with latest software.
Sent from my HTC One using xda premium
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
I think what happened was the new update screwed up the motochopper temp root exploit and that's y I think u can't s-off with the updated software. But there is always a way...
Sent from my HTC One using xda premium
TabascoJoe said:
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Click to expand...
Click to collapse
You can't use the AT&T RUU because your HBOOT is higher than the one in the RUU. S-ON is preventing any older HBOOT to be flashed.
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
It would certainly be worth a try. The hardware is the same, so I don't see why not... as long as your boot loader is 1.44.00000 (not sure on the amount of zero's) this should work.
I'm pretty sure there are nandroid images for TMO out there so give it a try.
vinny.1967 said:
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
Click to expand...
Click to collapse
let me know if it's work with you
me_rashad said:
let me know if it's work with you
Click to expand...
Click to collapse
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
vinny.1967 said:
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
Click to expand...
Click to collapse
I did get the OTA too and having the same pesky error -6. The bootloader version still says 1.44.0000, how do we know if its patched or not? Shouldn't the version number increase? What is your version?
I am trying to get my HTC One back to stock to install the 4.2.2 update. I prefer the HTC Sense rom compared to a custom rom.
It was purchased unbranded in Australia. I have flashed TWRP recovery and rooted. I can't find the correct RUU to restore.
Does anyone know which RUU to run, or if I can flash a stock recovery to do this update?
Fastboot Details:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-main: 1.29.980.17
version-misc: PVT SHIP S-ON
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__039
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
It depends...
nmarlor said:
I am trying to get my HTC One back to stock to install the 4.2.2 update. I prefer the HTC Sense rom compared to a custom rom.
It was purchased unbranded in Australia. I have flashed TWRP recovery and rooted. I can't find the correct RUU to restore.
Does anyone know which RUU to run, or if I can flash a stock recovery to do this update?
Fastboot Details:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-main: 1.29.980.17
version-misc: PVT SHIP S-ON
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__039
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
My understanding is that it depends... I'm pretty sure you can S-OFF and change the modelid and cidnum, so you can essentially use any RUU, or more specifically, use the RUU that is supplied by your service provider.
The other thing you can do is simply flash a stock ROM in recovery and that won't matter whether you have the settings correct or not.
The RUUs can be found here: http://forum.xda-developers.com/showthread.php?t=2377902
and stock ROM images can be found here: http://forum.xda-developers.com/showthread.php?t=2384631
It doesn't appear there is an RUU out for your phone yet as-is, so you'd probably have to change the MID and CID to use an RUU.
Progress.... Finally
Thanks for the reply.... I wish I had seen your stock recovery file earlier!
I am with Vodaphone and this is the first time in years that I have had good quality data connections with them. Due to this I am hesitant change the CIDNUM and flashing another RUU an possible another radio. The stock radio is working well and keeping the LTE working well is my main priortiy.
I have played with the GE 4.3 rom and also with Cyanogenmod 10.2. The GE was rather plain and I felt it was missing a lot of the standard android functions. I also missed having the white setup menu from the HTC rom. CM10.2 is only a new release. I have used CM10.1 on my old SG2 and enjoyed the rom and the daily updates. I missed having Beats audio (paying with the EQ's just doesn't sound the same over the HTCs spectacular speakers) and LTE never worked. This might be due to the fact that the model on the CM site is HTC One (GSM) which from what I have read is not an LTE model. I will try this again after 10.2 has settled down and they have fixed a lot of the bugs.
I figured out how to get the OTA update yesterday.
1. Restore the nandroid from here. This worked but I think the nandroid was from an Optus phone which had the CIDNUM change to HTC__039 before sale. There was one optus app (called "Sim Setup") installed after the restore.
2. CMW was still installed so I flashed the recovery.img from the same nandroid through fastboot. This took the recovery back to stock.
3. Relocked the bootlader.
4. OTA update then worked Downloaded >400mb over LTE in Coburg, Melbourne in less then 5 minutes.
4.2.2 is working well except there is now a vodaphone app (called "Updates"). This is a odd and I want a fully HTC stock rom. This weekend I will try restoring from a TWRP nandroid I made before I flashed any custom roms and then try OTA again. This should work ok but I will take another nandroid just in case.
I am happy to hare more details with other people who might be having probems restoring their HTC__039 back to stock to receive OTA.
When I originally unlocked the bootloader I used the HTC method as I wasn't aware of revone. Is it possible to use this now as I had no lock trying to S-OFF the device after the HTC method?
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
HTC One AT&T
S-off
Unlocked
Rooted
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT35SW904937
(bootloader) imei: 354439XXXXXXX65
(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: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read these threads very thoroughly before posting anything on forum.
Problems: No Sim detected, unknown baseband, imei #, no signal. All else seems to work. Getvar command will show IMEI & baseband.
I purchased from eBay as parts or repair because it was stuck on boot screen. Vendor sell mass phones and did not know the history. Figured it was worth a shot to fix.
Phone was stock AT&T 4.4 with 1.55. No modifications is was just stuck in boot loop. I tried newest version RUU Utility but same results, boot loop. I unlocked bootloader via htcdev and then flashed newest version cynogenmod (even with S-On) and was successful getting it to boot. All seemed great except the was no signal, unknown IMEI (with exception of getvar command), unknown baseband and also cannot save any APN. It won't allow. There are no APN profiles but when I create a new one and click save, it goes back to blank. Sim card is not issue. The problem seems to be with everything concerning network part of the phone. WifI works. I figured since boot issue is resolved I will try RUU utility again but got the same results, back to boot loop.
Next I reverted back to Cyno since it was bootable and I was able to acheive S-Off via firewater and got rooted. I have flashed from cyno 11 down to cyno 10 but same results, no service, imei unkown as well as the other related.
I have ended up with Google play version rom. Also downgraded from 1.55 to 1.54. The last two things a just done was flash darkboot, and reflashed AT&T radio version the showed in getvar and along with trying the newest radio.
Anything I flash goes thru no errors however, this most needed part of the phone won't wake up.
Maybe try international roms on it. Sounds the radio that you flashed or it has is not compatible with it's hardware.
Will do
Solarenemy68 said:
Maybe try international roms on it. Sounds the radio that you flashed or it has is not compatible with it's hardware.
Click to expand...
Click to collapse
I will try that. All I know is, it is a black version with AT&T logo on the rear. Like you stated, the radio or something is not compatible.
Whatever part of the phone that handles these missing functions is just not communicating with the rest of the phone.
Tried all the AT&T radios. None would help. Still no service, imei & baseband shows unknown, sim not detected, apn's won't save.
Tried everything imaginable. I wish I wasn't so determined I should have stopped many hours ago. Doesn't seem anyone knows what causes this. I can see my imei in the getvar but not in the OS. What's weird is that if I flashed a stock AT&T rom I go back to bootloop but I think that something totally different than the GSM part of the phone not working or detecting sim cards. I'm not sure but it seems that if the sim reader was bad I could still view IMEI in About Phone or when pressing * # 06 #
I am having exactly the same problems. Exactly. I was about to post something like this before I stumbled upon this thread. Please update if you find any solution.
Have you tried running any RUUs?
Sent from my HTC One using xda app-developers app
Yes I did. It starts bootlooping at the htc screen. It cannot b a hardware problem with right since we can see the imei in fastboot?
Sent from my HTC One using xda app-developers app[/QUOTE]
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Thanks
MLIGN said:
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Click to expand...
Click to collapse
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Nobody has it, run the ruu its safer and it appears to not have the [email protected] drain that they pulled the update because of
JEANRIVERA said:
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Click to expand...
Click to collapse
JEANRIVERA said:
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Click to expand...
Click to collapse
I haven't been running the AT&T version of this phone for the past week..
I also heard that they pulled the OTA..
As soon as it is back. I'll go back to AT&T to get the OTA, Radio, and Stock Backup for you all!
Which restore is the 4.4.2? My cousins phone is stuck rebooting, so I reset it and its stuck on boot.
AT&T stock recovery 2.23.502.3
For those that might need it, here is the stock recovery from the 2.23 RUU. If anyone is interested, I could also add to this post exactly how I get the recovery. It took me about 2 hours to get all the info together that I needed in order to pull it off.
Steps to extract stock recovery:
1. Flash stock RUU.
2. Boot into TWRP. Don't flash TWRP to phone, but boot into it running on computer. Do this by using the command "fastboot boot recovery.img". Same steps as flashing a new recovery, but in this case you just boot the phone into this version of recovery. You can use the instructions at the link below, just replace flash with boot.
http://teamw.in/project/twrp2/225
3. Root phone by installing SuperSU. Flash the SuperSU.zip from your booted recovery.
4. Reboot phone and update SuperSU from the play store.
5. Connect phone to computer and use ADB to copy recovery partition to img file on phone. I used the guide at this page:
http://forum.xda-developers.com/showthread.php?t=2450045
For the AT&T M8 the block you need to dump is mmcblk0p43
So the command will be this:
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
Is the 1.58.502.1 stock backup without root?
Answerd my own question by flashing it,no root witch is cool cause all I would have to do to receive ota is flash the stock recovery alongside. Thank you for this ,I used it to go back to stock and use SunShine to S-OFF
Sent from my SM-T700 using Tapatalk
how do you actually use these to get back to stock?
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
The_Zodiac said:
how do you actually use these to get back to stock?
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
Click to expand...
Click to collapse
Download zip file and extract it with root explorer of choice
:navigate to extract location and open the extracted folder,once in that folder you should open the next folder and copy the numbered folder over to your TWRP/backup folder as if it was a backup you made.
Or start searching how to RUU back to stock with adb/fastboot
Sent from my SM-T700 using Tapatalk
jball said:
Download zip file and extract it with root explorer of choice
:navigate to extract location and open the extracted folder,once in that folder you should open the next folder and copy the numbered folder over to your TWRP/backup folder as if it was a backup you made.
Or start searching how to RUU back to stock with adb/fastboot
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
yeah ended up finding the RUU to get back to stock, now my problem is i cant re unlock my bootloader
(Thread here http://forum.xda-developers.com/att-htc-one-m8/help/help-getting-to-stock-att-m8-t2912921)
thanks for helping man
With the OP permission I could make a video of how to use the stock backup from downloading of the file to executing the flashing for a more visual learning
Sent from my SM-T700 using Tapatalk
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
The_Zodiac said:
yeah ended up finding the RUU to get back to stock, now my problem is i cant re unlock my bootloader
(Thread here http://forum.xda-developers.com/att-htc-one-m8/help/help-getting-to-stock-att-m8-t2912921)
thanks for helping man
Click to expand...
Click to collapse
Are you still using the tool kit ?
Try your original key and use the adb/fastboot method .or how about posting the steps you've taken in attempts at unlocking your bootloader this time
Sent from my SM-T700 using Tapatalk
jball said:
With the OP permission I could make a video of how to use the stock backup from downloading of the file to executing the flashing for a more visual learning
Sent from my SM-T700 using Tapatalk
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
Are you still using the tool kit ?
Try your original key and use the adb/fastboot method .or how about posting the steps you've taken in attempts at unlocking your bootloader this time
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
was able to get it to work with a new unlock.bin from htd.dev
Great work. Helpful!
Thanks
I am currently on CM11 and want to get back to stock and update to latest firmware. I will need to flash both the backup and recovery 1.12.502.18 and then ota update. Then I can reflash a custom recovery again. Is that correct?
Here is my info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.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: *REMOVED
(bootloader) imei: *REMOVED
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
MLIGN said:
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Click to expand...
Click to collapse
how about earlier hboots ,to downgrade
mws1986 said:
I am currently on CM11 and want to get back to stock and update to latest firmware. I will need to flash both the backup and recovery 1.12.502.18 and then ota update. Then I can reflash a custom recovery again. Is that correct?
Here is my info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.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: *REMOVED
(bootloader) imei: *REMOVED
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you ever figure it out? I'm on the same boat and need to update my firmware. I have the same info as you, s-on, same bootloader version, same radio, etc. That's what I was thinking of doing. Flash stock rom, flash recovery, get ota, then flash twrp recovery again. I'm on att as well.
Gilbertinho said:
Did you ever figure it out? I'm on the same boat and need to update my firmware. I have the same info as you, s-on, same bootloader version, same radio, etc. That's what I was thinking of doing. Flash stock rom, flash recovery, get ota, then flash twrp recovery again. I'm on att as well.
Click to expand...
Click to collapse
That probably isn't going to do what you want. OTA will only update you to Android 4.4.2 and hboot 3.16, which is what you've already got.
What version firmware are you trying to update to. Or asked another way, what ROM are you trying to run? The issue is a bit complicated now, as the current custom ROMs are split on firmware 3.x or 4.x (neither of which are "officially" released by AT&T yet).
redpoint73 said:
That probably isn't going to do what you want. OTA will only update you to Android 4.4.2 and hboot 3.16, which is what you've already got.
What version firmware are you trying to update to. Or asked another way, what ROM are you trying to run? The issue is a bit complicated now, as the current custom ROMs are split on firmware 3.x or 4.x (neither of which are "officially" released by AT&T yet).
Click to expand...
Click to collapse
I am currently running ViperOneM8 1.8 and am trying to run ViperOneM8 2.5.0 which requires you to have the 4.4.3 base firmware. From my understanding AT&T released this OTA. The newer roms require 4.4.4 which AT&T has yet to release. I am not trying to update to 4.4.4 since that requires S-OFF, which I dont want to/don't know how to do. Thanks for the reply by the way!