Database Info

[Q] [q] stupid question in regards to flash

friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding. I have tried to reflash a new rom/ flash boot.img and the new rom installs and the same thing occurs. I know if i flash a default rom i will have to relock the BL but i will lose the ability to flash anything in the future?
some details you wil probably need on my screen
evita pvt ship S-on RL
S-ON( i have a feeling it has to do with this)
h-boot 1.09
radio 0.17.32
i have tried clean rom and viper rom and i get the same issue. suggestions?

all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.

DJSYNTHVIRUS said:
friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding.
Click to expand...
Click to collapse
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.

DvineLord said:
all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.
Click to expand...
Click to collapse
im going to fix permissions and see if i can reflash clean rom if that doesnt work i will try to update twrp then repeat. thanks for the help

hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP

redpoint73 said:
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.
Click to expand...
Click to collapse
can you suggest anything i cant figure out why its force closing like that? please and thank you

DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
Boot into bootloader, then select recovery. You'll be able to tell which one you have then.
---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------
DJSYNTHVIRUS said:
can you suggest anything i cant figure out why its force closing like that? please and thank you
Click to expand...
Click to collapse
CWM is not supported by the HTC One X/XL. TWRP does, which is why you're having some issues. I would recommend flashing TWRP over before you flash anything else. Doing something wrong on CWM could lead you in the path of being a proud owner of a $500 paper weight.

DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.

redpoint73 said:
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.
Click to expand...
Click to collapse
thnx to all of you, when booting into recovery i get into TWRP so it is most likely as you say my buddy who gave it to me most likely flashed CWM then TWRP , so your suggesting doing the above in that order?

Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.

ill try it thanks
QUOTE=redpoint73;33819696]Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.[/QUOTE]

HELP!! Removed OS on htc one m8 verizon wipe TWRP

My phone now no longer boots as I accidentally removed the OS. How can I fix this?

HeyNumbNutz said:
My phone now no longer boots as I accidentally removed the OS. How can I fix this?
Click to expand...
Click to collapse
If you are s-off you can simply download the RUU and put it on your ext sdcard and then follow the instructions in the post. If you are not s-off just download a custom rom to your ext card and flash it in twrp.

GoBears said:
If you are s-off you can simply download the RUU and put it on your ext sdcard and then follow the instructions in the post. If you are not s-off just download a custom rom to your ext card and flash it in twrp.
Click to expand...
Click to collapse
Hi, can you explain how I can get an RUU. I am new to android since I just switched from iOS and have no clue how to do this.

HeyNumbNutz said:
Hi, can you explain how I can get an RUU. I am new to android since I just switched from iOS and have no clue how to do this.
Click to expand...
Click to collapse
There's a thread in the development by dotthat with the RUU for our phone. Just follow his directions exactly and you'll be back to out of the box fresh but still s-off.
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Here's the thread for the RUU.
http://forum.xda-developers.com/showthread.php?t=2727831
Personally, I would just flash CleanROM. It's a super stable and slick cleaned up stock rom by an awesome dev.

GoBears said:
There's a thread in the development by dotthat with the RUU for our phone. Just follow his directions exactly and you'll be back to out of the box fresh but still s-off.
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Here's the thread for the RUU.
http://forum.xda-developers.com/showthread.php?t=2727831
Personally, I would just flash CleanROM. It's a super stable and slick cleaned up stock rom by an awesome dev.
Click to expand...
Click to collapse
After I restore it back to stock with RUU, will I have to redo root, s-off and twrp recovery? or will everything stay the same and I will just have to add Roms back on

HeyNumbNutz said:
After I restore it back to stock with RUU, will I have to redo root, s-off and twrp recovery? or will everything stay the same and I will just have to add Roms back on
Click to expand...
Click to collapse
You will keep root. I have an ruu mode TWRP posted there to for your convenience. Alternatively you could flash TWRP and go to advanced and select adb sideload. You can then adb side load a rom to your device

dottat said:
You will keep root. I have an ruu mode TWRP posted there to for your convenience. Alternatively you could flash TWRP and go to advanced and select adb sideload. You can then adb side load a rom to your device
Click to expand...
Click to collapse
Boom! There you go, doesn't get easier than that! Thank you Dottat for all the time and work you put into creating the RUU for us. It's very much appreciated.

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

(Q) downgrade to nougat

Hi
Now i on leedroid 3.00 oreo custom rom.
I want to go back to nougat.
My device is 128/6 dugl india.
If i flash nougat ruu firmware threw download mode it will be good?
Thank you

