Hello,
maybe this will help a few user's of Vodafone branded Desire X who want to receive OTA again.
This is tested and known to work with CID VODAP102
and may work for other VODAP CID's (UK) as the OTA Package said Vodafone UK
Steps by step:
1. Copy the TWRP Folder on your SD card
2. Flash TWRP if not flashed already
3. restore the backup named "B"
4. flash the boot.img via fastboot as recovery
5. flash the recovery_signed.img via fastboot as recovery
6. fastboot oem lock
7. cross fingers and reboot
Download: http://d-h.st/9wj
Hit the Thanks button if it helped
Jann F said:
Hello,
maybe this will help a few user's of Vodafone branded Desire X who want to receive OTA again.
This is tested and known to work with CID VODAP102
and may work for other VODAP CID's (UK) as the OTA Package said Vodafone UK
Steps by step:
1. Copy the TWRP Folder on your SD card
2. Flash TWRP if not flashed already
3. restore the backup named "B"
4. flash the boot.img via fastboot as recovery
5. flash the recovery_signed.img via fastboot as recovery
6. fastboot oem lock
7. cross fingers and reboot
Download: http://d-h.st/9wj
Hit the Thanks button if it helped
Click to expand...
Click to collapse
Can I just thank you again for this! I'm currently downloading the older OTA updates but soon I'll be on JB. I do not think it is necessary to relock the bootloader as I tried locking it then unlocking it again and I'm doing OTAs absolutely fine Cheers man
I think OTA's that will do more than change the system partition will require a locked bootloader
that's probably true, because i'm on 1.26.161.1 and it's refusing me OTA, going to have to lock bootloader
EDIT: Hmmm still being told my phone is up to date, suppose there's an issue with the ROM having VODAP102 and me having VODAP001?
Nope, Vodafone just hasn't branded the JB OTA yet, so we have to wait
If you received the update to 1.26 , the OTA should work normally when our JB OTA will come out...
Jann F said:
Nope, Vodafone just hasn't branded the JB OTA yet, so we have to wait
If you received the update to 1.26 , the OTA should work normally when our JB OTA will come out...
Click to expand...
Click to collapse
OHHH
I assumed you'd received it x_x I'm so so stupid,
Thanks for letting me know Well I'll set up camp on stock and just wait, that's given me hope
I'm sure it won't be long
Pff I wont wait for Vodafone, IÄm currently trying to get my cm9 built to boot
Jann F said:
Pff I wont wait for Vodafone, IÄm currently trying to get my cm9 built to boot
Click to expand...
Click to collapse
If you want I'll let you know when it comes out, I'll wait as long as it takes
hcdav said:
If you want I'll let you know when it comes out, I'll wait as long as it takes
Click to expand...
Click to collapse
oh can you inform me too pls?
Uhm, do you even read thread replys?
As I've written in the other thread, it was released today...
I have done all these things....
but now my phone only boots into the bootloader... nothing more...
Help please
Are you CID VODAP102/VODAP001?
yes, VODAP102
TheGreenSephiroth said:
yes, VODAP102
Click to expand...
Click to collapse
Follow these instructions as follows:
1) Extract B folder from that VODAP102 ZIP
2) Copy that B folder (somewhere inside the ZIP) to SDCARD\TWRP\BACKUPS\[SERIALNO]\
3) Boot into TWRP recovery, restore that nandroid.
4) Reboot to fastboot
5) Fastboot flash boot boot.img
(The boot.img from the VODAP102 ZIP must be with your fastboot files)
6) Fastboot flash recovery recovery_signed.img
(Must be the recovery_signed.img from the VODAP102 ZIP)
7) Boot into the phone, install the small incremental update.
8) Wait for it to reboot to stock recovery and do its thing.
9) When finished, check for updates and start downloading JB.
If you follow these instructions religiously, you won't have any problems.
I will create a update package for you in the next days to upgrade to 1.25 hboot and restore my new JB backup directly, but I got a lot theater stuff to do, I have to do all lightning things etc, so it will take till monday or so.
Haha, you wouldn't believe me what the problem was
Everyone said I have to lock my bootloader, so I did... Than I had always this boot problems...
So I tried different things...
I unlocked my bootloader again, and tried to reboot... And... Voila.. My DX was booting and also the update was no problem with the unlocked bootloader
Sent from my HTC Desire X using xda app-developers app
Hi all,
i tried every single step as told in the description. But my restore failed every time. Anyone knows what to do?
HTC Desire X - VODAP102
As I already told you... You can't restore an ICS backup on JB bootloader. Please tell us exactly what you have done, every single step starting from when you got your phone.
Do you have a JB hboot?
Maybe I can upload my old JB backup in the next days...
That'll be great to have. If you have hosting problems, I can load it up too when you give it to me.
Related
....
Thanks!
Step 2 is not possible, file is only available with login because too big...
Yezariael said:
Thanks!
Step 2 is not possible, file is only available with login because too big...
Click to expand...
Click to collapse
We need to have someone to upload the RUU somewhere else.
I can't as my server is already crowded :cyclops:
Will see if I can find a public and free hosting
Steve0007 said:
We need to have someone to upload the RUU somewhere else.
I can't as my server is already crowded :cyclops:
Will see if I can find a public and free hosting
Click to expand...
Click to collapse
Or split the package for free users, it's only a problem because it is in one package with more than 500 MB...
Steve0007 said:
We need to have someone to upload the RUU somewhere else.
I can't as my server is already crowded :cyclops:
Will see if I can find a public and free hosting
Click to expand...
Click to collapse
actually you don't need the whole ruu,
you only need the firmware.zip from here http://d-h.st/btN to update the hboot to 1.35
how you do it?
Here is the tutorial for ONE X .
http://forum.xda-developers.com/showthread.php?t=1920060
its the same drill for X+
long story short, you relock your bootloader, probably after this the phone will power up here you have 2 choices
1. wait for it to power up, enable usb debugging in settings, connect phone to pc, open cmd / terminal : adb reboot oem-78
OR to save time or in case for some reason your phone doesn't bootup there is variant 2.
2. force it to bootloader by holding vol-down and power button then w/ phone in fastboot and connect to pc from a terminal / cmd type: fastboot oem rebootRUU
then flash the firmware TWICE:
fastboot flash zip firmware.zip.
unlock your bootloader, flash recovery, flash ur custom rom 1.16 base boot.img, boot to recovery flash rom, profit.
!!!FINAL WARNINGS!!!
BE AWARE, doing so will wipe ALL YOU SDCARD DATA. again if you are not comfy with the procedure i suggest you don't attempt it, because 1.16 roms works just fine with old hboot
ALSO is best to have your phone ruu handy in case things go south and you end up with a nonbooting phone.
CID Restriction apply here too!
P.S. http://d-h.st/bYP the RUU without any restrictions, hosted on dev-host
Yep, for sure but I think it is much easier for users to just run the required RUU than flashing the firmware by fastboot + they can't go bad this way
baadnewz said:
actually you don't need the whole ruu,
you only need the firmware.zip from here http://d-h.st/btN to update the hboot to 1.35
how you do it?
Here is the tutorial for ONE X .
http://forum.xda-developers.com/showthread.php?t=1920060
its the same drill for X+
long story short, you relock your bootloader, probably after this the phone will power up here you have 2 choices
1. wait for it to power up, enable usb debugging in settings, connect phone to pc, open cmd / terminal : adb reboot oem-78
OR to save time or in case for some reason your phone doesn't bootup there is variant 2.
2. force it to bootloader by holding vol-down and power button then w/ phone in fastboot and connect to pc from a terminal / cmd type: fastboot oem rebootRUU
then flash the firmware TWICE:
fastboot flash zip firmware.zip.
unlock your bootloader, flash recovery, flash ur custom rom 1.16 base boot.img, boot to recovery flash rom, profit.
!!!FINAL WARNINGS!!!
BE AWARE, doing so will wipe ALL YOU SDCARD DATA. again if you are not comfy with the procedure i suggest you don't attempt it, because 1.16 roms works just fine with old hboot
ALSO is best to have your phone ruu handy in case things go south and you end up with a nonbooting phone.
CID Restriction apply here too!
P.S. http://d-h.st/bYP the RUU without any restrictions, hosted on dev-host
Click to expand...
Click to collapse
Steve0007 do you know if new hboot fixed issue with missing .apks after unlocking device via htc dev?
I don't know. Maybe one user upgrading his hboot and running Stock Rom with unlocked bootloader will let us know here
mike1986. said:
Steve0007 do you know if new hboot fixed issue with missing .apks after unlocking device via htc dev?
Click to expand...
Click to collapse
Steve0007 said:
I don't know. Maybe one user upgrading his hboot and running Stock Rom with unlocked bootloader will let us know here
Click to expand...
Click to collapse
Would be nice! Missing stock apps after unlocking is really frustrating. Hopefully new hboot is the way to fix it! From the other side I'm wondering how it's possible that HTC would release OTA update that removes content of virtual sd card
just a question, is it possible to revert to the old HBOOT after?
I don't think you can downgrade afterwards.
But what would be the purpose of downgrading the Hboot (since we have the official RUU for 1.16.401.6) ?
yosscal said:
just a question, is it possible to revert to the old HBOOT after?
Click to expand...
Click to collapse
Well finally i got my HTC One X + today and was searching a backup STOCK Rom online for the
baseband : 3.1024.168.32
Software number : 1.17.707.2
4.1.1 and sense 4+
Well here is the link for latest RUU, i havent check though. you guys can check it up ... its for Asia India
Includes all the Updates till june 2013
mod edit: removed
Please let me know if its working properly. :fingers-crossed:
Hit thanks if i had helped you.
and m working on HTC One Google Play edition and HTC One SENSE5 edition. will port it up and report back soon. Its a comback back soo many months. Feeling good ! :angel:
neelgangrade said:
Well finally i got my HTC One X + today and was searching a backup STOCK Rom online for the
baseband : 3.1024.168.32
Software number : 1.17.707.2
4.1.1 and sense 4+
Well here is the link for latest RUU, i havent check though. you guys can check it up ... its for Asia India
Includes all the Updates till june 2013
mod edit: removed
Please let me know if its working properly. :fingers-crossed:
Hit thanks if i had helped you.
and m working on HTC One Google Play edition and HTC One SENSE5 edition. will port it up and report back soon. Its a comback back soo many months. Feeling good ! :angel:
Click to expand...
Click to collapse
wow thx for the effort but it is the 1.17.707.1....not 2.....
4shared is not allowed as a file host, so link removed. OP please check your PM
pandaball said:
4shared is not allowed as a file host, so link removed. OP please check your PM
Click to expand...
Click to collapse
You forgot a link inside the quote
neelgangrade said:
Well finally i got my HTC One X + today and was searching a backup STOCK Rom online for the
baseband : 3.1024.168.32
Software number : 1.17.707.2
4.1.1 and sense 4+
Well here is the link for latest RUU, i havent check though. you guys can check it up ... its for Asia India
Includes all the Updates till june 2013
mod edit: removed
Please let me know if its working properly. :fingers-crossed:
Hit thanks if i had helped you.
and m working on HTC One Google Play edition and HTC One SENSE5 edition. will port it up and report back soon. Its a comback back soo many months. Feeling good ! :angel:
Click to expand...
Click to collapse
Does it work for hboot 1.4?
If it does, can you please pm me the link?
Hey can you please PM me the link too? I have been searching for this for days.
send it asap, Its urgent! Thanks in advance!
By the file name , it seems same as the one in whiskey's thread..
Sent from my GT-I9300 using xda premium
i really dont know what u r talking about ! but even if u want this one ...u can PM me ! will provide u the lik for that ! coz net speed is too slow to upload a large 690 mb file !
neelgangrade said:
i really dont know what u r talking about ! but even if u want this one ...u can PM me ! will provide u the lik for that ! coz net speed is too slow to upload a large 690 mb file !
Click to expand...
Click to collapse
What I meant is the ROM link you shared me with is already available on this thread :
http://forum.xda-developers.com/showthread.php?t=2094118
And unfortunately it does not work on hboot 1.4...
Addicted2xda said:
What I meant is the ROM link you shared me with is already available on this thread :
http://forum.xda-developers.com/showthread.php?t=2094118
And unfortunately it does not work on hboot 1.4...
Click to expand...
Click to collapse
Quick question bro..........I have taken the backup of the stock after unlocking the bootloader....
By doing that anyways i wouldn't be getting OTA updates right...........?????:fingers-crossed:
Danny Samuel said:
Quick question bro..........I have taken the backup of the stock after unlocking the bootloader....
By doing that anyways i wouldn't be getting OTA updates right...........?????:fingers-crossed:
Click to expand...
Click to collapse
I guess so
Any update after 1.17.707.2 ?
tufel said:
Any update after 1.17.707.2 ?
Click to expand...
Click to collapse
no
Addicted2xda said:
What I meant is the ROM link you shared me with is already available on this thread :
http://forum.xda-developers.com/showthread.php?t=2094118
And unfortunately it does not work on hboot 1.4...
Click to expand...
Click to collapse
No that one was not available over there .... thats an old version ! the link i had provided is of the latest RUU !
RUU ENRC2B U JB 45 hTC Asia WWE 1.17.707.1 Radio 3.1204.168.32 release 299722 signed.exe
its the latest one available out their !
its just a plain text... for link u have to PM me !
Danny Samuel said:
Quick question bro..........I have taken the backup of the stock after unlocking the bootloader....
By doing that anyways i wouldn't be getting OTA updates right...........?????:fingers-crossed:
Click to expand...
Click to collapse
once u r rooted ...u no longer will get OTA ! so better get back to stock ...sense 5 on it way this august ! :angel:
Danny Samuel said:
Quick question bro..........I have taken the backup of the stock after unlocking the bootloader....
By doing that anyways i wouldn't be getting OTA updates right...........?????:fingers-crossed:
Click to expand...
Click to collapse
Do you really care about OTA and Official Sense 5? :silly:
Addicted2xda said:
Do you really care about OTA and Official Sense 5? :silly:
Click to expand...
Click to collapse
NOOOO Not at All concerned........:laugh::laugh::laugh:
Help
Addicted2xda said:
What I meant is the ROM link you shared me with is already available on this thread :
http://forum.xda-developers.com/showthread.php?t=2094118
And unfortunately it does not work on hboot 1.4...
Click to expand...
Click to collapse
Hello,
I have the same problem. I tried rooting my phone and was successful upto the stage of flashing the CMW recovery and the SuperSU. When I used fastboot and flashed the boot image of the ROM i downloaded, installed the ROM & the Gapps ([ROM][OFFICIAL] 14/7/13 HTC OneX+ INTER CM10.1.1 stable) Something went wrong, not sure what, and it kept getting stuck on the initial screen where I see the CyanogenMod circular annimation. Does not move further at all. Any help on how I can resolve this? I did not flash a separate kernel only installed the ROM after flashing its boot.img via fastboot (using CMD) do you think flashing the BLADE kernel will resolve this?
Anyways...
Right now my battery is almost dead so I cannot flash anything and the phone is stuck on the fastboot screen. I am not sure if the battery charging but I have connected the phone to the charger plugged into a power socket. I have flashed the stock recovery and loacked bootloader, I tried to go back to stock using the RUU file mentioned in the below link. But it failed since i had 1.17.401.2. and the RUU was the 1.17.401.1 version.
Can anyone help me with the following:
1. Can I still flash the CyanogenMod ROM that I have on the phones SD card along with the Gapps and get back normal functionality?
2. Since I have locked the bootloader and flased the stock recovery should I wait for the RRU with the 1.17.401.2 to come up and then run RUU?
oceans2seas said:
Hello,
I have the same problem. I tried rooting my phone and was successful upto the stage of flashing the CMW recovery and the SuperSU. When I used fastboot and flashed the boot image of the ROM i downloaded, installed the ROM & the Gapps ([ROM][OFFICIAL] 14/7/13 HTC OneX+ INTER CM10.1.1 stable) Something went wrong, not sure what, and it kept getting stuck on the initial screen where I see the CyanogenMod circular annimation. Does not move further at all. Any help on how I can resolve this? I did not flash a separate kernel only installed the ROM after flashing its boot.img via fastboot (using CMD) do you think flashing the BLADE kernel will resolve this?
Anyways...
Right now my battery is almost dead so I cannot flash anything and the phone is stuck on the fastboot screen. I am not sure if the battery charging but I have connected the phone to the charger plugged into a power socket. I have flashed the stock recovery and loacked bootloader, I tried to go back to stock using the RUU file mentioned in the below link. But it failed since i had 1.17.401.2. and the RUU was the 1.17.401.1 version.
Can anyone help me with the following:
1. Can I still flash the CyanogenMod ROM that I have on the phones SD card along with the Gapps and get back normal functionality?
2. Since I have locked the bootloader and flased the stock recovery should I wait for the RRU with the 1.17.401.2 to come up and then run RUU?
Click to expand...
Click to collapse
Hi, Dude
There is no trouble do the following
1. The RUU wont work if u have the HBOOT as 1.40 so don't try that it of no use.
2. For ur problem to get sorted unlock ur bootloader and flash TWRP recovery from fastboot (once u have done this if the charge is too low Go into recovery and connect the phone to AC power not the usb and charge it at least to 70%)
3. after the phone is charged enough connect the phone into PC when in recovery mode
4. type "adb devices" it will show ur phones serial number and as in recovery(if ur not able to see the phone in recovery uninstall the drivers and
reinstall it again and try a reboot)
5. now do "adb shell" it will enter ur phone storage
6. type "mkdir /sdcard/0"
6. I recommend u going to CM10.1 itself since u have that with u so do "adb push ROM.zip /sdcard/0" and "adb push gapps.zip /sdcard/0"
7. Now go to install and navigate to sdcard>0 and there u will find the files u had copied through adb push
8. flash it.
9. In PC extract the boot.img alone from the CM10.1 to the fastboot folder
9. boot in bootloader and flash the boot.img using the "fastboot flash boot boot.img" and also do "fastboot erase cache"
10.now reboot the phone it ll work for sure if u have done all the mentioned above properly.
Hope it helps :good:
Hi
[email protected] said:
Hi, Dude
There is no trouble do the following
1. The RUU wont work if u have the HBOOT as 1.40 so don't try that it of no use.
2. For ur problem to get sorted unlock ur bootloader and flash TWRP recovery from fastboot (once u have done this if the charge is too low Go into recovery and connect the phone to AC power not the usb and charge it at least to 70%)
3. after the phone is charged enough connect the phone into PC when in recovery mode
4. type "adb devices" it will show ur phones serial number and as in recovery(if ur not able to see the phone in recovery uninstall the drivers and
reinstall it again and try a reboot)
5. now do "adb shell" it will enter ur phone storage
6. type "mkdir /sdcard/0"
6. I recommend u going to CM10.1 itself since u have that with u so do "adb push ROM.zip /sdcard/0" and "adb push gapps.zip /sdcard/0"
7. Now go to install and navigate to sdcard>0 and there u will find the files u had copied through adb push
8. flash it.
9. In PC extract the boot.img alone from the CM10.1 to the fastboot folder
9. boot in bootloader and flash the boot.img using the "fastboot flash boot boot.img" and also do "fastboot erase cache"
10.now reboot the phone it ll work for sure if u have done all the mentioned above properly.
Hope it helps :good:
Click to expand...
Click to collapse
Thank you for your revert.
I will try this method once TWRP has been downloaded. Can you suggest a link for this? Sorry I am trying to be really cautious with everything I do from now on.
When you say type adb XXX from points 4 to 6 you mean that I should open the CMD and type? If i am right then do I have to go all the way down to fastboot (as in C:\fastboot) ? or is there something else I need to do?
Really appreciate the time you have spent on this
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Wonders_Never_Cease said:
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Click to expand...
Click to collapse
Thanks! I hope I can extract the firmware.zip out of this and RUU mode flash it on my Dev. I only want the updated firmware.
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Wonders_Never_Cease said:
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Click to expand...
Click to collapse
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
guyd said:
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
Click to expand...
Click to collapse
Are you not super cid? When you say hard bricked what is your m8 doing now? Can you get to bootloader. You can't even flash unless you are soff or have true developer edition phone so I would assume you made your phone super cid too?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Wonders_Never_Cease said:
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
Click to expand...
Click to collapse
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
an0ther said:
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in
Click to expand...
Click to collapse
Tried those like fifty times! My device is is bricked harder than a diamond...
Wish I knew what exactly happened so I don't do it again. As I said in my previous post, I've done this same thing on my M7 several times without a hitch. Only difference I saw this time was that the RUU flash routine didn't stop after flashing the hboot like it did on my M7 and make me run it one more time to get the rest of the firmware flashed. To be sure I got it all, I flashed it a second time anyway. That was the only difference I saw!
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
Wonders_Never_Cease said:
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
Click to expand...
Click to collapse
I've ran the RUU flash command on my M7 with a custom recovery several times without incident. Didn't see why it would be any different on the M8, but something is. Wish I would have had an MD5 to verify my download, but it extracted fine so I think it was good.
Only one thing I found that was different from the M7 to the M8.
In the M7 it used hbootpreupdate:3
In the M8 it used hbootpreupdate:12
Wish I knew what this does different.
how did you remove the boot and recovery out of zip? Mine says corrupted when i try to unzip which usually means its encrypted. If you just manually zipped it back up that could be the problem. I don't know what happened and am interested to figure out. At least it is just dead and htc should swap it out no problem.
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Wonders_Never_Cease said:
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
Click to expand...
Click to collapse
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
I would suggest you make your phone super cid before you do any flashing.
Hes already running my rom....Not needed,using brightstar cid works fine as att and developer builds are same mid
an0ther said:
I would suggest you make your phone super cid before you do any flashing.
Click to expand...
Click to collapse
Ill send you a link in the a.m.,lol
skhullar said:
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Click to expand...
Click to collapse
Link and instructions sent...Enjoy
Thank You!
Wonders_Never_Cease said:
Link and instructions sent...Enjoy
Click to expand...
Click to collapse
So no definite way to convert to Dev Edition then I'm guessing, right?
HTC has halted this firmware due to battery drain. I'm sure another firmware will be out in a week or two. I'm sure if you just flash a rom afterwards there will be no battery drain, its probably just something in the software. This firmware will let you flash all of the "newer 2.**" international roms such as Viper etc.. properly with new sound drivers.
Confirmed working first by "italyforever" - I could not test myself since I sold my M8, just wanted to help others out. Confirmed working by several other members too.
At&t 2.23.502.3 Ruu has just come out and I have had requests for bootable RUU. Here it is first from me! Place this file in the root of your ext sd card and boot to hboot and hit vol up to update. If you are soff you do not have to lock boot loader. If you are s-on you must lock boot loader first. Please follow my guide for the 1.58 bootable RUU for any questions. It explains everything. Do not try to modify file as it is singed and encrypted by HTC and will cause issues if you mess with it. If you try to unzip it, it will say corrupt because this is an encrypted file. Just verify md5 to make sure your file is good. The restore takes 14-17 minutes. Plugging in phone is a good idea so there is no chance of battery dying. It will do a bunch of different unzipping and installing. It will bypass certain things too, this is normal. Let the update finish. It will say update complete press button to reboot. Do not touch phone during this process! This is ONLY for the at&t M8, no other variant. CWS__001 or 11111111 cid required. This will erase your phone like new so backup anything needed. I am NOT responsible for anything that happens! Please click my thanks button if I helped you.
2.23.502.3 bootable RUU - https://www.androidfilehost.com/?fid=23622183712463537
Old guide - http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Has anyone tested this? I get my M8 hopefully by Saturday and hoping to run this RUU as soon as I get it.
italyforever said:
I needed to go back to stock this morning, i used this. worked perfectly, thanks:laugh:
Click to expand...
Click to collapse
Does this re-enable S-On or would you still have to do that manually?
K.AuthoR said:
Does this re-enable S-On or would you still have to do that manually?
Click to expand...
Click to collapse
No. This will not touch bootloader or security. Never go s-on.
This will give me stock recovery?
snoopy1e11 said:
This will give me stock recovery?
Click to expand...
Click to collapse
Yes it should
an0ther said:
HTC has halted this firmware due to battery drain. I'm sure another firmware will be out in a day or two.
Confirmed working by "italyforever" - I could not test myself since I sold my M8, just wanted to help others out.
At&t 2.23.502.3 Ruu has just come out and I have had requests for bootable RUU. Here it is first from me! Place this file in the root of your ext sd card and boot to hboot and hit vol up to update. If you are soff you do not have to lock boot loader. If you are s-on you must lock boot loader first. Please follow my guide for the 1.58 bootable RUU for any questions. It explains everything. Do not try to modify file as it is singed and encrypted by HTC and will cause issues if you mess with it. This is ONLY for the at&t M8, no other variant. CWS__001 or 11111111 cid required. This will erase your phone like new so backup anything needed. I am NOT responsible for anything that happens! Please click my thanks button if I helped you.
2.23.502.3 bootable RUU - https://www.androidfilehost.com/?fid=23622183712463537
Old guide - http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Click to expand...
Click to collapse
the file is broken i downloaded twice and both time got a corrupted file
JEANRIVERA said:
the file is broken i downloaded twice and both time got a corrupted file
Click to expand...
Click to collapse
Are you trying to unzip it? I have had multiple people tell me it works great. You cannot unzip an encrypted file, it will say corrupt. This is noted in OP.
an0ther said:
Are you trying to unzip it? I have had multiple people tell me it works great. You cannot unzip an encrypted file, it will say corrupt. This is noted in OP.
Click to expand...
Click to collapse
no one here has said that this work that's why i asked
JEANRIVERA said:
no one here has said that this work that's why i asked
Click to expand...
Click to collapse
Just finished restoring right now.
I came from Viper 2.2x, TWRP, and I re-locked bootloader before starting this RUU. I have never done S-OFF, so I was S-ON when I did this.
Reverted phone to 100% stock, no issues. re-unlocked bootloader and flashed viper again. Perfect.
Just used this to update from `1.58 since I couldn't OTA. Works perfectly! I was worried at one point when it kept unzipping and updating the system over and over, but after about the fifth time it finished. Thanks again!
Blaze9 said:
Just finished restoring right now.
I came from Viper 2.2x, TWRP, and I re-locked bootloader before starting this RUU. I have never done S-OFF, so I was S-ON when I did this.
Reverted phone to 100% stock, no issues. re-unlocked bootloader and flashed viper again. Perfect.
Click to expand...
Click to collapse
I am glad it worked for you. It is really nice when people like you read the instructions and you knew to lock your boot loader since you are s-on.
akitten007 said:
Just used this to update from `1.58 since I couldn't OTA. Works perfectly! I was worried at one point when it kept unzipping and updating the system over and over, but after about the fifth time it finished. Thanks again!
Click to expand...
Click to collapse
I am glad it worked for you. I added to the OP that it takes about 14-17 minutes and there is a bunch of unzipping, flashing, and bypasses so other people don't get worried and try to power off their phone. This is also a nice file to just leave on your ext sd card in case you need a restore on the go. If booting to recovery, you can just press vol down to decline the update whenever you go to hboot.
snoopy1e11 said:
This will give me stock recovery?
Click to expand...
Click to collapse
Yes, this will make your phone completely stock except it does not mess with boot loader or security "s-on / s-off"
Thanks. Worked
I need to update my base. Flashed and worked perfectly... I'm s-off and unlocked... So after flashing just fastboot recovery and flash new rom... = win! Thanks
Sent from my iPad using Tapatalk
an0ther said:
HTC has halted this firmware due to battery drain. I'm sure another firmware will be out in a week or two. I'm sure if you just flash a rom afterwards there will be no battery drain, its probably just something in the software. This firmware will let you flash all of the "newer 2.**" international roms such as Viper etc.. properly with new sound drivers.
Confirmed working first by "italyforever" - I could not test myself since I sold my M8, just wanted to help others out. Confirmed working by several other members too.
At&t 2.23.502.3 Ruu has just come out and I have had requests for bootable RUU. Here it is first from me! Place this file in the root of your ext sd card and boot to hboot and hit vol up to update. If you are soff you do not have to lock boot loader. If you are s-on you must lock boot loader first. Please follow my guide for the 1.58 bootable RUU for any questions. It explains everything. Do not try to modify file as it is singed and encrypted by HTC and will cause issues if you mess with it. If you try to unzip it, it will say corrupt because this is an encrypted file. Just verify md5 to make sure your file is good. The restore takes 14-17 minutes. Plugging in phone is a good idea so there is no chance of battery dying. It will do a bunch of different unzipping and installing. It will bypass certain things too, this is normal. Let the update finish. It will say update complete press button to reboot. Do not touch phone during this process! This is ONLY for the at&t M8, no other variant. CWS__001 or 11111111 cid required. This will erase your phone like new so backup anything needed. I am NOT responsible for anything that happens! Please click my thanks button if I helped you.
2.23.502.3 bootable RUU - https://www.androidfilehost.com/?fid=23622183712463537
Old guide - http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Click to expand...
Click to collapse
thank you so much! I've been trying to update my firmware for awhile. AT&T wouldn't let me update when they said I had an update and then it kept saying that I was up to date. Now I can enjoy viper Rom. You're the best!
.
Downloaded multiple times and keep getting a corrupted file
Don't unzip it
.
I'm not
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.