Database Info

Bootloop issue

I am having issues after i flashed this Stock AT&T Deodexed JB 4.1.1 | Official AT&T 3.18.502.6 Update Rom..After htc logo at start up all i get is a blank screen and nothing else.S-off,unlocked bootloader & using TWRP here..
Need help as i am clueless right now :crying:
PS:Using At&t One x...Coming from a Nexus..Never thought that i'll get into this much trouble

Versions of TWRP after 2.3 have been known to be problematic. I'd try to install TWRP 2.3, or the official CWM.

So you mean to say that i should try 2.3 TWRP and try to flash the Rom again?

Can i run RUU after relocking the bootloader?
My PC can detect the phone in fastboot mode..

Sak3ater said:
So you mean to say that i should try 2.3 TWRP and try to flash the Rom again?
Click to expand...
Click to collapse
Precisely. What version of TWRP are you using currently? If its the latest (2.5.0.0), I'll bet this is the problem.
TWRP 2.3 seems to be the most stable version. I believe 2.3.1.1 is what you want. If you look through the TWRP thread, there are some folks that have posted links to this older version.
---------- Post added at 12:08 PM ---------- Previous post was at 12:08 PM ----------
Sak3ater said:
Can i run RUU after relocking the bootloader?
My PC can detect the phone in fastboot mode..
Click to expand...
Click to collapse
Since you are s-off, you don't need to relock the bootloader.
---------- Post added at 12:11 PM ---------- Previous post was at 12:08 PM ----------
Sak3ater said:
PS:Using At&t One x...Coming from a Nexus..Never thought that i'll get into this much trouble
Click to expand...
Click to collapse
HTC security can be a pain. But they aren't the only manufacturer with security measures. Every Android device is different. Don't blame the device. Learn, adapt and conquer.

If you have s-off you should be able to flash RUUs to your heart's content, recovery has nothing to do with it. You can try the other twrp by flashing it in fastboot then try flashing the rom again, or try another rom after transferring it in recovery
Sent from my HTC One X using xda premium

flyingriffin said:
If you have s-off you should be able to flash RUUs to your heart's content, recovery has nothing to do with it.
Click to expand...
Click to collapse
I think OP is asking about RUU as an alternative, just to get the phone back up and running again; not as a way to install the stock rooted ROM he linked.

Ok guys thanks for the suggestions...
Yeah i was using TWRP 2.5.0.0...
I had no other choice but to go for RUU...But first i did relock the bootloader & then went for the RUU..
Whole process went smoothly & i got the phone booted up fine..Today i learnt a lesson..Never ever flash anything without doing a backup first..
Yeah i know..I had Desire HD once & i dont wanna think about how i rooted it lol.& today i got stuck in another Htc device..Well it was my mistake in the first place because i forgot to take a backup of stock Rom..
Anyways i wana ask something else now..i used fastboot oem lock command to relock the bootloader..Now how to unlock it again?
htcdev method?I already have the Unlock_code file..
Also now can i flash 4.1.1 RUU this time?Right now i am on 4.0.4..
Thanks guys once again..All of you really were of great help..

Okay i can unlock it again using this command 'fastboot flash unlocktoken Unlock_code.bin'

Sak3ater said:
Okay i can unlock it again using this command 'fastboot flash unlocktoken Unlock_code.bin'
Click to expand...
Click to collapse
I don't recall the exact syntax. But you can reuse the unlock token, with the same fastboot command you unlocked with originally.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Sak3ater said:
I had no other choice but to go for RUU...
Also now can i flash 4.1.1 RUU this time?Right now i am on 4.0.4..
Thanks guys once again..All of you really were of great help..
Click to expand...
Click to collapse
Why? Did you try to just flash TWRP 2.3.1.1 (or newest CWM) then re-flash the ROM as previously recommended?
Sak3ater said:
Also now can i flash 4.1.1 RUU this time?Right now i am on 4.0.4..
Click to expand...
Click to collapse
Yes.

redpoint73 said:
Why? Did you try to just flash TWRP 2.3.1.1 (or newest CWM) then re-flash the ROM as previously recommended?
.
Click to expand...
Click to collapse
No..Actually i just pressed my panic button & went directly for the RUU without wasting any time :silly:
Left the recovery as it was
If it was the recovery issue then so sad..Ive been using Twrp in Nexus 4 without any issues..I wonder why it gave me trouble here..

Now i am in search of 4.1.1 RUU

[Q] one xl bricked need help

