Related
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
http://www.filefactory.com/file/7c4y4xrx25w3
MD5: 02f5c589d6d2bb0cc8678c7b76f2951b
Source: http://forum.xda-developers.com/showthread.php?t=1335368 (Football)
....and just after I finally managed to get the ota installed
Hi,
i have S-ON, bootloader unlocked, root, 2.13.401.3
after this update 2.26.401.3 stay still bootloader unlocked?
EDIT: maybe i need S-OFF, not possibly update my mobile...
you need to relock the bl in order to install any ruu.
i had a hard time updating my phone to 2.26
if you take a look at the first thread for this update, the ota update, there are details for how to update to this version and still keep bl-nlocked and easily root
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
Can anyone send me this file not via filefactory? There are no free slots in there at all
I relock bl and try new RUU 2.26, but problem with flashing. Can you pls describe steps by steps how can is possibly update from 2.13 to 2.26 ? I'm S-ON
I have Rom with 2.26 but I want update radio too....
Sent from my HTC Wildfire S A510e using xda premium
http://forum.xda-developers.com/showthread.php?t=1679010
try the process in this thread, if you can't get it to work straight away, try using the method i used (thanks to rezo).
1 - install the ruu for 2.14.401.1
(http://www.mediafire.com/download.php?o6ox43q3taa33iu)
1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1
http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade
2 - use htcdev process (without ruu step) to unlock bootloader
3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"
4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.
4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.
5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)
you should now have the latest stock rom, latest hboot, latest radio, and be root.
What's different in this new update 2.26. ?
Hi guys
I'm trying to download this new ruu for 2 days now from "filefactory" an still: "no free slots"! Ca anyone help me to download this new ruu from other sites?
Thank's in advance!
my current software version is 2.14.401.2, what is the difference if i update to 2.26.401.3? Does it gives any improvement on the performance or battery life?
Thx...
Gloris said:
http://forum.xda-developers.com/showthread.php?t=1679010
try the process in this thread, if you can't get it to work straight away, try using the method i used (thanks to rezo).
1 - install the ruu for 2.14.401.1
(http://www.mediafire.com/download.php?o6ox43q3taa33iu)
1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1
http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade
2 - use htcdev process (without ruu step) to unlock bootloader
3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"
4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.
4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.
5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)
you should now have the latest stock rom, latest hboot, latest radio, and be root.
Click to expand...
Click to collapse
I have problem with install RUU, why?
Zlobizlob said:
I have problem with install RUU, why?
Click to expand...
Click to collapse
what is the error code?
things to remember when you flash an ruu :-
you should not have modified system files (except for root)
you should have stock recovery to start with
you may need to create gold card
you should be relocked bootoader
if you are already on a software number which is higher than the ruu you are trying to install, you may need to downgrade first, using the guide posted above.
Is there anyway without S-OFF to update the radio? I would rather not loose any data too. I've manage to update everything but the radio.
Stevk said:
Is there anyway without S-OFF to update the radio? I would rather not loose any data too. I've manage to update everything but the radio.
Click to expand...
Click to collapse
if you're s-off already, can't you just flash the radio.img?
don't quote me on that, i'm not s-off myself, so i'm not reallu 'up' on all the thigns you can do and how you do them. but i was under the impression that with s-off you can flash it same as you flash recovery.img or system.img?
Do I need to flash radio? Because my girlfriends WFS has been t-mobile branded so I think I'm not able to flash RUU without gold crad?
Is it possible to flash system.img and boot.img only? Or will there be conflicts with radio/ramdisk etc...
BL is unlocked and device is rooted atm!
I installed this RUU to my Wildfire S by this tutorial
Code:
http://forum.xda-developers.com/showthread.php?t=1540952
My phone had unlocked bootloader (via htcdev.com), Root, S-On and my Hboot version was 1.09.0099. When I was trying to install RUU I got ERROR 140(bad hboot version). So I used mentioned tutorial to downgrade hboot and then I install new RUU.
I downloaded RUU 2.26.401.3 from this site because on Football's FileFactory link are allways full slots.
Code:
http://narod.ru/disk/51502291001.c558c29e878e383684edd1a956d417fd/RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.html
And there is a ZIP version if someone want
Code:
http://narod.ru/disk/51500892001.cf33d25826e44363856289cb11302527/PG76IMG%20-%20Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M.zip.html
Sorry for poor english.
Can anyone please upload the RUU to another server?
FileFactory is always overloaded. And the russian site is too slow to download from America. 3kbps gg.
Any issues unlocking BL and rooting this update? Any compelling reason to stay with 2.13.401.2/3?
Heritz said:
Can anyone please upload the RUU to another server?
FileFactory is always overloaded. And the russian site is too slow to download from America. 3kbps gg.
Click to expand...
Click to collapse
I can upload RUU from russian site. Choose on which file hosting server. I dont know which is good.
EDIT - I solved it.
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Yep,if your phone is supercid,u can flash that firmware...
hellcommando said:
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Click to expand...
Click to collapse
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
hdorius said:
Yep,if your phone is supercid,u can flash that firmware...
Click to expand...
Click to collapse
Thank you!
ckpv5 said:
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
Click to expand...
Click to collapse
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
hellcommando said:
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
Click to expand...
Click to collapse
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.707.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
ckpv5 said:
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.77.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
Click to expand...
Click to collapse
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
hellcommando said:
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
Click to expand...
Click to collapse
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
hellcommando said:
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
Click to expand...
Click to collapse
Great
Now you can flash any Sense 6 custom ROM that you like.
Only remember that you don't need to flash another firmware, your current one is good enough.. just flash ROM.
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
charkswitlazers said:
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
Click to expand...
Click to collapse
Stock ROMs and recoveries for HTC__044
http://forum.xda-developers.com/showthread.php?t=2701376
charkswitlazers said:
anyone have an idea where I should start?
Click to expand...
Click to collapse
Everything that you need is here : http://forum.xda-developers.com/showthread.php?t=2701376
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
ckpv5 said:
Everything that you need is here
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
Click to expand...
Click to collapse
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
I just got my m8 from Tmobile today, and I am on firmware 157.531.7
I've checked several times for updated firmware, but always comes back nothing.
Am I stuck on this, or will it take awhile for the network to "see me" and send it?
not rooted, fully stock for now
thanks so much!
charkswitlazers said:
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
Click to expand...
Click to collapse
If your main purpose to restore to stock to get SunShine working, then any nandroid backup will do either HTC__044 or WWE. You don't really need a rooted stock as SunShine works on non-rooted ROM too.
As you said you're a noob, that is why I suggest to restore to 1.54.707.7 then OTA to 2.22.707.3 so you don't need to manually flash firmware to get other custom ROMs running flawlessly. It is not necessary to have 2.22.401.4 firmware but it is necessary to have a 2.22.xxx.x firmware for those custom ROMs, unless you're not in Asia.
As you can see in my sig, I'm on 2.22.707.3 firmware, I can run any ROM without problem.
Being a noob, you may make a stupid mistake when flashing firmware.
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Slow Booting & Sense 6 Toolbox Not Working On ARHD v10.2
One-M8-Master said:
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Click to expand...
Click to collapse
Hi One-M8-Master,
I've read quite a few of your posts & given that your moniker seems appropriate, I'm wondering if you might be able to help me?
I've posted this on another thread but haven't got very far as yet, so am hoping that you might be able to get me out of the stupid hole I've dug myself into :fingers-crossed:
It is quite a long description but if you don't fall asleep reading it, I'd really appreciate any help you might be able to give me.....Here goes:
"Hi Guys,
Now I know you're all already thinking that I didn't update my firmware before I flashed ARHD & now I'm getting all the problems that come along with not doing that......& you'd be correct....kind of. HOWEVER, as it turns out, I already seem to have it. Let me explain.
As you can see, I'm relatively new to all this but successfully unlocked, rooted & installed a custom ROM on my ASUS TF700T tablet, so I wanted to do it with my One M8. I always do loads of reading before I start anything (I even read the instructions for new games before I attempt to play them because I'm a bit weird like that!) but what happened on this occasion was that I did the reading, unlocked the phone, flashed TWRP, & rooted it but then ran into the problem that some people appear to have had when trying to s-off via the adb commands & Firewater, that is, my pc could see the phone but when I gave the reboot command, it told me it wasn't connected.
I then got into hours of reading to try & solve this issue, discovered that (without Sunlight) on some devices it just doesn't work once you've accepted the 'should we allow this pc to connect every time' message (which I NEVER normally say 'yes' to), unless you install the Android Studio & Java Develpers Kits, update your version of adb, & force the phone to ask again (which I did but it turned out that I already had the latest version of adb, so that route proved fruitless!). I actually missed a night's sleep trying to resolve the problem, so work wasn't good the next day! but I think it is here is where my problems started because I was so tired & frustrated that I just picked a ROM & flashed it. I had even read the warning about not flashing it if you didn't have the correct firmware but I think that being so tired, it didn't really sink in, or I'd forgotten about it by the time I just flashed the ROM.
By this point, I'd been sat in front of my pc for about 30 hours & needed to go to work but the phone was actually booting through to ARHD, so I was relatively happy in the knowledge that at least I hadn't bricked it! On starting to use the phone that evening, I noticed the long boot times & then that my Sense 6 Toolbox didn't seem to be making any changes, even if I rebooted the device, so I went back to the beginning of this thread & started reading again. Thus, I re-read the firmware warning & panicked (my 2nd mistake!), thinking that I was getting the problems because I hadn't updated the firmware (it still didn't occur to me to just check because I think I just assumed that I wouldn't have it). So.....I tried to restore my TWRP backup of the stock ROM that I made after I had unlocked/rooted, with the intention of reverting to the stock ROM, getting the OTA update & then re-flashing ARHD but despite TWRP telling me that the backup had been successful, the phone went into a bootloop back into TWRP. I solved this by re-flashing the ARHD ROM that I knew at least would get my phone out of the bootloop & back into KitKat, which it did. I then checked what version of the firmware I had & to my surprise, my Build Number in About\Software Information\More says "2.22.401.4 CL365360 release-keys", so it looks like I had the correct firmware version all along?
The above being the case, I'm now puzzled as to why I'm getting the problems that I'm getting with ARHD? Does anyone have any clues/answers that might get me out of this hole I've dug for myself & get my awesome One M8 working like it should?
I know I've caused this problem by doing things when I was too tired to think straight but I'm fresh as a daisy now (still fairly noobish but fresh ) & now I need your help to sort myself out. I would be so grateful for any help anyone can give me to get me back on track.
I hope all of that makes sense & thanks in advance."
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Mr Hofs said:
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Click to expand...
Click to collapse
Hi.
This is my own fault but I'm getting really frustrated with it because I've probably spent a total of 40 hours on it so far
I tell you that because I know that I needed S-OFF & SUPER CID to be able to update my firmware, so I just thought "screw it" & I paid for Sunshine. I now have S-OFF & following Vomer's guide here:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I now have S-OFF & SUPER CID. I thought that would be the end of my issues but it would appear not!
Looking at my bootloader, you are correct, HBOOT is 3.16.0.0000!
However, I've tried to upgrade this firmware by downloading what I think is the correct update .zip from the list at the bottom of the aforementioned Vomer's guide (v2.22.401.5 (Rename to firmware.zip after downloading)), renaming it as suggested, & then flashing it in TWRP but it just keeps telling me that the update has failed!
Do I have to do it using the adb commands on Vomers guide? I didn't think so but it's just not working??
I appreciate any help you can give me with this. Given that I've spent so long on this & have paid for Sunshine, you can see that I'm trying to help myself but I've still got rain!!
EDIT
Just a thought, I do still have ARHD v10.2 installed at the moment because even though it's not working properly without the correct firmware, it's the only ROM I've got at the moment, so it means I can use the M8 to a degree; would that cause the problem with upgrading the firmware?
Firmware flash can be done via fastboot commands, that's how i did it
Installed rom has no influence on the to flash firmware, try it via fastboot
If I want to convert my carrier locked m8, Vodafone, to 401 unlocked, what is the correct steps and sequence ?
Am I right with this...
1. S-off with sunshine after taking out box AND before taking any ota updates.
2. Install custom recovery. (So I can flash stock 401 ROM)
3. Flash firmware that matches ROM
4. Flash stock recovery.
The only real doubts I have are the order of steps especially firmware and ROM.
Is it firmware or ROM first ?
Thanks
Sent from M8
Hi,
If it's a GSM phone, Here's the guide for it,
http://forum.xda-developers.com/showthread.php?t=2708567
Good luck!
Thanks for reply but it's not sim unlock I want. I want to convert it from Vodafone UK software to stock wwe, 401, system.
I know the steps, just wondering that I've got the correct sequence in my op.
It is gsm because it's a UK phone.
Thanks
Sent from M8
10rdan said:
Thanks for reply but it's not sim unlock I want. I want to convert it from Vodafone UK software to stock wwe, 401, system.
I know the steps, just wondering that I've got the correct sequence in my op.
It is gsm because it's a UK phone.
Thanks
Sent from M8
Click to expand...
Click to collapse
the only drawback to doing the firmware after the rom is the rom will not have wifi on the old firmware
So the correct order is
unlock bootloader
flash custom recovery / root
s-off
flash firmware
flash rom
flash stock recovery
take updates
clsA said:
the only drawback to doing the firmware after the rom is the rom will not have wifi on the old firmware
So the correct order is
unlock bootloader
flash custom recovery / root
s-off
flash firmware
flash rom
flash stock recovery
take updates
Click to expand...
Click to collapse
Ok, thanks. Just wanted it confirmed before I "melted" the phone.
Sent from M8
clsA said:
the only drawback to doing the firmware after the rom is the rom will not have wifi on the old firmware
So the correct order is
unlock bootloader
flash custom recovery / root
s-off
flash firmware
flash rom
flash stock recovery
take updates
Click to expand...
Click to collapse
Been thinking about this, cause I like to have things clear before starting.
If I s-off with sunshine, because it will unlock bootloader without using HTCdev, then
1. Flash TWRP
2. Take nand
3. Then run this https://www.androidfilehost.com/?fid=95784891001609293
4. Take any ota updates
Will that remove the need to flash 401 firmware, ROM and stock recovery as 3 individual processes ?
Thanks
Edit, will change cid to HTC__001 before running RUU.
Sent from M8
10rdan said:
Been thinking about this, cause I like to have things clear before starting.
If I s-off with sunshine, because it will unlock bootloader without using HTCdev, then
1. Flash TWRP
2. Take nand
3. Then run this https://www.androidfilehost.com/?fid=95784891001609293
4. Take any ota updates
Will that remove the need to flash 401 firmware, ROM and stock recovery as 3 individual processes ?
Thanks
Edit, will change cid to HTC__001 before running RUU.
Sent from M8
Click to expand...
Click to collapse
The RUU will certainly shorten the update process ...Running Sunshine to unlock the bootloader without Root could be a problem
clsA said:
The RUU will certainly shorten the update process ...Running Sunshine to unlock the bootloader without Root could be a problem
Click to expand...
Click to collapse
Sunshine unlocked my bootloader ok with the m8 I'm using just now. Can't remember which hboot I was on at the time. Wasn't rooted, completely stock.
That's why I intend using sunshine BEFORE I take any ota updates, ie, as soon as I get it out the box.
Didn't use sunshine to, primarily, unlock bootloader at the time. It was a welcome "extra".
Cheers
Edit
Copied from Sunshine web site........
SunShine unlocks your device's bootloader and sets it to s-off (HTC ONLY). SunShine does NOT install root binaries on the device. There are a few ways to root your device after using SunShine. The most common and reliable method would be to flash TWRP recovery to your device via fastboot, and flash the root binaries or a rooted ROM from within TWRP.
Sent from M8
Did this yesterday on my new m8. Worked flawlessly with temp root. Rooted after using adb and flashed SuperSU.
Same Question...
So, i've been reading a lot but still don't understand everything right...
I already use sunshine and now my AT&T (4.4.3 by RUU (this)) is s-off and bootloader unlocked. What should be my next step? Just run that RUU that you post will work? And after that i can flash any ROM that need 4.4.4?
guire01 said:
So, i've been reading a lot but still don't understand everything right...
I already use sunshine and now my AT&T (4.4.3 by RUU (this)) is s-off and bootloader unlocked. What should be my next step? Just run that RUU that you post will work? And after that i can flash any ROM that need 4.4.4?
Click to expand...
Click to collapse
What are you trying to do exactly? If your intent is to convert to WWE version, or run the phone on non-AT&T networks, that what you describe is probably right.
If you intend to just update firmware and run the phone on AT&T's network, I don't personally recommend the WWE firmware, as it has caused issues for a lot of folks on AT&T.
redpoint73 said:
What are you trying to do exactly? If your intent is to convert to WWE version, or run the phone on non-AT&T networks, that what you describe is probably right.
If you intend to just update firmware and run the phone on AT&T's network, I don't personally recommend the WWE firmware, as it has caused issues for a lot of folks on AT&T.
Click to expand...
Click to collapse
Thanks for answer! I Already use my phone on non-AT&T netwoorks, as i am from Brazil. I also planning flash Android Revolution or maybe SkyDragon, and both require 4.4.4.
guire01 said:
Thanks for answer! I Already use my phone on non-AT&T netwoorks, as i am from Brazil. I also planning flash Android Revolution or maybe SkyDragon, and both require 4.4.4.
Click to expand...
Click to collapse
You just need to update the firmware, not run the entire RUU. Instruction here: http://forum.xda-developers.com/showthread.php?t=2696282
RUU will do it too, but it seems a bit overkill for what you are trying to do.
redpoint73 said:
You just need to update the firmware, not run the entire RUU. Instruction here: http://forum.xda-developers.com/showthread.php?t=2696282
RUU will do it too, but it seems a bit overkill for what you are trying to do.
Click to expand...
Click to collapse
Ok, i'll update just the firmware, but everytime i read about i got lost... For this, do i need to change CID and MID on my phone? Or i can get any firmware and flash since i am with s-off?
Please help!! I tried to install a 3.x.x firmware ROM via TWPR 2.8.6.1 while my phone was still have 2.x.x firmware. The installation itself was succesful but when i tried to boot system it kept booting into bootloader screen. My phone is still S-ON and software is 2.11.425.7.
MM roms won't run on LP firmware. You need to roll back or upgrade your firmware to 6.0.
Ruu
Can you boot in bootloader ? Flash Ruu or Rom for 2.11.425.7 firmware in TWRP. Probably if firmware and rom version 2.11.425.7 is the same you can normal boot phone (if u see white screen with HTC logo you must WAAAAAAAAIT), or install RUU and update phone official to newest firmware and sofrware if u have Son. Next if u want, unlock bootloader and make SOFF and flash any rom if u want Sorry for my ENG
Bajdaspl: Yes i can boot into bootloader and can you please tell me how i can update its firmware? I've been told that to upgrade firmware my phone needs to be
S-OFF but my phone is still S-ON. I can't even find any RUU for my firmware version anywhere on the Internet. Would relocking helps????
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.