Okay so here is my issue. I'm literally stuck! I have no computer to go back and lock my bootloader and I'm not s-off. I have no way, to my knowledge, to install the new firmware to play with the new stock roms. If anybody has any suggestion, that would be terrific!
Are you on stock rom? If yes you only need to flash stock recovery. Relocking bootloader is not needed
stathis95194 said:
Are you on stock rom? If yes you only need to flash stock recovery. Relocking bootloader is not needed
Click to expand...
Click to collapse
How would I go about flashing stock recovery?
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
stathis95194 said:
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
Click to expand...
Click to collapse
I did it from a computer at work. I no longer have that job though. So I'm seriously stuck.
Surely, you know someone with a computer that they will let you use?
redpoint73 said:
Surely, you know someone with a computer that they will let you use?
Click to expand...
Click to collapse
This ^^^^
alright, here's an update. i went to my fiances house and used her mothers computer (worlds slowest internet, i think AOL is faster) and worlds oldest computer ... anyways... i locked my bootloader and flashed a stock recovery, i went back to my stock rom as well and checked the software update from AT&T (which said that I had an update before i did all this) but now when i check for an update it says that i'm currently up to date and when i check information from online and compare it to my information i can confirm that I am on 1.58 but i'm android 4.4.2 and VIPER calls for a stock firmware of 4.4.3 (i think) also i can't find anywhere online on information on what the current radio is of the newest update. i'm trying to make sure that everything that I have is current to date. I don't want to be outdated lol . anways , i'm trying to figure out how to run viper with the current firmware that they require. thank you for any help you can give me now
EDIT : i bought this phone about 3 months ago and i HAVENT made any updates since then. i rooted it as soon as i got it. so im not sure if i am up-to-date
PureLife90 said:
also i can't find anywhere online on information on what the current radio is of the newest update. i'm trying to make sure that everything that I have is current to date. I don't want to be outdated lol .
Click to expand...
Click to collapse
Radio associated with software 1.58 (latest software before the new 2.23 now rolling out) is: 1.16.21331931.LA11G_20.31A.4145.02L
But in any case, the RUU for 2.23 is now available. So you can just run the "official" RUU: http://www.htc.com/us/support/htc-one-m8-att/news/
Or the bootable version (no PC required) here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Just relock the bootloader (since you are s-on) and run the RUU. It doesn't matter if anything on the device is not updated, as RUU contains the complete image. Just backup your personal data, as it will be wiped.
stathis95194 said:
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
Click to expand...
Click to collapse
If he was rooted he could have restored the stock recovery without a PC pretty easily.
There used to be a command flash_image in the terminal emulator(Need to download binary for it I think). Don't know if it still works or not though
flash_image recovery /path-to-image/name_of_recovery.img
Even then there is always the "dd" command to use.
Download recovery file to phone, if it's zipped then uzip it and move the recovery.img file to /sdcard/ - Can use ES File explorer or Root explorer.
Open Terminal Emulator.
Type:
su - to get # if you don't have it.
cat /proc/emmc - this will dump all the partition info in the terminal, look for recovery. WWE should all be mmcblk0p43 , just make sure either way.
When you have the partition number for recovery go and type:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p43 - that's it.
You just "flashed" back stock recovery. No PC required.
Related
Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.
Just flash the RUU, update OTA and reroot.
Alright, will do and I'll let you know how it goes. Thanks
Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.
MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!
dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.
Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !
That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?
So, I got notification saying the new update is ready, I downloaded it clicked OK, rebooted the phone and said entering the recovery but it went directly to TWRP recovery ( previously I have unlocked bootloader and rooted my system and installed custom recovery)
So my question is how do I install this latest update ?
MJ999 said:
So my question is how do I install this latest update ?
Click to expand...
Click to collapse
Not wanting to hijack the OP, but I'm trying to install update version 3.28.401.6 on an unlocked UK M8 and I'm in the exact same boat. I heard that the stock recovery for the M8 is different for different providers, so not sure now feasible it is to restore stock recovery to receive the OTA, then go back to TWRP. Is there a way to manually install the update using TWRP?
MJ999 said:
So, I got notification saying the new update is ready, I downloaded it clicked OK, rebooted the phone and said entering the recovery but it went directly to TWRP recovery ( previously I have unlocked bootloader and rooted my system and installed custom recovery)
So my question is how do I install this latest update ?
Click to expand...
Click to collapse
So you title the thread with your own solution as well. "Cannot install update due to recovery change..." How do I install this update? "
Obviously it would mean you have to have stock recovery, not twrp.
Flash a stock recovery, reboot, install OTA update. Custom recovery can then be reflashed after the update
BerndM14 said:
So you title the thread with your own solution as well. "Cannot install update due to recovery change..." How do I install this update? "
Obviously it would mean you have to have stock recovery, not twrp.
Click to expand...
Click to collapse
hin
Is there any way to install the eye update from twrp itself ?
This is an update file right, like zip where we can flash from twrp ?
The thing is I cannot find the stock recovery for my model 2.23.118.3
Edit : Found stock recovery of my phone
Huge thanks to @vm54 fore uploading it
Peggy1104 said:
Flash a stock recovery, reboot, install OTA update. Custom recovery can then be reflashed after the update
Click to expand...
Click to collapse
The thing is I cannot find the stock recovery for my model 2.23.118.3
I dont want any recovery just my stock
MJ999 said:
hin
Is there any way to install the eye update from twrp itself ?
This is an update file right, like zip where we can flash from twrp ?
The thing is I cannot find the stock recovery for my model 2.23.118.3
The thing is I cannot find the stock recovery for my model 2.23.118.3
I dont want any recovery just my stock
Click to expand...
Click to collapse
If flashing stock recovery is too much of a hassle perhaps you shouldn't have started flashing in the first place, yes?
You won't be able to do OTA over TWRP, even the TWRP developers said as much.
Official Updates and TWRP
Excerpt: Installing official updates from your manufacturer or carrier is not supported by TWRP.
Period.
As for the stock recovery you need. Just copy the OTA.zip file to your PC and extract the recovery.img file within the firmware.zip file.
BerndM14 said:
If flashing stock recovery is too much of a hassle perhaps you shouldn't have started flashing in the first place, yes?
As for the stock recovery you need. Just copy the OTA.zip file to your PC and extract the recovery.img file within the firmware.zip file.
Click to expand...
Click to collapse
Yes, the main reason I unlocked my bootloader ..... was just for HK mod but then only I realized that my phone is S-ON and S-OFF is only possible using sunshine.
Ok now I have the recovery.img file for my phone.
What should I do with it ?
Using hassoon2000's toolkit select 'your own recovery' and flash that's it ?
And one more question my CIDnum is t-mob009
Does that mean my mobile is tmobile based ?
In my place we have only two carriers and we don't have tmobile,sprint or verizon here.
EDIT : @mroshaw I hope you got your answer from the post #6
EDIT 2 : @BerndM14 just flashed the stock recovery and updated my phone and happy with it
Thanks for helping me mate
Good Luck
Awesome, good stuff. This will definitely help me out too.
Can I ask one quick follow up - where on the phone is OTA.zip stored? I have Root Explorer so just a matter of knowing where to look.
mroshaw said:
Awesome, good stuff. This will definitely help me out too.
Can I ask one quick follow up - where on the phone is OTA.zip stored? I have Root Explorer so just a matter of knowing where to look.
Click to expand...
Click to collapse
In the download folder. /sdcard/Download
BerndM14 said:
In the download folder. /sdcard/Download
Click to expand...
Click to collapse
Brilliant, thank you so much mate! Copied that down to my PC, flashed the recovery.bin and the update applied itself just fine! Restored TWRP and I'm back in business.
Really appreciate the help from you and the OP - great stuff!
mroshaw said:
Brilliant, thank you so much mate! Copied that down to my PC, flashed the recovery.bin and the update applied itself just fine! Restored TWRP and I'm back in business.
Really appreciate the help from you and the OP - great stuff!
Click to expand...
Click to collapse
K, enjoy. :good:
Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api
would i be able to just flash this if i wanted to with twrp. just curious.
Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
dang. okay
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
do we just flash in twrp? Thank you by the way
No it's a stock ota you have to use HTC recovery.
rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted
Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.
Radio
Any chance someone can please post a flashable zip with the new t-mo radio?
Where would I get the stock recovery for this fw and update. I want to root but keep my ota
Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.
rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.
ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?
Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !
Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
Is this ok to install on the US variants?
Sent from my iPhone using Tapatalk
From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?
What version is this from?
hey bro did you have the flashligt icon and gesture in the new update?
Anyone flashed this with flash fire?
How to install on rooted devices???
sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
You didn't tell us what variant of the phone you have
How to install???
zimplemeh said:
Is this ok to install on the US variants?
Click to expand...
Click to collapse
No this is not recommended to install on US variant
saqlainrattansi said:
From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?
Click to expand...
Click to collapse
Yes you got it right
olive23 said:
What version is this from?
Click to expand...
Click to collapse
It's from build number *67
Jayesh Nirve said:
How to install???
Click to expand...
Click to collapse
Either use stock recovery or use Flashfire
zeft64 said:
You didn't tell us what variant of the phone you have
Click to expand...
Click to collapse
Indian Variant
Flash fire ain't working phone just reboots with no changes
can i install on retbr?
I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.
Pls tell me how u went back to 15 plsss
Aredhelelen said:
I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.
Click to expand...
Click to collapse
Exactly what I have been trying to tell. There is a fingerprint mismatch that happens. On a side note how did you manage to take yourself back from .35 to .15 and then update to .67. I get the last part, but downgrading with a higher bootloader; and where did you get the .15 build
You can simply install one of the stock versions already posted here in the forum, I just downloaded the .15 and installed it again via fastboot with the command lines (also explained in that post, in comments) like any other stock rom. Then, after starting the phone you must activate USB debbuging mode to be able to use ADB commands, so you can restart the phone in stock recovery and activate the push ota update via ADB.
Anyway, if this sounds complicated I think there is already a flashable .zip to apply ota, you can give it a try.