Database Develop

[Q] Strange issues - Return to Stock Needed...

Hi guys,
This is mostly my fault I believe. Like a young boy, excited about a new toy that just came out, I tried to flash the new Sprint OTA update in TWRP. Well, it failed just as I thought it may. Later on, I read that flashing that OTA in any recovery was something that should not be done. At any rate, it is too late to change what has been done.
The issue that I am facing, which seems to coincide with the day that I flashed the OTA in TWRP, is that people are only receiving only one part of my text messages. For instance, say I type a long message which would equal the length of 3 SMS messages. The recipient will only receive part 1/3 or part 3/3.
I updated my PRL and Profile.... No change... So, I decided to go back to stock and endure the grueling process of restoring my phone's SMS logs, contacts, configuration, etc, etc. I know that Google will sync and most of my contacts will be replaced. But some things like games I pay money to play must be reconfigured and other customizations will have to be "re-customized".
Regardless, I need to go back to stock and start all over. I tried several methods, all required that the bootloader be re-locked. This is when the trouble started. I relocked the bootloader via Fastboot. But running the RUU for version 1.29.651.7 fails as I am on 1.31 I believe? I will paste my specs below.
Anyway, it all boils down to a couple of things.
1.) Returning to Stock using an image that is NOT roooted (and also encrypted)?
2.) Returning my Bootloader to stock so that I can run the latest OTA (Is it recommended to run the latest OTA?)
3.) Doing it without bricking my device. Lol!
Now, I have the latest SDK for ADB installed. I have several different Stock images I've downloaded and tried but they all fail. I'm afraid that I am going to have to use one that is 1.31.xxx..
So here is my info from Fastboot, I can provide more detailed information if needed.
C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.194s
Click to expand...
Click to collapse
Again, the goal is stock (unrooted), just like it came out of the box. I will re-root again later but for now I need to fix this SMS issue as it's making it hard to communicate with my colleagues and friends. Again, should I flash the new Sprint OTA update that takes me up to 4.3.3? It does sound tantalizing to see what new features they have incorporated in this update. Here is the name of the OTA:
OTA_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2-1.31.651.2_release_335437r9p4z0zrva4gqsfs
Click to expand...
Click to collapse
As usual, any help or insight in to my problem(s) is appreciated. And for the record, the bootloader is again "unlocked". My plan as of right now is to recover using a NANDROID I made about a month ago. This should fix the SMS issue, but I still need to go back to stock so I can start from scratch.
Thanks in advance!
Regards,

Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

Here is a helpful link also: http://forum.xda-developers.com/showthread.php?t=2277892
Sent from my HTCONE using Tapatalk

Konfuzion said:
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll follow the instructions. Thank you for pointing me in the right direction. It does suck though, 4.3.3 is supposed to bring some new and exciting additions to the Android OS.
Anyway, I'll post if I run in to problems.
Thanks!

tonyrance said:
Here is a helpful link also: http://forum.xda-developers.com/showthread.php?t=2277892
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks Tonyrance!

PAinguINx said:
Ok, I'll follow the instructions. Thank you for pointing me in the right direction. It does suck though, 4.3.3 is supposed to bring some new and exciting additions to the Android OS.
Anyway, I'll post if I run in to problems.
Thanks!
Click to expand...
Click to collapse
You can update to 4.3 manually after getting s-off
Shoot me a PM if you need help with any of it

Konfuzion said:
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?

PAinguINx said:
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
Click to expand...
Click to collapse
Run the 1.29.651.10 RUU then use revone or mooshine to s-off

bigdaddy619 said:
Run the 1.29.651.10 RUU then use revone or mooshine to s-off
Click to expand...
Click to collapse
Ok, that's the RUU I have, well the only one I have that has a "Setup.exe" the others just contain misc files and a .img file..
Could you run through the process for installing revone via ADB please? I've seen several different methods. Just want to make sure everything works out properly.

Ok, following these instructions I still run in to issues with ADB. I was able to open a Shell while the phone was on and booted but when I boot in to recovery and try to start a shell it states "error: device not found".
This is what I'm doing...
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Click to expand...
Click to collapse
What am I doing wrong as to not obtain a shell?

PAinguINx said:
Ok, that's the RUU I have, well the only one I have that has a "Setup.exe" the others just contain misc files and a .img file..
Could you run through the process for installing revone via ADB please? I've seen several different methods. Just want to make sure everything works out properly.
Click to expand...
Click to collapse
Check PM

