Database Develop

I broke it, can you fix it?

I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.

I did s-off since you're unlocked. Probably the issue. Then I would go into fast boot to either ruu or transfer a rom
I think rumrunner is what works on 1.55 hboot
Sent from my HTC One

krankenator said:
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
Click to expand...
Click to collapse
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone

clsA said:
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
Click to expand...
Click to collapse
Not pro, but I hobble by. Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

krankenator said:
Not pro, but I hobble by. Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new

clsA said:
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
Click to expand...
Click to collapse
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.

krankenator said:
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
Click to expand...
Click to collapse
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995

clsA said:
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
Click to expand...
Click to collapse
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot

krankenator said:
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
I don't think that file requires s-off
but yes a locked boot loader is needed
fastboot oem lock

Well, time to try something else.
Any ideas anyone?

krankenator said:
Something didn't work. It only reboot to the bootloader.
Pro-Mac-Jesseesktop jesse$ ./fastboot oem lock
Click to expand...
Click to collapse
FAILED (remote: 12 signature verify fail)
I'll take a guess this means you need s-off
or a windows PC to run the RUU.exe I posted first

[Q] HELP with updating HTC One to 4.4...

Hello, I have a rooted international HTC One currently running 4.3 Android with Sense 5.0. I am trying to perform an OTA system update that I have received... I downloaded the new 4.4 Android (1.1 GB) and I have selected "Install Update". But when the phone restarts, it just enters recovery and opens TWRP by itself!
So then I try to flash the downloaded OTA file via TWRP, but that also fails... Does anyone know how I can get 4.4 on my HTC One? Thank you

arbank94 said:
Hello, I have a rooted international HTC One currently running 4.3 Android with Sense 5.0. I am trying to perform an OTA system update that I have received... I downloaded the new 4.4 Android (1.1 GB) and I have selected "Install Update". But when the phone restarts, it just enters recovery and opens TWRP by itself!
So then I try to flash the downloaded OTA file via TWRP, but that also fails... Does anyone know how I can get 4.4 on my HTC One? Thank you
Click to expand...
Click to collapse
You can't apply ota with a custom recovery, you need your stock recovery.

arbank94 said:
Hello, I have a rooted international HTC One currently running 4.3 Android with Sense 5.0. I am trying to perform an OTA system update that I have received... I downloaded the new 4.4 Android (1.1 GB) and I have selected "Install Update". But when the phone restarts, it just enters recovery and opens TWRP by itself!
So then I try to flash the downloaded OTA file via TWRP, but that also fails... Does anyone know how I can get 4.4 on my HTC One? Thank you
Click to expand...
Click to collapse
Depending on whats been done to the phone you can eather flash stock recovery and try the update from their or you have to ruu back to stock and take the update that way.
fastboot getvar all will tell you what stock recovery you need or what ruu to use

alray said:
You can't apply ota with a custom recovery, you need your stock recovery.
Click to expand...
Click to collapse
So would you recommend getting stock recovery following nkk71's guide in your signature, or should I just flash a 4.4 rom?

arbank94 said:
So would you recommend getting stock recovery following nkk71's guide in your signature, or should I just flash a 4.4 rom?
Click to expand...
Click to collapse
Do what cIsA said. Check the output of "fastboot getvar all". Look at your main-ver # and find the corresponding stock recovery. There is a thread in general section with a collection of stock recovery.
You can post the output of getvar here minus imei/sn and we will link you the correct recovery.

Okay so I ran a fastboot getvar all, and apparently there is no RUU for my device, because it is Latin American with a CID of HTC_332. (I searched almost everywhere)
Now, after flashing a 4.4 rom I downloaded, my HTC device wasn't turning on anymore (it was getting stuck at the HTC boot logo). So I restored from a backup I made in TWRP, and that didn't work either. So now my problem just got 1000x worse because of a mistake I just made now of completely wiping my device and the OS.
So for the moment I'll try to flash a new boot.img, get S-OFF again, and change the CID to 11111111 (as I have read) where I will then download a RUU I can use. I'll let you know what happens.