I have a one xl cid rogers001 hboot 2.14, baseband 0.23a.3 2.09.29.... jb 4.1 with sense 4+
I tried unlock bootloader by htcdev => ok
install recovery => ok. and when i installed this rom: http://forum.xda-developers.com/showthread.php?t=1868236, it was stuck in bootloader. i fogot root my phone before.
so i relock my device, and tried to flash this stock rom using adb : OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (was found in this thread: http://forum.xda-developers.com/showthread.php?t=2119610)
On cmd via fastboot i type fastboot erase cache =>ok
fastboot oem rebootRUU => ok
fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail") in the end cmd
What should i do now?
Thanks for reading and help me pls!!!!

Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita

timmaaa said:
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!

somebody help me pls

veveve said:
somebody help me pls
Click to expand...
Click to collapse
Please be patient, we all have lives outside XDA.
veveve said:
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
Click to expand...
Click to collapse
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita

timmaaa said:
Please be patient, we all have lives outside XDA.
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
Click to expand...
Click to collapse
yes, i did it more than once, now it's fixed, but when i mount it to Windows using TWRP, nothing happen, so i can't format it. and the same things when i tried to sideload. But in fastboot mode, it usual.
and i flashed the newest rom in this thread: http://forum.xda-developers.com/showthread.php?t=1868236 ViperXL 4.2 and i didn't check the MD5
back to my previous question, can i fash a custom rom without root?

I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita

Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.

nem1yan said:
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
Click to expand...
Click to collapse
I disagree. I think it's a better idea for him to get his head around the simple operations like flashing ROMs before attempting s-off.
Sent from my Evita

timmaaa said:
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Click to expand...
Click to collapse
Full ROM:
Jelly Bean - Android 4.2.2 / Sense 5
ViperXL 4.2.0
Main Link: http://www.androidfilehost.com/?fid=23134718111254927
Mirror 1: http://goo.im/devs/Turge/ViperXL/ViperXL_4.2.0.zip
Mirror 2: http://d-h.st/z4Q
Click to expand...
Click to collapse
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/showthread.php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Thanks!

I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita

timmaaa said:
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
Click to expand...
Click to collapse
it is ViperXL_4.2.0.zip
i'll do it next time!

No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...

veveve said:
it is ViperXL_4.2.0.zip
i'll do it next time!
Click to expand...
Click to collapse
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
You might be onto something.
Sent from my Evita

timmaaa said:
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
You might be onto something.
Sent from my Evita
Click to expand...
Click to collapse
I mean, i didn't do it and i will do it next time

bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
thanks, i will try.

Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita

timmaaa said:
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
but i still have trouble with mounting internal storage using TWRP on windows, should i try the older TWRP?

What version do you have installed?
Sent from my Evita

timmaaa said:
What version do you have installed?
Sent from my Evita
Click to expand...
Click to collapse
here
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/show....php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Click to expand...
Click to collapse

Back to stock

Can somebody explain me,how can i go back to stok to apply ota update if im rooted and have opend bootloader!?

krepsz said:
Can somebody explain me,how can i go back to stok to apply ota update if im rooted and have opend bootloader!?
Click to expand...
Click to collapse
Hi,
me too i want to back to stock but i think it's to complicated, so what i know : 1st backup ur current custom rom (for safe ^^);
2nd restore stock recovery; 3th restore RUU for your A9 (hiaeuhl or hiaeul etc ... ) that all i know but i heard that we need to restore the /system partition (i dont backup this before install cm13 :/ ) if anybody know what to do exactly :fingers-crossed: :silly:
the s-on/s-off scare me too xD i dont know what to do to restore stock properly ^^' maybe we have another thread for that i look later

S-on/off has nothing to do with going back to stock (unless you want to change version).
if you flash RUU you'll be 100% stock but you'll lose everything including root
bootloader is fine i guess.

syntenza said:
S-on/off has nothing to do with going back to stock (unless you want to change version).
if you flash RUU you'll be 100% stock but you'll lose everything including root
bootloader is fine i guess.
Click to expand...
Click to collapse
I relocked bootloader and flash stock recovery,but if i want flash the RUU fil i get this:
target reported max download size invalid sparse file format at header magi

krepsz said:
I relocked bootloader and flash stock recovery,but if i want flash the RUU fil i get this:
target reported max download size invalid sparse file format at header magi
Click to expand...
Click to collapse
Verify that you have the correct RUU for your phone. If you do, and it still isn't working, try the RUU .exe while your phone is in download mode. Also, make sure you're not using a USB 3.0 port. Sometimes that can cause problems.

CSnowRules said:
Verify that you have the correct RUU for your phone. If you do, and it still isn't working, try the RUU .exe while your phone is in download mode. Also, make sure you're not using a USB 3.0 port. Sometimes that can cause problems.
Click to expand...
Click to collapse
I found just one old RUU zip file for my phone.RUU.exe i dont know where i can found.Usb port working with all command before.

krepsz said:
I found just one old RUU zip file for my phone.RUU.exe i dont know where i can found.Usb port working with all command before.
Click to expand...
Click to collapse
What A9 version do you have? (Unlocked, carrier, EU, etc.)

CSnowRules said:
What A9 version do you have? (Unlocked, carrier, EU, etc.)
Click to expand...
Click to collapse
Vodafone UK
modelid: 2PQ910000
cidnum: VODAP001

Refer to this thread by @alray.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Download 1.27.161.6 from post #1, then follow the steps from post #2. I'd try the first method, first.
This should work unless your firmware was updated to a later version than 1.27.161.6.

CSnowRules said:
Refer to this thread by @alray.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Download 1.27.161.6 from post #1, then follow the steps from post #2. I'd try the first method, first.
This should work unless your firmware was updated to a later version than 1.27.161.6.
Click to expand...
Click to collapse
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!

krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
Gotcha, I'd recommend that you use the external sd/stock recovery method to return to stock. That's probably the most bulletproof way to return to stock. If you no longer have the stock recovery, no problem. It's pretty simple to extract the recovery from the RUU and flash it first.
Also, did you download the RUU again? It is possible that you may have a corrupted RUU.zip if it is crashing your fastboot.

So me i'm on CM13 nightlies with twrp and boot.img modified, to back to stock i had to flash stock recovery( * ) than flash the RUU( ** ) ? that all ?
*: i had to extract it from the RUU coresponding i'm good ? ^^"
**: my cid is HTC_034; my mid is 2PQ910000 so i had to take the 1.10.401.7 RUU i'm good ? ^^' or the 1.56.401.70 or 1.27.401.5 ? i'm lost, on my dowload mode it's say i'm on 1.10.401.7 (but i'm on cm13 latest nightlies ... >< )
Than, when i'm succefully back to stock if i choose to return to cm13 i can flash my backup(recovery+boot+/system+rom) of cm13 with twrp if firmware doesn't upgrade with OTA on stock i'm good ?
Lots of question i know ^^' thx for help.

krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
If you use the sd card method (copy the RUU.zip to external sd) fastboot is no longer necessary. The RUU is flashed using the stock recovery. There's no fastboot to crash at that point.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
ValdOr7 said:
So me i'm on CM13 nightlies with twrp and boot.img modified, to back to stock i had to flash stock recovery( * ) than flash the RUU( ** ) ? that all ?
*: i had to extract it from the RUU coresponding i'm good ? ^^"
**: my cid is HTC_034; my mid is 2PQ910000 so i had to take the 1.10.401.7 RUU i'm good ? ^^' or the 1.56.401.70 or 1.27.401.5 ? i'm lost, on my dowload mode it's say i'm on 1.10.401.7 (but i'm on cm13 latest nightlies ... >< )
Than, when i'm succefully back to stock if i choose to return to cm13 i can flash my backup(recovery+boot+/system+rom) of cm13 with twrp if firmware doesn't upgrade with OTA on stock i'm good ?
Lots of question i know ^^' thx for help.
Click to expand...
Click to collapse
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.

CSnowRules said:
If you use the sd card method (copy the RUU.zip to external sd) fastboot is no longer necessary. The RUU is flashed using the stock recovery. There's no fastboot to crash at that point.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
Click to expand...
Click to collapse
Could you state how this is done? I recently moved to the A9 from having the M7 since it came out, (which had NO external SD card support) , so this is the 1st I'm hearing of being able to apply an RUU Without fastboot... Does the RUU have to be in any specific folder, or the root of the external SD card?
Any details would be GREATLY appreciated.

bdizzle1686 said:
Could you state how this is done? I recently moved to the A9 from having the M7 since it came out, (which had NO external SD card support) , so this is the 1st I'm hearing of being able to apply an RUU Without fastboot... Does the RUU have to be in any specific folder, or the root of the external SD card?
Any details would be GREATLY appreciated.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showpost.php?p=63640734&postcount=2 explains in detail. I THINK this utilizes the stock recovery in the process. In any case, it allows flashing an RUU.zip without any fastboot involvement.

It's possible to return s-on and bootloader locked (not relocked)? Thank's.

