Related
Hi guys.
Finally today I receive the OTA upgrade to JB. First an smal upgrade was succesfully downloaded and installed, and then the firmware to upgrade the phone to JB (I had 4.03 custom rom).
After the phone install the JB upgrade the phone stuck on the HTC ONE white screen
I had a backup on the SD that let me recover the phone, I try to install the upgrade again, with the same luck. I read a post that said that erasing the SD will resolve the issue, and I have no better idea than do it!!! (yeah... really!!)
I read several post all day on XDA, I try to flash again the boot and ROM with the upgrade that I save on my PC, and with a Backup via
fastboot. But nothing work (I dont know if I did it right). I cant see the SD on fastboot, already try a factory reset, when I go to the recovery option on fastboot the phone just rebooted with no options.
My CID is BSTAR301
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON RH
HBOOT-1.39.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012, 13:59:37
Attached are the backup files that I have in my pc and the OTA upgrade files that my phone download.
Here there are many people who know a lot of this!!
Please help me to recover my phone!
u say you are on a custom rom, But you tried to update OTA?
Restore phone to complete stock ( even recovery) then you can update.
you could use an RUU or maybe a nandroid
{< r o N o $ said:
u say you are on a custom rom, But you tried to update OTA?
Restore phone to complete stock ( even recovery) then you can update.
you could use an RUU or maybe a nandroid
Click to expand...
Click to collapse
Sorry, I mean I had the ORIGINAL ROM (4.03), the only change that I made was root the phone.
My CID is BSTAR301, I only have the backup files that I copy to my pc and the OTA upgrade that the phone download. I attach the images of the files that I have.
Could you please tell me how to restore it to complete stock with the commands? which files should I use?
Thanks for you help.
guillerhcp said:
Sorry, I mean I had the ORIGINAL ROM (4.03), the only change that I made was root the phone.
My CID is BSTAR301, I only have the backup files that I copy to my pc and the OTA upgrade that the phone download. I attach the images of the files that I have.
Could you please tell me how to restore it to complete stock with the commands? which files should I use?
Thanks for you help.
Click to expand...
Click to collapse
I assume that you first installed CWM or TWRP recovery to root your HOX, and if you make backup of your recovery this is CWM or TWRP recovery.img, not stock recovery.img that is came with phone because you reflashed original one with TWRP or CWM and official ROM need official recovery.img. I hope that you make nandroid backup before root with TWRP or CWM because is it "must to do" in every installation guide. If so, when you wanted to update via OTA for official JB you needed to:
1. reverse to stock software (for you, you needed only to unroot or use nandroid backup if you have yours, if not try to find one in xda one x forum matching your current CID and main-version)
2. reverse to stock recovery.img that is matching your CID (exact matching) (you need to find it on xda one x forum section) - i see that you have firmware folder but dont know is it from your backup or from OTA, if it is from OTA than you can use recovery.img from that folder to flash stock recovery.img via fastboot commands (only recovery.img)
3. then you can do official JB update via OTA
And then if you have need to custom ROM you need flash again CWM or TWRP recovery.img
Also you can get full stock with RUU but RUU must fully match your CID and main version, but RUU isn't available for every phone version, and after RUU you can do officall OTA JB update (for RUU you need to lock bootloader)
Information that can help us is yours phone current main version (fastboot getvar version-main)
hpnxfox said:
I assume that you first installed CWM or TWRP recovery to root your HOX, and if you make backup of your recovery this is CWM or TWRP recovery.img, not stock recovery.img that is came with phone because you reflashed original one with TWRP or CWM and official ROM need official recovery.img. I hope that you make nandroid backup before root with TWRP or CWM because is it "must to do" in every installation guide. If so, when you wanted to update via OTA for official JB you needed to:
1. reverse to stock software (for you, you needed only to unroot or use nandroid backup if you have yours, if not try to find one in xda one x forum matching your current CID and main-version)
2. reverse to stock recovery.img that is matching your CID (exact matching) (you need to find it on xda one x forum section) - i see that you have firmware folder but dont know is it from your backup or from OTA, if it is from OTA than you can use recovery.img from that folder to flash stock recovery.img via fastboot commands (only recovery.img)
3. then you can do official JB update via OTA
And then if you have need to custom ROM you need flash again CWM or TWRP recovery.img
Also you can get full stock with RUU but RUU must fully match your CID and main version, but RUU isn't available for every phone version, and after RUU you can do officall OTA JB update (for RUU you need to lock bootloader)
Information that can help us is yours phone current main version (fastboot getvar version-main)
Click to expand...
Click to collapse
Thanks for your help! I got the an RUU, after that I sent my backup to SD and now I have 4.0.4.
Now my phone show me a message to install the OTA to 4.1.1, but when I select install the phone make a reboot and show me CWM recovery with the message:
Finding update package...
E:unknown volume for path [INTERNALSDCARDownload/OTA_ENDEAVOR_U_JB_S_BSTR_ESN_3.14.515.36-2.17.515.1....
E:Can't mount INTERNALSDCARD...
Installation aborted.
Why the phone can't mount the SD?
You need a stock recovery. Do :
Fastboot getvar version-main
And post the outcome !
Edit :
4.0.4 software....you need this recovery and then install the ota again
http://db.tt/U5CK4noo
Mr Hofs said:
You need a stock recovery. Do :
Fastboot getvar version-main
And post the outcome !
Edit :
4.0.4 software....you need this recovery and then install the ota again
This is the result:
C:\CustomRUU>Fastboot getvar version-main
version-main: 3.14.515.36
So... I just need to install the recovery that you send me, reboot and try to install the OTA?
Click to expand...
Click to collapse
Mr Hofs said:
You need a stock recovery. Do :
Fastboot getvar version-main
And post the outcome !
Edit :
4.0.4 software....you need this recovery and then install the ota again
Click to expand...
Click to collapse
THANKS HOFS!!!
After installing the stock recovery 2.17, JB was installed successfully.
You have no idea how much appreciate your help!
Thank you!!!!
Hello All,
So I recently bought a M8 and I just need some help in getting the steps nailed down correctly. Be warned long post with lots of questions...
Code:
fastboot getvar version-main
version-main: 3.32.111.3
fastboot oem readcid
(bootloader) cid: T-MOB101
That is basically my device, now due to it being 4.4.4 from factory I am unable to use Sunshine & Weaksauce. I could wait until the new year but why
bother .
First step:
Get my factory firmware image after reading this thread: http://forum.xda-developers.com/showthread.php?t=2701376 due to it being a T-Mobile and
Germany and 4.4.4 I am unable to run the command listed there to get the stock recovery, so how do I get the stock recovery for my device? @BerndM14
Has provided me with a link to download the latest firmware for my device but it has the TWRP recovery inside it, link is this one: http://www.handy-
faq.de/forum/htc_one_m8_custom_roms/304821-htc_one_m8_firmwaresammlung_ruus_otas_backups.html#post2832636. I should point out that I do have a OTA
waiting to download and install, should I download and install it? The version listed on the screen is 3.32.111.9 and is only 183.73MB. Would it have a
viable stock recovery? Can I downgrade to a older version for the stock recovery?
Second step:
Once the above is done and dusted my next step is getting root & S-OFF & custom recovery. This is relatively simple because all I need to do is visit
HTCDev, unlock and then S-OFF with Sunshine and then a custom recovery. Correct? Sounds and looks simple enough.
Third step:
Download ROM of choice and flash away. So I am going with InsertCoin due to user loyalty from the Desire days . However I see people in the thread
mentioning that they flashed the latest firmware to sort out a couple of issues, I take it they mean the ROM file and not HTC firmware?
Fourth and probably not needed step:
Changing the phone to WWE and SuperCID? Do I really need to do this? Benefit of changing to WWE is changing the HBOOT to a more universal one? The
reason why I am thinking of converting is because I would want to get rid of the red text on the boot screen as listed here: http://forum.xda-
developers.com/showpost.php?p=51744965&postcount=1 however for T-Mobile Dutch the HBOOT CIDS are T-MOB003, if I flash that would it cause a problem?
I would also be looking at running the commands to change the flags showing tampered and unlocked but that looks simple to do. Am I missing anything? For warranty purposes I would use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2710735 but download the recovery file for T-MOB Germany instead?
Thank you for reading the long post and I hope that I have made some sort of sense.
Yes it will have the firmware.zip with the recovery.img inside it. Even the small 47MB or so, OTA update for the WWE from 2.22.401.4 - 2.22.401.5 had the firmware.zip inside. So just download the OTA.zip copy to PC extract firmware.zip and grab the recovery.img.
Benefits to converting to WWE or even Developer edition also includes the fact that those devices will receive OTA updates before any carrier version, directly from HTC. It's a bonus if you're into the "latest & greatest" scene.
As for making a backup before flashing custom recovery, have you tried booting the custom recovery? Philz will probably be better if you want to use the booted custom recovery to make a backup of stock recovery. You could also try and boot either TWRP or Philz and see if you can root your device without flashing custom recovery, that way you can at least use the dd command to grab a copy of the recovery block. <My preferred method, though it's a terrible circle. Need to flash custom recovery to root, need root to make backup of stock recovery... So hopefully booting the custom recovery will work. That being said, easiest way still remains to grab it from the OTA.zip.
Perhaps you could even upload a copy of the OTA.zip and share it on here, I don't think the OP has a copy in the second post
ROM/Firmware. You need the latest firmware to run the latest ROM. For most it'll be firmware with 3.x. If you still run on 2.x(which you aren't) you'd have some problems with radio(bluetooth, gps, wifi, data etc)
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)
Click to expand...
Click to collapse
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
Hm, yeah I also had some problems booting a recovery, but I just tested it out again. I can at least boot TWRP version 2.8.3.0 so it still works for me. I'm on 3.28.1540.5 (Developer edition). Haven't tried Philz though, net a bit too slow to bother with even a small download
No problem. I am busy downloading the OTA.zip and once complete I will try the toolkit method and see what happens . Again, thank you for the reply.
I need some help... My phone seems to be stuck in fastboot mode and is not picked up in Device Manager of Windows. I can touch the fastboot screen and it vibrates but it does not nothing. I have held down the power button for 20 seconds with no result. I had just unlocked the bootloader and then tried pushing the Philz recovery image to the device with the command line:
Code:
C:\android\sdk\android\platform-tools>fastboot boot philz_touch_6.57.8-m8.img
downloading 'boot.img'...
OKAY [ 1.541s]
booting...
OKAY [ 0.002s]
finished. total time: 1.547s
*edit*
Holding volume up + power for 10 seconds helped *whew*...
Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
You don't need S-Off to root, just the unlocked bootloader, custom recovery, and superuser.
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Anakha56 said:
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Click to expand...
Click to collapse
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635
oops sorry.. i see you already been their
your hboot 3.19 will prevent booting to recovery ... and no TWRP doesn't backup stock recovery
you just need to find the OTA.zip for your version it must be out their somewhere
@clsA I have the file
3.32.111.3 - TWRP
Click to expand...
Click to collapse
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
Click to expand...
Click to collapse
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
it should work, recovery does not have to be exact just close
and the file you have doesn't include TWRP .. it was created with twrp ... big difference
Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
You can use any 3.32 based stock recovery for your phone. There are plenty of backups for that on this thread. No need to backup your own.
Thank you guys! That helps me a lot! Off I go to flash a custom recovery .
a friend rooted my phone tellng me how good it is and now he says hes wiped the os and root off so if anyone can help i would be gratefull
I have tried tried to find the right ruu and use all in one tools but it says 12 signiture verification error
please. if you could point me in the right direction
Okay, I'll do my best to guide you through this. We'll start with the unlock.bin that would have been obtained through the HTC developers website. Do you have it?
mrme01 said:
Okay, I'll do my best to guide you through this. We'll start with the unlock.bin that would have been obtained through the HTC developers website. Do you have it?
Click to expand...
Click to collapse
yes i have it
stephenp412 said:
I have tried tried to find the right ruu and use all in one tools but it says 12 signiture verification error
Click to expand...
Click to collapse
Did you relock the bootloader (this is required to RUU if s-on)?
If you did, than its not the right RUU.
Restore the nandroid if available (and this should always be the first thing that is done after installing custom recovery).
Another approach, if the bootloader is still unlocked, is to put a ROM on a removable SD card (using a computer and card reader), insert into the phone, and just flash the ROM from TWRP.
What CID?
What hboot number?
S-on or s-off?
my cid is 02-001 and i tried loads of ruu's but signiture fail
relocked
hboot / 3.16.0.0000
s-on
stephenp412 said:
relocked
hboot / 3.16.0.0000
s-on
Click to expand...
Click to collapse
You need to re unlock the bootloader, install proper TWRP, restore stock 1.54.206.10 backup and install its stock recovery and do OTA to the latest before you can install most of the Sense based custom ROM on XDA.
Give me a few minutes, I'll put up link to download the backup in this thread :
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You need to read :
post #1 : How-to
post #2 : to download the stock 1.54.206.10 TWRP backup
post #3 : to download the stock 1.54.206.10 recovery image
stephenp412 said:
my cid is 02-001 and i tried loads of ruu's but signiture fail
Click to expand...
Click to collapse
You can't just run any RUU. The RUU needs to match your CID. I don't think O2 has RUUs. So you can run RUUs until the world ends, and they still won't work.
Basd on that, I suggest following the previous comment to unlock the bootloader again. From there, flash TWRP, then flash a ROM or stock nandroid (either put it on a removable SD or use adb push).
can anybody link me to a rom to flash with twrp
stephenp412 said:
can anybody link me to a rom to flash with twrp
Click to expand...
Click to collapse
It's not easy to find a ROM for hboot 3.16.0000, there are some but it's bit tricky to find one. Maybe someone else can help you with custom ROM.
I can only help with TWRP backup - and I already put up link in the thread that I gave earlier.
So it's up to you how you want it.
stephenp412 said:
can anybody link me to a rom to flash with twrp
Click to expand...
Click to collapse
Try a 4.4.2 ROM (there are a couple in the Development section - but as mentioned not many). You'll have trouble with anything newer, due to outdated firmware (hboot, etc.).
img file
ckpv5 said:
You need to re unlock the bootloader, install proper TWRP, restore stock 1.54.206.10 backup and install its stock recovery and do OTA to the latest before you can install most of the Sense based custom ROM on XDA.
Give me a few minutes, I'll put up link to download the backup in this thread :
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You need to read :
post #1 : How-to
post #2 : to download the stock 1.54.206.10 TWRP backup
post #3 : to download the stock 1.54.206.10 recovery image
Click to expand...
Click to collapse
hi i have put the img file in the twrp/backups/serialno on my sd is that correct
Before I begin, I have already read through a lot of the guides but almost of all them are not updated enough for my case. If I am wrong please direct me to it.
I would like to restore AT&T stock rom on my phone which was previously converted to GPE Lollipop 5.1 (with root, bootloader unlocked and s-off).
Here's what I have already done.
Restored MID and CID to 0P6B12000 and CWS__001 (for AT&T) respectively.
Relocked the bootloader.
Restoring from a nandroid (before going GPE) fails.
Downloaded the most latest RUU file for AT&T model, and ran the process.
But RUU fails with error 155. And after reading online, any of the following could be cause of the problem.
Partition size difference in GPE and AT&T stock rom.
Difference in firmware version or may be HBOOT version.
GPE is lollipop 5.1 and I think AT&T's latest rom is 5.0.1. So may be this downgrade is causing the problem
The RUU file I was using: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
I think my first step would be to flash some correct firmware to be able to successfully run RUU, but I don't know how which one. Plus, will downgrading firmware cause problems?
I would appreciate any help in resolving this problem. At minimum, I would like to be able to flash some stock rom with all the sense and AT&T stuff.
My responses below in red font:
lief.erl said:
I would like to restore AT&T stock rom on my phone which was previously converted to GPE Lollipop 5.1 (with root, bootloader unlocked and s-off).
Here's what I have already done.
Restored MID and CID to 0P6B12000 and CWS__001 (for AT&T) respectively. correct
Relocked the bootloader. Not required, since you are s-off. Just making more work for yourself needlessly.
Restoring from a nandroid (before going GPE) fails. No way this would ever work. nandroid is just a backup of ROM and user data. Since the partition sizes are different, the Sense ROM won't fit on the system partition, and failure is a certainty. You need to re-partition via firmware/RUU.
Downloaded the most latest RUU file for AT&T model, and ran the process.
But RUU fails with error 155. And after reading online, any of the following could be cause of the problem.
Partition size difference in GPE and AT&T stock rom. This is most likely the cause.
Difference in firmware version or may be HBOOT version. Only a "downgrade of hboot is prohibited (trying to flash the same or higher number hboot is ok), and that is with s-on. Downgrade is even allowed with s-off.
GPE is lollipop 5.1 and I think AT&T's latest rom is 5.0.1. So may be this downgrade is causing the problem This also would not matter with s-off. Downgrades are ok
The RUU file I was using: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
I think my first step would be to flash some correct firmware to be able to successfully run RUU, but I don't know how which one. Plus, will downgrading firmware cause problems?
Click to expand...
Click to collapse
Find the 4.28.502.1 firmware zip and flash it in fastboot first. Then flash the RUU.
Some folks have been able to just RUU to get back to the Sense partition scheme. But many folks have to flash the firmware first, then RUU. Not sure why folks have different experiences.
redpoint73 said:
My responses below in red font:
Find the 4.28.502.1 firmware zip and flash it in fastboot first. Then flash the RUU.
Some folks have been able to just RUU to get back to the Sense partition scheme. But many folks have to flash the firmware first, then RUU. Not sure why folks have different experiences.
Click to expand...
Click to collapse
Thanks a lot.
Before I proceed, I have following questions.
How do I make sure that a RUU and the suggested firmware are compatible. Should I be looking at some thing in particular.
I was also curious about how do we decide which firmware to flash?
One again, thanks.
lief.erl said:
Before I proceed, I have following questions.
How do I make sure that a RUU and the suggested firmware are compatible. Should I be looking at some thing in particular.
I was also curious about how do we decide which firmware to flash?
Click to expand...
Click to collapse
You want the firmware that matches the RUU, they will have the same number (4.28.502.1).
The firmware was posted here: http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
redpoint73 said:
You want the firmware that matches the RUU, they will have the same number (4.28.502.1).
The firmware was posted here: http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
Click to expand...
Click to collapse
Looks like there are three[4.28.502.1] different firmware files.
4.28.502.1 OTA.ZIP
4.28.502.1 TWRP backup
4.28.502.1 Firmware
None of them say they are mirrors (ones which are have "mirror by" as prefix), so I am assuming some difference. Which one should I go with.
BTW, is it possible to go back to earlier android os, for example kit kat. I am asking this because going back might mean downgrading firmware.
lief.erl said:
Looks like there are three[4.28.502.1] different firmware files.
4.28.502.1 OTA.ZIP
4.28.502.1 TWRP backup
4.28.502.1 Firmware
None of them say they are mirrors (ones which are have "mirror by" as prefix), so I am assuming some difference. Which one should I go with.
Click to expand...
Click to collapse
Those aren't all firmware. Just the one that says "firmware" is firmware.
OTA.zip is the actual official OTA form AT&T, which would only work if you were on the Sense version directly preceding this update (so this is to go from stock Sense 3.42 > 4.28), and also stock recovery.
TWRP backup is just a backup of the ROM, and doesn't include firmware. Obviously, restore with TWRP as you would your own TWRP backup.
lief.erl said:
BTW, is it possible to go back to earlier android os, for example kit kat. I am asking this because going back might mean downgrading firmware.
Click to expand...
Click to collapse
Sure, you would just need the RUU for the desired version, and the matching firmware.
Downgrading firmware is only prohibited with s-on (version check prevents it).
You can find the RUUs here: http://forum.xda-developers.com/showthread.php?t=2751432
Some of the unmodified firmwares can be found at the bottom of the 1st post of the following thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
Those aren't all firmware. Just the one that says "firmware" is firmware.
OTA.zip is the actual official OTA form AT&T, which would only work if you were on the Sense version directly preceding this update (so this is to go from stock Sense 3.42 > 4.28), and also stock recovery.
TWRP backup is just a backup of the ROM, and doesn't include firmware. Obviously, restore with TWRP as you would your own TWRP backup.
Sure, you would just need the RUU for the desired version, and the matching firmware.
Downgrading firmware is only prohibited with s-on (version check prevents it).
You can find the RUUs here: http://forum.xda-developers.com/showthread.php?t=2751432
Some of the unmodified firmwares can be found at the bottom of the 1st post of the following thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
Do you know which version of android os will ruu 1.58.502.1 install?
Some guides say to rename the firmware file to SOMETHINGfirmware.zip, while others say to rename to 0P6BIMG.zip. Does it depend on how I am flashing. For the first one I will flash using fastboot, and for the other one I will flash by putting the file on the sd card.
lief.erl said:
Do you know which version of android os will ruu 1.58.502.1 install?
Click to expand...
Click to collapse
Android 4.4.2
Software 1.x = Android 4.4.2
2.x = 4.4.3
3.x = 4.4.4
4.x = 5.0
lief.erl said:
Some guides say to rename the firmware file to SOMETHINGfirmware.zip, while others say to rename to 0P6BIMG.zip. Does it depend on how I am flashing. For the first one I will flash using fastboot, and for the other one I will flash by putting the file on the sd card.
Click to expand...
Click to collapse
Yes, it depends on how you flash (fastboot vs. putting file on the phone).
redpoint73 said:
Android 4.4.2
Software 1.x = Android 4.4.2
2.x = 4.4.3
3.x = 4.4.4
4.x = 5.0
Yes, it depends on how you flash (fastboot vs. putting file on the phone).
Click to expand...
Click to collapse
I am sorry to bother you again, but I can't seem to find RUU and a firmware for android 4.4.2 for AT&T.
The closest thing I have found is http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
which is a bootable zip.
I am trying to avoid using any method other than official RUU.
lief.erl said:
I am sorry to bother you again, but I can't seem to find RUU and a firmware for android 4.4.2 for AT&T.
The closest thing I have found is http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
which is a bootable zip.
I am trying to avoid using any method other than official RUU.
Click to expand...
Click to collapse
Link to the 1.58 RUU is in my Index thread, which I indicated in Post #6 above (1st link).
On my Index thread, under RUUs, its the 1st link under "Official" RUUs.
I'll see if I can find the firmware zip for that RUU.
EDIT: Here you go: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F502%2F
Linked from here (so you know its a reliable XDA source): http://forum.xda-developers.com/showthread.php?t=2696282
redpoint73 said:
Link to the 1.58 RUU is in my Index thread, which I indicated in Post #6 above (1st link).
On my Index thread, under RUUs, its the 1st link under "Official" RUUs.
I'll see if I can find the firmware zip for that RUU.
EDIT: Here you go: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F502%2F
Linked from here (so you know its a reliable XDA source): http://forum.xda-developers.com/showthread.php?t=2696282
Click to expand...
Click to collapse
One last question (I think), how do I determine what should be the name of the firmware zip, if I am going to be flashing from PC.
lief.erl said:
One last question (I think), how do I determine what should be the name of the firmware zip, if I am going to be flashing from PC.
Click to expand...
Click to collapse
I actually do not think it matter, as long as its a zip.
Some instructions will say firmware.zip. Others will call it something else, such as the specific file name including software number. And in fact, this guide says: fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
If you look at the syntax of the command, its simply flashing a zip and not even specific to firmware: "fastboot flash zip blahblahblah.zip" and its what is inside the zip that determines what is being flashed to what partition on the phone.
Just make sure if you rename the file, that you don't have the Windows option enabled to hide file extensions. Otherwise you may name the file firmware.zip.zip and not realize it. This is a common error, since hiding the file extensions is typically enabled by default in Windows.
redpoint73 said:
I actually do not think it matter, as long as its a zip.
Some instructions will say firmware.zip. Others will call it something else, such as the specific file name including software number. And in fact, this guide says: fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
If you look at the syntax of the command, its simply flashing a zip and not even specific to firmware: "fastboot flash zip blahblahblah.zip" and its what is inside the zip that determines what is being flashed to what partition on the phone.
Just make sure if you rename the file, that you don't have the Windows option enabled to hide file extensions. Otherwise you may name the file firmware.zip.zip and not realize it. This is a common error, since hiding the file extensions is typically enabled by default in Windows.
Click to expand...
Click to collapse
Thanks for all the help, but this method didn't work for me. After I was successful in flashing older firmware, M8 refused to the go in the the actual android os which is required for RUU (.exe) to work its magic (needs adb). May be because older firmware and latest OS (GPE 5.1) weren't compatible with each other. So I ended up using a bootable RUU with excellent result. Though the deed is done and I have returned the phone (Color banding was too much bear), I am curious whether it would have worked if adb was enabled inside TWRP.
lief.erl said:
Thanks for all the help, but this method didn't work for me. After I was successful in flashing older firmware, M8 refused to the go in the the actual android os which is required for RUU (.exe) to work its magic (needs adb). May be because older firmware and latest OS (GPE 5.1) weren't compatible with each other. So I ended up using a bootable RUU with excellent result. Though the deed is done and I have returned the phone (Color banding was too much bear), I am curious whether it would have worked if adb was enabled inside TWRP.
Click to expand...
Click to collapse
You can RUU with the phone in fastboot mode as well as booted into the OS. The only difference with booted into OS, is that the RUU will reboot into fastboot anyway. RUU will not work in TWRP (with adb enabled).
And yes, running "newer" version of OS with older firmware will result in issues. Extreme long boot times (and broken WiFi) are the most common issues. So its possible the phone would have booted eventually (just taking a really long time, and not completely "stuck").
Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
@Flippy498 maybe you have an idea? You have so much knowledge on this!
I haven't seen a 4.x RUU for the SKU 401, yet. You therefore would need to flash one of Sneakyghost's 3.x firmware packs before you're able to use a 3.x RUU, again. The encryption key changed between firmware 3.x and 4.x. Therefore you can't use 4.x RUUs on firmware 1.x to 3.x and vice versa.
In contrast to the flashing command the command for booting TWRP via fastboot needs to be used while the phone is booted to the bootloader instead of the download mode. However, since I haven't seen a publicly available TWRP backup for the latest 401 firmware, yet, TWRP won't help you much in your situation. (Or do you have your own backup?)
That means on the other hand that you currently need to downgrade to 3.35.401.12 and to re-install the OTAs for 3.35.401.32 and 4.14.401.7 since the latest RUU is for version 3.35.401.12.
Edit: Oh, and the only RUU.exe for SKU 401 that I know is for that 1.x firmware wird the 17 at the end. You shouldn't use that one. The corresponding OTA only got distributed for one single CID (I forgot which one it was). That means that you won't receive OTAs if you aren't using that specific CID on your phone. That means you would need to flash another RUU afterwards for getting away from that firmware version. And instead of flashing two RUUs you could save some time and directly flash the second one.
Sent from my HTC One M9 using XDA Labs
mrsmtt said:
Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
Click to expand...
Click to collapse
1 - Try 0(zero)PJAIMG and not O
2 - Restore to stock recovery
3 - Start phone in download mode and push volume UP
benshoes said:
1 - Try 0(zero)PJAIMG and not O
Click to expand...
Click to collapse
Oh, I missed that typo.
benshoes said:
2 - Restore to stock recovery
Click to expand...
Click to collapse
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Flippy498 said:
Oh, I missed that typo.
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Click to expand...
Click to collapse
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
mrsmtt said:
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
Click to expand...
Click to collapse
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Flippy498 said:
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Click to expand...
Click to collapse
Thanks for your support! Anyway i'm going to do the whole thing tomorrow.. I was reading the instructions on Sneakyghost's thread and he recommend to use his tool because it contains the htc_fastboot that works better than google's one but I don't see any option to lunch the flash zip firmware command from the tool so I decided to get the htc_fastboot.exe file and move it inside another folder (a new one) in wich i'll put both firmware and rom zip to flash. I'm saying this because i'm not 100% sure this is correct so just to clear all doubts..
Once again @Flippy498 you saved me and I say thank you a million times I promise i'll take a break at trying to destroy my m9 so you'll definitely not hear me / see me here anymore hehe