Whoa there.. No need to flash boot.IMG.
What's you're steps? I think you are about to make it worse
sent from my mobile device

Okay well I'm in a tight situation atm.
My phone is completely wiped, with no OS or anything. The only thing I have access to is fastboot, and the TWRP bootloader. Also considering my phone is wiped, I believe I have S-ON as well.
So what is the first step to just get a boot going? (unless I'm not completely screwed that is..)
EDIT- I have successfully flashed Android Revolution to my phone from TWRP by pushing the zip via adb fastboot. Got my phone running again. Step 1 complete.
Step 2 now is to get S-OFF again...
Step 3- Change my CID to 11111111 using the SuperCID method (there is no RUU for my Latin American CID; HTC_332)
Step 4- Use an appropriate RUU to get 4.4 stock after I have changed my CID.
Before I continue with these steps, can anyone confirm with me if I am on the right path?

Step 2 - Confirmed.
Step 3 & Step 4 ... What is an appropriate RUU? You have not yet posted a fastboot getvar all output yet. (remove imei)

SaHiLzZ said:
Step 2 - Confirmed.
Step 3 & Step 4 ... What is an appropriate RUU? You have not yet posted a fastboot getvar all output yet. (remove imei)
Click to expand...
Click to collapse
I had the same cid when I bought mine. Irc, MID was PN0711000 with s.w. X.XX.599.X.
so he could use the 1.29.401.2 ruu on htc1guru but he have to change cid.
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
arbank94 said:
EDIT- I have successfully flashed Android Revolution to my phone from TWRP by pushing the zip via adb fastboot. Got my phone running again.
Before I continue with these steps, can anyone confirm with me if I am on the right path?
Click to expand...
Click to collapse
You could just stay with arhd, its a very good rom...

alray said:
You could just stay with arhd, its a very good rom...
Click to expand...
Click to collapse
Agreed!:laugh:

alray said:
I had the same cid when I bought mine. Irc, MID was PN0711000 with s.w. X.XX.599.X.
so he could use the 1.29.401.2 ruu on htc1guru but he have to change cid.
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
You could just stay with arhd, its a very good rom...
Click to expand...
Click to collapse
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>adb push htcrom2.zip /sdcard/
3455 KB/s (1180577030 bytes in 333.659s)
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH392W901414
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e0349bfc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
So yeah... there's no RUU as I said.
alray, in order to use that 1.29.401.2 RUU, what do I have to change my CID to?
EDIT: I'll just stick with your suggestion alray and stay with ARHD lol. (but in case I change my mind, what CID should I change to for that RUU?... so that I won't have to bump this thread or make a new one later)

arbank94 said:
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>adb push htcrom2.zip /sdcard/
3455 KB/s (1180577030 bytes in 333.659s)
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH392W901414
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e0349bfc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
So yeah... there's no RUU as I said.
alray, in order to use that 1.29.401.2 RUU, what do I have to change my CID to?
EDIT: I'll just stick with your suggestion alray and stay with ARHD lol. (but in case I change my mind, what CID should I change to for that RUU?... so that I won't have to bump this thread or make a new one later)
Click to expand...
Click to collapse
These CID:
HTC__001
HTC__J15
HTC__A48
HTC__M27
are compatible with the 1.29.401.2 ruu.zip so i'll suggest you to use HTC__001 if you change your mind. Personally, I would stay on ARHD. No benefit to flash that RUU vs ARHD. ARHD is always up to date...

[Q] Switching To Developers Edition

Hey, Im s-off on bell mobility in canada. Hboot 1.57. Was wondering what my best way to change over to a developers edition would be>

Howie3045 said:
Hey, Im s-off on bell mobility in canada. Hboot 1.57. Was wondering what my best way to change over to a developers edition would be>
Click to expand...
Click to collapse
I changed my India Rom to US dev edition Rom
1 S Off
2 Install TWRP
3 use Aroma MID changer tool change MID to PN0712000
4 change CID BS_US001
5 now flash any US dev edition firmware
6 Flash RUU of US dev edition