CSnowRules said:
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
Click to expand...
Click to collapse
Yes i know but u dont understand me i think, for the RUU there 3 version for my phone 1.10 -> 1.27 -> 1.56 so witch one i had to take ? CM13 run with 1.27 ? 1.10 with cm13 isn't possible no ? because on my download mode(bootloader) it's say : OS-1.10.401.7 in theory i would take the 1.10.401.7 RUU but a man (on this forum) tell me this was a bug of cm13 and its run with 1.27 it's wrong ??

ValdOr7 said:
Yes i know but u dont understand me i think, for the RUU there 3 version for my phone 1.10 -> 1.27 -> 1.56 so witch one i had to take ? CM13 run with 1.27 ? 1.10 with cm13 isn't possible no ? because on my download mode(bootloader) it's say : OS-1.10.401.7 in theory i would take the 1.10.401.7 RUU but a man (on this forum) tell me this was a bug of cm13 and its run with 1.27 it's wrong ??
Click to expand...
Click to collapse
Any one of the three would return you to stock, as long as the version number is greater than or equal to the firmware that you have installed. (Which is the topic of this tread...)
As far as compatibility with CM, you should check that thread...but I think CM is compatible with the 1.27 firmware. If you're still s-on, you DO NOT want to upgrade the firmware to a newer version than CM supports, if you intend to use CM.
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
CEDRIC23 said:
It's possible to return s-on and bootloader locked (not relocked)? Thank's.
Click to expand...
Click to collapse
I'm sure it's possible...just a matter of finding exactly what you need to hex edit and where it is. Experimenting with this likely carries a chance of bricking your device, since the variables would have to be used by HBOOT and/or download mode. Maybe someone else has already accomplished this?

krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a RUU, not the regular fastboot.exe from the android sdk.
CSnowRules said:
This http://forum.xda-developers.com/showpost.php?p=63640734&postcount=2 explains in detail. I THINK this utilizes the stock recovery in the process. In any case, it allows flashing an RUU.zip without any fastboot involvement.
Click to expand...
Click to collapse
The stock recovery is not used when flashing a RUU from the sdcard. The bootloader handles the process, not the recovery. Stock recovery isn't needed at all, using fastboot or the sdcard methods.

alray said:
The stock recovery is not used when flashing a RUU from the sdcard. The bootloader handles the process, not the recovery. Stock recovery isn't needed at all, using fastboot or the sdcard methods.
Click to expand...
Click to collapse
Thanks, Alray, for the clarification on the sd card method.

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8

TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.

zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.

This is the stock recovery version, correct?

koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.

TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.

Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones

koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.

Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.

Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.

Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )

kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.

TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.

kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.

Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"

s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!

It works in LOCKED BOOTLOADER??? .-.

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.

TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.

[How-to][ruu] Flash ruu.zip to factory

