Database Info

[Q] HTC Sensation XE - Bootloop, no recovery.. HELP:(

Hi im new to these forums
Anyway, on my HTC i am currently stuck on the bootloader screen. If I press recovery or anything it just shows the "HTC" logo screen and boots back to the bootloader. What do I do anyone? I think my ROM has been wiped

BilalH said:
Hi im new to these forums
Anyway, on my HTC i am currently stuck on the bootloader screen. If I press recovery or anything it just shows the "HTC" logo screen and boots back to the bootloader. What do I do anyone? I think my ROM has been wiped
Click to expand...
Click to collapse
Hi,
Are you s-off?
Did you wipe your old ROM?
What have you done?
What are you trying to do?
A little more information is quite useful to those who want to help...

malybru said:
Hi,
Are you s-off?
Did you wipe your old ROM?
What have you done?
What are you trying to do?
A little more information is quite useful to those who want to help...
Click to expand...
Click to collapse
Hi
I'm S-ON.
I think I accidently wiped my old rom
Im trying to get back to the stock ROM i Just want my phone working agian.

BilalH said:
Hi
I'm S-ON.
I think I accidently wiped my old rom
Im trying to get back to the stock ROM i Just want my phone working agian.
Click to expand...
Click to collapse
flash an RUU - go into hboot and find out what ROM version you were running before (by using fastboot getvar mainversion) then find an RUU with the same or higher version number and download then run it.

BilalH said:
Hi
I'm S-ON.
I think I accidently wiped my old rom
Im trying to get back to the stock ROM i Just want my phone working agian.
Click to expand...
Click to collapse
Jonny said:
flash an RUU - go into hboot and find out what ROM version you were running before (by using fastboot getvar mainversion) then find an RUU with the same or higher version number and download then run it.
Click to expand...
Click to collapse
Hi when I put in "fastboot getvar mainversion" in command prompt it says
C:\Users\amd>fastboot getvar mainversion
getvar:mainversion FAILED < remote: unknown command >
finished. total time: 0.008s
I was currently using official fw 4.0.3 with sense 3.6 before

BilalH said:
Hi when I put in "fastboot getvar mainversion" in command prompt it says
C:\Users\amd>fastboot getvar mainversion
getvar:mainversion FAILED < remote: unknown command >
finished. total time: 0.008s
I was currently using official fw 4.0.3 with sense 3.6 before
Click to expand...
Click to collapse
Then your safe just to download the 3.33.401.6 RUU and it should flash no problems

BilalH said:
Hi
I'm S-ON.
I think I accidently wiped my old rom
Im trying to get back to the stock ROM i Just want my phone working agian.
Click to expand...
Click to collapse
Hi,
As has been mentioned, flashing a RUU will get you back to a working phone.
Look HERE

Jonny said:
Then your safe just to download the 3.33.401.6 RUU and it should flash no problems
Click to expand...
Click to collapse
Ah thanks Il give this a try, previously Ive tried download 3.32 RUU's and theyve all said its the wrong version. Downloading from filefactory right now, taking a long time unfortuantly, 2 hours Thanks
Just downloading this RUU
RUU​_PYRAMID​_ICS​_HTC​_Europe​_3.33​.401​.6_Radio​_11.76A​.3504.00U_11.24A.3504.31_M_release_266171_signed.exe

Hi
I tried the RUU and get the following error
ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utitlity and try again.
My current RUU says im on 3.32.206.112 and I pressed update, the update went on for a while and this error popped up.

BilalH said:
Hi
I tried the RUU and get the following error
ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utitlity and try again.
My current RUU says im on 3.32.206.112 and I pressed update, the update went on for a while and this error popped up.
Click to expand...
Click to collapse
Hi,
You are using the wrong RUU.
Check the link I gave you earlier to find your CID,and the correct RUU,and how to install it.

malybru said:
Hi,
You are using the wrong RUU.
Check the link I gave you earlier to find your CID,and the correct RUU,and how to install it.
Click to expand...
Click to collapse
Hi thhere been searching trying to find my RUU but I cant seem to find it
My CID is 02_001, therefore o2
CAn you link me to the RUU I need? Thanks

BilalH said:
Hi thhere been searching trying to find my RUU but I cant seem to find it
My CID is 02_001, therefore o2
CAn you link me to the RUU I need? Thanks
Click to expand...
Click to collapse
Hi,
Have you tried taking a general European RUU and Adding your CID to the PGIMG.zip
It is 4.2 in the guide.

malybru said:
Hi,
Have you tried taking a general European RUU and Adding your CID to the PGIMG.zip
It is 4.2 in the guide.
Click to expand...
Click to collapse
Hi Ive tried following the method.
when I get up to the part where you have to type 'fastboot flash zip PG58IMG.zip it says this:
C:\android-sdk-windows\tools>fastboot flash zip PG58IMG.zip
sending 'zip' <432384 KB>...
OKAY [56.745s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature fail)
finished. total time: 130.818s

BilalH said:
Hi Ive tried following the method.
when I get up to the part where you have to type 'fastboot flash zip PG58IMG.zip it says this:
C:\android-sdk-windows\tools>fastboot flash zip PG58IMG.zip
sending 'zip' <432384 KB>...
OKAY [56.745s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature fail)
finished. total time: 130.818s
Click to expand...
Click to collapse
Hi,
I am not sure why you are trying to flash the PG58IMG
Can you not change the text file in the PG58IMG and then run the RUU from your PC.
Make sure your phone is in fastboot,then connect your USB cable,(it should say "fastboot USB" ) then,run the RUU.

malybru said:
Hi,
I am not sure why you are trying to flash the PG58IMG
Can you not change the text file in the PG58IMG and then run the RUU from your PC.
Make sure your phone is in fastboot,then connect your USB cable,(it should say "fastboot USB" ) then,run the RUU.
Click to expand...
Click to collapse
Hi yes I have changed the 'android-info.txt' file in PG58IMG but now what do I do? The PG58IMG.zip is in my android-sdk/tools folder.

BilalH said:
Hi yes I have changed the 'android-info.txt' file in PG58IMG but now what do I do? The PG58IMG.zip is in my android-sdk/tools folder.
Click to expand...
Click to collapse
Hi,
You do not need to extract the PG58IMG
Just open it,change it,and close it.
It remains zipped,and you can run the RUU.

malybru said:
Hi,
You do not need to extract the PG58IMG
Just open it,change it,and close it.
It remains zipped,and you can run the RUU.
Click to expand...
Click to collapse
Okay let me start from the top, where exactly do I find this PG58IMG.zip? Thanks.
Btw another question, is there a way for me to charge my phone because my battery says its below 30% if I try to install an RUU

Paste the output for
Code:
fastboot getvar all
Remove the IMEI number & serial number from the output.
I'll link you to the right RUU or tell you what else you can try.
For now, don't do anything else.
You cannot flash a modified RUU because you are S-ON; so changing the android-info file will not help.

kgs1992 said:
Paste the output for
Code:
fastboot getvar all
Remove the IMEI number & serial number from the output.
I'll link you to the right RUU or tell you what else you can try.
For now, don't do anything else.
You cannot flash a modified RUU because you are S-ON; so changing the android-info file will not help.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.206.112
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.505s
Yeah so which RUU do I need or what do I need to do?

BilalH said:
(bootloader) version-main: 3.32.206.112
(bootloader) product: pyramid
(bootloader) modelid: PG5813001
(bootloader) cidnum: O2___001
(bootloader) security: on
Yeah so which RUU do I need or what do I need to do?
Click to expand...
Click to collapse
I don't think there is any O2 ICS RUU let alone 3.32 & you're S-ON, so can't flash a lower RUU.
But fortunately, all is not lost. Let's try this.
Please type these commands one after the other & paste the whole output for everything:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
fastboot getvar cid
It's okay if any of them fail, you must execute all three commands one after the other & paste the output.

[Q] [Help] [Solved] One X Stuck at Fastboot, Out of Ideas, Failed RUU

Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.

I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.

Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita

whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.

brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.

I honestly don't think that's going to help you anyway.
Sent from my Evita

timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)

Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).

redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?

It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita

timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.

MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.

MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita

Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.

redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?

<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.

You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita

timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.

It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita

timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.

HTC One M8 Error while flashing RUU

Hello. I am not sure if I am the only one with this issue but here it is.
I have a Verizon HTC One M8. Here is the condition:
NOT rooted
NO OS installed
Stock recovery installed (Can't flash a custom recovery)
S-ON
LOCKED bootloader
Here is some other useful information:
HBoot-3.19.0.0000
Radio-1.14.20.0930
OS-6.21.605.3
Okay, so it is very possible that there is no hope for this phone, but I still feel like there could be. In the state that it is in, I have assumed that I could just flash an RUU so that I would return to stock. This wouldn't work. Every time I would try to flash it through fastboot on the device, I would get part of the way through flashing and then it would say:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I have been told that this could mean that the that I have downloaded is possibly corrupt. This seems to not be the case as I have tried downloading it 3 different times. I have also checked the MD5 and they match. I have also tried flashing the RUU by using the executable version. This as well doesn't work. When I try to flash, It gets near to the end of the process and then fails with the error [132] stating that I need to find a RUU that matches my firmware (You can see this in the video linked below). The problem with this is that the RUU that I am using seems to match my firmware. Here is a copy of the txt document that is located within the rom for the RUU.
DelUserData:0
modelid: 0P6B20000
cidnum: VZW__001
mainver: 6.21.605.3
btype:1
aareport:1
hbootpreupdate:12
DelCache:1
DelFrp:1
Seeing the mainver number leads me to believe that this will work on my device. Feel free to link me to the proper RUU if this is wrong.
One other problem is that in order to install a recovery, I need access to adb. I don't have access to adb as I can't turn on USB Debugging because my device doesn't have a OS installed on it. If you have any suggestions or solutions to my problem, please let me know! Thanks!
Here is the link to the video of the RUU error: https://www.youtube.com/watch?v=9aKecZuhWl0&authuser=0
This error happens when attempting to flash RUU through executable file.

Cozmikk said:
Hello. I am not sure if I am the only one with this issue but here it is.
I have a Verizon HTC One M8. Here is the condition:
NOT rooted
NO OS installed
Stock recovery installed (Can't flash a custom recovery)
S-ON
LOCKED bootloader
Here is some other useful information:
HBoot-3.19.0.0000
Radio-1.14.20.0930
OS-6.21.605.3
Okay, so it is very possible that there is no hope for this phone, but I still feel like there could be. In the state that it is in, I have assumed that I could just flash an RUU so that I would return to stock. This wouldn't work. Every time I would try to flash it through fastboot on the device, I would get part of the way through flashing and then it would say:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I have been told that this could mean that the that I have downloaded is possibly corrupt. This seems to not be the case as I have tried downloading it 3 different times. I have also checked the MD5 and they match. I have also tried flashing the RUU by using the executable version. This as well doesn't work. When I try to flash, It gets near to the end of the process and then fails with the error [132] stating that I need to find a RUU that matches my firmware (You can see this in the video linked below). The problem with this is that the RUU that I am using seems to match my firmware. Here is a copy of the txt document that is located within the rom for the RUU.
DelUserData:0
modelid: 0P6B20000
cidnum: VZW__001
mainver: 6.21.605.3
btype:1
aareport:1
hbootpreupdate:12
DelCache:1
DelFrp:1
Seeing the mainver number leads me to believe that this will work on my device. Feel free to link me to the proper RUU if this is wrong.
One other problem is that in order to install a recovery, I need access to adb. I don't have access to adb as I can't turn on USB Debugging because my device doesn't have a OS installed on it. If you have any suggestions or solutions to my problem, please let me know! Thanks!
Here is the link to the video of the RUU error: https://www.youtube.com/watch?v=9aKecZuhWl0&authuser=0
This error happens when attempting to flash RUU through executable file.
Click to expand...
Click to collapse
Do you have an SD-Card?
I find the best way to do an RUU is using the SD-Card. Very safe, as power could turn off or something.
EDIT: I see in the video you tried that.
Sorry. :-/
more RUU's to try?
https://www.androidfilehost.com/?fid=24438995911975667
https://www.androidfilehost.com/?fid=24052804347813946

andybones said:
Do you have an SD-Card?
I find the best way to do an RUU is using the SD-Card. Very safe, as power could turn off or something.
EDIT: I see in the video you tried that.
Sorry. :-/
more RUU's to try?
https://www.androidfilehost.com/?fid=24438995911975667
https://www.androidfilehost.com/?fid=24052804347813946
Click to expand...
Click to collapse
I have already tried the android 6.0 RUU. I can't try the 5.0.1 RUU because I don't have S-Off and I am already on the 6.0 firmware and can't downgrade.

Cozmikk said:
I have already tried the android 6.0 RUU. I can't try the 5.0.1 RUU because I don't have S-Off and I am already on the 6.0 firmware and can't downgrade.
Click to expand...
Click to collapse
Wish I could be of help.

andybones said:
Wish I could be of help.
Click to expand...
Click to collapse
Its okay. I am talking to someone right now who should be able to help me with javacard or something near to it so I can at least get s-off.

Cozmikk said:
Its okay. I am talking to someone right now who should be able to help me with javacard or something near to it so I can at least get s-off.
Click to expand...
Click to collapse
Glad to hear. :good:

Hey did you find a solution? I have pretty much the same problem (Except, I do have S-OFF, but I relocked my bootloader so I still can't flash a custom recovery...)

MSFTGhoul said:
Hey did you find a solution? I have pretty much the same problem (Except, I do have S-OFF, but I relocked my bootloader so I still can't flash a custom recovery...)
Click to expand...
Click to collapse
You can. I have posted ruu mode custom firmware zips that have twrp included just for this scenario. Then you can unlock the bootloader. Your scenario is not at all the same as the above.
Sent from my HTC6545LVW using Tapatalk

RUU collection for HTC U Ultra (Only Nougat for now)

Check CID of your phone and find RUU for your Ultra in here: Androidfilehost
Source: http://forum.gsmdevelopers.com
Thanks @zohrann for sharing.

Fixed link

HTC U Ultra Dual Sim
My HTC is bricked and I can not access RUUmode, it is S-on and locked. There is no way to recover by fastboot? I tried but it leaves the message that is not possible in S-on. Thanks everyone for tries help me.

marcosviniciusf17 said:
My HTC is bricked and I can not access RUUmode, it is S-on and locked. There is no way to recover by fastboot? I tried but it leaves the message that is not possible in S-on. Thanks everyone for tries help me.
Click to expand...
Click to collapse
You need unlock your bootloader and use HTC Version Tool to downgrade to Nougat

Thanks @minhnewpro
At last we have now one place for the RUU.
I did notice a new Oreo RUU in Chinese forums but I think it's for a single SIM

ForceField said:
Thanks @minhnewpro
At last we have now one place for the RUU.
I did notice a new Oreo RUU in Chinese forums but I think it's for a single SIM
Click to expand...
Click to collapse
I saw it, i will wait for more Oreo RUU from other region.

HTC U Ultra Dual Sim
minhnewpro said:
You need unlock your bootloader and use HTC Version Tool to downgrade to Nougat
Click to expand...
Click to collapse
Thanks for answering! Yes, I tried this, however I can't get the code to paste into the htcdev site. Error message, incorrect command or unknown command appears. I have already researched several tutorials to confirm the command and I can't. Any tipos?

marcosviniciusf17 said:
Thanks for answering! Yes, I tried this, however I can't get the code to paste into the htcdev site. Error message, incorrect command or unknown command appears. I have already researched several tutorials to confirm the command and I can't. Any tipos?
Click to expand...
Click to collapse
Check your HTC driver, my driver version is HTC-Mobile-Driver-v4.17.0.001. Make sure PC reconized your phone and you have folder contain adb stuff.

Hey thanx for the collection, wanted to use it, but how do I fix the error "RU_MAIN_VER_FAIL os-version in android-info missing or i"? I have CID 034 so I used the CID_001_034 RUU.

TheGreatB said:
Hey thanx for the collection, wanted to use it, but how do I fix the error "RU_MAIN_VER_FAIL os-version in android-info missing or i"? I have CID 034 so I used the CID_001_034 RUU.
Click to expand...
Click to collapse
Make sure you download RUU for right version. Enter right version RUU Nougat on HTC Version Tool
etc: Dual Sim (DUGL) or Single Sim (UHL)

How to unlock bootloader if S ON, and can not access your phone (phone brick)?

banlc said:
How to unlock bootloader if S ON, and can not access your phone (phone brick)?
Click to expand...
Click to collapse
Anyone help me, please!, @minhnewpro giúp mình với.

@minhnewpro I tried, unlock the bootloader but it does not give results. I already checked the adb / fastboot package, drivers, but nothing solves it.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
banlc said:
How to unlock bootloader if S ON, and can not access your phone (phone brick)?
Click to expand...
Click to collapse
I have the same problem

marcosviniciusf17 said:
@minhnewpro I tried, unlock the bootloader but it does not give results. I already checked the adb / fastboot package, drivers, but nothing solves it.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
I have the same problem
Click to expand...
Click to collapse
Try reflash RUU if you are using android 7. Or reflash OTA file if you are using android 8.

Big Question
I install an RUU Rom but inow i have no IMEI and No Baseband Radio. how can i solve this?. Please.

adfy said:
I install an RUU Rom but inow i have no IMEI and No Baseband Radio. how can i solve this?. Please.
Click to expand...
Click to collapse
I'm running into this same issue. I can't boot into my phone. Phone keeps rebooting on my splash screen. I can go into only fastboot screen. When I try and select either Boot to Download or Boot to Recovery mode it gots to the htc screen and then reboots and goes to the splash screen thus continuously rebooting. I have an unlocked AT&T US HTC U Ultra. When i run the below getvar I don't get any sim data.
Code:
fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdbf000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xdc000000
(bootloader) serialno:FA72R1703082
all:
Finished. Total time: 0.390s
I tried flashing with 2PZFIMG_OCEAN_NOTE_UHL_N70_SENSE80GP_NA_Gen_Unlock_1.64.617.3_Radio_1.0.U010051c\@70809_58.34_release_509387_signed_.......AJA.zip from gsmdevelopers, but I was unsucessfull. What I did for this was to run the following
Code:
fastboot reboot recovery
fastboot flash recovery 2PZFIMG_OCEAN_NOTE_UHL_N70_SENSE80GP_NA_Gen_Unlock_1.64.617.3_Radio_1.0.U010051c\@70809_58.34_release_509387_signed_.......AJA.zip
fastboot flash recovery 2PZFIMG_OCEAN_NOTE_UHL_N70_SENSE80GP_NA_Gen_Unlock_1.64.617.3_Radio_1.0.U010051c\@70809_58.34_release_509387_signed_.......AJA.zip
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 1297259318 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 760392502 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 223525686 is not a multiple of the block size 4096
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
Aborted (core dumped)
Unsuccessful. Not sure what else to do.

Problem need help

My htc u11 is just relock, then when it back factory reset ask me for password, but they touchpal force close
I can't enter password
I can't enter twrp because relock
I was trying to flash ruu over download mode but always said FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
My HTC U11 is 2PZC10
CID is HTC__39

zeropop2018 said:
My htc u11 is just relock, then when it back factory reset ask me for password, but they touchpal force close
I can't enter password
I can't enter twrp because relock
I was trying to flash ruu over download mode but always said FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
My HTC U11 is 2PZC10
CID is HTC__39
Click to expand...
Click to collapse
I also S-ON
I try flash ruu all version i can, but return error:
19_RU_MAIN_VER_FAIL
Please help

are you try with fastboot commands using windows prompt?
all ruu for htc u11 ------>https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0

Yes, i try
fastboot rebootRUU
then
htc_fastboot flash zip "firmware_xxx.zip"
it always give me error:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.47.1405.2
found large-zip header, file count: 23
processing file 1/23...
sending 'zip' (391927 KB)...
OKAY [ 15.204s]
writing 'zip'...
(bootloader) HOSD CL#1002308
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
finished. total time: 23.238s
htc_fastboot finished. total time: 28.075s
I don't know what to do know, anyway my firmware version is: 2.33.710.9

fabrizio b92 said:
are you try with fastboot commands using windows prompt?
all ruu for htc u11 ------>https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Which version is right ?

zeropop2018 said:
Which version is right ?
Click to expand...
Click to collapse
where do you live? single or dual sim? is it brand or is it free sim?
can you reboot in fastboot mode? here you can find all information
for example my phone codename is ocndugl = DUGL DUAL SIM EMEA
this is my htc u11 fastboot----- >https://drive.google.com/file/d/19g5JiOs72VV_GKjh9f7b51B6cUN0TtKW/view?usp=sharing
Or if you can reinstall twrp recovery, you can bypass pin screen
Follow this instruction ------> https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/

fabrizio b92 said:
where do you live? single or dual sim? is it brand or is it free sim?
can you reboot in fastboot mode? here you can find all information
for example my phone codename is ocndugl = DUGL DUAL SIM EMEA
this is my htc u11 fastboot----- >https://drive.google.com/file/d/19g5JiOs72VV_GKjh9f7b51B6cUN0TtKW/view?usp=sharing
Or if you can reinstall twrp recovery, you can bypass pin screen
Follow this instruction ------> https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
Click to expand...
Click to collapse
I live in Viet Nam. Single. Freesim i think so.
I can reboot in fastboot mode, but i cannot flash RUU, because all error.
My fastboot mode the same as you without RELOCKED, because i relocked it.
That's why i can't find way to reinstall twrp recovery.

Can somebody help ?
Is it brick and never go back ?

zeropop2018 said:
Can somebody help ?
Is it brick and never go back ?
Click to expand...
Click to collapse
Try to unlock bootloader and install twrp recovery to unbrick your phone for now

fabrizio b92 said:
Try to unlock bootloader and install twrp recovery to unbrick your phone for now
Click to expand...
Click to collapse
How to unlock if i can't go to usb debug ?

To sum it up, he
1. somehow tinkered with his phone when unlocked
2. relocked bootloader before restoring a stock pristine system
3. is now soft bricked cause he needs to RUU which isn't available as of yet, and we don't know if it'll get leaked
4. he can't boot to OS to re-unlock, S-OFF to downgrade, due to the above mentioned problems.
We're out of options here for the time being. Only one who might currently be able to restore the device might be HTC Support. But that may cost him, as they'll see that the device has been tinkered with.
Sent from my HTC U12+ using XDA Labs

zeropop2018 said:
How to unlock if i can't go to usb debug ?
Click to expand...
Click to collapse
If you have saved the unlock token from the first time you unlocked the phone, you can use this token again!
Simply flash unlock_code.bin with the command:
fastboot flash unlocktoken Unlock_code.bin

scotty2000 said:
If you have saved the unlock token from the first time you unlocked the phone, you can use this token again!
Simply flash unlock_code.bin with the command:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I'm not the one who unlock it so i can't find it ....
Why it so hard

like a genius got too far into the tinkering and have done same. S-On so cannot change CID and re-locked so wont let me get into TWRP. Still have unlock bin but no joy as when I flashed custom it would have reset oem unlock to off so i get following:
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Obviously can't get back into Android to enable said unlock so seemingly out of options unless there is a way to flip that byte.
---------- Post added at 03:26 PM ---------- Previous post was at 03:23 PM ----------
ngodber said:
like a genius got too far into the tinkering and have done same. S-On so cannot change CID and re-locked so wont let me get into TWRP. Still have unlock bin but no joy as when I flashed custom it would have reset oem unlock to off so i get following:
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Obviously can't get back into Android to enable said unlock so seemingly out of options unless there is a way to flip that byte.
Click to expand...
Click to collapse
Also device is Telstra and there is apparently not a single Telstra (Australia) RUU for U11 on face of earth.
---------- Post added at 03:54 PM ---------- Previous post was at 03:26 PM ----------
I do have a second Telstra U11 device around the house. Is there a way to image from that device to this one?

The problem is obvious. It's a Chinese phone. The firmware currently loaded is Chinese and you're trying to flash a Taiwanese firmware on a multi region cid.
My guess is that the phone has been messed with.
If flashing the same version firmware as what is on it now (2.47.1405.2) fails you will need to get the mid to check it matches the cid for region. If not you have problems ahead.

shivadow said:
The problem is obvious. It's a Chinese phone. The firmware currently loaded is Chinese and you're trying to flash a Taiwanese firmware on a multi region cid.
My guess is that the phone has been messed with.
If flashing the same version firmware as what is on it now (2.47.1405.2) fails you will need to get the mid to check it matches the cid for region. If not you have problems ahead.
Click to expand...
Click to collapse
Thank God i fixed my phone, i gave it to a friend and he had tool to s-off ...
Thank God

zeropop2018 said:
Thank God i fixed my phone, i gave it to a friend and he had tool to s-off ...
Thank God
Click to expand...
Click to collapse
So do you know what "tool" he had that fixed your phone?
Sent from my coconut frond hut using Tapatalk

mauiblue said:
So do you know what "tool" he had that fixed your phone?
Sent from my coconut frond hut using Tapatalk
Click to expand...
Click to collapse
He said that tool use to connect to china server

zeropop2018 said:
Thank God i fixed my phone, i gave it to a friend and he had tool to s-off ...
Thank God
Click to expand...
Click to collapse
Can I ask what that tool was? And where did he get it? . Also when he went s- off what did he do to fix it? Just curious as I have been following this thread . Thanks

Cool. Maybe I could could have connected to this "tool" and fixed my U11 [emoji20][emoji22]. I also "relocked" my phone and couldn't find figure out how to fix it. I had to send my phone to the HTC repair shop a couple weeks ago. Still waiting for a positive response from them.
Sent from my coconut frond hut using Tapatalk