yatindroid said:
I changed my India Rom to US dev edition Rom
1 S Off
2 Install TWRP
3 use Aroma MID changer tool change MID to PN0712000
4 change CID BS_US001
5 now flash any US dev edition firmware
6 Flash RUU of US dev edition
Click to expand...
Click to collapse
which firmware should i install if i am using this ruu.exe http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/
my htc one isnt a dual sim. its the bell mobility one

Howie3045 said:
which firmware should i install if i am using this ruu.exe http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/
my htc one isnt a dual sim. its the bell mobility one
Click to expand...
Click to collapse
if you flash the 3.22.1540.1 decrypted ruu from htcguru.com, you dont need to flash the firmware, just follow yatin's instructions. firmware is included in the ruu.

alray said:
if you flash the 3.22.1540.1 decrypted ruu from htcguru.com, you dont need to flash the firmware, just follow yatin's instructions. firmware is included in the ruu.
Click to expand...
Click to collapse
where would i find these instructions. would love some sort of guide so i dont mess this up lol.

Howie3045 said:
where would i find these instructions. would love some sort of guide so i dont mess this up lol.
Click to expand...
Click to collapse
yatin and me can assist you in this thread.
first post the output of "fastboot getvar all" so we can determine what steps are required for you to do the conversion. dont post your IMEI nor the SERIALNO strings of your getvar

alray said:
yatin and me can assist you in this thread.
first post the output of "fastboot getvar all" so we can determine what steps are required for you to do the conversion. dont post your IMEI nor the SERIALNO strings of your getvar
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s

Howie3045 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
1st change cid to BS_US001
Flashing Firmware 3.22.1540.1
fastboot oem rebootRUU
fastboot flash zip firmware.zip (2 times)
fastboot flash zip firmware.zip
fastboot reboot-bootloader
after that Run RUU 4.19.1540.9 then update OTA

Howie3045 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
ok in your case, this will be very easy :good:
first backup every important file (if any) from your phone to your computer, everything will be wiped, including your sdcard content (picture, song, video)
reboot phone in bootloader mode by holding power and volume down
when in bootloader, open a terminal window from your fastboot/adb folder and type:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then download this ruu and save it to your adb/fastboot folder. you can rename it ruu (ruu.zip), it will be easier in the terminal.
with phone still on bootloader mode, from the terminal window type:
Code:
fastboot oem rebootRUU
make sure "RUU" in rebootRUU are capital letters. you will now see a black screen with silver htc logo
type:
Code:
fastboot flash zip ruu.zip
it will say something like: "failed, flush image again immediately" so do the same command again:
Code:
fastboot flash zip ruu.zip
then
Code:
fastboot reboot
now your phone will boot normally (first boot can take longer than usual).
when phone is booted, go trough the setup process and then go in settings ---> phone ---> software update.
download and install each ota update from 3.22.1540.1 to 6.07.1540.1 (6 updates total)
or you can proceed like @yatindroid said, 2 differents ways for the same result. both method will works.

alray said:
ok in your case, this will be very easy :good:
first backup every important file (if any) from your phone to your computer, everything will be wiped, including your sdcard content (picture, song, video)
reboot phone in bootloader mode by holding power and volume down
when in bootloader, open a terminal window from your fastboot/adb folder and type:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then download this ruu and save it to your adb/fastboot folder. you can rename it ruu (ruu.zip), it will be easier in the terminal.
with phone still on bootloader mode, from the terminal window type:
Code:
fastboot oem rebootRUU
make sure "RUU" in rebootRUU are capital letters. you will now see a black screen with silver htc logo
type:
Code:
fastboot flash zip ruu.zip
it will say something like: "failed, flush image again immediately" so do the same command again:
Code:
fastboot flash zip ruu.zip
then
Code:
fastboot reboot
now your phone will boot normally (first boot can take longer than usual).
when phone is booted, go trough the setup process and then go in settings ---> phone ---> software update.
download and install each ota update from 3.22.1540.1 to 6.07.1540.1 (6 updates total)
or you can proceed like @yatindroid said, 2 differents ways for the same result. both method will works.
Click to expand...
Click to collapse
with your method i dont have to flash firmware first? just change the CID and flash the RUU? I noticed my MID is the same as the Developer Edition anyway.