PAinguINx said:
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
Click to expand...
Click to collapse
This is the easiest way I know of to use Revone
http://forum.xda-developers.com/showthread.php?p=42452138#post42452138
However moonshine might be a better bet since it has the modified hboot which gets rid of the red warning text on boot. I am guessing bigdaddy pointed you in the right direction for the RUU.

bigdaddy619 said:
Check PM
Click to expand...
Click to collapse
I thought I messaged you man. But I didn't get a confirmation. Anyway, I donated $25 to you. Thanks again for your help bro. It has been appreciated!

[SOLVED][Q] Fully backing up before tampering (CID HTC__332) [Conversion to WWE]

Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it

mbinic said:
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
Click to expand...
Click to collapse
I just went through this a couple days ago with someone
go here and read pages 2-5 and see if you understand or still have questions read it all before moving on
http://forum.xda-developers.com/showthread.php?t=2593387&page=2

Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone

mbinic said:
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
Click to expand...
Click to collapse
yes after the conversion to .401 you will have a EU device and can update and flash all the new roms as they come out.
make note of the 2 links posted about changing your MID / CID their important steps in the whole process
http://forum.xda-developers.com/showthread.php?t=2535365
this guide by @nkk71 is a good source of information your just doing a few things differently
http://forum.xda-developers.com/showthread.php?t=2541082

OK, so part one is going mostly smoothly for now - unlocked bootloader, flashed TWRP, backed up (uploading for sharing) + saved partitions for rumrunner if I end up needing them (also uploading), had a few bootloops but managed to get ARHD 31.6 running. Now onto rumrunner...

I got S-OFF with rumrunner in the first try! Now to re-read and change CID and MID (4:40 AM, fingers crossed, heart pounding)

I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?

mbinic said:
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
Click to expand...
Click to collapse
Almost
1- change you MID to PN071000 using the tool
2- with SuperCID you cannot receive OTAs, so you need to change CID to European unbranded, there are several (this will affect the country/language options): http://forum.xda-developers.com/showpost.php?p=48195855&postcount=98 (instructions are also in that post)
so for example, if you wanted Eastern European languages you would need to set CID to HTC__032
3- since you're on hboot 1.55, you need to downgrade that separately to 1.44
4- you can leave the phone UNLOCKED, and even TAMPERED, but if you prefer to set them LOCKED and remove TAMPERED you can follow my guide.
5- run the RUU you mentioned
6- KEEP S-OFF!!
OTAs will not be affected by unlocked bootloader, or S-Off
let me know if you need more details

Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!

mbinic said:
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
Click to expand...
Click to collapse
yep, that works!
don't want to confuse you , but 1 2 and 3 can be run in any order, most important is to do run the ruu as last step, once the ruu has completed you should immediately receive OTAs.
remember, stay S-Off, consider it your "get out of jail" card, in case you ever want to change something again.

Thanks again I'll try it in a couple of hours and report my progress.
Edit:
OK, got CID HTC__032 and changed MID successfully. AROMA hung at 0.00%, but a restart helped like it was described in the post. Now onto HBOOT and RUU.
Edit 2:
Installed HBOOT 1.44 and the Guru Bootloader reset - removed tampered and set locked (why not ). Running RUU in a few minutes...

So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there

mbinic said:
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
Click to expand...
Click to collapse
Congrats mate
Can you also edit main thread title to include [SOLVED], thanks

Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end

mbinic said:
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
Click to expand...
Click to collapse
4.4 (hopefully 4.4.2) not out yet for most, only US Dev Edition, and has a few "bad habits" for the rest of the world... no need to change CIDs, it'll come soon enough....
ARHD 41.0 and MaximusHD are based on the US Dev Edition, not the WWE edition.

I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!

my htc
mbinic said:
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
Click to expand...
Click to collapse
hi friends first my english is not so good so excuse me i a have some mistakes, then i want to say i was reading your experience, i got the same version of htc one HTC_332 this is the cid for latin america this is what htc supports tell me by email, ok i got a little questions maybe u can help me
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
for last i want to thanks for the time you take to anwer me

Hello edulaffont,
edulaffont said:
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
Click to expand...
Click to collapse
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here

first
mbinic said:
Hello edulaffont,
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
Click to expand...
Click to collapse
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english

edulaffont said:
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
Click to expand...
Click to collapse
I also got that update as soon as I bought the phone, some time in October/November I think, it's old.
I didn't change the firmware when I was converting to WWE, a .401 version wasn't out yet.
I did change it last night though, and installed ARHD 51 (it gives me more options than stock) and everything went smoothly (I even did a dirty flash).
Anyway, I recommend you stick to the original instructions (use old ARHD for rumrunner), and when you're done converting to WWE, ran the RUU and everything works you can choose wheter you want to get the OTAs and stay stock (KitKat 4.4.2 OTA for WWE just came out, with new firmware), or root and install any ROM you wish