If you have some problem with your phone like me (Settings app fc always) you can download your RUU.zip and flash it.
If your bootloader unloced no problem no need to relock.
Go to download mode and type:
Code:
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
Code:
htc_fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error (pre-hboot update: please flush immediately) and maybe your phone reboot sometimes.
Make sure device is still in ruu mode(black HTC screen).
Let it run and it should finish this time
After completed :
Code:
fastboot reboot
It will reboot to a fully stock build.
Just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically :
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
Enjoy your stock phone again.
RUU.zip links:
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_Europe_1.10.401.23_Radio_8998-002772-1711021849_release_516987_signed_2_4.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.05.709.12_Radio_8998-002772C-1710231751_release_515062_signed_2_4.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.10.709.23_Radio_8998-002772-1711021849_release_516988_signed_2_4.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.23.709.3_Radio_8998-002772-1711161638_release_518568_signed_2_4_2.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_India_SEA_1.10.400.23_Radio_8998-002772-1711021849_release_517155_signed_2_4_2.zip
If link is dead you can searc here: 2Q4DIMG
Yes i tried and worked every time for me!
You can't make a downgrade with out S-OFF!!!
(I'm not using HTC anymore but this process still working)
HTC Fastboot in 2nd post. You only need paste to fastboot and adb folder.

If you want to decrypt RUU you can use : HTC RUU Decrypt tool . You will got a system.img, boot.img, recovery.img etc...
HTC Fastboot exe : https://androidfilehost.com/?fid=95916177934550031

Thank you. I was wondering how to flashing the zips.

Thanks OP.
I want to extract the stock boot and recovery from RUU but it appears the format of RUU provided here is different from the others.
Is it still possible to extract them?
And could this RUU rename to 2Q4DIMG.zip and place to sdcard and flash from device with download mode?

bnwg said:
Thanks OP.
I want to extract the stock boot and recovery from RUU but it appears the format of RUU provided here is different from the others.
Is it still possible to extract them?
And could this RUU rename to 2Q4DIMG.zip and place to sdcard and flash from device with download mode?
Click to expand...
Click to collapse
If y want to decrypt the RUU y need this : HTC RUU Decrypt tool
You can decrypt the ruu file and y can find the system.img, boot.img, recovery.img.
I think you can place to sdcard but i didn't try this.

czifraj2 said:
If y want to decrypt the RUU y need this : HTC RUU Decrypt tool
You can decrypt the ruu file and y can find the system.img, boot.img, recovery.img.
I think you can but i didn't try this.
Click to expand...
Click to collapse
I tried this tool but it is very complicated 1

czifraj2 said:
If y want to decrypt the RUU y need this : HTC RUU Decrypt tool
You can decrypt the ruu file and y can find the system.img, boot.img, recovery.img.
I think you can but i didn't try this.
Click to expand...
Click to collapse
Yes. Confirmed it can be decrypted by the tool. Thanks.

Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.

Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
hi, did you get the problem said file corrupt?
of if you have the zip, could you please upload it for me?
thank you.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
yayyyy!! finally!! it works now! thank you so much! I did tried thousands of method but this one made my phone alive again! :laugh::good:

dazehaze said:
hi, did you get the problem said file corrupt?
of if you have the zip, could you please upload it for me?
thank you.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
yayyyy!! finally!! it works now! thank you so much! I did tried thousands of method but this one made my phone alive again! :laugh::good:
Click to expand...
Click to collapse
:good::good::good::good::good:

Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
Yes i know no need to unlock bootloader but i tried root my phone

Would this allow ota again after getting red triangle error?
Thanks
Sent from my SM-N950F using Tapatalk

Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
I tried to downgrade from 1.24.401.2 to 1.10.401.23 with the SD-card method (non root) because of wakelocks and the low percentage of Deep Sleep of screen time off (confirmed today by HTC Nordic today and that HTC are working on a new update. The support person didn't know any ETA).
Everything seems okay underway when flashing but after boot and finishing the setup procedure, Wifi, Google account etc. I'm still on 1.24.401.2. I used the 1.10.401.23 in the first post.
Have anyone else tried to downgrade with non root?

fasst said:
I tried to downgrade from 1.24.401.2 to 1.10.401.23 with the SD-card method (non root) because of wakelocks and the low percentage of Deep Sleep of screen time off (confirmed today by HTC Nordic today and that HTC are working on a new update. The support person didn't know any ETA).
Everything seems okay underway when flashing but after boot and finishing the setup procedure, Wifi, Google account etc. I'm still on 1.24.401.2. I used the 1.10.401.23 in the first post.
Have anyone else tried to downgrade with non root?
Click to expand...
Click to collapse
My HK model got an update today to 1.24.400.03 and devcheck is reporting 61% deep sleep.
I have had almost none since the update from 1.10 to 1.24.400.01. the .03 update seems to have solved this.
Sent from my HTC U11 plus using Tapatalk

RUU decrypt tool
dazehaze said:
I tried this tool but it is very complicated 1
Click to expand...
Click to collapse
Have a look here
This is just a FYI

fasst said:
I tried to downgrade from 1.24.401.2 to 1.10.401.23 with the SD-card method (non root) because of wakelocks and the low percentage of Deep Sleep of screen time off (confirmed today by HTC Nordic today and that HTC are working on a new update. The support person didn't know any ETA).
Everything seems okay underway when flashing but after boot and finishing the setup procedure, Wifi, Google account etc. I'm still on 1.24.401.2. I used the 1.10.401.23 in the first post.
Have anyone else tried to downgrade with non root?
Click to expand...
Click to collapse
Downgrade has nothing to do with root. You have to be S-off.

I have problem when trying to flash firmware in fastboot when I get to htc_ fastboot flash zip in terminal it's doesn't recognize order but when I try without htc_ only fastboot get error file to big, I'm using Mac!

dane1312 said:
I have problem when trying to flash firmware in fastboot when I get to htc_ fastboot flash zip in terminal it's doesn't recognize order but when I try without htc_ only fastboot get error file to big, I'm using Mac!
Click to expand...
Click to collapse
You are in oemRUU?

czifraj2 said:
You are in oemRUU?
Click to expand...
Click to collapse
Yes

I'll appreciate if you could share the HTC Arabic (HTC__J15) RUU .