i wanna say thanks. sure i can click a button but i want you guys to know you've been very help and i appreciate it. ive been pulling my hair out with this phone every since i rooted it. I think after i do this ill be back to where i want to be. Id love to be Bell stock again but i find bell stuff hard too find. Developers Edition shud suit me just fine

Howie3045 said:
with your method i dont have to flash firmware first? just change the CID and flash the RUU? I noticed my MID is the same as the Developer Edition anyway.
Click to expand...
Click to collapse
yes you can try this way but if RUU give error try you need flash firmware

yatindroid said:
yes you can try this way but if RUU give error try you need flash firmware
Click to expand...
Click to collapse
where can i grab that firmware just in case

Howie3045 said:
with your method i dont have to flash firmware first? just change the CID and flash the RUU? I noticed my MID is the same as the Developer Edition anyway.
Click to expand...
Click to collapse
exactly.
MID is already correct
just change mid to BS_US001
and flash the 3.22.1540.1 ruu.
advantage of my method is that its simpler
disadvantage is that its an old version and you'll have to download and install 6 ota updates.
advantage of yatin's method is that its a less old version and will only require 2 ota updates
disadvantage (not really big disadvantage) is to flash the firmware first, if not the ruu.exe will not flash. Personally i don't use 4.xx.xxx.x RUU because I never found any clue that they are official ruu released by HTC (not on their website). But it seem to works fine, I think yatin converted his phone using that ruu
both solution are good, just make sure you flash the right firmware if you go with the 4.xx.1540 ruu

alray said:
exactly.
MID is already correct
just change mid to BS_US001
and flash the 3.22.1540.1 ruu.
advantage of my method is that its simpler
disadvantage is that its an old version and you'll have to download and install 6 ota updates.
advantage of yatin's method is that its a less old version and will only require 2 ota updates
disadvantage (not really big disadvantage) is to flash the firmware first, if not the ruu.exe will not flash. Personally i don't use 4.xx.xxx.x RUU because I never found any clue that they are official ruu released by HTC (not on their website). But it seem to works fine, I think yatin converted his phone using that ruu
both solution are good, just make sure you flash the right firmware if you go with the 4.xx.1540 ruu
Click to expand...
Click to collapse
bootloader will stay unlocked correct? i like simple lol. im downloading the RUU for your method now. I already have all my pictures backed up on a flash drive. ill have to back up a cpl other small things but ill prob give this a try tonight.

Howie3045 said:
bootloader will stay unlocked correct? i like simple lol. im downloading the RUU for your method now. I already have all my pictures backed up on a flash drive. ill have to back up a cpl other small things but ill prob give this a try tonight.
Click to expand...
Click to collapse
yes bootloader will stay unlocked and no need to relock it since dev edition phone came with an unlock bootloader from factory.

alray said:
yes bootloader will stay unlocked and no need to relock it since dev edition phone came with an unlock bootloader from factory.
Click to expand...
Click to collapse
I ran the RUU this morning. phone booted up fine. downloading first update as i type this. awesome. thank you guys so much

and updates are installing....very happy right now.
question though, once i get fully update to date with the dev edition, can i install TWRP and when any new updates come just install the stock recovery? i like using HTC One Tweaker and Sense 6 toolbox.

Howie3045 said:
and updates are installing....very happy right now.
question though, once i get fully update to date with the dev edition, can i install TWRP and when any new updates come just install the stock recovery? i like using HTC One Tweaker and Sense 6 toolbox.
Click to expand...
Click to collapse
if your bootloader is already unlocked, yes you can flash a custom recovery and then revert back to the stock 6.07.1540.1 recovery and install ota.
if your bootloarder is locked, you'll need to unlock it in order to flash a custom recovery and that will wipe /data/preload files and you'll will not be able to install ota directly.
to install ota, you need:
stock recovery
untouched /data/preload files
untouched /system files
Best thing to do is to make a nandroid backup right after flashing twrp. So if some /system files get modified (with a custom kernel for example) you'll be able to restore the backup, flash the stock recovery and install ota.
in last resort you can always flash your phone back to stock with a ruu and apply all ota.

