Motorola xt1250 bricked - Moto Maxx Q&A, Help & Troubleshooting

Hi, I need some help to unbrick this phone ... i have read all post, download a lot of stock firmwares, and have a same result allways, phone cant boot normally, only boot to bootloader screen. One friend give me this phone dead, the phone before was in 4.4.4 stck firmware and was locked bootloader, my friend update to 5.1, but use xt1254 stock firmware (he tell me that ...), have an error, and phone was dead, actualy I intented flash a stock firmware for xt1250 variant but no have succses (RSD or mfastboot), allways have error like prevalidation filed, etc.
In bootloader screen show : BL : moto-apq8084-70.86 (sha-88bfdfd, 2015-04-06 16:09:43)
Baseband:
Product/variant : quark xt1250 32gb PP4A
Serial number : xxxxxxxxxx
CPU: apq8084 ES1.1
eMMC : 32GB Sandisk RV=07 PV=01 TY=57
DRAM: 3072 MB Samsung s8 sdram die=6gb
Console[NULL]: null
Battery OK
Device is LOCKED. Status code: 0
Software Status: Official
I cant see wich firmware select to back to life the phone, i read many post, but finally totally confused, the phone came from USA, I search a lots of stock roms, but allwas get error If somebody can helpme to know process or how select correct firmware for them, i will totally apreciate. Sorry the english.

You can boot into fastboot which is a good sign, are you able to use fastboot and unlock the bootloader?
There is a thread with official firmwares in this forum, I believe stock xt1250 firmware with flashing instructions should be present

Nitefire77 said:
You can boot into fastboot which is a good sign, are you able to use fastboot and unlock the bootloader?
There is a thread with official firmwares in this forum, I believe stock xt1250 firmware with flashing instructions should be present
Click to expand...
Click to collapse
Thanks for reply, im not problem with try unlock bootloader, I just Think in this state i cant unlock bootloader, and try restore them with a stock firmware. I test 2 firmwares in oficial firmware section (only see 2 there for xt 1250) and get same error when try to write. If yo can helpme with links of roms or any other proces i will try, thanks a lot for your help ¡¡¡ If you need other data, just tell me.

Somebody can help me to try back to life this phone ?? Is dead yet, and i try a lot of solutions, but no results

soft360 said:
Thanks for reply, im not problem with try unlock bootloader, I just Think in this state i cant unlock bootloader, and try restore them with a stock firmware. I test 2 firmwares in oficial firmware section (only see 2 there for xt 1250) and get same error when try to write. If yo can helpme with links of roms or any other proces i will try, thanks a lot for your help ¡¡¡ If you need other data, just tell me.
Click to expand...
Click to collapse
if you try to flash XT1250 firmware do not flash the bootloader part. It had 4.4.4 and your friend -- WITH A LOCKED BOOTLOADER WHICH IS STUPID -- tried to flash XT1254 over the phone. Now it probably has a Lollipop locked bootloader. You will not succeed in flashing the entire XT1250 firmware package back to 4.4.4. You can only downgrade back to 4.4.4 by leaving the bootloader portion out.
If you try to flash 5.0.2 XT1250 firmware (if you can find it), still do NOT flash the bootloader portion.
First thing I do when I get a phone is unlock the bootloader and root. And never re-lock the bootloader. Just asking for trouble.

ChazzMatt said:
if you try to flash XT1250 firmware do not flash the bootloader part. It had 4.4.4 and your friend -- WITH A LOCKED BOOTLOADER WHICH IS STUPID -- tried to flash XT1254 over the phone. Now it probably has a Lollipop locked bootloader. You will not succeed in flashing the entire XT1250 firmware package back to 4.4.4. You can only downgrade back to 4.4.4 by leaving the bootloader portion out.
If you try to flash 5.0.2 XT1250 firmware (if you can find it), still do NOT flash the bootloader portion.
First thing I do when I get a phone is unlock the bootloader and root. And never re-lock the bootloader. Just asking for trouble.
Click to expand...
Click to collapse
Ok, i will try to flash 5.0.2 w/o boot loader section, and post result, i think is a good phone to leave dead, otherwise I wait for marshmallow update

soft360 said:
Ok, i will try to flash 5.0.2 w/o boot loader section, and post result, i think is a good phone to leave dead, otherwise I wait for marshmallow update
Click to expand...
Click to collapse
You find any solution? I'm in the same situation, already tried everything. Please, help!