yossim66 said:
Hi
Now i on leedroid 3.00 oreo custom rom.
I want to go back to nougat.
My device is 128/6 dugl india.
If i flash nougat ruu firmware threw download mode it will be good?
Thank you
Click to expand...
Click to collapse
If you flashed a full Oreo firmware instead of just the dsp, radio and bluetooth images you won't be able to downgrade. Firmware can only be downgraded if S-OFF, and that's not yet available on Oreo. If that's the case you are very well stranded on Oreo for the time being.
To be honest those things are quite basic knowledge you should have learned before you started tinkering with your device. Today most people just start flashing away, while I - when I started it myself back on the Desire days - read up on XDA and other forums for about three weeks to know what is to know. Still reading and learning new ways to accomplish what I want from instructions by developers, themer and many other users. Might never stop doing so until I'll stop tinkering.
Sent from my HTC U11 using XDA Labs

I flash before only bt+dsp, not full oreo firmware

yossim66 said:
I flash before only bt+dsp, not full oreo firmware
Click to expand...
Click to collapse
Download frimwore 1.27.401.11 and flash it
Because base your phone is nogat .
Before flash Unlock your phone's screen to decrypt it later restore back up
---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------
I think you should go on the ruu mod by
Fastboot oem rebootRUU
Fastboot flash zip frimware.zip
(Again)
Fastboot flash zip frimware.zip

mehrdad_esmaeeli said:
Download frimwore 1.27.401.11 and flash it
Because base your phone is nogat .
Before flash Unlock your phone's screen to decrypt it later restore back up
---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------
I think you should go on the ruu mod by
Fastboot oem rebootRUU
Fastboot flash zip frimware.zip
(Again)
Fastboot flash zip frimware.zip
Click to expand...
Click to collapse
If he has the wrong or to old fastboot on his PC, he won't be able to flash the RUU, due to file size restrictions in older fastboot versions. On the other hand, I'd personally prefer the SD card method instead of fastboot RUUing, as that always avoids such problems.
Sent from my HTC U11 using XDA Labs

5m4r7ph0n36uru said:
If he has the wrong or to old fastboot on his PC, he won't be able to flash the RUU, due to file size restrictions in older fastboot versions. On the other hand, I'd personally prefer the SD card method instead of fastboot RUUing, as that always avoids such problems.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
very well. So please explain step by step

Hi.
Everything o. K., i flash nougat ruu threw download mode from ext. Sd card. Everything goes well.
I am on nougat viper 1.80.
Thank you for helping.

yossim66 said:
Hi.
Everything o. K., i flash nougat ruu threw download mode from ext. Sd card. Everything goes well.
I am on nougat viper 1.80.
Thank you for helping.
Click to expand...
Click to collapse
Who to?
Please explain

I download ruu firmware, put it on root of ext. Sdcard.
Reboot the phone to download mode. In the starting of download mode, it give you to choose, vol + to flash, vol - to cancel.
The ruu firmware must rename to "2PZCIMG. Zip",
If you have twrp, you must wipe data.

May I ask why you decide to switch back?

mehrdad_esmaeeli said:
very well. So please explain step by step
Click to expand...
Click to collapse
There is a guide in the OP of my collection thread. No need to do a step by step yet again. Just got to the first page of my pinned topic in the guides section and you find it, as long as you care to read the first 5 posts carefully.
yossim66 said:
Hi.
Everything o. K., i flash nougat ruu threw download mode from ext. Sd card. Everything goes well.
I am on nougat viper 1.80.
Thank you for helping.
Click to expand...
Click to collapse
Glad it helped mate. Have fun with your U11.
Sent from my HTC U11 using XDA Labs

Sorry.you flashed ruu frimware or ruu ROM?
Why should I before flash wiped data?

https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview#
This is the link to download the firmware according the model of your device.
Wipe data is to prevent errors.

yossim66 said:
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview#
This is the link to download the firmware according the model of your device.
Wipe data is to prevent errors.
Click to expand...
Click to collapse
Sorry before flash ruu ROM zip you do relocked the bootloader or not?

mehrdad_esmaeeli said:
Sorry before flash ruu ROM zip you do relocked the bootloader or not?
Click to expand...
Click to collapse
No.
My device is still unlocked.

yossim66 said:
No.
My device is still unlocked.
Click to expand...
Click to collapse
So build 401 not updated to oero yet?

mehrdad_esmaeeli said:
So build 401 not updated to oero yet?
Click to expand...
Click to collapse
I don't know, i been on viper 2.01 after flash radio, bt, dsp.
Now i return to viper 1.80 custom rom.
In custom rom you don't get official update.

???Ok I flashed ruu rom 1.27.401.11 ocndul Europe and returned to nogat successfully
Later I really not like android 7.1.1 and again returned to oero
So well . later for getting ota official again returned to nogat