Related
I've been trying to reset my HOX to stock for OTA JB update, but it keeps going into boot loops in which the only solution is to hold down the vol_down to go into bootloader.
I've been following vladnosferatu's method 2:
Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)
Extract boot.img, system.img, signed_recovery.img from rom.zip
Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot erase cache
-fastboot oem lock
Power on the phone
Run the RUU exe file (of your CID) and upgrade your phone
Click to expand...
Click to collapse
the bootloops start after oem lock.
I tried ClydeB1's noob-friendly method first, but it won't work since I'm already on 2.xxxxxxxx, and it refuses to downgrade to 1.xxxxxxxx
and I was on Renovate rom before this.
I have reset to Stock from Renovate once before, but now I can't seem to do it again. I have adb, fastboot and RUU(and extracted rom.zip)
What should I do? I've considered re-flashing CWM, flashing a Renovate again and restart the entire process, but I would like to confirm whether it would work first.
Thanks in advance for all responses!
UPDATE: I have just realised that there are 2.14 and 2.17 RUUs for my .707. I am now downloading those and trying if re-applying the steps using the updated RUUs will work.
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.
donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
Because I have done this before perfectly fine, so I didn't expect anything to go wrong. I'd be sure to do it next time.
Seelendrache said:
if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.
Click to expand...
Click to collapse
My hboot is 2.x, but it's not even the JB hboot of 3.x. I have been able to flash ROMs just fine on 2.x, so why can't I revert to stock? The 2.x hboot is obtained from stock OTA in the first place, too.
Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------
donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
What are you doing here, Don ? Change phone ?
ckpv5 said:
Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
Click to expand...
Click to collapse
Hi ckpv5, I have also noticed that the 3.14.707 and 3.17.707 RUU has been uploaded. Can I just RUU the 3.17.707, skipping the manual 2.17.707? Because the only reason why I'm reverting to stock, is to update my hboot to 3.x, so that I can flash JB ROMs. Bypassing the 2.17-3.17 OTA would save quite some time.
Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.
-- question deleted cause I saw some numbers wrongly that caused confusion =/ --
Hehe no ....just got bored from the one v forums ...nothing new happening :thumbdown:
ckpv5 said:
Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Unfortunately this doesn't seem to work. The 3.14 gives me an error saying something about finding the right RUU for my device. Now downloading 2.17.707. Man htcruu downloads keep timing out halfway and I have to restart over and over :crying:
UPDATE: Yeah so it seems I had to RUU 2.17, and manually get 3.14 from OTA in order to upgrade. Can't skip that step.
Hi, I'm heading back to stock JB Sense from the original JB Maximus rom (which worked very well). I relocked in fastboot and went to flash original RUU (3.14.401.31) and I got the error message to use the correct RUU. My cid is HTC__001, it's from Clove UK. Do I need to change the HBOOT? It's from the first Maximus JB rom. It's just booting to the bootloader now. Thanks for any help!
Do this:
fastboot getvar version-main
and post the result here...
vin4yak said:
Do this:
fastboot getvar version-main
and post the result here...
Click to expand...
Click to collapse
3.09.401.100
Thanks very much!
Firs you need to update your firmware to 3.14.401.31 with Hboot 1.39..
Download (firmware): http://www.androidrevolution.nl/downloader/download.php?file=3.14.401.31.zip
And then run this RUU:
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Hi, thanks very much, that was the RUU I used but I'll try with that firmware and report back. Cheers for the prompt help!!
Hi, I've downloaded the firmware a few times but when I try to flash it I'm getting "cannot determine image filename for 'firmware.zip'
I moved the firmware download to my fastboot folder and renamed it firmware.zip. Then I did "fastboot flash firmware.zip" < EDIT YEP THAT was the problem
Thanks again!
Honestly at this point I'd just even go back to Maximus 4.1 at this point, but those threads all disappeared.
EDIT: I got the firmware updated, now going for the RUU
Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger
Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Click to expand...
Click to collapse
That's what I got the first time I tried to run the RUU, before flashing the new firmware. You may need firmware with a higher HBOOT to use this JB RUU. Once I flashed the firmware above, the RUU in this thread worked fine. I'm having some flashing now but heck, I had that when my phone was stock when I first got it, heh. I remember that issue now!
otarinz said:
Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.
Click to expand...
Click to collapse
Glad you sorted it out mate!
if you had just gone to stock to update... Then I will recommend you to use a custom sense rom if your attached to sense that much!
Use ViperX... It needs Hboot 1.31 at least..
Steps for flashing are the same as any other rom...
1. Wipe Data..Wipe Cache...Wipe Dalvic Cache... Or use Super Wipe Script(Recommended) : https://www.dropbox.com/s/0y31poo1kiaif4y/Super wipe script.zip
2. Flash rom. Flash Patch. (Check ViperX Thread)
3. Reboot.
Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger
Click to expand...
Click to collapse
You first have to update your firmware... Download this : http://goo.gl/M0hLq
and then run the ruu...
Hey there,
it sounds as if the HBOOT is in fact my problem. Quick question: How exactly did you flash the firmware, especially the HBOOT? I flashed the boot.img and recovery.img via command since I have no SD card access, but this doesn't seem to have changed the HBOOT.
Thanks again
Froschfinger
Relock the bootloader:
"fastboot oem lock"
Reboot RUU:
"fastboot oem rebootRUU"
Flash the firmware:
fastboot flash zip firmware.zip
You might get an error the first time you do it... try again until you get a successful message.
After successful flashing...
Go to fastboot again,,,
Now if you want to install a custom rom, you need to flash custom recovery by unlocking the bootloader... or if you want to go full stock then run the RUU...
Hey vin4yak,
that was the missing piece in the puzzle. Flashing the whole .zip file. Finally I got it working - thank you so much!!!!
All the best
Froscher
Hello all,
The name of this post says it all really, I am trying to update to Hboot 1.72 but I have no idea how This may be difficult as I have a new computer, and don't have any of the old folder I used to do this before so I will have to start from scratch again I have the Android SDK, so I can take any files needed from there, but apart from that I literally have nothing. Also, I am a complete novice with all this stuff so you may need to "dumb down" your answers a bit Thanks in advance.
Current:
Hboot: 1.32.0000
CID: HTC_001
CWM: 5.8.4.0
TheBlaaaaah said:
Hello all,
The name of this post says it all really, I am trying to update to Hboot 1.72 but I have no idea how This may be difficult as I have a new computer, and don't have any of the old folder I used to do this before so I will have to start from scratch again I have the Android SDK, so I can take any files needed from there, but apart from that I literally have nothing. Also, I am a complete novice with all this stuff so you may need to "dumb down" your answers a bit Thanks in advance.
Current:
Hboot: 1.32.0000
CID: HTC_001
CWM: 5.8.4.0
Click to expand...
Click to collapse
Read THIS for the simple method.
Since you are HTC__001 you'll get the ota soon you just need to be on stock rom, kernel and recovery and you are good to go
desmond1303 said:
Since you are HTC__001 you'll get the ota soon you just need to be on stock rom, kernel and recovery and you are good to go
Click to expand...
Click to collapse
The reason I'm trying to do this is because I'm on CyanogenMod 10.1 and the 10.2 update (Android 4.3) requires the newer hboot, so how would I go about doing this myself (step by step)?
Also Tigerlight, I'm fairly confident that JB FW doesn't let you use non Sense based ROM's afterwards, and to be honest I prefer doing things like this myself rather than letting software do it for you
Well...
You should be able to have CM 1.2 on 1.39...
But you Will have to wait for the firmware zip to be uploaded here http://forum.xda-developers.com/showthread.php?t=1957376
in order to be able to update it manually... You could download the OTA files and extract that firmware.zip yourself and than find a tutorial on how to flash a firmware.zip... there are plenty of them out here
TheBlaaaaah said:
The reason I'm trying to do this is because I'm on CyanogenMod 10.1 and the 10.2 update (Android 4.3) requires the newer hboot, so how would I go about doing this myself (step by step)?
Also Tigerlight, I'm fairly confident that JB FW doesn't let you use non Sense based ROM's afterwards, and to be honest I prefer doing things like this myself rather than letting software do it for you
Click to expand...
Click to collapse
JBFW flasher upgrades hboot, which has nothing whatsoever to do with what Sense or AOSP ROM you flash afterward so long as that hboot is compatible.
And why on earth type all the instructions manually when the tools exist.
And the 1.72 hboot firmware has been uploaded HERE.
Tigerlight said:
JBFW flasher upgrades hboot, which has nothing whatsoever to do with what Sense or AOSP ROM you flash afterward so long as that hboot is compatible.
And why on earth type all the instructions manually when the tools exist.
And the 1.72 hboot firmware has been uploaded HERE.
Click to expand...
Click to collapse
Ok, may have been a bit wrong there..... :silly: Still, I like to learn how to do this sort of thing so that if anything ever goes wrong I have the knowledge to fix it. Once I have the firmware, what do I need to do?
Just downloaded JBFW out of interest, and when you go to update it says this: After upgrade you will not be able to - Install a fully functional Non-Sense ROM, so I was right that I can't use that software, and anyway wouldn't want to tbph Anyone know how to manually update hboot given that I have no files from when I rooted anymore? :laugh:
Once you have the firmware.zip file you have to
1:relock the bootloader
Fastboot oem lock
2: boot into ruu mode
Fastboot oem rebootRUU
3: flash the firmware.zip
Fastboot flash zip firmware.zip
Maybe needed twice (only if the command returns an error)
Then unlock the bootloader and flash a custom recovery. Preferably repacked twrp, or philz touch recovery.
Then full wipe the phone in recovery and install the rom.zip and fastboot flash the boot.img.
That sums it up pretty much
Mr Hofs said:
Once you have the firmware.zip file you have to
1:relock the bootloader
Fastboot oem lock
2: boot into ruu mode
Fastboot oem rebootRUU
3: flash the firmware.zip
Fastboot flash zip firmware.zip
Maybe needed twice (only if the command returns an error)
Then unlock the bootloader and flash a custom recovery. Preferably repacked twrp, or philz touch recovery.
Then full wipe the phone in recovery and install the rom.zip and fastboot flash the boot.img.
That sums it up pretty much
Click to expand...
Click to collapse
Thanks Mr Hofs,
Already found out about 20 mins ago: you actually responded to someone else a while back and I used those instructions. I may have messed up quite a lot though: forgot to put the CM 10.2 zip on the phone before hand and now the phone is acting really weird..... I'll let you know if I need help but I have a few ideas first
Thanks again, I appreciate the help.
i modified my platform.xml to enable w/r access for the sdcard a few months back.
there was a copy of the original, er, 'somewhere' but i cant find it now.
i have removed the line added i in before but the 4.4.4 ota update is failing because of platform.xml.
anyone have a stock unmodified platform.xml they could upload here or pm?
my M8 is a dual sim version if that makes any difference.
thanks.
You should be able to find your RUU here and extract the file in question:
http://forum.xda-developers.com/showthread.php?t=2701376
berndblb said:
You should be able to find your RUU here and extract the file in question:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Nope, dont see it. is there one? (its a dual sim version)
couldnt see one on htcdev either.
i already have a signed zip file
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip
but as it is signed i cannot extract anything from it
winrar always say corrupt image, is there another way?
Solved?
Did you solve the problem? I have exactly the same issue . . .
gazzacbr said:
Nope, dont see it. is there one? (its a dual sim version)
couldnt see one on htcdev either.
i already have a signed zip file
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip
but as it is signed i cannot extract anything from it
winrar always say corrupt image, is there another way?
Click to expand...
Click to collapse
simonvfr said:
Did you solve the problem? I have exactly the same issue . . .
Click to expand...
Click to collapse
Hi,
not exactly. but i am on 4.4.4
i was toying with the idea of winding back to stock using nandroid, rooting and copying out platform.xml, then having another go at OTA...
but, i thought i might as well give MaximusHD 4.4.4 for dual sim a go as i was going to wipe anyway.
i flashed TWRP latest 2.8.1 and updated firmware (link is on Maximus page) and then ROM.
so thats where i am now and happy with the rom.
100% stable, no issues noticed at all and aroma removed some bloat for me as i installed.
no need to go back now.
i will wait for lollipop from HTC and all those custom roms for M8 dual sim to try out (er, joke)
gazzacbr said:
Hi,
not exactly. but i am on 4.4.4
i was toying with the idea of winding back to stock using nandroid, rooting and copying out platform.xml, then having another go at OTA...
but, i thought i might as well give MaximusHD 4.4.4 for dual sim a go as i was going to wipe anyway.
i flashed TWRP latest 2.8.1 and updated firmware (link is on Maximus page) and then ROM.
so thats where i am now and happy with the rom.
100% stable, no issues noticed at all and aroma removed some bloat for me as i installed.
no need to go back now.
i will wait for lollipop from HTC and all those custom roms for M8 dual sim to try out (er, joke)
Click to expand...
Click to collapse
Thanks. As I am rooted, with TWRP, but S-ON, I think I can't flash the new firmware. Or am I wrong on that?
I have nandroid backup from my original stock, so could go back to that and re-lock and then do the OTA, but it's a long slow way of getting to 4.4.4!
An alternative would be Cyanogenmod - but although CM11 supports multi-sim phones I can find nothing clear about whether the official builds support the M8 dual-sim.
Finding the M8 ROM situation frustrating after messing around endlessly with custom ROMs on Acer dual sim phone . . . .
simonvfr said:
Thanks. As I am rooted, with TWRP, but S-ON, I think I can't flash the new firmware...
Click to expand...
Click to collapse
you can but you have to re-lock the boot loader which will wipe your phone.
i used these instructions (I am S-OFF already) and firmware from link on Maximus site:
-------------------------------------------------------
How to flash firmware
### If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol DOWN + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
### Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Flash firmware.zip again just to make sure.
Type: fastboot reboot-bootloader
-------------------------------------------------------
what i am sure of is that without the new firmware you will not have wifi
i thought i flashed the firmware first but didnt do it twice and it didnt stick. after the rom was installed i had no wifi but guessed that was the problem and re flashed the firmware. then it was ok.
as for cyanogenmod, unless it states it is for M8 Dual SIM then i wouldnt bother unless youve got time to experiment and hope for updates.
i know there are many arguments as to why you dont really need S-OFF for most normal operations but it a real fail-safe when things get messed up (my 2c)
just find the $25 for sunshine, its worth it.
gazzacbr said:
you can but you have to re-lock the boot loader which will wipe your phone.
i used these instructions (I am S-OFF already) and firmware from link on Maximus site:
-------------------------------------------------------
How to flash firmware
### If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol DOWN + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
### Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Flash firmware.zip again just to make sure.
Type: fastboot reboot-bootloader
-------------------------------------------------------
what i am sure of is that without the new firmware you will not have wifi
i thought i flashed the firmware first but didnt do it twice and it didnt stick. after the rom was installed i had no wifi but guessed that was the problem and re flashed the firmware. then it was ok.
as for cyanogenmod, unless it states it is for M8 Dual SIM then i wouldnt bother unless youve got time to experiment and hope for updates.
i know there are many arguments as to why you dont really need S-OFF for most normal operations but it a real fail-safe when things get messed up (my 2c)
just find the $25 for sunshine, its worth it.
Click to expand...
Click to collapse
Thanks for response. In the meantime I have gone S-OFF with Sunshine, but I have not yet flashed the new firmware or the ROM.
For firmware flashing, I was going to use the process described here on XDA. Seems very simple . . .
simonvfr said:
Thanks for response. In the meantime I have gone S-OFF with Sunshine, but I have not yet flashed the new firmware or the ROM.
For firmware flashing, I was going to use the process described here on XDA. Seems very simple . . .
Click to expand...
Click to collapse
But in the end I had to use the method you suggest, as once the ROM was installed I had no firmware and was therefore stuck in bootloader. With some fiddling I managed to sort it all out, and everything is now running.
Thanks for your help
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735
I cant do that because i am not s-off
marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result
marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then
I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse