Hy guys, i hope someone can help me with this one.
I try the other days to root my phone, and all got smoth, then i update my firmware because WiFi will not work and i read somewhere that will be problem. And i update my firmware too, all was good, everything instaled sucefull but when i try to open it stay blocked on main screen. How to make more clear than that? The phone freeze where the HTC logo appear, i can't do anything more than that.
Some info i can get from fastboot:
*** Software status: Modified ***
*** RELOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-3.11.1700.5
eMMC- boot 2048MB
I think when i installed the firmware the proces delete everything on my phone, i dont have recovery or anything else. Can someone help please to restore to stock? Or at least to a soft that my phone to work?
Thanks! (And sorry for my bad english, not my first language)
pant3ras said:
Hy guys, i hope someone can help me with this one.
I try the other days to root my phone, and all got smoth, then i update my firmware because WiFi will not work and i read somewhere that will be problem. And i update my firmware too, all was good, everything instaled sucefull but when i try to open it stay blocked on main screen. How to make more clear than that? The phone freeze where the HTC logo appear, i can't do anything more than that.
Some info i can get from fastboot:
*** Software status: Modified ***
*** RELOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-3.11.1700.5
eMMC- boot 2048MB
I think when i installed the firmware the proces delete everything on my phone, i dont have recovery or anything else. Can someone help please to restore to stock? Or at least to a soft that my phone to work?
Thanks! (And sorry for my bad english, not my first language)
Click to expand...
Click to collapse
You still have KitKat firmware, as shown by your OS version. You CANNOT flash a modified firmware package while S-On. You need to either run a signed RUU, or go back to stock and use HTC's/your carrier's OTA updates.
Do you have a stock ruu? or maybe how to s-off? because i cant find anywhere firewater.
Maybe this will help with something:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
So can anybody can help me? Please i am stuck on this. And when i want to flash the RUU from AT&T i still get the error 155: Unknow Error. Can someone help me? Please.
What firmware did you try to flash? It looks like it was GPE firmware.
Is your bootloader screen black or white now?
My bootloader screen it's black, it's that important?...
And the firmware was download from HDRevolution website.
pant3ras said:
My bootloader screen it's black, it's that important?...
Click to expand...
Click to collapse
Yup, that's very important. Black hboot screen is the GPE version (and white is Sense version hboot). You at least partially flashed a GPE firmware. This isn't supposed to happen with s-on (firmware for other versions should be blocked). But I do remember a while back, a few folks having the same issue; where a GPE firmware or RUU partially flashed (with s-on) and caused some problems.
pant3ras said:
And the firmware was download from HDRevolution website.
Click to expand...
Click to collapse
That doesn't help. Quite a few firmwares are posted there. What specific number firmware did you flash? Did you flash the firmware number (3.11.1700.5) shown OS number on your hboot screen?
---------- Post added at 12:03 PM ---------- Previous post was at 12:03 PM ----------
pant3ras said:
And when i want to flash the RUU from AT&T i still get the error 155: Unknow Error.
Click to expand...
Click to collapse
What RUU (file name) are you trying to flash?
redpoint73 said:
That doesn't help. Quite a few firmwares are posted there. What specific number firmware did you flash? Did you flash the firmware number (3.11.1700.5) shown OS number on your hboot screen?
Click to expand...
Click to collapse
The firmware i flash was 3.11.1700.5 yes.
redpoint73 said:
What RUU (file name) are you trying to flash?
Click to expand...
Click to collapse
That from the official page, this one:
"RUU_M8_UL_L50_SENSE60_ATT[email protected]_40.45.C33065.00_F_release_446225_signed_2"
And also i was trying with this one:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 I dont know where exactly i find this one, but this one like the one above give me the same error, now and before trying rooting my htc.
pant3ras said:
The firmware i flash was 3.11.1700.5 yes.
Click to expand...
Click to collapse
I don't know why you flashed this. Not only is it not current firmware (Kitkat, as another noted before), but its not even for your version (its GPE version firmware, as I mentioned).
pant3ras said:
That from the official page, this one:
"RUU_M8_UL_L50_SENSE60_ATT[email protected]_40.45.C33065.00_F_release_446225_signed_2"
Click to expand...
Click to collapse
That is the proper RUU for the AT&T version; and your bootloader is relocked, as it should be for RUU.
So I think the problem is the GPE firmware you flashed before.
Try flashing the proper firmware first, then RUU again, and hopefully that will work.
I can't find the 4.28.502.2 firmware. But 4.28.502.1 firmware is posted on the following. Use the Full stock firmware. Hopefully, this is close enough to 4.28.502.2 to work.
EDIT: Forgot to post the firmware link: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
pant3ras said:
And also i was trying with this one:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 I dont know where exactly i find this one, but this one like the one above give me the same error, now and before trying rooting my htc.
Click to expand...
Click to collapse
That RUU will not work, anyway. Its for the Developer Edition, so the only way to run it would be to change your CID (s-off required, and working OS is needed to s-off).
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
pant3ras said:
or maybe how to s-off? because i cant find anywhere firewater.
Click to expand...
Click to collapse
Firewater was discontinued by its devs in December 2014. Since it has an online component (needed to connect to servers), it won't work even if you find the firewater binary.
Sunshine is the only current working s-off method, and as I mentioned, it requires a working OS to work.
redpoint73 said:
I don't know why you flashed this. Not only is it not current firmware (Kitkat, as another noted before), but its not even for your version (its GPE version firmware, as I mentioned).
Click to expand...
Click to collapse
I flash that firmware because have my cidnum and modelid, and i read that the firmware need to have the same cidnum and modelid.
redpoint73 said:
I can't find the 4.28.502.2 firmware. But 4.28.502.1 firmware is posted on the following. Use the Full stock firmware. Hopefully, this is close enough to 4.28.502.2 to work
Click to expand...
Click to collapse
Where can i find this firmware?
And i didn't know that firewater doesnt work anymore, and sunshine i think you have to pay 25$ per month, right?
pant3ras said:
I flash that firmware because have my cidnum and modelid, and i read that the firmware need to have the same cidnum and modelid.
Click to expand...
Click to collapse
Yes, firmware needs to have the same CID and MID. But the 3.11.1700.5 firmware doesn't go with your CID and MID (CWS__001 and 0P6B12000)
"1700" firmwares (such as 3.11.1700.5) are for the Google Play Edition (GPE) with CID of GOOGL001 and MID of 0P6B17000.
Proper firmwares for your AT&T CID and MID will have the number "502" in the position x.xx.502.x
pant3ras said:
Where can i find this firmware?
Click to expand...
Click to collapse
Sorry, forgot to post the link. I had the page open, and everything: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
pant3ras said:
And i didn't know that firewater doesnt work anymore, and sunshine i think you have to pay 25$ per month, right?
Click to expand...
Click to collapse
That's right. And as I already stated, sunshine requires a working OS, which you don't have. And since getting the OS working again seems to be the main reason you want to get s-off, you see its quite pointless.
redpoint73 said:
Sorry, forgot to post the link. I had the page open, and everything: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml.
Click to expand...
Click to collapse
No problem And to flash this firmware i can do it like this:
f you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse
pant3ras said:
No problem And to flash this firmware i can do it like this:
Click to expand...
Click to collapse
Yes, exactly.
redpoint73 said:
Yes, exactly.
Click to expand...
Click to collapse
I get this error when i try to flash the firmware:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1826418688 bytes
sending 'zip' (57484 KB)...
OKAY [ 2.570s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.611s
Click to expand...
Click to collapse
pant3ras said:
I get this error when i try to flash the firmware:
Click to expand...
Click to collapse
You used the "full stock" firmware 4.28.502.1, correct? Not the "Combined, No wipe" one?
You can also try the 3.42.502.1 firmware.
redpoint73 said:
You used the "full stock" firmware 4.28.502.1, correct? Not the "Combined, No wipe" one?
You can also try the 3.42.502.1 firmware.
Click to expand...
Click to collapse
Yes, i use the full stock firmware. Now i will try with 3.42.502.1
Later edit: I get the same error when i try with the 3.42.502.1 stock
pant3ras said:
Yes, i use the full stock firmware. Now i will try with 3.42.502.1
Later edit: I get the same error when i try with the 3.42.502.1 stock
Click to expand...
Click to collapse
Those might be unsigned firmwares, but I thought they were signed.
I think your options at this point:
1) Find signed firmwares of the versions I recommended.
2) Unlock the bootloader again, flash TWRP again, then flash a 3.xx based custom or stock ROM (which will have working WiFi). Then s-off by sunshine so you can fix the firmware (will allow an unsigned firmware to be flashed).
Another thing to note, when you flashed the GPE firmware, it reverted the recovery back to stock recovery. Which is why you no longer have custom recovery.
redpoint73 said:
Those might be unsigned firmwares, but I thought they were signed.
I think your options at this point:
1) Find signed firmwares of the versions I recommended.
2) Unlock the bootloader again, flash TWRP again, then flash a 3.xx based custom or stock ROM (which will have working WiFi). Then s-off by sunshine so you can fix the firmware (will allow an unsigned firmware to be flashed).
Another thing to note, when you flashed the GPE firmware, it reverted the recovery back to stock recovery. Which is why you no longer have custom recovery.
Click to expand...
Click to collapse
And how i can unlock the bootloader again? and flash the TWRP?
pant3ras said:
And how i can unlock the bootloader again? and flash the TWRP?
Click to expand...
Click to collapse
Unlock the bootloader by HTCDev.com. Then flash TWRP with fastboot.
redpoint73 said:
Unlock the bootloader by HTCDev.com. Then flash TWRP with fastboot.
Click to expand...
Click to collapse
Ok, i succed to instal the TWRP and i unlock the phone, but i have no ideea what rom to instal. Can you help me with that please? I'm scare i will broke my phone again if i install something on my own again )
Related
I just got an update.
my current ver is : 2.22.709.3
Update ver: 2.22.709.4
I have a custom recovery and root. no s-off.
How do i correctly update the phone without doing any dmg?
i know i need to download the update, extract the recovery.img, flash it so i will have the original recovery.
but do i need to unroot and lock bootloader?
Harellevy said:
I just got an update.
my current ver is : 2.22.709.3
Update ver: 2.22.709.4
I have a custom recovery and root. no s-off.
How do i correctly update the phone without doing any dmg?
i know i need to download the update, extract the recovery.img, flash it so i will have the original recovery.
but do i need to unroot and lock bootloader?
Click to expand...
Click to collapse
Sure you can download it and extract OR you can just go COLLECTION of Stock backup's and download the stock recovery. Both the 2.22.709.3 and 2.22.709.4 is in that thread.
Flash back the stock recovery and lock bootloader seeing as you're S-ON. Do the update and you can go ahead and do what you want again. You'll probably lose root yes, you can just get it back again no problem.
Edit: Not needed to relock bootloader as mentioned by ckpv5 :good: :victory:
There is no need to extract the stock recovery from the OTA, we have stock recovery 2.22.709.3 and 2.22.709.4 here : http://forum.xda-developers.com/showthread.php?t=2701376
There is no need to unroot as you will lose root anyway with the update, then you need to re-root
And most important is there is no need to lock bootloader. Leave it unlocked.
---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------
BerndM14 said:
Flash back the stock recovery and lock bootloader seeing as you're S-ON. Do the update and you can go ahead and do what you want again. You'll probably lose root yes, you can just get it back again no problem.
Click to expand...
Click to collapse
You beat me this time
But I need to correct one thing, there is no need to relock bootloader for OTA whether it's S-On or S-Off.
Relock bootloader for S-On is needed only when flashing signed htc firmware or run RUU
ckpv5 said:
There is no need to extract the stock recovery from the OTA, we have stock recovery 2.22.709.3 and 2.22.709.4 here : http://forum.xda-developers.com/showthread.php?t=2701376
There is no need to unroot as you will lose root anyway with the update, then you need to re-root
And most important is there is no need to lock bootloader. Leave it unlocked.
---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------
You beat me this time
But I need to correct one thing, there is no need to relock bootloader for OTA whether it's S-On or S-Off.
Relock bootloader for S-On is needed only when flashing signed htc firmware or run RUU
Click to expand...
Click to collapse
Ah ok, I can remember in the stock collection thread it was mentioned that we needed to relock if S-ON, I did see someone else say different but wasn't sure about it. That's cool then. :good:
another 2 really quick questions:
1 - My HTC wont go into debugging mode. i enable it, there is that little window popping and saying if i want to accept this computer, i checked "YES", and then nothing happends. even ADB Devices wont recognize.
2 - You guys recommend s-off? whenever HTC releases Android L, having S - Off would be good or bad?
BerndM14 said:
Ah ok, I can remember in the stock collection thread it was mentioned that we needed to relock if S-ON, I did see someone else say different but wasn't sure about it. That's cool then. :good:
Click to expand...
Click to collapse
Yeah ... many times people say this ... until Mr Hofs himself ask one fellow from where he got the info that need to relock bootloader for OTA
See this for example : http://forum.xda-developers.com/showpost.php?p=55148300&postcount=3
---------- Post added at 11:23 PM ---------- Previous post was at 11:19 PM ----------
Harellevy said:
another 2 really quick questions:
1 - My HTC wont go into debugging mode. i enable it, there is that little window popping and saying if i want to accept this computer, i checked "YES", and then nothing happends. even ADB Devices wont recognize.
2 - You guys recommend s-off? whenever HTC releases Android L, having S - Off would be good or bad?
Click to expand...
Click to collapse
1. make sure your ADB version is not lower than 1.0.31
2. S-Off is good and bad..
good for people who knows what he is doing
and bad for people who doesn't know what he is doing as he can easily brick his device.
When HTC release Android L... it got nothing to do with S-On or S-Off
ckpv5 said:
Yeah ... many times people say this ... until Mr Hofs himself ask one fellow from where he got the info that need to relock bootloader for OTA
See this for example : http://forum.xda-developers.com/showpost.php?p=55148300&postcount=3
---------- Post added at 11:23 PM ---------- Previous post was at 11:19 PM ----------
1. make sure your ADB version is not lower than 1.0.31
2. S-Off is good and bad..
good for people who knows what he is doing
and bad for people who doesn't know what he is doing as he can easily brick his device.
When HTC release Android L... it got nothing to do with S-On or S-Off
Click to expand...
Click to collapse
when android L will be released, guys with root and unlocked bootloader will need to relock them, unroot them and return to stock recovery and only then we could update the phone? just want know what am i against in a few months
and where can i find the OTA update in my phone?
thanks alot for all the help!!
Harellevy said:
when android L will be released, guys with root and unlocked bootloader will need to relock them, unroot them and return to stock recovery and only then we could update the phone? just want know what am i against in a few months
and where can i find the OTA update in my phone?
thanks alot for all the help!!
Click to expand...
Click to collapse
You are not reading.....it's been said 2 times at least :
1: you do NOT have to relock for an ota !
2: what you need is
- stock rom with UNMODIFIED system (root is NO issue)
- stock kernel (boot.img)
- stock recovery
Then you can update !
Hello guys, anyone knows where can I download the stock recovery 2.22.709.4? I can't find the file in the link that ckpv5 share:
"we have stock recovery 2.22.709.3 and 2.22.709.4 here : http://forum.xda-developers.com/show....php?t=2701376"
Regards.
A4ar0oN said:
Hello guys, anyone knows where can I download the stock recovery 2.22.709.4? I can't find the file in the link that ckpv5 share:
"we have stock recovery 2.22.709.3 and 2.22.709.4 here : http://forum.xda-developers.com/show....php?t=2701376"
Regards.
Click to expand...
Click to collapse
I'll give you link when I'm home in two hours
ckpv5 said:
I'll give you link when I'm home in two hours
Click to expand...
Click to collapse
Thank you ckpv5
A4ar0oN said:
Thank you ckpv5
Click to expand...
Click to collapse
No problem...
Stock recovery 2.22.709.3 : http://sourceforge.net/projects/htconem8/files/Recovery/2.22.709.3_recovery.img/download
Stock recovery 2.22.709.4 : http://sourceforge.net/projects/htconem8/files/Recovery/2.22.709.4_recovery.img/download
ckpv5 said:
No problem...
Stock recovery 2.22.709.3
Stock recovery 2.22.709.4
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR THE RECOVERY'S
I don't know if this question goes here, if not im sorry
I follow a video tutorial: how-to-get-ota-updates-on-a-rooted-htc-one-m8
to install stock recovery and get ota updates.
My HTC M8 has the cidnum: HTC__621 that's the reason that i need the stock recovery 2.22.709.4 so... I flashed the stock recovery and i get this results from adb:
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash recovery
2.22.709.4_recovery.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14480 KB)...
OKAY [ 1.375s]
writing 'recovery'...
OKAY [ 0.605s]
finished. total time: 1.983s
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.011s
but when I try to reboot in recovery mode a image with a red triangle appears on the phone.
You know what is wrong?
Best regards
A4ar0oN said:
but when I try to reboot in recovery mode a image with a red triangle appears on the phone.
You know what is wrong?
Best regards
Click to expand...
Click to collapse
It's nothing wrong, that's the stock recovery.
You're not supposed to reboot in recovery mode.
Just reboot your device, check for OTA and let the system do everything for you.
Do you have the correct stock ROM for your current firmware ?
ckpv5 said:
It's nothing wrong, that's the stock recovery.
You're not supposed to reboot in recovery mode.
Just reboot your device, check for OTA and let the system do everything for you.
Do you have the correct stock ROM for your current firmware ?
Click to expand...
Click to collapse
My htc die, the OTA was installed successfully but my htc does not start
when I press the power button the htc stuck in the htc logo
================================
I apply a NANDROID BACKUP and my htc is working perfectly again but I loose LOLLIPOP
A4ar0oN said:
I apply a NANDROID BACKUP and my htc is working perfectly again but I loose LOLLIPOP
Click to expand...
Click to collapse
How can you have lollipop when you asked for 2.22.709.4 recovery
I'm asking again ... what is your stock ROM version ?
Post result of command fastboot getvar all minus the serial no. & imei no.
ckpv5 said:
How can you have lollipop when you asked for 2.22.709.4 recovery
I'm asking again ... what is your stock ROM version ?
Post result of command fastboot getvar all minus the serial no. & imei no.
Click to expand...
Click to collapse
When I buy the HTC came with lollipop and and when I had this problem a couple of guys told me that i need the 2.22.709.4 recovery
I'm a noob sorry I don' know what is the stock rom version :silly:
This is the result of fastboot getvar all:
xxxxxxxxxxxxxxx
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 59ee16dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Regards.
A4ar0oN said:
When I buy the HTC came with lollipop and and when I had this problem a couple of guys told me that i need the 2.22.709.4 recovery
I'm a noob sorry I don' know what is the stock rom version :silly:
This is the result of fastboot getvar all:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-main: 4.24.709.2
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
Regards.
Click to expand...
Click to collapse
This is the reason why you have that problem device not booting.
You can't use a very low version recovery like 2.22.709.4, it won't work.
You can use only 4.24.709.2 recovery and nandroid backup or in case you want to go lower to do OTA again, you can use only the lowest is 4.16.709.9 recovery and nandroid backup. Cannot go more than one version lower.
Do you still have the current ROM 4.24.709.2 backup ?
What was the problem with 4.24.709.2 that you seek advise from some people who simply give wrong advise ? Yours is the latest update lollipop 5.0.2 .. remember that.
You can try the one posted here : http://forum.xda-developers.com/showpost.php?p=59953829&postcount=5068
See whether you can download it or not.
If cannot, I will see whether I have time to upload my own backup for 4.24.709.2
ckpv5 said:
This is the reason why you have that problem device not booting.
You can't use a very low version recovery like 2.22.709.4, it won't work.
You can use only 4.24.709.2 recovery and nandroid backup or in case you want to go lower to do OTA again, you can use only the lowest is 4.16.709.9 recovery and nandroid backup. Cannot go more than one version lower.
Do you still have the current ROM 4.24.709.2 backup ?
What was the problem with 4.24.709.2 that you seek advise from some people who simply give wrong advise ? Yours is the latest update lollipop 5.0.2 .. remember that.
You can try the one posted here : http://forum.xda-developers.com/showpost.php?p=59953829&postcount=5068
See whether you can download it or not.
If cannot, I will see whether I have time to upload my own backup for 4.24.709.2
Click to expand...
Click to collapse
OHHHH
I don't have any problem with 4.24.709.2 like you said I just received wrong advice
I don't have the ROM 4.24.709.2 backup, I will try to download the file with the link that you provided me, once the file was downloaded I just need to flash with TWRP is correct?
I have no idea about that backup whether it is for TWRP or CWM. But backup is for restore not flash. Unzip on PC and transfer to custom recovery backup folder. Boot to recovery then restore the transferred backup
I don't understand why you flashed the wrong stock recovery when your latest ROM has no problem.
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.9.710.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP021
Click to expand...
Click to collapse
First off, can you boot into download mode and try this? http://forum.xda-developers.com/one-m9/general/hima-stock-rom-collection-htc-one-m9-t3095746
Otherwise, your phone is effectively bricked & there isn't a known workaround so far :/ . In this case it's best that you contact your isp or htc for servicing.
As I can see you need a Vodafone Australian RUU equal or higher than your version-main number.
Unfortunately I could not find one for you.
racerboy3801 said:
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
Click to expand...
Click to collapse
try this: http://llabtoofer.com/htc-ruu-flashing-service/
Thanks for the advice guys, i've since sent it back to the shop to see what they can do. Cheers
racerboy3801 said:
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
Click to expand...
Click to collapse
you can try this thread http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
i ran across it the other day looking for my sprint ruu
racerboy3801 said:
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
Click to expand...
Click to collapse
An RUU will do the job, might not even have to be from the same region, just to get you back up and running.
You should be able to force the device into recovery if you can get to the bootloader.
From the bootloader, i'm sure you could flash a recovery and perhaps even root the device (could be wrong there)
either way there would have been a way out of it.
Yeah so i couldn't get into a recovery as i had twrp running, and i couldnt flash a new one as it was relocked. I couldn't unlock it as i had no rom to boot into to turn the unlock flag. So yeah stuck in the bootloader. It's supposed to be back tomorrow so i'll keep you guys posted.
Hello,
I got an OTA update for my HTC one but i wasnt able to install it normally. so i went into TWRP recovery and FULLY-wiped my phone(system,data,cache,dalvik). When i proceeded to install the zip, i got an error saying:
file_getprop: failed to stat "/system/build.prop": No such file or directory.
E:Error executing updater binary in zip '...'
I got the same error when i tried flashing another ROM, dirty unicorns. I tried restarting my phone and installing again WITHOUT wiping anything and still nothing. When i connect the phone to my laptop, it shows the phone as a CD DRIVE. Can someone PLEASE help me?
TWRP:2.7.0.2
**TAMPERED**
**UNLOCKED**
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA10G
eMMC-boot 2048mb
OTA updates usually cannot be updated via Custom recoveries like CWM or TWRP. I suggest you do roll back to a stock rom using TWRP backups found in the forums, flash a recent version of TWRP and then try flashing custom roms.
Suggesting that you start with updating your current TWRP to 3.0.2
what's the OTA file name and size ?
can you post the result of getvar all after removing serialno and imei
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
what's the OTA file name and size ?
can you post the result of getvar all after removing serialno and imei
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Htc on(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And the name of the file is:
OTA_M8_UL_K44_SENSE60_MR_hTC_Asia_WWE_2.22.707.4-1.54.707.7_release_387917.zip
@Younuszain
from that i see you can access fastboot
well there is no RUU for your device but there is stock firmware,stock backup and stock recovery
you need to flash the firmware then flash twrp recovery then restore the backup and flash the stock recovery
by doing that you will be completely stock
ahmed.ismael said:
@Younuszain
from that i see you can access fastboot
well there is no RUU for your device but there is stock firmware,stock backup and stock recovery
you need to flash the firmware then flash twrp recovery then restore the backup and flash the stock recovery
by doing that you will be completely stock
Click to expand...
Click to collapse
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Younuszain said:
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Click to expand...
Click to collapse
I distinctly remember that I tried flashing the Unlocked/Developer firmware from this website: http://www.htc.com/us/support/rom-downloads.html
But, i got the same error as I've stated above while flashing.
Younuszain said:
I distinctly remember that I tried flashing the Unlocked/Developer firmware from this website: http://www.htc.com/us/support/rom-downloads.html
But, i got the same error as I've stated above while flashing.
Click to expand...
Click to collapse
You can't flash that RUU. Its not for your version, its for the US Unlocked or Developer's Edition, and that specific carrier ID (CID) and Model ID (MID) only. You don't have the right CID and MID to flash that RUU.
There seems to be a notion that the particular RUU is for any unlocked M8; and that notion is completely incorrect.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
Younuszain said:
I got the same error when i tried flashing another ROM, dirty unicorns.
TWRP:2.7.0.2
Click to expand...
Click to collapse
Your hboot and TWRP versions are far too old to install or run any current ROMs.
redpoint73 said:
You can't flash that RUU. Its not for your version, its for the US Unlocked or Developer's Edition, and that specific carrier ID (CID) and Model ID (MID) only. You don't have the right CID and MID to flash that RUU.
There seems to be a notion that the particular RUU is for any unlocked M8; and that notion is completely incorrect.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
Your hboot and TWRP versions are far too old to install or run any current ROMs.
Click to expand...
Click to collapse
So You're saying if i update my TWRP version, I should be able to install any other ROM?
Younuszain said:
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Click to expand...
Click to collapse
You'll find the files and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Either flash updated firmware, the corresponding TWRP backup, as previously indicated. Or alternately, restore the TWRP backup that corresponds to your current firmware, restore corresponding stock recovery, then do multiple OTA updates to get to current firmware & software.
redpoint73 said:
You'll find the files and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Either flash updated firmware, the corresponding TWRP backup, as previously indicated. Or alternately, restore the TWRP backup that corresponds to your current firmware, restore corresponding stock recovery, then do multiple OTA updates to get to current firmware & software.
Click to expand...
Click to collapse
What if i just want to install a custom ROM, dirty unicorns?
Younuszain said:
What if i just want to install a custom ROM, dirty unicorns?
Click to expand...
Click to collapse
Update the firmware then flash the latest TWRP and flash your rom
Download the stock backup just in case you need it
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
Update the firmware then flash the latest TWRP and flash your rom
Download the stock backup just in case you need it
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Yeah but where do i find the latest firmware?! Apparently the one on the htc website corresponds only to the U.S variants. :/
Younuszain said:
Yeah but where do i find the latest firmware?! Apparently the one on the htc website corresponds only to the U.S variants. :/
Click to expand...
Click to collapse
It's the thread which redpoint link it
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
all you meed is there read to learn
Firmware section is post #5
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
It's the thread which redpoint link it
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
all you meed is there read to learn
Firmware section is post #5
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Ok So i follewed the instructions to flash the firmware and twas successful. Now my screen looks like thisThe bootloader had to be locked to flash the firmware):
**Software status: Modified**
**RELOCKED**
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
But now when i go to recovery, My screen blanks out and I get a Triangle with a red exclamation mark! So i went to FASTBOOT USB and ran:
fastboot flash recovery twrp.img
Which was given on the TWRP website. I got an error saying:
FAILED <remote: signature verify fail>
I even tried running:
fastboot oem rebootRUU
fastboot flash zip ".." for BOTH the twrp img file and the TWRP backup given in the link.
I get an error FAILED <remote: 12 signature verify fail>
I read somewhere that to flash TWRP I need to unlock the bootloader again and i have give the token on the HTCdev wesbite. But i tried registering there but i received no email from them.
What do i do now? :/
Younuszain said:
Ok So i follewed the instructions to flash the firmware and twas successful.
But now when i go to recovery, My screen blanks out and I get a Triangle with a red exclamation mark!
Click to expand...
Click to collapse
As would be expected, that is the stock recovery, which is a part of the stock/signed firmware; and therefore was installed when you flashed the stock firmware. You need to unlock the bootloader, and put TWRP back on the phone, if TWRP is what you want.
Younuszain said:
So i went to FASTBOOT USB and ran:
fastboot flash recovery twrp.img
I got an error saying:
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
This is normal, and expected. Unlock the bootloader again, either with the existing bin code, or go through the HTCDev.com process again, to get a new bin code.
You can't flash a custom recovery such as TWRP (or any other unsigned file) to recovery partition, with a locked bootloader. That is what it means to have a locked bootloader; and specifically what an unlocked bootloader allows you to do.
Younuszain said:
I even tried running:
fastboot oem rebootRUU
fastboot flash zip ".." for BOTH the twrp img file and the TWRP backup given in the link.
I get an error FAILED <remote: 12 signature verify fail>
Click to expand...
Click to collapse
Do not make up fastboot commands.Its simply a horrible idea. Unless you know exactly what you are doing you should only type in fastboot commands exactly as directed. You probably can't do any permanent damage with s-on, but you certainly can mess things up pretty well with the wrong fastboot commands.
For instance, what partition would TWRP be installing to, if you don't specify? Yeah, I don't know either. And that isn't a good thing.
Additionally, you don't seem to know what the TWRP backup file is. Its not a flashable zip. You shouldn't be flashing things, without bothering to read the instructions, and understand what they even are.
redpoint73 said:
As would be expected, that is the stock recovery, which is a part of the stock/signed firmware; and therefore was installed when you flashed the stock firmware. You need to unlock the bootloader, and put TWRP back on the phone, if TWRP is what you want.
This is normal, and expected. Unlock the bootloader again, either with the existing bin code, or go through the HTCDev.com process again, to get a new bin code.
You can't flash a custom recovery such as TWRP (or any other unsigned file) to recovery partition, with a locked bootloader. That is what it means to have a locked bootloader; and specifically what an unlocked bootloader allows you to do.
Do not make up fastboot commands.Its simply a horrible idea. Unless you know exactly what you are doing you should only type in fastboot commands exactly as directed. You probably can't do any permanent damage with s-on, but you certainly can mess things up pretty well with the wrong fastboot commands.
For instance, what partition would TWRP be installing to, if you don't specify? Yeah, I don't know either. And that isn't a good thing.
Additionally, you don't seem to know what the TWRP backup file is. Its not a flashable zip. You shouldn't be flashing things, without bothering to read the instructions, and understand what they even are.
Click to expand...
Click to collapse
Well, Thanks a lot for that info . As far as me not knowing, guess theres a first time for everything.
Could you direct me as to how to get the existing bin code to unlock the bootloader? Because i guess thats what I have to do next inorder to get my phone up and running again.
Younuszain said:
As far as me not knowing, guess theres a first time for everything.
Click to expand...
Click to collapse
My advice, is to learn by reading and understanding the guides and threads on this forum.
Do not learn by trial and error, unless you want to end up making your phone into an expensive paperweight. Don't experiment, don't make things up.
I recommend anyone wanting to mod these phones, to spend a minimum few hours reading and understanding the basic concepts, guides, etc. before doing anything. And if there is anything you don't fully understand, just come and ask, as there are plenty of folks here willing and able to help.
Younuszain said:
Could you direct me as to how to get the existing bin code to unlock the bootloader?
Click to expand...
Click to collapse
If you don't have it on your computer (and know where it is) then it can't be "retrieved".
Just go to HTCDev.com, and follow the instructions there to unlock the bootloader.
redpoint73 said:
My advice, is to learn by reading and understanding the guides and threads on this forum.
Do not learn by trial and error, unless you want to end up making your phone into an expensive paperweight. Don't experiment, don't make things up.
I recommend anyone wanting to mod these phones, to spend a minimum few hours reading and understanding the basic concepts, guides, etc. before doing anything. And if there is anything you don't fully understand, just come and ask, as there are plenty of folks here willing and able to help.
If you don't have it on your computer (and know where it is) then it can't be "retrieved".
Just go to HTCDev.com, and follow the instructions there to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the guidance. Will definitely be more careful from next time.
The Dev website isn't sending the confirmation mail though.
Younuszain said:
The Dev website isn't sending the confirmation mail though.
Click to expand...
Click to collapse
The website can be buggy. I think when I unlocked the bootloader on this or a previous HTC device, I had to use 3 different emails, before I got the confirmation email.
Hello everyone, I wanted to unroot my phone, I have read other posts on this topic but I am still confused. The getvar results of my phone are as follows:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
I bought this phone brand new locked to Rogers. I didn't want to mess anything up by downloading the wrong stock recovery. Thanks!
How is it rooted? SuperSu? Magisk?
maultasche said:
How is it rooted? SuperSu? Magisk?
Click to expand...
Click to collapse
Good question.
And also to the OP, what is the exact eason for unrooting?
maultasche said:
How is it rooted? SuperSu? Magisk?
Click to expand...
Click to collapse
It is rooted using SuperSu, and the reason for unrooting is that I have been having a few problems with the phone and want to see if unrooting will help, but it is probably just something wrong with my power button. Sometimes when I press it, the phone thinks I long pressed the power button.
SuperSu has an option in settings to unsu. There might also be a flashable zip somewhere in the Su-thread to remove SuperSu completely.
But your issue sounds like a hardware issue. I don't think unrooting will help.
maultasche said:
SuperSu has an option in settings to unsu. There might also be a flashable zip somewhere in the Su-thread to remove SuperSu completely.
But your issue sounds like a hardware issue. I don't think unrooting will help.
Click to expand...
Click to collapse
Ok I thought so but I feel like I might as well try at this point, sorta wanted to unroot it anyways. So If I got into SuperSu and click on FUll Unroot, that should be all I have to do? Won't have do anything else like follow this guide:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Because that was the most confusing part. Thanks
gurkang10 said:
Ok I thought so but I feel like I might as well try at this point, sorta wanted to unroot it anyways. So If I got into SuperSu and click on FUll Unroot, that should be all I have to do? Won't have do anything else like follow this guide:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Because that was the most confusing part. Thanks
Click to expand...
Click to collapse
That guide is for people going back on stock via TWRP if they don't have a backup at hand or want to update stock ROM and/or firmware.
It should be enough to use the unroot option in SuperSu.
maultasche said:
That guide is for people going back on stock via TWRP if they don't have a backup at hand or want to update stock ROM and/or firmware.
It should be enough to use the unroot option in SuperSu.
Click to expand...
Click to collapse
Thank you so much for your help!
maultasche said:
That guide is for people going back on stock via TWRP if they don't have a backup at hand or want to update stock ROM and/or firmware.
Click to expand...
Click to collapse
That being said, the OP is still on Lollipop firmware (and presumably stock Lollipop ROM) and it could use an update to Marshmallow (the latest/last update provided by HTC). That can be done either by restoring stock TWRP backup that was linked, then OTA update. Or will RUU.
RUU would be a complete factory re-image (although it also wipes the phone). This might eliminate the possibility that the power button issue is being caused by a software problem. Although it does sound like a hardware problem to me. I haven't heard of any similar issue being cause by software.
Ok I have one more question, I am using Android Revolution HD on my phone, do I have to do anything to get rid of that or will using the unroot option in SuperSu still be enough
redpoint73 said:
That being said, the OP is still on Lollipop firmware (and presumably stock Lollipop ROM) and it could use an update to Marshmallow (the latest/last update provided by HTC). That can be done either by restoring stock TWRP backup that was linked, then OTA update. Or will RUU.
RUU would be a complete factory re-image (although it also wipes the phone). This might eliminate the possibility that the power button issue is being caused by a software problem. Although it does sound like a hardware problem to me. I haven't heard of any similar issue being cause by software.
Click to expand...
Click to collapse
So at this point I have already lost root access by doing what the other poster suggested. If I wanted to do this would I still be able to?
gurkang10 said:
So at this point I have already lost root access by doing what the other poster suggested. If I wanted to do this would I still be able to?
Click to expand...
Click to collapse
Root isn't required to do either of the things I mentioned, no. I mentioned two different approaches:
a) Restore stock TWRP backup (then OTA update to Marshmallow): Does not require root, but requires having TWRP installed, which you should still have after unrooting.
b) RUU: this is an official HTC tool, does not require root. Just run the RUU
Method "b" is probably the more straightforward method, but would wipe all data from the phone.
redpoint73 said:
Root isn't required to do either of the things I mentioned, no. I mentioned two different approaches:
a) Restore stock TWRP backup (then OTA update to Marshmallow): Does not require root, but requires having TWRP installed, which you should still have after unrooting.
b) RUU: this is an official HTC tool, does not require root. Just run the RUU
Method "b" is probably the more straightforward method, but would wipe all data from the phone.
Click to expand...
Click to collapse
I ended up going with method "a" but when I get to flashing the stock recovery it gives me this message :
D:\platform-tools>fastboot flash recovery 4.20.631.2_recovery.img
target reported max download size of 1826418688 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.482s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.498s
gurkang10 said:
I ended up going with method "a" but when I get to flashing the stock recovery it gives me this message :
D:\platform-tools>fastboot flash recovery 4.20.631.2_recovery.img
target reported max download size of 1826418688 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.482s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.498s
Click to expand...
Click to collapse
First of all, you did all the steps up to this point? Because flashing the stock recovery is step #11 of the instructions.
Second, why did you choose 4.20.631.2? Based on the info in your top post, the current version is 4.16.401.10
So you want to restore the stock TWRP backup with that same number (4.16.401.10) and the stock recovery 4.16.401.10
redpoint73 said:
First of all, you did all the steps up to this point? Because flashing the stock recovery is step #11 of the instructions.
Second, why did you choose 4.20.631.2? Based on the info in your top post, the current version is 4.16.401.10
So you want to restore the stock TWRP backup with that same number (4.16.401.10) and the stock recovery 4.16.401.10
Click to expand...
Click to collapse
Yes I did all the steps to that point. And the reason I chose 4.20.631.2 is that this was the only one available for my original CID, which is rogers in Canada
gurkang10 said:
Yes I did all the steps to that point. And the reason I chose 4.20.631.2 is that this was the only one available for my original CID, which is rogers in Canada
Click to expand...
Click to collapse
Your original CID is irrelevant. It's gone and replaced with SuperCID 11111111. It still has the Model ID (MID) for Rogers, but I believe that will be bypassed by SuperCID (and therefore MID won't matter) when you try to install the Marshmallow update. At least that is what happens most of the time.
Restoring the 4.20.631.2 backup and corresponding stock recovery, I don't think will work. The OTA update will detect your current firmware version is 4.16.401.10, which conflicts the software and recovery versions (4.20.631.2), and the update will fail.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
gurkang10 said:
writing 'recovery'...
FAILED (remote: not allowed)
Click to expand...
Click to collapse
On the bootloader screen on the phone, does it say LOCKED, RELOCKED, or UNLOCKED near the top of the screen?
redpoint73 said:
Your original CID is irrelevant. It's gone and replaced with SuperCID 11111111. It still has the Model ID (MID) for Rogers, but I believe that will be bypassed by SuperCID (and therefore MID won't matter) when you try to install the Marshmallow update. At least that is what happens most of the time.
Restoring the 4.20.631.2 backup and corresponding stock recovery, I don't think will work. The OTA update will detect your current firmware version is 4.16.401.10, which conflicts the software and recovery versions (4.20.631.2), and the update will fail.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
On the bootloader screen on the phone, does it say LOCKED, RELOCKED, or UNLOCKED near the top of the screen?
Click to expand...
Click to collapse
It let me restore the backup with no problem.
It says locked
Ok I got it to work, just needed to unlock it again, so I downloaded SuperSu, unclocked the device, then flashed the recovery
redpoint73 said:
Your original CID is irrelevant. It's gone and replaced with SuperCID 11111111. It still has the Model ID (MID) for Rogers, but I believe that will be bypassed by SuperCID (and therefore MID won't matter) when you try to install the Marshmallow update. At least that is what happens most of the time.
Restoring the 4.20.631.2 backup and corresponding stock recovery, I don't think will work. The OTA update will detect your current firmware version is 4.16.401.10, which conflicts the software and recovery versions (4.20.631.2), and the update will fail.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
On the bootloader screen on the phone, does it say LOCKED, RELOCKED, or UNLOCKED near the top of the screen?
Click to expand...
Click to collapse
I am now going to download the 4.16.401.10 stock backup , didn't try updating my device with the other backup. So now I am going to use the backup, flash the recovery, then lock the device and lastly unroot my phone. Hopefully all goes to plan, thanks for your help
Ok so the problem I have with using the 4.16.401.10 stock backup is that I don't get LTE data now, just 4G even though my access points are correct.
anyone know where i can get the RUU for HTC10 unlocked international but nougat?.... as my firmware is nougat, i need to install the nougat RUU, so i can get the OTA to orea so i can then go to leodroid oreo .... or am i misunderstanding .... all i can find for HTC10 is oreo, can't find RUU's for nougat....
https://www.htc.com/us/support/updates.aspx
OR am i doing this all wrong .... i'm on leodroid nougat and iw ant to go to leodroid oreo, i'm S-ON but bootloader unlocked. Other websites that say they have hte direct link to the 7.0 RUU all give a 404 when trying to download the .exe
aerospyke said:
anyone know where i can get the RUU for HTC10 unlocked international but nougat?.... as my firmware is nougat, i need to install the nougat RUU, so i can get the OTA to orea so i can then go to leodroid oreo .... or am i misunderstanding .... all i can find for HTC10 is oreo, can't find RUU's for nougat....
https://www.htc.com/us/support/updates.aspx
OR am i doing this all wrong .... i'm on leodroid nougat and iw ant to go to leodroid oreo, i'm S-ON but bootloader unlocked. Other websites that say they have hte direct link to the 7.0 RUU all give a 404 when trying to download the .exe
Click to expand...
Click to collapse
Oreo RUU for US Unlocked
https://androidfilehost.com/?fid=962157660013070850
No need to flash Nougat just flash the Oreo ruu.
yldlj said:
Oreo RUU for US Unlocked
https://androidfilehost.com/?fid=962157660013070850
No need to flash Nougat just flash the Oreo ruu.
Click to expand...
Click to collapse
Probably getting errors because you need to flash the firmware first. Better to flash the nougat ruu and take the ota.
And he types international unlocked, so that is confusing. It's either US unlocked or international.
---------- Post added at 05:17 AM ---------- Previous post was at 05:14 AM ----------
aerospyke said:
anyone know where i can get the RUU for HTC10 unlocked international but nougat?.... as my firmware is nougat, i need to install the nougat RUU, so i can get the OTA to orea so i can then go to leodroid oreo .... or am i misunderstanding .... all i can find for HTC10 is oreo, can't find RUU's for nougat....
https://www.htc.com/us/support/updates.aspx
OR am i doing this all wrong .... i'm on leodroid nougat and iw ant to go to leodroid oreo, i'm S-ON but bootloader unlocked. Other websites that say they have hte direct link to the 7.0 RUU all give a 404 when trying to download the .exe
Click to expand...
Click to collapse
Please open a Q&A for proper help. This all doesn't belong here. We can help you there. And a tip, use the zip versions here. Exe files will give you a massive headache
Mr Hofs said:
Probably getting errors because you need to flash the firmware first. Better to flash the nougat ruu and take the ota.
And he types international unlocked, so that is confusing. It's either US unlocked or international.
---------- Post added at 05:17 AM ---------- Previous post was at 05:14 AM ----------
Please open a Q&A for proper help. This all doesn't belong here. We can help you there. And a tip, use the zip versions here. Exe files will give you a massive headache
Click to expand...
Click to collapse
Thanks everyone... yes the oreo RUU isn't working, it's complaining. and yes sorry ... i'm international (australia), CID 621 though which loks like it says taiwan? *sigh* i only asked here coz i'm trying to upgrade my leedroid 7 to leedroid 8
aerospyke said:
Thanks everyone... yes the oreo RUU isn't working, it's complaining. and yes sorry ... i'm international (australia), CID 621 though which loks like it says taiwan? *sigh* i only asked here coz i'm trying to upgrade my leedroid 7 to leedroid 8
Click to expand...
Click to collapse
Your not on international or Australian. Your on TW you need x.xx.709 RUU
https://androidfilehost.com/?fid=745849072291681183
Please post your OS from download mode before flashing anything.
Provide us the info from the download mode. OS line and such. Much easier to get the proper ruu
@aerospyke
For future threads, Remember to post them in the correct forums, I've moved a few posts and formed a new thread for you to continue discussion for this in the proper area.
Thankyou Critical Detox, i went to create the new thread as everyone asked me and saw it i Q&A and got real confused! ....
As for what is being asked of, the OS is 2.41.709.7 .... that sounds like YLDLJ said.... any other lines you need specifically? (so i know what it all means eheh) i have
*** UNLOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-V20.0.8996.00007.0809
OS-2.41.709.7
So that link from yldlj is the correct one for me?
aerospyke said:
Thankyou Critical Detox, i went to create the new thread as everyone asked me and saw it i Q&A and got real confused! ....
As for what is being asked of, the OS is 2.41.709.7 .... that sounds like YLDLJ said.... any other lines you need specifically? (so i know what it all means eheh) i have
*** UNLOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-V20.0.8996.00007.0809
OS-2.41.709.7
So that link from yldlj is the correct one for me?
Click to expand...
Click to collapse
Yes because as you can see the file has the same version number as your firmware. It will put the device to stock, boot it and take the ota to Oreo
Mr Hofs said:
Yes because as you can see the file has the same version number as your firmware. It will put the device to stock, boot it and take the ota to Oreo
Click to expand...
Click to collapse
thanks eveyrone, i'm now on oreo and flashing custom. something i noticed though on my bootloader after OTA to oreo is it now says fused... i.e.
*** UNLOCKED ***
*** FUSED ***
What does that mean? Sounds ominous
aerospyke said:
thanks eveyrone, i'm now on oreo and flashing custom. something i noticed though on my bootloader after OTA to oreo is it now says fused... i.e.
*** UNLOCKED ***
*** FUSED ***
What does that mean? Sounds ominous
Click to expand...
Click to collapse
Normal. It's something the Oreo firmware does to the bootloader. No worries. Have fun with leedroid oreo
Hmm... It's been so long since I've done anything with phones, I'm running stock rooted nougat. Bootloader unlocked but still s-on
Is it safe to just run the Oreo OTA and then re root my device or do i need to remove root or anything first?
If any other info is needed let me know, thanks!
demkantor said:
Hmm... It's been so long since I've done anything with phones, I'm running stock rooted nougat. Bootloader unlocked but still s-on
Is it safe to just run the Oreo OTA and then re root my device or do i need to remove root or anything first?
If any other info is needed let me know, thanks!
Click to expand...
Click to collapse
You can just run ota. It might unroot but that's all.
kazuki1 said:
You can just run ota. It might unroot but that's all.
Click to expand...
Click to collapse
Thanks! Appreciate that, been way too long for me to just give in?
Update won't work with root, also not with removed root. It leaves traces. Either go back to stock with the nougat ruu and take the ota or revert to a PURE stock NON rooted backup and take the ota. Or flash the Oreo firmware and then the Oreo ruu .......
yldlj said:
Oreo RUU for US Unlocked
https://androidfilehost.com/?fid=962157660013070850
No need to flash Nougat just flash the Oreo ruu.
Click to expand...
Click to collapse
Do you Flashboot this or TWRP?
magistrateee said:
Do you Flashboot this or TWRP?
Click to expand...
Click to collapse
Download mode after renaming the zip
Where can I get international RUU??? Can't seem to find it anywhere. Heres my info for clarification.
PS C:\adb> fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA75PBN00312
(bootloader) current-slot:
(bootloader) imei: 354259071010296
(bootloader) version-main: 2.41.592.51
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: HTC__332
Donnie267 said:
Where can I get international RUU??? Can't seem to find it anywhere. Heres my info for clarification.
PS C:\adb> fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA75PBN00312
(bootloader) current-slot:
(bootloader) imei: 354259071010296
(bootloader) version-main: 2.41.592.51
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: HTC__332
Click to expand...
Click to collapse
As i have answered you here. Your version main is NOT the international one. The international one is 2.41.401 (for nougat)
https://forum.xda-developers.com/htc-10/help/problems-to-stock-t3744765/page2