alray said:
if your bootloader is already unlocked, yes you can flash a custom recovery and then revert back to the stock 6.07.1540.1 recovery and install ota.
if your bootloarder is locked, you'll need to unlock it in order to flash a custom recovery and that will wipe /data/preload files and you'll will not be able to install ota directly.
to install ota, you need:
stock recovery
untouched /data/preload files
untouched /system files
Best thing to do is to make a nandroid backup right after flashing twrp. So if some /system files get modified (with a custom kernel for example) you'll be able to restore the backup, flash the stock recovery and install ota.
in last resort you can always flash your phone back to stock with a ruu and apply all ota.
Click to expand...
Click to collapse
im back up and running with all updates. i just ran the RUU u suggested so i assume my bootloader should still be unlocked. i didnt relock it or anything

HTC One (M7) Unroot

Hello people.
I need your help regarding my AT&T HTC One M7.
My phone is rooted, has unlocked bootloader, and stock recovery. I want to unroot it and lock the bootloader
I tried the method with locking the bootloader and flashing stock RUU compatible with my CID and MID, but when I locked the bootloader the device couldn't boot to Android. Instead, it booted to fastboot. Anyways I continouted with the process and I tried to install my RUU, but in the middle of installation it gave me [error 155]. It gave me the same error with any other RUU I tried to install, can you help me?
Here is what i get when i type "getvar all" command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Torcidas1950 said:
Hello people.
I need your help regarding my AT&T HTC One M7.
My phone is rooted, has unlocked bootloader, and stock recovery. I want to unroot it and lock the bootloader
I tried the method with locking the bootloader and flashing stock RUU compatible with my CID and MID, but when I locked the bootloader the device couldn't boot to Android. Instead, it booted to fastboot. Anyways I continouted with the process and I tried to install my RUU, but in the middle of installation it gave me [error 155]. It gave me the same error with any other RUU I tried to install, can you help me?
Here is what i get when i type "getvar all" command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.

majmoz said:
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.
Click to expand...
Click to collapse
I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/

I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/
majmoz said:
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.
Click to expand...
Click to collapse

Torcidas1950 said:
I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/
Click to expand...
Click to collapse
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
In a command window type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

majmoz said:
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
Click to expand...
Click to collapse
Thanks, I will try that. But can I brick my phone or something else like that?

majmoz said:
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
Click to expand...
Click to collapse
Should I maybe try this older RUU.exe
http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

Can you run getvar all so we can see what firmware version you are on? Be sure to remove your IMEI and serial numbers.

MarkBell said:
Can you run getvar all so we can see what firmware version you are on? Be sure to remove your IMEI and serial numbers.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

the 3.17.502.3 ruu should work for you (with a relocked bootloader)
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
what error did you get?

nkk71 said:
the 3.17.502.3 ruu should work for you (with a relocked bootloader)
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
what error did you get?
Click to expand...
Click to collapse
Error 155, every time with any of these RUU's :/

Torcidas1950 said:
Error 155, every time with any of these RUU's :/
Click to expand...
Click to collapse
can you find the debug log, or use the ROM.ZIP in fastboot:
the usual procedure is:
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice!!
fastboot reboot-bootloader
but during the first flash it will throw an error, let's see what it is
to get the ROM.ZIP, run the RUU, once the first screen shows up there will be a new folder in %TEMP%, within it you will find a 1GB file called ROM.ZIP
if it's due to the missing version-main, you can fix that using the misctool http://forum.xda-developers.com/showthread.php?t=1526316

