[Q] Rogers Nandroid backup

[Q] Rogers Nandroid backup - HTC Jetstream

is it possible for anyone to post a rogers nandroid back up
i flashed osimod rom buh when i tried flashing the RUU downloaded from http://forum.xda-developers.com/showthread.php?t=1287553
and i keep getting stuck on the error described below, i also tried using the exe and locking the bootloader
C:\android-sdk-windows>fastboot flash zip update.zip
sending 'zip' (456867 KB)...
OKAY [ 39.978s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.170s
with bootloader locked and updating updating through .exe i get error on line 8 -Fail-Pu
get partition update fail

Oi vey.
That's not how you update your device. When you get an update.zip for a custom ROM, such as the ones you'll find here on XDA, you need to flash it via ClockworkMod Recovery.
In the Jetstream - Android Development forum you'll find instructions on how to root your device and install the custom recovery image. Once that's done, you'll boot your device into recovery mode, and install your update.zip from there.
I have no idea what "fastboot flash zip" even does. You may have completely screwed your device. That being said, head here: http://forum.xda-developers.com/showthread.php?t=1418084 and follow the instructions to install ClockworkMod Recovery.
I'm not sure just how well that'll work for you. Good luck, sir!

i m able to flash the rom buh it wont boot up when connected to pc it shows the tablet is running but the screen will remain black,
finally able to fix it i went to cwm mounts and storage formatted the system, date and everything tht had format on it and somehow it fixed it, do u have any suggestion on how to flash the stock rom?

http://forum.xda-developers.com/showthread.php?t=1287553
That thread points to a collection of all the RUU's available for download. I haven't had any luck flashing my own, so good luck!

I tried that didn't wrk

Related

[Q][VIEW]bootloops, seems ota update failed

i applied the latest HC ota update, it seemed like it finished the update, was stuck at the htc logo. i waited about an hour and decided to restart. my phone now gets stuck in a bootloop. it gets to the sprint animation and back to the htc logo.
i'm s-on
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
eMMC-boot
oct 25, 2011, 16:35:13
any suggestions on what i can try? i tried placing the ota zip on the sd card and renamed it to p41img.zip, it starts but seems to stop right after it says something about parsing. stock recovery just shows a red exclamation point. i hope i don't have to send it in, this sucks

newalker91 said:
You need to press Vol Up + Power once you see the red ! in stock recovery. Wipe your data. The boot looping is due to corrupted data after a software version change.
Click to expand...
Click to collapse
yea i tried that. at the bottom it says can't open cache/recovery/command, but i still went ahead and wiped data. i want to overwrite /system but the img files are too big for fastboot. can i reapply, just the system part of the update? i'm assuming i might have to create a system.img.

looks like i'm stuck until someone can get custom recovery to work on the new hboot

That's not going to happen any time soon (custom recovery).
It looks like the second stage of the upgrade didn't happen.
Unzip the ota zip file, and extract the firmware.zip from inside it (do not extract firmware.zip ) Copy that to the SD-CARD and rename if PG41IMG.zip and try installing from the bootloader. If that fails then this is a standard support request.
You will not be the only one who has issues like this during this type of upgrade, and unless footballcomesup trumps again and finds the RUU it will mean a service call to fix the software in a partial upgrade.

globatron said:
That's not going to happen any time soon (custom recovery).
It looks like the second stage of the upgrade didn't happen.
Unzip the ota zip file, and extract the firmware.zip from inside it (do not extract firmware.zip ) Copy that to the SD-CARD and rename if PG41IMG.zip and try installing from the bootloader. If that fails then this is a standard support request.
You will not be the only one who has issues like this during this type of upgrade, and unless footballcomesup trumps again and finds the RUU it will mean a service call to fix the software in a partial upgrade.
Click to expand...
Click to collapse
didn't work that sucks. i managed to do the htc unlock but that didn't help. i tried doing fastboot oem rebootRUU and then fastboot flash zip firmware.zip and got this:
sending 'zip' (17224 KB)...
OKAY [ 2.146s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 11.730s
oh well guess to htc it is and i just bought this crap for myself for xmas and won't even be able to use it during xmas, f*ck man!

[Q] EVO V Bootloop Problem

Hey Guys,
Last night I was attempting a Revolutionary S-off hack and during the first step where youre supposed to downgrade the software to 1.13 my restarted for updates -___- Since I relocked the bootloader to start the process (my phone was rooted and flashed with Harmonia) , I retried the process. I kept getting errors that said I was using the wrong updater for the process to work. (I wasnt). So i attepmted to work around the updater and found a copy of the RUU i needed (1.13) for the EVO V for Virgin Mobile earlier today and tried to flash the zip using the fastboot commands but it keeps telling me this:
C:\Users\Shaun\Desktop\Android>fastboot flash zip PG86IMG.zip
sending 'zip' (6882 KB)...
OKAY [ 2.465s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 4.449s
I cant access the recovery to try it there either. It just takes me back to the same white bootloader screen. It says its locked there. In fact, it wont let me flash anything, TWRP or the RUU or any other ROM for that matter. It just tells me "signature verify fail" So im completely stuck. Im out of ideas completely. Someone please help.

[SOLVED]I need some help. Can't boot anymore.

[SOLVED]
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
EDIT :
My actual bootloader :
Code:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OPENDSP-v33.1.0.45.1128
eMMC-boot
Aug 22 2013, 11:48:30:-1
I tried to check my version for RUU reset
Code:
c:\Fastboot>fastboot getvar version-main
version-main: 5.08.163.2
finished. total time: 0.003s
Couldnt find any .exe RUU to help.
Thanks !

ethanon said:
Are you using the latest CM 4.4 nightlies ? If yes these rom wont install using TWRP , you need to install either Lloir or Philz CMW recovery to flash them. This is clearly mentioned on Lloir's Post.Again make sure you are Using the enrc2b version of the phone..
http://forum.xda-developers.com/showthread.php?t=2510836
Click to expand...
Click to collapse
Thank You for your answer, but i've been using stable cm-10.2.1-enrc2b. So i'm not sure that is the problem, because i've been having the same signature verify fail with other custom roms...
EDIT : Apparently i can't send anything to the /sdcard , i tried to send the right original OTA RUU, for flashing it from the original recovery, still getting this verify signature failed

Bruwno said:
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
EDIT :
My actual bootloader :
Code:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OPENDSP-v33.1.0.45.1128
eMMC-boot
Aug 22 2013, 11:48:30:-1
I tried to check my version for RUU reset
Code:
c:\Fastboot>fastboot getvar version-main
version-main: 5.08.163.2
finished. total time: 0.003s]/code]
Couldnt find any .exe RUU to help.
Thanks ![/QUOTE]
[QUOTE="Bruwno, post: 50774443, member: 5754687"]Thank You for your answer, but i've been using stable cm-10.2.1-enrc2b. So i'm not sure that is the problem, because i've been having the same signature verify fail with other custom roms...
EDIT : Apparently i can't send anything to the /sdcard , i tried to send the right original OTA RUU, for flashing it from the original recovery, still getting this verify signature failed[/QUOTE]
Sorry Missed that the phone that you are using is EVITA (TelUs vesion of the phone ) and not the enrc2b (International version), Since you are trying to install the cm-10.2.1-enrc2b (International) version of the ROM it is failing .. enrc2b and EVITA are two different phones internally .They have different roms so try installing ROMS meant for EVITA(At&t) and not enrc2b .. This is kinda risky ... might just brick your phone ..
You can try this CM version on your phone
http://forum.xda-developers.com/showthread.php?t=2547118
Click to expand...
Click to collapse

ethanon said:
Sorry Missed that the phone that you are using is EVITA (TelUs vesion of the phone ) and not the enrc2b (International version), Since you are trying to install the cm-10.2.1-enrc2b (International) version of the ROM it is failing .. enrc2b and EVITA are two different phones internally .They have different roms so try installing ROMS meant for EVITA(At&t) and not enrc2b .. This is kinda risky ... might just brick your phone ..
You can try this CM version on your phone
http://forum.xda-developers.com/showthread.php?t=2547118
Click to expand...
Click to collapse
Nope, still nothing able to be uploaded got this verify signature failed error again and again...

Bruwno said:
Nope, still nothing able to be uploaded got this verify signature failed error again and again...
Click to expand...
Click to collapse
which ROM are you installing? also try installing the correct Recovery which is meant for EVITA (HOX) version and try installing the correct rom again. TRY HOX ROMS NOT HOX+ ROMS.

ethanon said:
which ROM are you installing? also try installing the correct Recovery which is meant for EVITA (At&t) version and try installing the correct rom again.
Click to expand...
Click to collapse
Well well well, i see progress down there !
I just tried something. I used the TWRP mount option to mount the sdcard, as it poped on my computer i was able to paste directly the ROMS which was unable to transfer before. I'll try EVITA CM first, after wyping data/cache. I'll let you know. This is pretty encouraging. Thanks for the reading, the ideas !

Bruwno said:
Well well well, i see progress down there !
I just tried something. I used the TWRP mount option to mount the sdcard, as it poped on my computer i was able to paste directly the ROMS which was unable to transfer before. I'll try EVITA CM first, after wyping data/cache. I'll let you know. This is pretty encouraging. Thanks for the reading, the ideas !
Click to expand...
Click to collapse
Make sure you download the HOX Roms from Cyanogenmod website and also my bad I gave you a wrong link in the previous post..

SOLVED
ethanon said:
Make sure you download the HOX Roms from Cyanogenmod website and also my bad I gave you a wrong link in the previous post..
Click to expand...
Click to collapse
After fighting hours to solve the problem, i was able to use a custom recovery to mount the sdcard and transfert it from a graphic interface. Then install it from recovery on the phone.
I still doesn't know why it wasnt transfering before, and why i got the failed verify signature using flash command in fastboot.
I'll run some simulation in order to found out why it's going this way and try to find a solution. I saw a lot of post mentionning this problem but still no solutions.
Thank you though, everything is ok now.

Bruwno said:
After fighting hours to solve the problem, i was able to use a custom recovery to mount the sdcard and transfert it from a graphic interface. Then install it from recovery on the phone.
I still doesn't know why it wasnt transfering before, and why i got the failed verify signature using flash command in fastboot.
I'll run some simulation in order to found out why it's going this way and try to find a solution. I saw a lot of post mentionning this problem but still no solutions.
Thank you though, everything is ok now.
Click to expand...
Click to collapse
For your case in particular I think it has to do with the wrong ROM selection . as you were trying to install enrc2b ROM and Recovery meant for enrc2b.

Help me Convert M8 to Developer Edition

Good Day community, I have a question to see if you can help me or someone who has already done.
I have my M8 (CID CWS_001 was originally AT & T) and I have SuperCID, I'm s-off, I have unlocked the bootloader, I installed the firmware 2.22.401.5 and TWRM 2.7.1 rom with 7.1 HD Maximus, good now my question is: I want to make the official Developer Edition version of HTC (CID BS_US002 and firmware 2.22.1540.3) the idea is to stick with OTA updates and all could help me with what I want? thank you very much to all.
the idea is that it looks as if you had bought the developer edition version and not the at & t
greetings,

the easiest way would be to run the dev edition RUU, thats what i did, just be sure to change the cid to match.

chizler said:
the easiest way would be to run the dev edition RUU, thats what i did, just be sure to change the cid to match.
Click to expand...
Click to collapse
and where I downloaded the developer edition of RUU friend?
Enviado desde mi HTC One_M8 mediante Tapatalk

the htc dev website, http://www.htcdev.com/devcenter/downloads/P00. just select what you need.

chizler said:
the htc dev website, http://www.htcdev.com/devcenter/downloads/P00. just select what you need.
Click to expand...
Click to collapse
The only file for the Developer Edition that I could find is the MR1 file, but no RUU. I have an AT&T branded M8, fully converted to GPe. Is there a way to run the MR1 to convert my current setup to the Developer Edition?

https://www.dropbox.com/s/txz5sv2r3...31A.4145.02L_release_372510_signed_2.exe?dl=0
That should be the link to it in my dropbox. just give it a min to upload.

Thanks for posting the RUU! I changed my phone's CID to BS_US002 and ran the RUU, only to get the dreaded 159 error. I find myself missing Sense, but I really don't want to revert to AT&T's bloatware-infested version and deal with their constant update delays.
I wonder If the error has something to do with the HBOOT version on the 4.4.4 GPe firmware?

Pretty sure you have to convert back to sense before you run the RUU.

Believe you are [email protected]

jsaldarriaga said:
Good Day community, I have a question to see if you can help me or someone who has already done.
I have my M8 (CID CWS_001 was originally AT & T) and I have SuperCID, I'm s-off, I have unlocked the bootloader, I installed the firmware 2.22.401.5 and TWRM 2.7.1 rom with 7.1 HD Maximus, good now my question is: I want to make the official Developer Edition version of HTC (CID BS_US002 and firmware 2.22.1540.3) the idea is to stick with OTA updates and all could help me with what I want? thank you very much to all.
the idea is that it looks as if you had bought the developer edition version and not the at & t
greetings,
Click to expand...
Click to collapse
I converted my AT&T One M8 to US unlocked version (CID: BS_US001) using the directions in the thread below:
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
This assumes you have S-OFF, and unlocked bootloader and i started with an AT&T stock rom with no root. I am not sure if that is a requirement. For this i did the AT&T RUU by installing an older stock recovery. (AT&T 4.4.3 RUU)
1. Change CID to BS_US001 - open command prompt on your computer and navigate to your fastboot folder; alternatively open the fastboot folder and hold down shift and rightclick, and select open command prompt here. turn USB debugging ON on your phone and connect it to your computer in fastboot mode (turn your phone off and while holding the VOL down button press the power button, the phone goes to bootloader mode, select the fastboot [first option] and press power button, connect the phone to computer and it should say fastboot-usb), verify connection by typing fastboot devices in cmd prompt, it should give your device code. after confirming you are connected via fastboot, type "fastboot oem writecid BS_US001" Reboot bootloader and confirm CID change by typing "fastboot getvar all" and your CID should read "BS_US001".
2. Restore developer nand - for this you will need a custom recovery like TWRP or CWM. If you already have TWRP, then please proceed. To install custom recovery, download TWRP from here. save the twrp recovery image file to your fastboot folder. put your phone in fastboot mode and connect to computer and open cmd prompt from your fastboot folder and type "fastboot flash recovery recoveryname.img", recoveryname should be exactly what the same as TWRP recovery filename. Verify TWRP installation by typing "fastboot reboot-bootloader" and selecting recovery. TWRP recovery should load. Download BS-US001 stock nand from here. At this point boot your phone normally and connect to computer. The navigate to the TWRP folder and backup folder, and paste the BS_US001 nand zip file here. Reboot to TWRP recovery and select restore and select the BS_US001 file you just copied.
3. Install Unlocked version (BS_US001) firmware which includes stock recovery - Download the unlocked version firmware from here. For installing firmware i used this thread. There are two methods however, i used the following method and is my favorite. For this it is recommended that the HT sync manager be uninstalled leaving just the HTC drivers. Place the firmware zip in the fastboot folder. Put your phone in fastboot mode and connect to computer. Open cmd prompt in your fastboot folder. Type "fastboot oem rebootRUU", phone will turnoff and a dark screen with only HTC will appear (this is the RUU mode), now type "fastboot flash zip firmware.zip" replace firmware with the actual filename of the firmware zip. You will see a green progress bar while the firmware is being flashed. I read somewhere that the flash will fail the first time so reflash the firmware a second time by typing "fastboot flash zip firmware.zip". It did fail for me the first time and installed the firmware a second time and it worked. type "fastboot reboot-bootloader" from here select option to reboot your phone normally. Once booted and connected to the internet, you will receive an OTA update notification for 4.4.3. After installing that, another OTA for GPS improvements will appear.
This worked for me. If you are stuck at some point, please read through the original threads. Especially the firware installation thread has a nice FAQ. Goodluck. Please remember, you can not install an OTA while you have a custom recovery. Please wait until you install the firmware zip for accepting the OTA. If the firmware does not install fro some reason, you can pull the stock recovery from the firmware zip and install this recovery using fastboot. Then you can accept the OTAs.
Let me know how it goes.

Converting back to Sense from GPe prior to running the RUU is what I was afraid of. Oh well, I guess I'll have to set aside a couple of hours this weekend. Thanks for the clarification, guys!

here is a link to show you how to do it, once you have all the files it doesnt take 10 mins. i have done it at least 3 times without a problem.
http://forum.xda-developers.com/showthread.php?t=2733523

chizler said:
here is a link to show you how to do it, once you have all the files it doesnt take 10 mins. i have done it at least 3 times without a problem.
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
It worked like a charm. I'm now running a full DevEd. Thanks for all your help!

Glad it worked for you.

This was my first full day running the phone since I converted to DevEd and the first thing I've noticed is that the battery life is through the roof. With moderately heavy usage, I currently have about 40% of battery life left. The phone would have been dead by 6 pm when I was running GPe.

Some Help Please!
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!

lsv-1 said:
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
Click to expand...
Click to collapse
I'm having the same problem. I want to convert to Developer edition using a RUU, but none of the Windows 7 machines I can find will run the exe file properly. It's so incredibly frustrating for me! All I need is a working ZIP that doesn't give me the 32 header error

lsv-1 said:
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
Click to expand...
Click to collapse
If you are GPe converted then to need to follow the instructions here to go back to Sense.
http://forum.xda-developers.com/showthread.php?t=2733523
Sent from my HTC One_M8 using Tapatalk

[Q] Phone unlocked but Fastboot will not flash recovery

Hello all, I recently started the process of rooting my HTC One X+ and it all went smoothly until it came time to flash a recovery.
I used Windroid Universal toolkit to get started, thinking it would make things easier (not that I haven't rooted a phone before).
I unlocked the bootloader just fine, in the bootloader it gives "*unlocked*".
Next, I tried flashing TWRP with the toolkit, it brings me to bootloader, but when going to HBOOT and hitting recovery, it just brings me back to bootloader. Hmm, weird. So I decide to do it manually, download latest TWRP for evitareul (2.8.5.0), reboot into fastboot.
Execute: fastboot flash recovery twrp-2.8.5.0-evitareul.img
and it gives me this:
"sending 'recovery' (8224 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 1.153s"
I don't know whether it matters, but when going into HBOOT it pops up with some errors saying something along the lines of unable to access SD or something. It goes too fast to really write it down.
So I think maybe deleting cache would help, and to no avail. I look up online for the error code and nobody seems to have an answer for it. I apologize if this has been answered elsewhere on the forums, I looked for quite some time before posting a new thread. I'm not sure what is going wrong.
My end goal was to flash recovery, make a back up, then flash superSU but if I can't flash recovery then I'm not going to do anything else and risk a brick.
Does anyone know what's up with this error and how to fix it?

You're flashing a wrong recovery.

Coolgoly said:
You're flashing a wrong recovery.
Click to expand...
Click to collapse
What recovery should I be flashing then? My device is Evitare_UL, and I am getting img files from
HTML:
https://dl.twrp.me/evitareul/
.
I have tried other versions to no avail.

Evitareul should only have 2.5 TWRP out....

Better Mobile App

welcome