[q] htc one bicked - start up loop (cant find ruu file)

I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921

abreu6 said:
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
Click to expand...
Click to collapse
There is an RUU for your One. The only issue is that ur S-ON and the RUU is for a lower firmware version than the one you have. To flash the RUU, you will have to downgrade your firmware, which needs S-OFF
Post the output of your getvar all. It'll help a lot
And do u have custom recovery?? What exactly did you do which bricked the phone ??

raghav kapur said:
There is an RUU for your One. The only issue is that ur S-ON and the RUU is for a lower firmware version than the one you have. To flash the RUU, you will have to downgrade your firmware, which needs S-OFF
Post the output of your getvar all. It'll help a lot
And do u have custom recovery?? What exactly did you do which bricked the phone ??
Click to expand...
Click to collapse
Hello, Thanks for helping out. I have a taiwan build of the phone, for some reason I got the message prompt to upgrade to kitkat and sense 5.5 ( the release isnt officially out in my region) I'm thinking I got it because of the firmware build of my phone, once i tried to upgrade thats where the stall happened.
To get S-Off i need to root my phone from my understanding is this correct ? I dont have a custom recovery will post the get var here.
Thanks again.

Since you bricked your phone, I'm going to safely assume you were at least on an unlocked bootloader. If that's the case, you can download the TWRP recovery image onto your PC and boot into it off your phone with the fastboot command "fastboot boot (recovery name).img". Once there, you can go to TWRP's advanced settings and turn on ADB sideload to install a ROM. After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON). That should get your phone back on.
My friend did the same thing the other day and that was how I got theirs working again.
Sent from my HTC One using xda app-developers app

decayer177 said:
"fastboot boot (recovery name).img".
Click to expand...
Click to collapse
That only works on hboot 1.44, "fastboot boot ...." was patched/broken after 1.44.
decayer177 said:
After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON).
Click to expand...
Click to collapse
That's not needed on the M7, it'll get flashed automatically during the install even with S-On.

decayer177 said:
Since you bricked your phone, I'm going to safely assume you were at least on an unlocked bootloader. If that's the case, you can download the TWRP recovery image onto your PC and boot into it off your phone with the fastboot command "fastboot boot (recovery name).img". Once there, you can go to TWRP's advanced settings and turn on ADB sideload to install a ROM. After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON). That should get your phone back on.
My friend did the same thing the other day and that was how I got theirs working again.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help, no its locked and not tampared. I'm guessing i do all of the above but unlook my bootloader first.

abreu6 said:
Thanks for the help, no its locked and not tampared. I'm guessing i do all of the above but unlook my bootloader first.
Click to expand...
Click to collapse
Which RUU file do you recommend I can downgrade to. The version I have is 3.63.709.3 is there a site with ruu files. I have the latest ota file from the htc website, is the ruu file in there ?
Will try the procedure today and re post here.

abreu6 said:
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
Click to expand...
Click to collapse
Here's a copy of my getvar, -
Version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.213263.04
version-cpld: None
version-micorp: None
version-main: 3.63.709.04
version-misc: PVT SHIP S-On
serialno:HT3AJW906862
ProductL m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC_621
battery-status: low
battery-voltage: 3475mV
partition-layout: Generic
security: on
build-mode:SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-a448e85a
hboottpreupdate: 11
gencheckpt: 0
i tried to get my phone fixed but because its cross region nothing htc can do, and cost is as much as value of the phone. Will try all the tips here and repost. Thanks for everyone's help. Really appreciate it, this is a great forum
If anyone else has any other suggestions let me know.

nkk71 said:
That only works on hboot 1.44, "fastboot boot ...." was patched/broken after 1.44.
That's not needed on the M7, it'll get flashed automatically during the install even with S-On.
Click to expand...
Click to collapse
Yup the fastboot thingy doesnt work, anyother way i can use twrp if this is required. Unlocked my boot loader, are there any short cuts in this. Cant I just unlock, s-off and download any of the latest ruu files to bring my phone back to life ?

abreu6 said:
Yup the fastboot thingy doesnt work, anyother way i can use twrp if this is required. Unlocked my boot loader, are there any short cuts in this. Cant I just unlock, s-off and download any of the latest ruu files to bring my phone back to life ?
Click to expand...
Click to collapse
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!