Ferreira_F10 said:
You find any solution? I'm in the same situation, already tried everything. Please, help!
Click to expand...
Click to collapse
You have an XT1250 U.S. Moto Maxx with a locked bootloader? You tried to flash XT1254 firmware over it without first unlocking the bootloader and you've now bricked it? You never flash firmware for another phone with a locked bootloader, even if it can be compatible. It it messes up you are in trouble.
Unlocking the XT1250 and XT1225 bootloader is FREE. FREE with request code from Motorola. I don't understand why people don't unlock their bootloader before doing stuff like this. It's only the XT1254 bootloader that is not free, that you need Sunshine to unlock because of stupid Verizon.
You need to re-flash XT1250 5.0.2 firmware -- but if you do that, you need to omit gpt.bin in the flash commands. I'm not sure it's going to work.

ChazzMatt said:
You have an XT1250 U.S. Moto Maxx with a locked bootloader? You tried to flash XT1254 firmware over it without first unlocking the bootloader and you've now bricked it? You never flash firmware for another phone with a locked bootloader, even if it can be compatible. It it messes up you are in trouble.
Unlocking the XT1250 and XT1225 bootloader is FREE. FREE with request code from Motorola. I don't understand why people don't unlock their bootloader before doing stuff like this. It's only the XT1254 bootloader that is not free, that you need Sunshine to unlock because of stupid Verizon.
You need to re-flash XT1250 5.0.2 firmware -- but if you do that, you need to omit gpt.bin in the flash commands. I'm not sure it's going to work.
Click to expand...
Click to collapse
No, I have a XT1225 locked bootloader. It only turns on in fastboot mode, without the green android robot. I already tried flashing everything, but everything returns me the same error.
C:\Users\Felipe\Desktop\XDA\XT1225\Firmwares>fastboot devices
9911e06b fastboot
C:\Users\Felipe\Desktop\XDA\XT1225\Firmwares>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
Click to expand...
Click to collapse
EVERYTHING gives me that error.
Information with getvar commmand:
C:\Users\Felipe\Desktop\XDA\XT1225\Firmwares>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-70.86(*)
(bootloader) product: quark
(bootloader) board: quark
(bootloader) secure: yes
(bootloader) hwrev: 0x84A0
(bootloader) radio: 0x5
(bootloader) emmc: 64GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Hynix S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 9911e06b
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 8F644E0111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V70.86-0-g88bfdfd
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.147s
Click to expand...
Click to collapse
Already tried all options in the thread https://forum.xda-developers.com/moto-maxx/general/tuto-unbrick-xt1225-100-t3483623 and I don't know what to do. If the bootloader is locked, it should flash only the firmware compatible with my bootloader, right? But I can't do anything. I can't unlock bootloader with the command "oem get_unlock_data".
C:\Users\Felipe\Desktop\XDA\XT1225\Firmwares>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.007s
Click to expand...
Click to collapse
My fastboot screen: http://imgur.com/a/Zoh5k

Ferreira_F10 said:
No, I have a XT1225 locked bootloader. It only turns on in fastboot mode, without the green android robot. I already tried flashing everything, but everything returns me the same error.
EVERYTHING gives me that error.
Information with getvar commmand:
Already tried all options in the thread https://forum.xda-developers.com/moto-maxx/general/tuto-unbrick-xt1225-100-t3483623 and I don't know what to do. If the bootloader is locked, it should flash only the firmware compatible with my bootloader, right? But I can't do anything. I can't unlock bootloader with the command "oem get_unlock_data".
Click to expand...
Click to collapse
No, you cannot unlock the bootloader with just the adb command you describe. See my GUIDE.. You need the unlock code from Motorola to use in ADB.
Please unlock your bootloader first chance you get. If you have access to ADB it's possible you can still do it now. If not now, then immediately after you recover your phone.
___________
What version was the phone on and what are you trying to flash? With locked bootloader, you can flash same bootloader firmware or higher, just not lower. (With an unlocked bootloader you can flash lower version, but you just have to omit the gpt.bin command when flashing.)
Are you using the most recent firmware? A few months ago an update to Marshmallow was released which added an "S" to the firmware name. Easy to overlook.. MPGS. Here's all the Quark firmware ever released.
https://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
Either one of these found on that site would work for your XT1225, the BR one is Brazil, the LA one I believe is Mexico, but either should work.
XT1225_QUARK_RETBR_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
XT1225_QUARK_RETLA_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
it's a very slow download site, but it does have all the comprehensive software for our Quarks.
Wait, here's faster from @bhb27:
XT1225_QUARK_RETBR_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
https://www.androidfilehost.com/?fid=385035244224403573
___________
also read this Guide:
https://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724
You may know it all, but there's something in there that may help you. Just be sure to flash ALL the sparse chunks, not just the number given in the example.

