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 Guys,
i am completely new to Android, had my One X for 6 months now.
i really want to upgrade to JB, the renovate ROM.
i have CID_016 and HBOOT 1.12.
can any1 tell me the steps i need to take, i will do my best to find the detailed instructions on each step.
but i just need to know exactly what i need to do...upgrade HBOOT? if so what version? if im on 1.12 - do i have to do 1 or 2 version before going to the final version etc...etc
i really dont want to brick my device.
thanks
Okay first thing I would do is have a look at the renovate ROM thread, because the OP would most likely be a nice person and have some instructions. Let's see what they write......
http://forum.xda-developers.com/showthread.php?t=1705334
"How To Flash:
For the Jellybean update you need to have flashed the updated firmware. Please have a look at the many guides available on how to do this"
Oh, so they want us to flash updated firmware, how should I do this? Well look! Conveniently stickied is a thread called "[07.12.2012] Jelly Bean firmware collection for different Carriers ID (CID)", let's go there!
http://forum.xda-developers.com/showthread.php?t=1957376
Oh I see my CID number listed underneath!
I will then proceed to download the firmware.zip file.
Okay I downloaded, now what? Well let me scroll down the page and see if there are any instructions:
"Flash firmware.zip using following terminal commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip"
Okay, I see I have to be in fastboot mode in order to do this. But I must not forget to relock the bootloader first. So I use the command 'fastboot oem lock' to first lock my bootloader, and then proceed to complete the above instructions to flash the firmware.
Okay now what? Well I think I should relock my bootloader now that I want to flash renovate, so I do by using 'fastboot flash unlocktoken unlock_code.bin'. Done.
Next, ...........
Or seriously just use this tool: http://forum.xda-developers.com/showthread.php?t=1924003
You need either HBOOT 1.31, 1.33 or 1.36 for this ROM.
Click to expand...
Click to collapse
So...yes U have to upgrade your HBOOT.
All other steps for flashing are described in every rom thread.
thanks tomascus - that last link is what i needed.
i know there are detailed threads on the ROM links, and i cant ask questions on there, so just wanted to know about what order to do things, and if i needed to upgrade my HBOOT to some other version first before going to the latest etc...dont ahve money for a new phone so dont wanna brick it
i've already downloaded firmware with HBOOT 1.36, as well as a custom ROM, busy downloading JBFWTOOL now.
can i go straight from HBOOT 1.12 to 1.36? running ICS obviously
thanks a mil.
tradroid said:
thanks tomascus - that last link is what i needed.
i know there are detailed threads on the ROM links, and i cant ask questions on there, so just wanted to know about what order to do things, and if i needed to upgrade my HBOOT to some other version first before going to the latest etc...dont ahve money for a new phone so dont wanna brick it
i've already downloaded firmware with HBOOT 1.36, as well as a custom ROM, busy downloading JBFWTOOL now.
can i go straight from HBOOT 1.12 to 1.36? running ICS obviously
thanks a mil.
Click to expand...
Click to collapse
Yes you can, mate.
PS. phone is almost unbrickable, I don't actually think there is a way to brick it unless you flash something meant for another device...
tomascus said:
Yes you can, mate.
PS. phone is almost unbrickable, I don't actually think there is a way to brick it unless you flash something meant for another device...
Click to expand...
Click to collapse
cool, thats good to know. thanks for the help.
last question, i hope - what is this "unlock_code.bin" that i see certain instructions talk about?
in bootloader it says "S-ON" - do i need this unlock_code.bin and if so how do i get it?
tradroid said:
last question, i hope - what is this "unlock_code.bin" that i see certain instructions talk about?
in bootloader it says "S-ON" - do i need this unlock_code.bin and if so how do i get it?
Click to expand...
Click to collapse
You get it when you unlock at htcdev. You will need it when unlocking bootloader.
S-ON has nothing to do with this don't worry about it.
Sent from my HTC One X
TToivanen said:
You get it when you unlock at htcdev. You will need it when unlocking bootloader.
S-ON has nothing to do with this don't worry about it.
Sent from my HTC One X
Click to expand...
Click to collapse
and this HAS to be done in order to flash a custom rom right?
tradroid said:
and this HAS to be done in order to flash a custom rom right?
Click to expand...
Click to collapse
Yes, at the moment you can't do anything without unlocking the bootloader at htcdev.com.
And I really recommend this tool for unlocking and installing custom recovery, it truly is noob-proof.
After using that tool you will have all pre-requirements and tools needed for installing custom roms. :good:
Hi All,
I really hate running RUU's, but now I think I must run one, and use the newer kernel..
I have HTC_001 - with my version being the .401. one...
I have now downloaded two RUU's that both fail on the Signature Error - Error code 132.
I'm fastboot oem lock, then running the RUU... Is there anything I must do?
At the moment I'm restoring my nandroid backup from before trying (tried at least 10 since last night, 2 different computers too), as I need my phone...
Is there any other way to do it? I just want a newer hboot, but am on 0.43 now...
Any help apprciated...
Thanks, Matt
EDIT: I'm on <fastboot getvar mainver> 1.26.401.2 - I'm now downloading an ICS ruu, and if that works, will do the ota (hopefully)... Still any help appreciated..
Could you do: fastboot get main-version
If you wont to upgrade to JB with RUU i think your HBOOT version is to low, so you first need to upgrade firmware:
1. You can upgrade firmware to "middle" version if you use ICS RUU
2. Then you can use JB RUU, or only JB firmware
cid firmware for you :http://forum.xda-developers.com/showthread.php?t=1957376 this is the latest HBOOT.
But first post info after : fastboot get main-version
hpnxfox said:
Could you do: fastboot get main-version
If you wont to upgrade to JB with RUU i think your HBOOT version is to low, so you first need to upgrade firmware..
Click to expand...
Click to collapse
haha, just edited my post... 1.26.401.2
But how can I upgrade my firmware - this ruu is supposed to do that...
As said, I'm downloading an ICS ruu, then I guess will OTA if that works... - Only thing is... The ruu will take at least 1 Hour to download, with my bad download speeds...
So, yes you need first to use RUU with matching CID and main version, then you can do OTA upgrade all the way to JB and HBOOT 1.39..
But be aware if you do officially OTA upgrade to JB yours phone touch.img will be also updated and you have problems with touch in custom recoveries like CWM or TWRP!
If you do official update to JB:
1. TWRP 2.5.0.0 or 2.4.0.0 - reapcked version have touch but usb mass storage in recovery and adb isn't functional
2. CWM 6.0.3.0-have adb and usb mass storage but no touch because of developer restriction
So it is better to upgrade OTA to latest ICS version and manually just upgrade HBOOT to 1.39..
hpnxfox said:
So, yes you need first to use RUU with matching CID and main version, then you can do OTA upgrade all the way to JB and HBOOT 1.39..
But be aware if you do officially OTA upgrade to JB yours phone touch.img will be also updated and you have problems with touch in custom recoveries like CWM or TWRP!
If you do official update to JB:
1. TWRP 2.5.0.0 or 2.4.0.0 - reapcked version have touch but usb mass storage in recovery and adb isn't functional
2. CWM 6.0.3.0-have adb and usb mass storage but no touch because of developer restriction
So it is better to upgrade OTA to latest ICS version and manually just upgrade HBOOT to 1.39..
Click to expand...
Click to collapse
Thanks, will give it a go...
If anything, I will compile a touch version of CWM and use that for personal use... (I have done in the past (6.0.2.7)).
So if this ICS ruu works, then just the FW JB Flasher Tool to upgrade to latest hboot? If so, sounds good
To flash firmware with fastboot commands after you upgrade to latest ICS - i am not using tools ore similar one click tools , but for flashing firmware you cant just flash
You need to lock bootloader again for flashing firmware (it should bee locked already because you need to lock to flash RUU) and then when phone is in bootloader(fastboot usb mode actually):
1.fastboot oem rebootRUU
2.fastboot flash zip firmware.zip
After HBOOT upgrade boot to hboot to check is it really there, and then unlock bootloader again, and flash custom recoveries..
And here are the links for working custom recoveries(with mentioned restrictions in previous post) if you decide to upgrade via OTA all the way to JB
1.TWRP 2.5.0.0 http://forum.xda-developers.com/showpost.php?p=40120901&postcount=509
2.CWM 6.0.3.0 http://forum.xda-developers.com/showthread.php?t=1941630
3.CWM Advanced Edition] PhilZ Touch http://forum.xda-developers.com/showpost.php?p=40442326&postcount=1
hpnxfox said:
To flash firmware with fastboot commands after you upgrade to latest ICS - i am not using tools ore similar one click tools , but for flashing firmware you cant just flash
You need to lock bootloader again for flashing firmware (it should bee locked already because you need to lock to flash RUU) and then when phone is in bootloader(fastboot usb mode actually):
1.fastboot oem rebootRUU
2.fastboot flash zip firmware.zip
After HBOOT upgrade boot to hboot to check is it really there, and then unlock bootloader again, and flash custom recoveries..
And here are the links for working custom recoveries(with mentioned restrictions in previous post) if you decide to upgrade via OTA all the way to JB
1.TWRP 2.5.0.0 http://forum.xda-developers.com/showpost.php?p=40120901&postcount=509
2.CWM 6.0.3.0 http://forum.xda-developers.com/showthread.php?t=1941630
3.CWM Advanced Edition] PhilZ Touch http://forum.xda-developers.com/showpost.php?p=40442326&postcount=1
Click to expand...
Click to collapse
Thnaks for all the help here... I am now on the newer hboot (1.39) Yay!!
However, just tried to reflash a recvoery and it didnt work lol... It failed to write it... So will keep trying this, but any pointers? <- helps if I spell recovery properly, doesn't it... lol
Restoring my nandroid backup from when I locked the device.... and on newer hboot... thanks a lot!!
Did you unlock bootloader again with bootloader unlocking procedure with unlock key from htcdev? (you talking about flashing custom recovery.img?)
hpnxfox said:
Did you unlock bootloader again with bootloader unlocking procedure with unlock key from htcdev?
Click to expand...
Click to collapse
I edited my post;
Code:
c:\android\tools>fastboot flash recvoery "C:\Users\Webmaster\Documents\My Dropbox\Android\recoveries
\recovery-6.0.2.3-endeavoru.img"
sending 'recvoery' (6058 KB)...
OKAY [ 0.724s]
writing 'recvoery'...
FAILED (remote: not allowed)
finished. total time: 0.939s
All looks good to me...
Thanks a lot for your help...
Ah "recvoery"..yes, always the smallest things good luck with HOX
And "button thanks" to you also, it was one more new experience to me!
hpnxfox said:
Ah "recvoery"..yes, always the smallest things good luck with HOX
Click to expand...
Click to collapse
Yep, everything is working... Back into my rom now too, so im very happy!!
You say good luck with the HOX, I actually have a rom out (actually a few) for the HOX... I am a skilled user (if I do say so myself)... Just I hate RUU's, and with my previous HTC deivce (HTC Desire), I was always told it was a bad move to flash RUU's...
I must admit it is a bit of a pain, but all is working now... And I didnt even do the OTA to JB, just got the ICS main-version, and the JB hboot... as you suggested - Sweet
Again, thank you for all your help
mattmanwrx said:
Yep, everything is working... Back into my rom now too, so im very happy!!
You say good luck with the HOX, I actually have a rom out (actually a few) for the HOX... I am a skilled user (if I do say so myself)... Just I hate RUU's, and with my previous HTC deivce (HTC Desire), I was always told it was a bad move to flash RUU's...
I must admit it is a bit of a pain, but all is working now... And I didnt even do the OTA to JB, just got the ICS main-version, and the JB hboot... as you suggested - Sweet
Again, thank you for all your help
Click to expand...
Click to collapse
I see that you are "Big Boy" in android land You don't have so many thanks buttons because of nothing
I'm on beginning, i'm not in developers waters..i tried but i missing knowledge..
hpnxfox said:
Ah "recvoery"..yes, always the smallest things good luck with HOX
And "button thanks" to you also, it was one more new experience to me!
Click to expand...
Click to collapse
after reading this thread......Yeah it could have been easier
hpnxfox said:
I see that you are "Big Boy" in android land You don't have so many thanks buttons because of nothing
I'm on beginning, i'm not in developers waters..i tried but i missing knowledge..
Click to expand...
Click to collapse
Well I started off theme'ing, then moved to modding apps, now playing with source, it has only taken me 2 years lol!!!
Mr Hofs said:
after reading this thread......Yeah it could have been easier
Click to expand...
Click to collapse
What is the easier way Mr Hofs? Just for anyone else who might ask? or if I need to do it again etc?
You only needed to install the 1.26, 1.28, 1.29 or the 2.17 ruu....they will work right away. A JB ruu only works when you are on at least a 2.17 based software.
Or flash the JB firmware right away. This will actually lift the hboot directly to 1.39.....
It could be done in 2 posts ..... but we are all here to learn so this all has been a very good experience :thumbup:
Ow and losing the touch function on the official newer base is no problem at all, all the cwm recoverys can be controlled with the volume and power button !
I don't argue with Mr Hofs , he is expert and have all info in his head, i just can blindly follow his instructions without struggling :laugh:
Mr Hofs said:
You only needed to install the 1.26, 1.28, 1.29 or the 2.17 ruu....they will work right away. A JB ruu only works when you are on at least a 2.17 based software.
Or flash the JB firmware right away. This will actually lift the hboot directly to 1.39.....
It could be done in 2 posts ..... but we are all here to learn so this all has been a very good experience :thumbup:
Ow and losing the touch function on the official newer base is no problem at all, all the cwm recoverys can be controlled with the volume and power button !
Click to expand...
Click to collapse
But as I was on 0.43 hboot, I couldnt flash the firware.zip to bring hboot up? or could I... I was in the understanding of I needed newer than 0.43 to flash a newer hboot...
But also, it would have helped me to know that I cannot go straight to JB RUU from 0.43 - that would have saved me a lot of time lol!!
anyways, i flashed the 1.28, which bought me up to 0.96 (I think), then changed hboot to 1.39 - so all is fine for me now
Thanks for the suggestions though, I might need them for when I buy my HTC One lol
Yeah that's good too no problem there.
The thing is that the standalone firmware flash to upgrade the hboot can be done from any low hboot.
Only the JB ruu can be installed from the 1.12 or higher...
Well, all I know, is that is is done now!! lol...
So I'm happy... and I guess can make this thread as "Solved"
Very true ! And a :thumbup: up for hpn !
I will answer you PM tonight Mr Hpn
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 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