nkk71 said:
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
Click to expand...
Click to collapse
will do, didnt realize i did that, thanks !

nkk71 said:
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
Click to expand...
Click to collapse
All removed, when i do the fastboot devices, the scrambled reply comes up which means im connected, but getvar all brings back nothing. I worried I may have done something wrong. Thanks

HTC one bricked
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA34MW909277
INFOimei: 354439059885634
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 3882mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
please help me out. I am using custom rom now .... no network .... no baseband. i am also confused that ruu is for me... i tried one but failed

[Q] I've fallen and I can't get up!

I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s

It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904

There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646

twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old

BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.

twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?

bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.

BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035

BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?

Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.

BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.

bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6

BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?

bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?

BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.

bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery

Unable to return my ONE to stock via RUU

Hey Guys,
I am pulling my hair out trying to return my HTC one M7 back to stock. Selling it to a friend that knows nothing about rooting and is not tech savy.
Anyways I cant seem to get the RUU to do. I have the correct file (I am with Rogers in Canada) that is the most up to date (see pictures).
I keep getting the Error 158 Image Error when I run the setup.
My phone is Locked as well which i know is the main cause for this error.
I am also running HD Revolution 84.0 at the moment.
I also set the CID to 11111111, hoping this might fix it but no luck
Any help is most appreciated.

FowlMouthedDuck said:
Hey Guys,
I am pulling my hair out trying to return my HTC one M7 back to stock. Selling it to a friend that knows nothing about rooting and is not tech savy.
Anyways I cant seem to get the RUU to do. I have the correct file (I am with Rogers in Canada) that is the most up to date (see pictures).
I keep getting the Error 158 Image Error when I run the setup.
My phone is Locked as well which i know is the main cause for this error.
I am also running HD Revolution 84.0 at the moment.
I also set the CID to 11111111, hoping this might fix it but no luck
Any help is most appreciated.
Click to expand...
Click to collapse
I should also note I am running TWRP v2.8.4.0

FowlMouthedDuck said:
I should also note I am running TWRP v2.8.4.0
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number please.

Seanie280672 said:
post your fastboot getvar all please without imei and serial number please.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4256mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT

FowlMouthedDuck said:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4256mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
Click to expand...
Click to collapse
Ok never mind, version main is missing, I suggest you find the firmware and flash that first then whilst still in the bootloader with fastboot USB on the screen, run the RUU

Seanie280672 said:
Ok never mind, version main is missing, I suggest you find the firmware and flash that first then whilst still in the bootloader with fastboot USB on the screen, run the RUU
Click to expand...
Click to collapse
Where is the best spot to download the firmware?

FowlMouthedDuck said:
Where is the best spot to download the firmware?
Click to expand...
Click to collapse
you should be able to pull it from the ruu, when you start the ruu and it extracts itself, make sure your computer is showing hidden files and folders then goto C:\users\(your user name)\app data\ local\(lots of strange characters and numbers folder) before closing the RUU and copy the firmware to a different location on your computer.
However, also as your s-off, you are aware you can flash any RUU like the 401 (WWE) or developer edition, its all stock.

Seanie280672 said:
you should be able to pull it from the ruu, when you start the ruu and it extracts itself, make sure your computer is showing hidden files and folders then goto C:\users\(your user name)\app data\ local\(lots of strange characters and numbers folder) before closing the RUU and copy the firmware to a different location on your computer.
However, also as your s-off, you are aware you can flash any RUU like the 401 (WWE) or developer edition, its all stock.
Click to expand...
Click to collapse
1. Is it in the Temp folder?
2. if It flash one of those RUU's, can I still update to Lollipop when it is available?

FowlMouthedDuck said:
Where is the best spot to download the firmware?
Click to expand...
Click to collapse
Your hboot 1.44 means the firmware has never been updated or did you put that their returning to stock ?
Maybe try an older RUU like >> http://forum.xda-developers.com/showthread.php?t=2529225

FowlMouthedDuck said:
1. Is it in the Temp folder?
2. if It flash one of those RUU's, can I still update to Lollipop when it is available?
Click to expand...
Click to collapse
Yup, dev edition will be the first to get it too.

Seanie280672 said:
Yup, dev edition will be the first to get it too.
Click to expand...
Click to collapse
Is it the Rom.zip file? When I tried to copy to the phone in windows 7 to the phone, it just gives me a "Cannot copy item" msg. The device has either stopped responding or has been disconnected.
I am thinking maybe the dev edition might be the best bet because my friend might be switching to another carrier instead of Rogers