nkk71 said:
can you find the debug log, or use the ROM.ZIP in fastboot:
the usual procedure is:
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice!!
fastboot reboot-bootloader
but during the first flash it will throw an error, let's see what it is
to get the ROM.ZIP, run the RUU, once the first screen shows up there will be a new folder in %TEMP%, within it you will find a 1GB file called ROM.ZIP
if it's due to the missing version-main, you can fix that using the misctool http://forum.xda-developers.com/showthread.php?t=1526316
Click to expand...
Click to collapse
Can I do any damage to my phone if the ZIP RUU fails?

Torcidas1950 said:
Can I do any damage to my phone if the ZIP RUU fails?
Click to expand...
Click to collapse
nope, especially with S-ON and a signed/encrypted RUU.ZIP (the one contained in the RUU.EXE is signed/encrypted), so when you try to flash it using fastboot (which is the same thing the RUU.EXE does, but doesn't show textual progress - though there should be a log somewhere), the fastboot flash will start by various checks, if and only if all the checks pass (meaning the signature, MID, CID, etc are correct for your phone), the ruu will begin installation.
the first flash will do the hboot preupdate and say "failed flush again immediately", the second flash would continue flashing all other partitions

nkk71 said:
nope, especially with S-ON and a signed/encrypted RUU.ZIP (the one contained in the RUU.EXE is signed/encrypted), so when you try to flash it using fastboot (which is the same thing the RUU.EXE does, but doesn't show textual progress - though there should be a log somewhere), the fastboot flash will start by various checks, if and only if all the checks pass (meaning the signature, MID, CID, etc are correct for your phone), the ruu will begin installation.
the first flash will do the hboot preupdate and say "failed flush again immediately", the second flash would continue flashing all other partitions
Click to expand...
Click to collapse
So, does that mean it will fail like the RUU.exe did because I'ts the same way of installing, just its showing install wizard instead of CMD?

Torcidas1950 said:
So, does that mean it will fail like the RUU.exe did because I'ts the same way of installing, just its showing install wizard instead of CMD?
Click to expand...
Click to collapse
yes most probably it will fail, the RUU.EXE is basically just a "container" for the ruu.zip (called ROM.ZIP).... the exe will extract fastboot/adb/rom.zip/etc files into a temp directory and then basically do the commands i listed above.
(I do believe the "wizard" does some initial checks just for the sake of visual feedback, but the actual flashing is done using fastboot commands in the background)

nkk71 said:
yes most probably it will fail, the RUU.EXE is basically just a "container" for the ruu.zip (called ROM.ZIP).... the exe will extract fastboot/adb/rom.zip/etc files into a temp directory and then basically do the commands i listed above.
(I do believe the "wizard" does some initial checks just for the sake of visual feedback, but the actual flashing is done using fastboot commands in the background)
Click to expand...
Click to collapse
Then where can I find that debug log from previous attempts? Its too much things to do just to see where is the error

Torcidas1950 said:
Then where can I find that debug log from previous attempts? Its too much things to do just to see where is the error
Click to expand...
Click to collapse
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever

nkk71 said:
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever
Click to expand...
Click to collapse
Something like this? I have around 10 of these in my C:\Temp\HTC folder
Start time: 2014/6/22, 13:1:7
Main
readConfig ok
InitInstance
HSM OLD HTC driver 3.0 is not installed.
Check Driver Version = 4.11.0.001
HSM OLD HTC driver 4.0 is needed to be upgraded.
The USB driver is needed to be upgraded
HSM already installed
WMP version = 12.0.7601.18150
Copy Installer folder from H:\ to C:\TEMP\HTCDriver
HSM OLD HTC driver is not existed
Check Driver Version = 4.11.0.001
HSM OLD HTC driver is installed.
Start to uninstall HSM OLD htc driver.
Uninstall HSM OLD htc driver finished.
New Driver Version = 4.3.0.001
Start to execute HTCDriverInstaller.
HTCDriverInstaller is finished.
Delete Installer folder C:\TEMP\HTCDriver
Please replug USB cable before using the USB functions.
HTC Sync Manager autorun,finished
End time: 2014/6/22, 13:3:18

nkk71 said:
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever
Click to expand...
Click to collapse
Here is the file i found in C:\ruu_log\
I had to .zip it because it didn't want to upload in .log format

[Q] AT&T HTC One Lollipop RUU update issue

Hi ,
I unlocked the bootloader last and installed JB successfully. Now i downloaded the Lollipop RUU from HTC website and trying to update but it is going upto sending files(0/5) . i waited till 30 mins as it is showing it will take ten minutes. im uploading the screenshot of the update.Please help me on this.
thanks,
sai

gopiann said:
Hi ,
I unlocked the bootloader last and installed JB successfully. Now i downloaded the Lollipop RUU from HTC website and trying to update but it is going upto sending files(0/5) . i waited till 30 mins as it is showing it will take ten minutes. im uploading the screenshot of the update.Please help me on this.
thanks,
sai
Click to expand...
Click to collapse
If you are S-ON then you need to have your bootloader "locked/relocked" before the RUU will run successfully.

majmoz said:
If you are S-ON then you need to have your bootloader "locked/relocked" before the RUU will run successfully.
Click to expand...
Click to collapse
My bootloader is already locked .Here is the screenshot.I am getting the Error when i trying to update the rom. I tried in both Windows 7 and 8.1 . SS is attached.

gopiann said:
My bootloader is already locked .Here is the screenshot
Click to expand...
Click to collapse
Can you post a fastboot getvar all except remove your imei and serialno prior to posting?
What RUU are you trying to run and where did you get it?

gopiann said:
My bootloader is already locked .Here is the screenshot.I am getting the Error when i trying to update the rom. I tried in both Windows 7 and 8.1 . SS is attached.
Click to expand...
Click to collapse
majmoz said:
Can you post a fastboot getvar all except remove your imei and serialno prior to posting?
What RUU are you trying to run and where did you get it?
Click to expand...
Click to collapse
I got this RUU from HTC website lollipop update
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(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: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s

gopiann said:
I got this RUU from HTC website lollipop update
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(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: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
Click to expand...
Click to collapse
@clsA Do you have any idea why he is not able to run the Lollipop RUU?
Try these steps:
Boot your phone into Bootloader
Plug your phone into your computer you should see FASTBOOT USB
Run the RUU

majmoz said:
@clsA Do you have any idea why he is not able to run the Lollipop RUU?
Try these steps:
Boot your phone into Bootloader
Plug your phone into your computer you should see FASTBOOT USB
Run the RUU
Click to expand...
Click to collapse
I posted the rom.zip with instructions here it might help
http://forum.xda-developers.com/htc-one-att/general/capture-3-31-15-lollipop-ota-update-ruu-t3070978
the firmware and stock recovery are also their

clsA said:
I posted the rom.zip with instructions here it might help
http://forum.xda-developers.com/htc-one-att/general/capture-3-31-15-lollipop-ota-update-ruu-t3070978
the firmware and stock recovery are also their
Click to expand...
Click to collapse
majmoz said:
@clsA Do you have any idea why he is not able to run the Lollipop RUU?
Try these steps:
Boot your phone into Bootloader
Plug your phone into your computer you should see FASTBOOT USB
Run the RUU
Click to expand...
Click to collapse
I tried to as you said but i got error as
Loading zip info fail
update fail!

clsA said:
I posted the rom.zip with instructions here it might help
http://forum.xda-developers.com/htc-one-att/general/capture-3-31-15-lollipop-ota-update-ruu-t3070978
the firmware and stock recovery are also their
Click to expand...
Click to collapse
Can i try this process?
I'm also uploading the Rom.zip from the 7.23.502.1 RUU here >> https://www.androidfilehost.com/?fid=95916177934550030
fastboot oem rebootRUU
fastboot flash zip Rom.zip
fastboot flash zip Rom.zip
fastboot reboot

gopiann said:
Can i try this process?
I'm also uploading the Rom.zip from the 7.23.502.1 RUU here >> https://www.androidfilehost.com/?fid=95916177934550030
fastboot oem rebootRUU
fastboot flash zip Rom.zip
fastboot flash zip Rom.zip
fastboot reboot
Click to expand...
Click to collapse
for this command it is showing fastboot oem rebootRUU "Waiting for devices"

gopiann said:
for this command it is showing fastboot oem rebootRUU "Waiting for devices"
Click to expand...
Click to collapse
You need to install the HTC drivers if your phone is not seen in fastboot

clsA said:
You need to install the HTC drivers if your phone is not seen in fastboot
Click to expand...
Click to collapse
thanks but its already installed latest drivers and tested on both Windows 7 and 8.1

gopiann said:
thanks but its already installed latest drivers and tested on both Windows 7 and 8.2
Click to expand...
Click to collapse
155 error is wrong RUU and I can see from your fastboot getvar all its the wrong RUU, your on 4xxxx firmware and trying to flash 7xxxxxx firmware, you need all of the 5xxxx and 6xxxxxx first before the RUU will work, you cant just jump straight from 4 to 7, if you had of got it to work you would have a nice new paperweight now, only way too do that is get s-off.

Seanie280672 said:
155 error is wrong RUU and I can see from your fastboot getvar all its the wrong RUU, your on 4xxxx firmware and trying to flash 7xxxxxx firmware, you need all of the 5xxxx and 6xxxxxx first before the RUU will work.
Click to expand...
Click to collapse
then i have yo update first 5.XXX then 7.XXXX right?

gopiann said:
then i have yo update first 5.XXX then 7.XXXX right?
Click to expand...
Click to collapse
you need all of the 5xxxx firmware packages and all of the 6xxxxxx packages, then after you've finished all of those, you can run the Lollipop 7xxxx RUU.
You may be able to find them in the HTC One AT&T forums http://forum.xda-developers.com/htc-one-att/general

Seanie280672 said:
you need all of the 5xxxx firmware packages and all of the 6xxxxxx packages, then after you've finished all of those, you can run the RUU.
You may be able to find them in the HTC One AT&T forums http://forum.xda-developers.com/htc-one-att/general
Click to expand...
Click to collapse
after 5.XXXX, they released 7.XXXXX i guess

gopiann said:
after 5.XXXX, they released 7.XXXXX i guess
Click to expand...
Click to collapse
couldnt tell you myself, do you have an AT&T sim in your phone ?

Seanie280672 said:
couldnt tell you myself, do you have an AT&T sim in your phone ?
Click to expand...
Click to collapse
sorry bro i forgot to tell that mobile is using now in India.

gopiann said:
sorry bro i forgot to tell that mobile is using now in India.
Click to expand...
Click to collapse
thats why you cant do OTA's, you better off just getting s-off and converting the phone, you must be connected to the AT&T network to get OTA's.
To get s-off though, you will need to use sunshine which will cost $25 and need a working stock rom on your phone.
if your going to flash firmware on your phone whilst s-on, you need to be very careful you dont skip any steps or packages or you'll brick your phone.

gopiann said:
sorry bro i forgot to tell that mobile is using now in India.
Click to expand...
Click to collapse
Seanie280672 said:
thats why you cant do OTA's, you better off just getting s-off and converting the phone, you must be connected to the AT&T network to get OTA's.
To get s-off though, you will need to use sunshine which will cost $25 and need a working stock rom on your phone.
if your going to flash firmware on your phone whilst s-on, you need to be very careful you dont skip any steps or packages or you'll brick your phone.
Click to expand...
Click to collapse
First off their was no 6.x firmware for AT&T ... he's on 4.x so a 5.x firmware followed by the RUU should work
If your getting waiting on device after fastboot oem rebootRUU your drivers are not installed correctly
See post 2 FAQ 2 of nkk71 guide here on how to get fastboot driver working >> http://forum.xda-developers.com/showthread.php?t=2541082
I updated one phone with the OTA and another with the RUU so I know they both work, problem is I could not locate the first OTA to 5.32.502.3
So flashing just the OTA is out until I get that missing file (you would also need s-off to use the OTAPkg.zip's)