ChazzMatt said:
No, you cannot unlock the bootloader with just the adb command you describe. See my GUIDE.. You need the unlock code from Motorola to use in ADB.
Please unlock your bootloader first chance you get. If you have access to ADB it's possible you can still do it now. If not now, then immediately after you recover your phone.
___________
What version was the phone on and what are you trying to flash? With locked bootloader, you can flash same bootloader firmware or higher, just not lower. (With an unlocked bootloader you can flash lower version, but you just have to omit the gpt.bin command when flashing.)
Are you using the most recent firmware? A few months ago an update to Marshmallow was released which added an "S" to the firmware name. Easy to overlook.. MPGS. Here's all the Quark firmware ever released.
https://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
Either one of these found on that site would work for your XT1225, the BR one is Brazil, the LA one I believe is Mexico, but either should work.
XT1225_QUARK_RETBR_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
XT1225_QUARK_RETLA_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
it's a very slow download site, but it does have all the comprehensive software for our Quarks.
Wait, here's faster from @bhb27:
XT1225_QUARK_RETBR_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
https://www.androidfilehost.com/?fid=385035244224403573
___________
also read this Guide:
https://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724
You may know it all, but there's something in there that may help you. Just be sure to flash ALL the sparse chunks, not just the number given in the example.
Click to expand...
Click to collapse
I know, but I can't get the unlock data from my phone to get the unlock data from Motorola. As I wrote above, it returns me the error:
"(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)"
So I can't unlock my bootloader.
--------------------------
I don't know what version it was. I picked the phone with a guy that I know, he doesn't know how to fix this, and I thought it was very simple to fix.
I tried flashing all retbr variants, from 4.4 to 6.0.1, and everything gaves me that error. I can't flash gpt.bin, motoboot.img, radio, bootloader, sparsechunk, nothing. Already tried with RSD Lite too.
Yes, I think that I already tried that MPGS firmware.
At the moment, I'm downloading ALL XT1225, XT1250 and XT1254 stock builds ever released from Firmware Center, so in a few hours (when I download everything), I will try flashing EVERY firmware. Maybe RETLA works, I didn't tried it.
----------------------
Thanks for the help, I will try all this. I'll post my problem in the Q&A section.

Ferreira_F10 said:
I know, but I can't get the unlock data from my phone to get the unlock data from Motorola. As I wrote above, it returns me the error:
"(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)"
So I can't unlock my bootloader.
--------------------------
I don't know what version it was. I picked the phone with a guy that I know, he doesn't know how to fix this, and I thought it was very simple to fix.
I tried flashing all retbr variants, from 4.4 to 6.0.1, and everything gaves me that error. I can't flash gpt.bin, motoboot.img, radio, bootloader, sparsechunk, nothing. Already tried with RSD Lite too.
Yes, I think that I already tried that MPGS firmware.
At the moment, I'm downloading ALL XT1225, XT1250 and XT1254 stock builds ever released from Firmware Center, so in a few hours (when I download everything), I will try flashing EVERY firmware. Maybe RETLA works, I didn't tried it.
----------------------
Thanks for the help, I will try all this. I'll post my problem in the Q&A section.
Click to expand...
Click to collapse
Don't try flashing XT1254/XT1250 firmware on the XT1225. They have different FCC ID.
(@iiwoodstock did make a ROM that's basically XT1225 stock Brazilian 6.0.1 firmware that WILL work on all Quarks, but it uses an older specific @bhb27 custom kernel, and you need TWRP and unlocked bootloader. He also added CDMA references to build prop. That is the only instance of cross flashing over different FCC ID, and even then it's only because it's technically been converted into a custom ROM.)
My theory was maybe your XT1225 tried to take the MPGS OTA update, it got messed up and now you can't flash the older MPG firmware because the bootloader is now on MPGS. That would explain your GPT.bin error.
At this point in time I wouldn't flash anything lower than MPGS.

ChazzMatt said:
Don't try flashing XT1254/XT1250 firmware on the XT1225. They have different FCC ID.
(@iiwoodstock did make a ROM that's basically XT1225 stock Brazilian 6.0.1 firmware that WILL work on all Quarks, but it uses an older specific @bhb27 custom kernel, and you need TWRP and unlocked bootloader. He also added CDMA references to build prop. That is the only instance of cross flashing over different FCC ID, and even then it's only because it's technically been converted into a custom ROM.)
My theory was maybe your XT1225 tried to take the MPGS OTA update, it got messed up and now you can't flash the older MPG firmware because the bootloader is now on MPGS. That would explain your GPT.bin error.
At this point in time I wouldn't flash anything lower than MPGS.
Click to expand...
Click to collapse
I'll try flashing every MPGS firmware.
In the "bootloader logs" section of my bootloader, it always have the information:
Fastboot Reason: Failed to initialize partition table
Click to expand...
Click to collapse
Every time I try flashing a gpt.bin file (including RETBR 6.0.1 MPGS), in the bootloader logs on my phone, returns me (last line in pink):
USB connected
cmd: getvar:max-sparse-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Click to expand...
Click to collapse
And in cmd, the error "preflash validation failed FAILED (remote failure)

Ferreira_F10 said:
I'll try flashing every MPGS firmware.
In the "bootloader logs" section of my bootloader, it always have the information:
Every time I try flashing a gpt.bin file (including RETBR 6.0.1 MPGS), in the bootloader logs on my phone, returns me (last line in pink):
And in cmd, the error "preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
Everything I read about that error says it's because of trying to flash lower firmware/bootloader than what the device thinks you have, when you have a locked bootloader. And right now there's no higher firmware than MPGS.
There's fastboot and there's mfastboot. Have you tried both? One person said they couldn't flash with just fastboot, they were only able to successfully flash with mfastboot (something about the image size).

Minimal ADB and fastboot.
https://forum.xda-developers.com/showthread.php?t=2317790

Ferreira_F10 said:
I'll try flashing every MPGS firmware.
In the "bootloader logs" section of my bootloader, it always have the information:
Every time I try flashing a gpt.bin file (including RETBR 6.0.1 MPGS), in the bootloader logs on my phone, returns me (last line in pink):
And in cmd, the error "preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
Did you solve your problem?
I'm in the same situation.
All the technicians here in Brazil tell me that it will be necessary to change the mother board.

thalescandido said:
Did you solve your problem?
I'm in the same situation.
All the technicians here in Brazil tell me that it will be necessary to change the mother board.
Click to expand...
Click to collapse
No, I gave up. Tried everything, nothing works.

Good afternoon, I had this phone for over a year in my hands and I could not repair it by any method; I finally decided to buy the main board on ebay, two days ago I got it, I changed it and it worked fine, but it was in version 4.4.4, I decided to update it via OTA, for fear something went wrong, downloaded the update, restarted and Surprise! The touch does not work anymore, this phone is definitely not for me I do not know what to do anymore. Apparently the bootloader is blocked, but I can not use the touch, it is in the initial configuration screen, I bought it was from xt1250, and the equipment I have is an xt1250, I do not understand why it stopped working .... Anyone know if there is any fix for this?

Related

[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.

help please , no os

sorry for my bad english (french)
Hi all, this is a little worry
Jai unlock the BL
Put the twrp
And the most way to reboot on Android
I try to ruu, custom nothing from nothing
It and s-on
I'm looking for a ruu in 2.16.1020.4
Cid 247 I believe
If someone has it would be nickel I am without such thanks
I believe your phone has to be locked when flashing a RUU. I think the right fastboot command for that is "fastboot oem lock". Then reboot your device with "fastboot reboot". Once re-locked install the right RUU. You can unlock afterwards if you'd like. Now I'm no pro, so don't blame me for bricking your device. But this seems to be pretty safe and is worth the try.
antho59124 said:
sorry for my bad english (french)
Hi all, this is a little worry
Jai unlock the BL
Put the twrp
And the most way to reboot on Android
I try to ruu, custom nothing from nothing
It and s-on
I'm looking for a ruu in 2.16.1020.4
Cid 247 I believe
If someone has it would be nickel I am without such thanks
Click to expand...
Click to collapse
2.16.1020.4 is available on easy-firmware.com, unfortunately you must register a paid account to download.
alray said:
2.16.1020.4 is available on easy-firmware.com, unfortunately you must register a paid account to download.
Click to expand...
Click to collapse
Thanks, but no way to have it elsewhere, or a firmware that works on my phone?
Suddenly I came out my old sony ericon x10 but it makes me crazy lol
antho59124 said:
Thanks, but no way to have it elsewhere, or a firmware that works on my phone?
Suddenly I came out my old sony ericon x10 but it makes me crazy lol
Click to expand...
Click to collapse
Your phone is s-on so that's the file you need. I don't know anywhere else where you could download this file from. It's either that or you can pay for sunshine s-off and convert to another version using a ruu from the ruu collection thread (i.e convert to the 2.xx.401.x version)
Another option would be to manually edit your version-main to 1.56.1020.70, flash a 1.56.1020.70 signed firmware and then the 1.56.1020.70 ruu.
The 1.56.1020.70 ruu is available at the ruu collection thread but not the 1.56.1020.70 firmware. So you would need to find one to use this solution (signed firmware.zip can be extracted from ota update so if you can find the 1.56.1020.70 ota we should be able to do something). You can read "how to downgrade with s-on" at the FAQ of the ruu thread to understand what i'm talking about. Once downgraded you will be able to install ota updates to be back on the latest version.
alray said:
Your phone is s-on so that's the file you need. I don't know anywhere else where you could download this file from. It's either that or you can pay for sunshine s-off and convert to another version using a ruu from the ruu collection thread (i.e convert to the 2.xx.401.x version)
Another option would be to manually edit your version-main to 1.56.1020.70, flash a 1.56.1020.70 signed firmware and then the 1.56.1020.70 ruu.
The 1.56.1020.70 ruu is available at the ruu collection thread but not the 1.56.1020.70 firmware. So you would need to find one to use this solution (signed firmware.zip can be extracted from ota update so if you can find the 1.56.1020.70 ota we should be able to do something). You can read "how to downgrade with s-on" at the FAQ of the ruu thread to understand what i'm talking about. Once downgraded you will be able to install ota updates to be back on the latest version.
Click to expand...
Click to collapse
I have just done what you said to change the version, it puts me "fail ruu12 zip error
error: write_sparse_skip_chunk: don't care size 304141584 is not a multiple of t
he block size 4096
sending sparse 'zip' (733592 KB)...
error: write_sparse_skip_chunk: don't care size 1055339792 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 1055339792 is not a multiple of
the block size 4096
OKAY [ 32.097s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_I
(bootloader) X91A2
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.400s
help me please
Here is the -- 1.56.1020.70_Images hope is help for you.
download mode
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
nenebear said:
Here is the -- 1.56.1020.70_Images hope is help for you.
download mode
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you, I try his and I come back to you, thank you again
Oh thanks, its worked !!! A huge thank you I saw myself already swing my htc by the balcony ^^

Bricked my U11 - Stuck in Download/Bootloader

Hello,
i hope some of you got an idea for fixing my problem.
1. One month ago i unlocked my bootloader and tested LeeDrOiD U11 V3.1.0 R107 because i had some problems with the camera and the battery. LeeDrOiD does'nt fixed the problems because it seems like a hardware battery problem.
2. After a few days i roled back to stock rom with my TWRP Backup without any new problems.
3. The battery problems are very irritating, so I decided to lock the bootloader and ship it to HTC. After saving my data with TWRP i locked the bootloader via fastboot. The status of the bootloader is no "Relocked".
4. The relocking of the bootloader the device booted without problems until the screen poped up: Your phone is encrypted. (i did not configured this before)
Status:
I can't fix the enryption problem. I have -5 try's left... i don't know how this can happen
I can't get into recovery because i get a Screen with: Your device is corrupt. It can't be trusted and will not boot
I tested a lot of RUU's and stock recovery's from the Google Docs Spreadsheet "HTC U11 - RUU/Firmware/Recovery/OTA Collection"
Tried
Flash the RUU. Every RUU i tested is denied because theres a "Security Version Problem"
Flash Recovery (stock and twrp) = Bootloader Locked
C:\Android>fastboot flash recovery twrp-3.2.1-2-ocn.img
target reported max download size of 1560800000 bytes
sending 'recovery' (39676 KB)...
OKAY [ 2.227s]
writing 'recovery'...
(bootloader) HOSD CL#1002308
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
Flash Unlock_Code.bin = Bootloader Locked (it's not possible to activate the setting in the developer settings, because the phone does'nt boot)
(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!
Deviceinfo
kernel: lk
product: htc_ocnuhl
version: 1.0
max-download-size: 1560800000
version-main: 2.33.401.10
boot-mode: download
version-baseband: 8998-002772-1711161638
version-bootloader: 1.0.0.0000
mid: 2PZC10000
cid: HTC__034
Thank you in advance. :good:
maxi.schwarte said:
Hello,
i hope some of you got an idea for fixing my problem.
Thank you in advance. :good:
Click to expand...
Click to collapse
For future reference, relocking the bootloader too early did this.
You can only do that after running the exact correct RUU for your version of U11 so that
you end up with stock recovery and locked system.
michaelbsheldon said:
For future reference, relocking the bootloader too early did this.
You can only do that after running the exact correct RUU for your version of U11 so that
you end up with stock recovery and locked system.
Click to expand...
Click to collapse
Thank you for your Answer. Do you know where can i get the right RUU? I can't find the right one...
maxi.schwarte said:
Thank you for your Answer. Do you know where can i get the right RUU? I can't find the right one...
Click to expand...
Click to collapse
Yes, these contributors are U11 heroes.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
michaelbsheldon said:
Yes, these contributors are U11 heroes.
Click to expand...
Click to collapse
Is it possible to fix this problem with the right RUU or is the device bricked and only HTC can fix it?
I fixed the Problem. I downloaded again the correct RUU from google spreadsheet and copied it into the root of a micro sd card and boot to download mode. (rename the RUU file to 2PZCIMG.zip)
maxi.schwarte said:
I fixed the Problem. I downloaded again the correct RUU from google spreadsheet and copied it into the root of a micro sd card and boot to download mode. (rename the RUU file to 2PZCIMG.zip)
Click to expand...
Click to collapse
Yay !
Please help
I have the exact same problem. I tried to do my do-diligence and have searched the forums and google for days trying to find a solution. All I wanted to do was install TWRP and relock the bootloader. I understand my mistake was relocking to quickly. Its now soft bricked with a locked bootloader and am only able to access bootloader and download. I have been unable to find the correct RUU for my model:
kernel: lk
product: htc_ocnuhljapan
version: 1.0
max-download-size: 1560800000
serialno: FA76V1803367
slot-count: 0
current-slot:
imei: 356134080328971
version-main: 2.53.454.4
boot-mode: download
version-baseband: 8998-002772-1802141355
version-bootloader: 1.0.0.0000
mid: 2PZC20000
cid: 11111111
Can anyone help? I would greatly appreciate it. This device was supposed to be a birthday gift. Messed it up good.
Thank you
nv1086 said:
I have the exact same problem. I tried to do my do-diligence and have searched the forums and google for days trying to find a solution. All I wanted to do was install TWRP and relock the bootloader. I understand my mistake was relocking to quickly. Its now soft bricked with a locked bootloader and am only able to access bootloader and download. I have been unable to find the correct RUU for my model:
kernel: lk
product: htc_ocnuhljapan
version: 1.0
max-download-size: 1560800000
serialno: FA76V1803367
slot-count: 0
current-slot:
imei: 356134080328971
version-main: 2.53.454.4
boot-mode: download
version-baseband: 8998-002772-1802141355
version-bootloader: 1.0.0.0000
mid: 2PZC20000
cid: 11111111
Can anyone help? I would greatly appreciate it. This device was supposed to be a birthday gift. Messed it up good.
Thank you
Click to expand...
Click to collapse
i See you have U11 KDDI version, i can upload it for you.
YGRamadhan said:
i See you have U11 KDDI version, i can upload it for you.
Click to expand...
Click to collapse
That would be greatly appreciated, thank you.
nv1086 said:
That would be greatly appreciated, thank you.
Click to expand...
Click to collapse
check your PM i send it over there.
I have an HTC U11, and it's soft-bricked because I tried installing TWRP as my new recovery and it turned out to be corrupt. Now my phone is on a boot loop. Please help.
MikeG123 said:
I have an HTC U11, and it's soft-bricked because I tried installing TWRP as my new recovery and it turned out to be corrupt. Now my phone is on a boot loop. Please help.
Click to expand...
Click to collapse
How about trying to install another recovery over the top of the old one see if that works, or just flash the correct ruu in download mode and just start over

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

Categories

Resources