FowlMouthedDuck said:
Is it the Rom.zip file? When I tried to copy to the phone in windows 7 to the phone, it just gives me a "Cannot copy item" msg. The device has either stopped responding or has been disconnected.
I am thinking maybe the dev edition might be the best bet because my friend might be switching to another carrier instead of Rogers
Click to expand...
Click to collapse
then try here >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
theirs also a RUU here 6.07.1540.2 >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Also their is no Firmware.zip in a RUU their found in OTA update packages

clsA said:
then try here >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
theirs also a RUU here 6.07.1540.2 >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Click to expand...
Click to collapse
Will this still allow the phone to be unlocked and switched to another carrier here in Canada? (ex. rogers to telus).

FowlMouthedDuck said:
Is it the Rom.zip file? When I tried to copy to the phone in windows 7 to the phone, it just gives me a "Cannot copy item" msg. The device has either stopped responding or has been disconnected.
I am thinking maybe the dev edition might be the best bet because my friend might be switching to another carrier instead of Rogers
Click to expand...
Click to collapse
well if you go to dev edition be sure to note clsA link incase of any problems and you have to return it to Rogers.
also need to know if you backflashed your HBOOT to 1.44 yourself ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:45 PM ----------
clsA said:
then try here >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
theirs also a RUU here 6.07.1540.2 >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Also their is no Firmware.zip in a RUU their found in OTA update packages
Click to expand...
Click to collapse
sorry missed this, thanks :good:

Seanie280672 said:
well if you go to dev edition be sure to note clsA link incase of any problems and you have to return it to Rogers.
also need to know if you backflashed your HBOOT to 1.44 yourself ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:45 PM ----------
sorry missed this, thanks :good:
Click to expand...
Click to collapse
Can to simply take the firmware from the OTA? If so, do I install the .zip like any ROM? Because I am trying to do that and as soon as I hit install in TWRP, it just reboots the recovery.
And yes I did backflash the HBOOT. I believe i had to do it when I had the lastest Viperone rom installed.

FowlMouthedDuck said:
Can to simply take the firmware from the OTA? If so, do I install the .zip like any ROM? Because I am trying to do that and as soon as I hit install in TWRP, it just reboots the recovery.
And yes I did backflash the HBOOT. I believe i had to do it when I had the lastest Viperone rom installed.
Click to expand...
Click to collapse
Disregard my last post. I forgot you had to use fastboot to update firmware. So I used the firmware.zip from the OTA. Now after rebooting, i get no display. I still have my usb plugged in and I can hear windows connecting and disconnecting but nothing is happening when I hold down power

FowlMouthedDuck said:
Disregard my last post. I forgot you had to use fastboot to update firmware. So I used the firmware.zip from the OTA. Now after rebooting, i get no display. I still have my usb plugged in and I can hear windows connecting and disconnecting but nothing is happening when I hold down power
Click to expand...
Click to collapse
Crap .. what firmware did you flash ?? and you never answered how did you get to hboot 1.44
you have to flash those OTA firmware.zip in order 3.x to 4.x to 5.x to 6.x ... you cant just jump to the newest firmware
when you plug in your phone check device manager for QHSUSB_DLOAD

Oops I forgot to finish my post. I did downflash the hboot when I downloaded the latest viperone rom (i think it asked me to if I remember correctly).
So device manager has QHUSB_DLOAD, what should i do with it?
Sorry for all the headaches. I am still a little new to the firmware stuff and going back to stock

FowlMouthedDuck said:
Oops I forgot to finish my post. I did downflash the hboot when I downloaded the latest viperone rom (i think it asked me to if I remember correctly).
So device manager has QHUSB_DLOAD, what should i do with it?
Sorry for all the headaches. I am still a little new to the firmware stuff and going back to stock
Click to expand...
Click to collapse
Yeah that sucks .. hope you can make this work
http://forum.xda-developers.com/showthread.php?t=2770684

FowlMouthedDuck said:
So I used the firmware.zip from the OTA.
Click to expand...
Click to collapse
you should be able to pull it from the ruu
Click to expand...
Click to collapse
he said, not from an ota. Ota fimware are only patches and must be flashed incrementally like clsA said.
So device manager has QHUSB_DLOAD, what should i do with it?
Click to expand...
Click to collapse
Looks like you make the situation worse. you could have avoided that by following what they said... :angel:
Now follow this guide: http://forum.xda-developers.com/showthread.php?t=2770684