Related
I restored my M8 International Unlocked Dual SIM Version to stock through a nandroid backup and then flashed one of the recoveries I found online but my phone won't update through OTA. I then tried restoring different backups. Some of which worked and some didn't even boot.
I finally came to the conclusion that it was because of the HBOOT version and maybe the version-main.
I want to know:
1- Understand version-main.
2- How can I know which nandroid backup is right for me. (and if possible point me to the right ones for me).
I searched quite some time but couldn't turn up with a complete answer. Forgive me if I missed something.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__J15
(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: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
GeekOmar said:
1- Understand version-main.
2- How can I know which nandroid backup is right for me. (and if possible point me to the right ones for me).
[/CODE]
Click to expand...
Click to collapse
I don't own the dual SIM, and can't speak that specifically on it. But what I can say:
1) Main version is the firmware number. It won't change when you restore a nandroid.
2) You will want a nandroid that matches your firmware number. If you are trying to flash backups for the "regular" (single SIM) M8, these will never work on your phone. Dual SIM nandroids are probably pretty limited.
GeekOmar said:
....but my phone won't update through OTA.
Click to expand...
Click to collapse
What's the error ?
Is it stuck on red triangle ? If yes, press & hold volume up button and press power button once. This will get you to recovery and read what error that you have there.
redpoint73 said:
I don't own the dual SIM, and can't speak that specifically on it. But what I can say:
1) Main version is the firmware number. It won't change when you restore a nandroid.
2) You will want a nandroid that matches your firmware number. If you are trying to flash backups for the "regular" (single SIM) M8, these will never work on your phone. Dual SIM nandroids are probably pretty limited.
Click to expand...
Click to collapse
Thank you Redpoint,
I bricked my phone before, and was able to fix it using the backups and recovery from the below link and everything was fine, I was able to install two OTAs and get lollipop.
http://forum.xda-developers.com/htc-one-m8/help/rooted-m8-dual-sim-bricked-s-t2979774
But now, when I restore that backup and original recovery, then install any OTA update, the screen becomes black. I know the phone is working fine as I can hear the sound when pressing the volume key or when someone calls. But no screen! The link above is to a thread made by me and the only difference i can see between that time and now is the HBOOT version and the radio/baseband. This is driving me crazy!
ckpv5 said:
What's the error ?
Is it stuck on red triangle ? If yes, press & hold volume up button and press power button once. This will get you to recovery and read what error that you have there.
Click to expand...
Click to collapse
The screen just becomes black. Phone works fine as I can hear incoming calls.
Come on people, is it that hard! There must be something that can be done.
Sent from my HTC One_M8 dual sim using XDA Forums
GeekOmar said:
Come on people, is it that hard! There must be something that can be done.
Click to expand...
Click to collapse
This is sounding really rude. How about asking nicely?
Nobody here is getting paid for their time, or sitting at their computer 24 hours a day to help you. You need some patience.
Plus, the dual SIM version is not terribly common/popular, so getting the specific help and files needed may be a challenge. Folks here are helping as much as they can, when they can.
Its hard enough, that you can't figure it out, right?
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
GeekOmar said:
But now, when I restore that backup and original recovery, then install any OTA update, the screen becomes black.
Click to expand...
Click to collapse
What backup and what OTAs specifically? The statement is to vague for me to see what you did.
List the version of the backup (link to a link to a link doesn't help me) and what version OTAs did you try.
Where did you get the OTA files from (specific post, if applicable)?
GeekOmar said:
the only difference i can see between that time and now is the HBOOT version and the radio/baseband.
Click to expand...
Click to collapse
This means your firmware is different for before. This is not a minor thing, its a huge difference.
GeekOmar said:
The screen just becomes black. Phone works fine as I can hear incoming calls.
Click to expand...
Click to collapse
That's because you restored a very low version of backup when you have a high version firmware installed.
What I understand here, you restored 1.45.401.12 but your firmware is 4.30.401.15
When you restore a backup (when your device is S-On), the lowest version that may work on your device is 3.33.401.6 but not 1.45.401.12.
And the correct version to restore is 4.30.401.15
If you don't have this 4.30.401.15 backup and unable to find it for now, just to have a good running device, you can install custom ROM made for your device.
I believe this is a good one : http://llabtoofer.com/2015/05/08/htc-one-m8-dual-sim-maximushd-3-0-0/
(note : you should have made your own backup when you first fixed your previous problem)
redpoint73 said:
This is sounding really rude. How about asking nicely?
Nobody here is getting paid for their time, or sitting at their computer 24 hours a day to help you. You need some patience.
Plus, the dual SIM version is not terribly common/popular, so getting the specific help and files needed may be a challenge. Folks here are helping as much as they can, when they can.
Its hard enough, that you can't figure it out, right?
Click to expand...
Click to collapse
I didn't mean to sound rude. What I meant by my last post, was to encourage readers as I know it is a challenge and I wanted them to share their thoughts. I assure you that I AM grateful for your help otherwise I wouldn't thank you for your first post which suggested to restore a nandroid backup for a dual SIM which I already did.
Anyway, please accept my apologies for this misunderstanding.
What backup and what OTAs specifically? The statement is to vague for me to see what you did.
Click to expand...
Click to collapse
I restored the same backup that I used to fix my phone the first time. It is currently deleted but it said it was version 1.45.401.12. Which worked flawlessly and I was able to install OTA updates.
The update I'm trying to install currently is version: 3.33.401.6. for Android 4.4.4. It is an over the air update by the phone it self.
ckpv5 said:
That's because you restored a very low version of backup when you have a high version firmware installed.
What I understand here, you restored 1.45.401.12 but your firmware is 4.30.401.15
When you restore a backup (when your device is S-On), the lowest version that may work on your device is 3.33.401.6 but not 1.45.401.12.
And the correct version to restore is 4.30.401.15
If you don't have this 4.30.401.15 backup and unable to find it for now, just to have a good running device, you can install custom ROM made for your device.
I believe this is a good one : http://llabtoofer.com/2015/05/08/htc-one-m8-dual-sim-maximushd-3-0-0/
(note : you should have made your own backup when you first fixed your previous problem)
Click to expand...
Click to collapse
I'm keeping ROMs as a last option
How do you suggest I update my firmware?
Again, all are thanked for their valuable contributions.
This should help you : http://forum.xda-developers.com/htc-one-m8/help/m8-dugl-lollipop-upgrade-unlocking-t3098463
GeekOmar said:
Anyway, please accept my apologies for this misunderstanding.
Click to expand...
Click to collapse
No worries, your apology is accepted. And I gave you your first "Thanks" too!
I look at most all new posts in this section, and respond if I have something to contribute when I have the time (and ckpv5 looks to operate very much the same way). So the lack or response was due to me not being online, and otherwise unable to spend the time on XDA (and nagging won't change that). Therefore, "bumping" a thread to the top is usually not necessary. Or if you choose to do so, try to pose it as a polite appeal for help (in the form of a question, and using the word "please" can work wonders).
The way you posted it, sounded more like you were making a demand or giving orders.
GeekOmar said:
I restored the same backup that I used to fix my phone the first time. It is currently deleted but it said it was version 1.45.401.12. Which worked flawlessly and I was able to install OTA updates.
The update I'm trying to install currently is version: 3.33.401.6. for Android 4.4.4. It is an over the air update by the phone it self.
Click to expand...
Click to collapse
Did you install the 2.xx.401 OTA before trying 3.33.401? Because this is mandatory (OTAs need to be installed in sequence, and you can't skip any).
GeekOmar said:
How do you suggest I update my firmware?
Click to expand...
Click to collapse
Your main version, hboot, and radio numbers given in your top post all indicate you are on the current Lollipop firmware.
The issue is getting a ROM on the phone that matches the firmware, as ckpv5 has given you suggestions on how to do (4.30.401 nandroid is what you want, if you can find it).
You may be confusing "firmware" with "ROM", as they are not the same thing.
He can use one version lower 3.33.401.6 too.
And he can find that 3.33.401.6 backup in the link that I posted above.
Did you install the 2.xx.401 OTA before trying 3.33.401? Because this is mandatory (OTAs need to be installed in sequence, and you can't skip any).
Click to expand...
Click to collapse
I update as the phone asks. I abide by what it is asking.
Your main version, hboot, and radio numbers given in your top post all indicate you are on the current Lollipop firmware.
The issue is getting a ROM on the phone that matches the firmware, as ckpv5 has given you suggestions on how to do (4.30.401 nandroid is what you want, if you can find it).
You may be confusing "firmware" with "ROM", as they are not the same thing.
Click to expand...
Click to collapse
What I understand now, is that I got the firmware of Lollipop but I am still running Kitkat. Couldn't find any 4.30.401 nandroid.
ckpv5 said:
This should help you : http://forum.xda-developers.com/htc-one-m8/help/m8-dugl-lollipop-upgrade-unlocking-t3098463
Click to expand...
Click to collapse
I tried, that method. Flashed the rom, and it asked me to install Lollipop, which is good. But when flash stock recovery lock the bootloader. It boots straight to fastboot!
GeekOmar said:
I tried, that method. Flashed the rom, and it asked me to install Lollipop, which is good. But when flash stock recovery lock the bootloader. It boots straight to fastboot!
Click to expand...
Click to collapse
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
ckpv5 said:
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
Click to expand...
Click to collapse
I flashed the stock recovery so I locked the bootloader to install the OTA. Don't you need a locked boot loader to install an OTA?
Man, don't make me feel stupid more than I do now. I'll get a Nokia and then kill myself. [emoji30] [emoji379]
I'll try one of your recoveries as soon as I'm home.
ckpv5 said:
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
Click to expand...
Click to collapse
Sent from my TF700T using Tapatalk
GeekOmar said:
I flashed the stock recovery so I locked the bootloader to install the OTA. Don't you need a locked boot loader to install an OTA?
Click to expand...
Click to collapse
No .. no need a relocked bootloader for OTA. (doesn't matter your device is S-On or S-Off)
Relocked bootloader only needed when your device is S-On and you want to :
1. Install a HTC RUU
2. Install a HTC signed firmware
ckpv5 said:
No .. no need a relocked bootloader for OTA. (doesn't matter your device is S-On or S-Off)
Relocked bootloader only needed when your device is S-On and you want to :
1. Install a HTC RUU
2. Install a HTC signed firmware
Click to expand...
Click to collapse
Understood.
Ok, so I flashed that stock rom you mentioned earlier and and one of your stock recoveries and Voila! Everything is perfect, except WiFi. When I turn on WiFi, it says "Turning on.." and stays like this indefinitely. Any idea?
Well, I have tried everything to fix the WiFi problem to no avail. Finally I got fed up and decided to use the room you provided. Thanks ckpv for your help. I appreciate it.
Sent from my TF700T using Tapatalk
GeekOmar said:
Well, I have tried everything to fix the WiFi problem to no avail. Finally I got fed up and decided to use the room you provided. Thanks ckpv for your help. I appreciate it.
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse
I don't have your device version so I can't confirm anything why the wifi won't work on your device.
Anyway .. when you want to try again - see this : http://forum.xda-developers.com/showpost.php?p=56681264&postcount=113
a nandroid backup that you can restore and install the stock recovery and try to OTA again.
ckpv5 said:
I don't have your device version so I can't confirm anything why the wifi won't work on your device.
Anyway .. when you want to try again - see this : http://forum.xda-developers.com/showpost.php?p=56681264&postcount=113
a nandroid backup that you can restore and install the stock recovery and try to OTA again.
Click to expand...
Click to collapse
I'll give it a try.
Thank you for your help, you've done enough.
Sent from my HTC One_M8 dual sim using Tapatalk
Hi! I know it's not the most elegant thing to come here looking for help when I don't post but I've been all day reading guides and tutorials and I'm in the edge between life and death and willing to destroy the city, so...
Ok, had the HTC One M9 with Stock Rom, Orange in my case, and wanted to root it. Looked for tutorials, and used the Windroid Toolkit 3.1, to unlock bootloader, install TWRP and flash SuperSU.
I managed to unlock bootloader, install the Custom Recovery and flash SuperSU. But oh, surprise, when rebooting, I got stuck in bootloop with the HTC Logo. I come back to the Custom Recovery to reboot again and it says "No OS Installed, you sure you want to reboot"? Ok, I get it, I guess I deleted the ROM, somehow.
The thing is, now I'm in this situation, no ROM so no system so no party. I've already investigated, and I'm in this situation:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxx
(bootloader) version-main: 3.35.75.14
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_95.00.51130G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG309
Bootloader: UNLOCKED (I tried to relock it and yep, I can, but doesn't seem to be useful for something)
S-ON
Click to expand...
Click to collapse
So now: what the hell I'm supposed to do. Yep, I saw the tutorials to come back to Stock. I saw the RUU thing, and I guess I have to download the ORANG309 one. I did and tried, but when installing it (with fastboot or with the .exe program when RUUs come in .exe) there's always some kind of error, in fastboot specifically, or a 9 (I guess) error about mismatch in CID or MID (CID matches, so guess it's MID but can't find the right RUU), o something like unable to flash from .zip, or so.
I saw that about renaming it to 0PJAIMG.zip, put it into SD's root, boot in download mode and Volume +. I tried and it says "22 RU_HEADER_ERROR", I guess the renaming is not correct but... what am I supposed to do, put the MID or...?
Oh, I just installed the Stock Recovery I found here in XDA just in case it's necessary, I have both (TWRP and Stock) here so if TWRP is necessary again, just tell me.
THOUSANDS OF THANKS IN ADVANCE, YOU'RE ALMOST SAVING MY WHOLE LIFE <3
Flash twrp 2.9.0.1 and supersu 2.65 from here https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
Double check filesizes and md5 before flashing.
Beamed in by telepathy.
Filesizes and md5 you mean, double check when downloading and when flashing to see if nothing has changed in the process?
That should be enough to unbrick/make it alive again, no flashing a ROM or whatever? *.* thank you so much for your help, honestly ?
shivadow said:
Flash twrp 2.9.0.1 and supersu 2.65 from here https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
Double check filesizes and md5 before flashing.
Beamed in by telepathy.
Click to expand...
Click to collapse
why this old twrp? 300-2 should be best for marshmallow and is working fine.
shivadow said:
Flash twrp 2.9.0.1 and supersu 2.65 from here
Double check filesizes and md5 before flashing.
Beamed in by telepathy.
Click to expand...
Click to collapse
Ok, now I can't flash twrp 2.9.0.1 .-. I guess it's from fastboot --> flashboot flash recovery <nameofthetwrp.img> right? It installs good but reboots and says "Unable to reboot from recoery mode" :crying::crying::crying:
Ok I can't flash twrp 2.9.0.1 you provided, I managed to install 2.8.7.0 from the twrp.me web, for my device, and it worked, so I flashed the SuperSU 2.65 you provided but it anyways I'm in the same situation, does not boot at all.
You most likely tried an old version for your phone of the ruu, so you don't install the ruu and since you don't have a system running it won't work. Get a twrp backup which suits your main version / cid and restore it in twrp, so you have a system. Then you can root.
You most likely uninstalled the system before rooting
sent from my HTC One m9 using xda premium 5
DeeZZ_NuuZZ said:
You most likely tried an old version for your phone of the ruu, so you don't install the ruu and since you don't have a system running it won't work. Get a twrp backup which suits your main version / cid and restore it in twrp, so you have a system. Then you can root.
You most likely uninstalled the system before rooting
sent from my HTC One m9 using xda premium 5
Click to expand...
Click to collapse
Ok, hope this is the last answer which will mean that it worked. I found that twrp backup, I'm trying to put it into SD, but the system_image.emmc.win is 4,5GB, which I don't care, my SD is 8GB capacity and is empty, but when trying to put it inside, it says that it's too large. I guess it's because the format, but it is in FAT32 already, it has to be in FAT32? Or can I in NTFS? I haven't tried cause as far as I know NTFS is for reading only but... I'm the noob here :_)
Thanks! <3
Ok, finally, that was the thing, I formatted in exFAT, somewhere I read that 3.0.0.0-2 TWRP worked with that, and yep it did, I guess now I can't update via OTA from Orange but... after all these days, who cares.
Thank you both, really helped, thank you so much ^^
SOLVED!
Hey Guys,
I just bought a used HTC One M8 and love the phone. Unfortunately the phone was rooted and ran with a CM Nightly, the camera didnt work, the flash neither and so on. Im no big fan of custom Firmware if the stock experience has all the features I need in the phone. Coming from Android 4.2, Marshmallow is certainly enough.
So I grabbed a Stock 4.2 Backup and flashed it. Then I went through all the OTA´s. I had to flash the kernel because it was still custom, but I couldnt find the stock one, so I got ElementalX. It all went alright until I got to Lollipop (and I dont like Lollipop at all, the version before was much more pleasing to me).
I dont get the OTA if I search for it and after asking google I found that you have to be Bootloader locked to get the OTA. Does anyone know why HTC decided to do it with Marshmallow but no other OTA before? Anyway i locked my bootloader, but then it didnt boot. It always booted into the bootloader. After a quick search it seems that it happens when you are not full stock (i guess because of my kernel?).
I then tried to flash the Marshmallow OTA over recovery, but it said I got an error, because the update expects another Version.
What are my options now? Ideally I want stock Marshmallow, Sense or Play Edition I dont care, but since my phone is Sense I think its way easier. I dont want root, because Pokemon Go blocks it (y i know the workarounds, but they could ban people for that or make the workarounds not work) and because I want my Camera and Speakers to work perfectly.
Has anyone the stock Lollipop Kernel for me to flash so I can lock the bootloader again? Is there anything I did wrong? Please guys, I need your help, because I really really enjoy this phone coming from a Galaxy Nexus!
Here are Screenshots of the System Info:
vaZeEK2.png
ZyUB9yp.png
These are the Imgur Codes, because I cant post external links having less than 10 Posts
Thanks for any Reply! I really appreciate this community since I rooted my Nexus
My responses below in red font:
wollen said:
So I grabbed a Stock 4.2 Backup and flashed it. Then I went through all the OTA´s. I had to flash the kernel because it was still custom, but I couldnt find the stock one, so I got ElementalX.
This doesn't make much sense. The stock backup you restored would have (should have) included the stock kernel. And the subsequent updates would have also updated (replaced) the kernel. I don't see how it could have still been a custom kernel after restoring the backup, and the OTA updates. I think you are mistaken on this.
I dont get the OTA if I search for it and after asking google I found that you have to be Bootloader locked to get the OTA.
This is false, and wherever you got this info from, its incorrect. MM OTA will install fine with an unlocked bootloader (but probably not with a custom kernel). You only need to relock the bootloader to flash RUU, which is a very different animal.But that may be the source of confusion, as folks often mix up the requirements for OTA vs. RUU.
Anyway i locked my bootloader, but then it didnt boot. It always booted into the bootloader. After a quick search it seems that it happens when you are not full stock (i guess because of my kernel?). Not booting after relocking the bootloader has nothing to do with not being stock, or having custom kernel. No boot after relocking is normal, expected, and happens even if fully stock. Relocking expects the RUU to be run.
I then tried to flash the Marshmallow OTA over recovery, but it said I got an error, because the update expects another Version.
Not sure, but I would guess the custom kernel is the reason for the OTA failure. I would think the custom kernel would trip the "Modified Software" flag.
What are my options now?
Click to expand...
Click to collapse
If you are currently bootloader locked, and the intent is to go full MM stock, you may just be best off running RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) if you need help finding the right RUU.
Normally, I would warn that the RUU wipes all the data from the phone; but I think you already did that when you relocked the bootloader.
There are other paths forward, such as unlocking the bootloader again, and flashing stock TWRP backup and stock recovery. But it would probably be more steps to end up at the same place.
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
I now see from your screenshots, that you seem to have the O2 version of the M8. I don't know if there is an RUU for that version. If not, you may indeed need to unlock the bootloader again (either try the same unlock bin code, or get a new one via HTCDev.com), flash TWRP back onto the phone, then restore the stock TWRP backup 4.20.206.2 from here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
After that, restore the stock recovery 4.20.206.2, and you should be able to OTA to MM.
But again, I'd like to see the getvar output to make sure this is the best way forward (the data presented in the phone settings is not always accurate, depending on what you flashed).
When I flashed the Stock ROM, the WiFi stopped working. I searched in the Internet and someone said that the kernel could be wrong. I was very surprised because i also thought that the ROM overrides the kernel. But when i looked in phone settings there was a custom kernel. When I flashed the ElementalX the WiFi worked again. When I upgraded my way up to Lollipop I had to flash the ElementalX Kernal several times because WiFi almost always stopped working after an OTA.
Here is my getvar Output:
Why do I have to delete Serial and IMEI, because of hacking attempts?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(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: d9e7383b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I hope you are sure about your thesis, because OTAing from 4 to 5 took several hours
But even when its wrong thank you so much for help so far!!
Again, my comments in red font:
wollen said:
When I flashed the Stock ROM, the WiFi stopped working. I searched in the Internet and someone said that the kernel could be wrong. I was very surprised because i also thought that the ROM overrides the kernel. But when i looked in phone settings there was a custom kernel.
When you say stock ROM, do you mean a stock TWRP backup, like the ones in the link I provided in my last post? If its a TWRP backup you restored, its possible you forgot to restore boot.img contained in the backup file. In the Restore section of TWRP, you need to select System and Boot.img when restoring a stock TWRP backup. In that case, its indeed possible that whatever kernel was there before, was not over-written by the stock kernel.
When I flashed the ElementalX the WiFi worked again. When I upgraded my way up to Lollipop I had to flash the ElementalX Kernal several times because WiFi almost always stopped working after an OTA.
I'm not sure why that happened. You shouldn't have to flash a custom kernel after an OTA update. Maybe having a custom kernel on the phone when trying to OTA, mucked things up somehow.
Here is my getvar Output:
Why do I have to delete Serial and IMEI, because of hacking attempts? Something like that. Those numbers are personal info, and can be used by others for nefarious purposes.
I hope you are sure about your thesis, because OTAing from 4 to 5 took several hours
I don't see how me being right or not has anything to do with the OTA taking a long time.
Click to expand...
Click to collapse
---------- Post added at 03:07 PM ---------- Previous post was at 03:02 PM ----------
Your getvar data confirms what I stated before. I don't think the O2 version has RUU, so I suggest trying the following:
redpoint73 said:
unlock the bootloader again (either try the same unlock bin code, or get a new one via HTCDev.com), flash TWRP (2.8.7.0) back onto the phone, then restore the stock TWRP backup 4.20.206.2 from here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 Be sure to restore both System and boot.img this time (its in the instructions)!
After that, restore the stock recovery 4.20.206.2, and you should be able to OTA to MM.
Click to expand...
Click to collapse
So I should now flash the provided TWRP Backup using the Boot.img and then all should work? So the Boot.img is no extra step just the normal way to do it? The first time I did all thing with the One M8 All in One Tool Kit.
And yeah Sorry about that thing with taking a long time, I think it was my way to get the steam off of having to go through all this today ^^.
EDIT: Just saw your edit, will do exactly that and tell if it has worked
Thank you so much for your help so far!
redpoint73 said:
I don't think the O2 version has RUU...
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24369303960686241
Or another possible method, is:
1) Keep the bootloader locked for now.
2) Flash firmware 6.13.206.5 as posted here. Instruction on how to flash on the bottom of the thread.
3) Unlock the bootloader again
4) Flash TWRP 3.0.2
5) Restore the backup 6.13.206.5 from here. Again, make sure you restore both system and boot partitions.
6) Reboot, and you should be on MM. No need to flash stock recovery, unless HTC releases any more OTA (which is unlikely).
My Bootloader is unlocked because I couldnt start the phone, so I had to unlock it. I just Flashed TWRP 2.8.7.0., but now there seems to be a RUU. Is it better to use the RUU and if yes, what do I do with it? Just flash it with TWRP and then proceed to OTA?
ckpv5 said:
https://www.androidfilehost.com/?fid=24369303960686241
Click to expand...
Click to collapse
Nice. There's the RUU for 4.20.206.2
Keep the bootloader locked and run this. Easiest way (if you have an SD card) is:
1) Rename to 0P6BIMG.zip
2) Put the file on SD card.
3) Insert card into phone
4) Reboot into bootloader, and it should run the RUU automatically
After that, reboot and see if the OTA update comes through.
---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------
wollen said:
My Bootloader is unlocked because I couldnt start the phone, so I had to unlock it. I just Flashed TWRP 2.8.7.0., but now there seems to be a RUU. Is it better to use the RUU and if yes, what do I do with it? Just flash it with TWRP and then proceed to OTA?
Click to expand...
Click to collapse
I guess whether you restore a stock TWRP backup, or RUU is a tossup at this point. You would need to relock the bootloader to RUU. But it might be less daunting, if the instruction to restore a TWRP backup looks confusing to you.
But you run the RUU using the method I stated above (or if you don't have an SD card, le me know and I can tell you the fastboot method). You can not flash the RUU with TWRP.
Ok I will relock and use the RUU!
I have an SD Card but no Reader, so my only way is to have it inside the phone to get files on there. Is it a problem?
I would now:
- Put the Zip on the SD Card
- Take the SD Card out
- Relock the Bootloader
- Insert the SD Card
- Let the magic happen
Is it safe and right for me to do it that way?
wollen said:
So I should now flash the provided TWRP Backup using the Boot.img and then all should work? So the Boot.img is no extra step just the normal way to do it? The first time I did all thing with the One M8 All in One Tool Kit.
Click to expand...
Click to collapse
If you restore a TWRP backup, you check the boxes for the partitions you want to restore. You need to check both system (ROM) and boot (kernel).
However, if you flashed something with the toolkit, I don't think it was a TWRP backup, but probably a flashable ROM zip. In that case, the kernel flashes automatically.
Flashing a ROM is different from restoring a TWRP backup.
Also, I would advise against using the toolkit. It hasn't been updated in over a 2 years. It causes more problems than it solves; and everything it does, you can be done yourself manually. The toolkit is also the reason your main version is blank in getvar and on the bootloader screen (OS number). Toolkit installs a very old, obsolete version or TWRP which wipes out the OS (firmware) number. It should say 4.20.206.2.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
wollen said:
Ok I will relock and use the RUU!
I have an SD Card but no Reader, so my only way is to have it inside the phone to get files on there. Is it a problem?
Click to expand...
Click to collapse
That's fine. My understanding, the phone is currently working. So you can download the RUU direct to it, or use it to transfer the RUU to the SD card from your computer.
wollen said:
Ok I will relock and use the RUU!
I have an SD Card but no Reader, so my only way is to have it inside the phone to get files on there. Is it a problem?
I would now:
- Put the Zip on the SD Card
- Take the SD Card out
- Relock the Bootloader
- Insert the SD Card
- Let the magic happen
Is it safe and right for me to do it that way?
Click to expand...
Click to collapse
Adding a post, to bump. This is a test.
wollen said:
I would now:
- Put the Zip on the SD Card
- Take the SD Card out
- Relock the Bootloader
- Insert the SD Card
- Let the magic happen
Is it safe and right for me to do it that way?
Click to expand...
Click to collapse
You should be able to just leave the SD card in the phone.
Basically, any time the phone is booted into bootloader, and it sees a file on the SD card named 0P6BIMG.zip, than it will try to install it.
But I suppose it doesn't hurt to take the card out, on the off-chance that relocking the bootloader wipes the SD card (its not supposed to, but hey you never know).
Sigh.. Im slowly losing hope..
I tried to copy the RUU to my SD card, but Windows gives me an error all the time. Even when I try to copy it to the Phones Storage. Images and the old ROM are easy to copy, maybe it´s because of its size? The RUU is 1.6gb and the old rom 1.2gb for example.
The Error message is as follows, translated by me from german:
Element can not be copied.
The device does not respond or the connection has been disconnected.
I tried Google Search but did not find anything, because the Card works with alle other files. Is there a way to apply the RUU from the PC?
So I just did the method over TWRP and it worked. Thanks so much for helping me through this, I would have never made it with out you!
Hi folks, So finally i am ready to update my Supersu rooted,S-OFF, Rogers M8 to the marshmallow OTA update which has been showing as a notification from the last couple of months.I asked same question last year but at that time there was no easy way to update the rooted phone other than finding stock backup.
Any new way came to update without finding stock backup?I would really appreciate if someone can give step by step.Thanks.
C:\>cd adb
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: 4a2bcc8a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
Click to expand...
Click to collapse
ninja_zx11 said:
Hi folks, So finally i am ready to update my Supersu rooted,S-OFF, Rogers M8 to the marshmallow OTA update which has been showing as a notification from the last couple of months.I asked same question last year but at that time there was no easy way to update the rooted phone other than finding stock backup.
Any new way came to update without finding stock backup?I would really appreciate if someone can give step by step.Thanks.
Click to expand...
Click to collapse
hi
you can just flash the RUU which will update your device to official marshmallow ( and it will wipe your internal storage so make sure to backup all your data )
here is the RUU
https://www.androidfilehost.com/?fid=24459283995310669
and here is the guide ( replace the RUU by the one i linked ) and you don't need to relock the bootloader
start from
2. Download htc_fastboot.exe here
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ahmed.ismael said:
here is the RUU
https://www.androidfilehost.com/?fid=24459283995310669
Click to expand...
Click to collapse
Thanks ahmed for your reply.I got one question.Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
ninja_zx11 said:
Thanks ahmed for your reply.I got one question.Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
Click to expand...
Click to collapse
Depends on the RUU and the provider
You have to decide what you will do
You came here asking for help and when you find your answer you got suspicious
Anyway you choose if you want to download the 3rd party website RUU or not
Sent from my HTC M8 using XDA Labs
ninja_zx11 said:
Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
Click to expand...
Click to collapse
The file says "signed". If that is true, there is virtually no way (at least form a practical/feasible sense) for it to be anything but an official HTC RUU. My understanding, the encryption involved with being a signed file is far too complicated for anyone to bother messing with (never heard of anyone breaking that encryption to make a file "signed"). At least, its not worth it to spend all the time to make it "signed" just for the purpose of malware, etc. Far too many other "lower hanging fruit" possibilities.
That being said, since are s-off, I don't know how you would verify that file is truly signed. With s-off, you can flash unsigned RUU files. With s-on, only signed RUUs will flash. But I don't know its worthwhile to go s-on just for the purpose of making sure the RUU is signed.
You've already flashed custom recovery and a SuperSU file, all from 3rd parties (maybe from reputable sources, or not). There is no more or less reason to believe those files are safe.
ahmed.ismael said:
Depends on the RUU and the provider
You came here asking for help and when you find your answer you got suspicious
Click to expand...
Click to collapse
Hi ahmed, I assure you that i was asking that question about in a constructive way and i really appreciate your help and i think that's what i will be doing.I just put up my genuine fear/concern in a positive way.
redpoint73 said:
The file says "signed". If that is true, there is virtually no way (at least form a practical/feasible sense) for it to be anything but an official HTC RUU. My understanding, the encryption involved with being a signed file is far too complicated for anyone to bother messing with (never heard of anyone breaking that encryption to make a file "signed"). At least, its not worth it to spend all the time to make it "signed" just for the purpose of malware, etc. Far too many other "lower hanging fruit" possibilities.
That being said, since are s-off, I don't know how you would verify that file is truly signed. With s-off, you can flash unsigned RUU files. With s-on, only signed RUUs will flash. But I don't know its worthwhile to go s-on just for the purpose of making sure the RUU is signed.
You've already flashed custom recovery and a SuperSU file, all from 3rd parties (maybe from reputable sources, or not). There is no more or less reason to believe those files are safe.
Click to expand...
Click to collapse
Thanks redpoint for your reply.Yes i agree with you.I am gonna go ahead and flash that RUU as ahmed said.
I have my own full TWRP backup which i made before touching my M8 last year but it was from kitkat.
Can i run that backup to go back to kitkat and start from there?Thanks again ahmed and redpoint!!
ninja_zx11 said:
........I have my own full TWRP backup which i made before touching my M8 last year but it was from kitkat.
Can i run that backup to go back to kitkat and start from there?.......
Click to expand...
Click to collapse
if your backup is non rooted then you can just restore it and flash the stock recovery and do OTA ( multiple until marshmallow ) this way you will be sure that the download from HTC directly to your device
i'm curious to know how do you concern about the downloaded RUU while you have s-off rooted device ?
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
i'm curious to know how do you concern about the downloaded RUU while you have s-off rooted device ?
Click to expand...
Click to collapse
Its because i did rooting and S-off by myself (i am not an expert in any way.Did it by reading and getting help from XDA)on my brand new phone using third-party software (But well known and reputable sources-SuperSu and Sunshine).
I am not saying at all that downloaded RUU is infected or has some problem.It could be 100% stock and i might go that way you had described in your first post.I just expressed my genuine concern.But if that disturbed you then accept my apologies....
ninja_zx11 said:
Its because i did rooting and S-off by myself (i am not an expert in any way.Did it by reading and getting help from XDA)on my brand new phone using third-party software (But well known and reputable sources-SuperSu and Sunshine).
I am not saying at all that downloaded RUU is infected or has some problem.It could be 100% stock and i might go that way you had described in your first post.I just expressed my genuine concern.But if that disturbed you then accept my apologies....
Click to expand...
Click to collapse
no need to an apology that's your own security
but my point is you did unlock your device bootloader,flash custom recovery,flash supersu and used sunshine to s-off ( for what purpose all of this )
you just killed all of this device security
ahmed.ismael said:
no need to an apology that's your own security
but my point is you did unlock your device bootloader,flash custom recovery,flash supersu and used sunshine to s-off ( for what purpose all of this )
you just killed all of this device security
Click to expand...
Click to collapse
Yes i know i did.
But don't you think that downloading RUU from unknown source (If someone has injected something) is more dangerous than doing S-off and unlocking bootloader?I think after s-off and rooting ,It depend on me how i use my phone.Hope you understand my point.
I think there is no end of this security discussion.We can stretch it as much as we want and better...
ninja_zx11 said:
Yes i know i did.
But don't you think that downloading RUU from unknown source (If someone has injected something) is more dangerous than doing S-off and unlocking bootloader?I think after s-off and rooting ,It depend on me how i use my phone.Hope you understand my point.
I think there is no end of this security discussion.We can stretch it as much as we want and better...
Click to expand...
Click to collapse
I can't say anything
But as redpoint73 said earlier the signed RUU is protected by htc sign keys and i don't think that someone will decrypt then encrypt the RUU to push a malware software inside it
at the end it's your device,your own security and your decision
do what you see right
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
if your backup is non rooted then you can just restore it and flash the stock recovery and do OTA ( multiple until marshmallow ) this way you will be sure that the download from HTC directly to your device
Click to expand...
Click to collapse
The stock TWRP non rooted backup from the same phone when it was brand new is from android 4.4.3. Will it go backwards and accept that 4.4.3 old version? Thanks
ninja_zx11 said:
The stock TWRP non rooted backup from the same phone when it was brand new is from android 4.4.3. Will it go backwards and accept that 4.4.3 old version? Thanks
Click to expand...
Click to collapse
yes it will update to the latest but you need the proper recovery version to flash the OTA
ahmed.ismael said:
yes it will update to the latest but you need the proper recovery version to flash the OTA
Click to expand...
Click to collapse
I think my question wasn't clear.
Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.
So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
ninja_zx11 said:
I think my question wasn't clear.
Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.
So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
Click to expand...
Click to collapse
yes it will work no worry
ahmed.ismael said:
yes it will work no worry
Click to expand...
Click to collapse
Thanks for confirming!! will try this weekend.
ninja_zx11 said:
I think my question wasn't clear.
Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.
So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
Click to expand...
Click to collapse
You can use your TWRP backup 2.23.631.2 that you already have and you need to install 2.23.631.2 stock recovery to accept and install OTA but this is not productive. See option 2 below for the reason.
You have 3 options :
Option 1 :
You can install the RUU zip as mentioned in post #2 - http://forum.xda-developers.com/showpost.php?p=70110165&postcount=2
It is a HTC Signed RUU and that's the reason why you need to use htc_fastboot to install the RUU not the generic fastboot
Personally, I don't like to use RUU as it is a hassle to backup all my files from Internal Storage as this RUU will wipe everything on the phone.
Option 2 :
As you have a S-Off device, you can use your TWRP backup 2.23.631.2 that you already have but you need to have stock recovery 2.23.631.2 installed to proceed with OTA.
But this is not productive as you need to accept and install multiple OTAs
2.23.631.2 --> 3.34.631.4 --> 4.20.631.2 --> 4.20.631.3
Also you need to restore all boot, data & system from 2.23.631.2 as your current data on 4.20.631.3 won't work on 2.23.631.2
Option 3 :
As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.
You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7
You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Download the 4.20.631.3 backup
2. Download the 4.20.631.3 stock recovery
3. Restore 4.20.631.3 backup (select only boot & system)
4. Install 4.20.631.3 stock recovery
5. Reboot
6. Check for update
7. Accept, download and install OTA
8. Done.
ckpv5 said:
You can use your TWRP backup 2.23.631.2 that you already have and you need to install 2.23.631.2 stock recovery to accept and install OTA but this is not productive. See option 2 below for the reason.
You have 3 options :
Option 1 :
You can install the RUU zip as mentioned in post #2 - http://forum.xda-developers.com/showpost.php?p=70110165&postcount=2
It is a HTC Signed RUU and that's the reason why you need to use htc_fastboot to install the RUU not the generic fastboot
Personally, I don't like to use RUU as it is a hassle to backup all my files from Internal Storage as this RUU will wipe everything on the phone.
Option 2 :
As you have a S-Off device, you can use your TWRP backup 2.23.631.2 that you already have but you need to have stock recovery 2.23.631.2 installed to proceed with OTA.
But this is not productive as you need to accept and install multiple OTAs
2.23.631.2 --> 3.34.631.4 --> 4.20.631.2 --> 4.20.631.3
Also you need to restore all boot, data & system from 2.23.631.2 as your current data on 4.20.631.3 won't work on 2.23.631.2
Option 3 :
As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.
You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7
You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Download the 4.20.631.3 backup
2. Download the 4.20.631.3 stock recovery
3. Restore 4.20.631.3 backup (select only boot & system)
4. Install 4.20.631.3 stock recovery
5. Reboot
6. Check for update
7. Accept, download and install OTA
8. Done.
Click to expand...
Click to collapse
Thanks a lot ckpv5!!! Will try as you described.I really appreciate your help!
ckpv5 said:
Option 3 :
As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.
You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7
You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Download the 4.20.631.3 backup
2. Download the 4.20.631.3 stock recovery
3. Restore 4.20.631.3 backup (select only boot & system)
4. Install 4.20.631.3 stock recovery
5. Reboot
6. Check for update
7. Accept, download and install OTA
8. Done.
Click to expand...
Click to collapse
Hi ckpv5, Thanks for your help and i finally updated my M8 using your option 3.It really saved my time as i didn't have to delete my data and pics..
One question, Even after updating to marshmallow,the android security patch is still dated to dec 2015? Is it the latest patch and nothing came after?Thanks.
ninja_zx11 said:
........One question, Even after updating to marshmallow,the android security patch is still dated to dec 2015? Is it the latest patch and nothing came after?Thanks.
Click to expand...
Click to collapse
yes it's the latest
no more updates or security patches
Hi Folks,
I wonder if anyone can point me in the right direction please. Here's the story:
I bought a T-mobile branded HTC One M9
Changed it to WWE and ran with a it for a while without issue
Changed to Dev edition and applied the Android7OTA.zip (4.14.617.6) then TWRP, currently running without issue.
I got a notification of another OTA (4.19.617.1) earlier this evening.
Flashed the stock recovery I extracted from the android 7 dev RUU
Downloaded the OTA on the phone and once the phone booted into the stock recovery, I'm told:
'this package is for "htc_himaulatt" devices; this is a "htc_himauhl". Installation aborted'
Fastboot getvar all currently shows:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) serialno: xxxx
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 4.14.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440971_103.00.61018G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001
I've read of using a cid of BS_US002, I've changed to that and retried applying the OTA, but it did the same (so I changed it back).
Assuming the Product reported by fastboot is what's being checked... fastboot's reporting it's already set to what the stock recovery seems to be saying it needs to be. It was happy flashing the first RUU, I'm not sure what might be different this time round.
I bet there's a small thing I might need to change, but I don't know what.
Does anyone else please?
Also.. I've not found much info at all about the OTA to 4.19.617.1. Is it new enough that me somehow getting it off the phone (will probably need brief instructions) could be useful to anyone?
TIA!
Currently having the same problem.
Will post here if i have any luck.
Thanks philicibine.
I've just tried it with supercid too (fastboot oem writecid 11111111), but it didn't do the trick.
Before the phone reboots into the stock recovery, it says ''we have determined that your phone may be running a modified version of its system software....'.
ok so my phone is currently accepting the update!
The problem for me was I had installed TWRP. In trying to restore the stock recovery i was restoring the one from the NoWipe firmware file i used to upgrade to Nougat.
To solve, I extracted the recovery.img from the OTA.zip and flashed that.
Almost finished updating!
here is the recovery.img if you want to try it >> https://drive.google.com/open?id=0BzkydKcZdx9YWW55UDlIOV95UDA
philicibine said:
ok so my phone is currently accepting the update!
The problem for me was I had installed TWRP. In trying to restore the stock recovery i was restoring the one from the NoWipe firmware file i used to upgrade to Nougat.
To solve, I extracted the recovery.img from the OTA.zip and flashed that.
Almost finished updating!
here is the recovery.img if you want to try it >> https://drive.google.com/open?id=0BzkydKcZdx9YWW55UDlIOV95UDA
Click to expand...
Click to collapse
It was the stock recovery from the first android7 devRUU that I've been trying this with. Which OTA did you get this one from?
I've flashed it and the newest OTAs downloading again as I type..
edit: the file you posted a link to (thanks!) and the recovery I was originaly using are definitely different... My phones just failed to apply the update again, but given a different reason 'system parition has unexpected contents'. Guess I've not left system untouched as I thought.
I've just tried extracting system from the original devAndroid7RUU.zip and now I'm getting errors about it not being able to decrypt the .zip.. so must have somehow taken the recovery from another RUU.zip earlier this evening (which wouldn't have been a devRUU, but a WWE-explaining why it reported my phone didnt match the dev edition details). I was doing it remotely form work, while working-must be more careful, I guess.
This means I cant extract system from the right RUU.zip though.
I think I could flash the RUU.zip again (wiping everything, grrr), then let it install the later OTA before doing anything that could amend system.
I'd realy like to not wipe it if posible though.
How did you get the recovery you posted out of the OTA.zip please?
It maybe the same recovery then as I got it from the Dev ota. Seemed to work for me. Maybe you could flash the nowipe firmware and then this if it doesn't work?
---------- Post added at 10:53 PM ---------- Previous post was at 10:40 PM ----------
mad_tunes said:
How did you get the recovery you posted out of the OTA.zip please?
Click to expand...
Click to collapse
I simply unzipped it. It was in the firmware.zip archive inside the OTA.zip
I'm pretty confident the two recovery's are different, my phone does different things with the OTA depanding on which of the recovery's I've flashed.
I used 'HTC_RUU_Decrypt_Tool_3.1.0-WINDOWS64' to extract the recovery from what I thought was the devRUU.zip. This wont open the devRUU.zip now though, so I must have had it extract the wrong RUU earlier.
I've just flashed the stock android7 firmware and the recovery you posted a link to and the OTAs re-downloading
Edit:
I'm still in the same situation, it's reporting system's modified
I think I might just RUU it again. I need my phone running and set up over the next few days though, so it'll have to wait until Christmas is out the way.
Many thanks for your help though.
Do you see many differences after you've applied it?
(And I managed to type ota instead of ruu in the op, I've amended)
Hey guys,
I'm having the exact same issue. The way I was working it around was flashing the update via RUU from laptop but now I'm tired kf doing that every time when there is an update. I will restore my factory recovery and will try it again. After I've done so, I'll get back to you about it.
Best Regards
I couldn't sleep last night, so went for it with the DevRUU.zip I originally used..
It flashed fine as before, then my phone downloaded and applied the OTA just fine.
I couldn't get SuperSU to install properly afterwards though, so restored a TWRP backup so I could use my phone today.
I've been getting the OTA notification repeatedly during the day today though. Seems you can only postpone it for up to 4 hours, rather than dismiss it or turn off checking entirely. It's annoying.
So, I might give it another go pretty soon!
I just RUUd again and then did the OTA.
SuperSU-v2.65 (that I was using pre-OTA) woudn't install, showing 'Patching secpol. Failed. Arborting'
SuperSU-v2.79 installed just fine.
Sorted.
Hey guys. Just went to stock recovery. Unzipped from ota.zip>installed it>recovery works>phone reboot into system>finds the new update>starts to install>rebokts to recovery>starts updating up to 24%25% and then gets me back to recovery saying there is some error. What should I do? I don't want to update via RUU. Thanks
dohcvtec said:
Hey guys. Just went to stock recovery. Unzipped from ota.zip>installed it>recovery works>phone reboot into system>finds the new update>starts to install>rebokts to recovery>starts updating up to 24%25% and then gets me back to recovery saying there is some error. What should I do? I don't want to update via RUU. Thanks
Click to expand...
Click to collapse
100% working method. keep these conditions and everything is working and updated - unlocked cid BS__US001 S-OFF mid 0PJA11000. then install from sd card 0PJAIMG nougat download the update OTA 4.19.617.1 and everything is fine to install without errors!!!!!!!!!!!! check for yourself!!!!!
asar201 said:
100% working method. keep these conditions and everything is working and updated - unlocked cid BS__US001 S-OFF mid 0PJA11000. then install from sd card 0PJAIMG nougat download the update OTA and everything is fine to install without errors!!!!!!!!!!!! check for yourself!!!!!
Click to expand...
Click to collapse
But if I follow those steps, this means fresh new install of the os which is basically the same as RUU install. Or you nent something else? Thanks
P. S. I just fully unrooted my phone so now it is exactly the way you described above but the new update still doesn't install. It gives me this error and I don't understand why: 'system parition has unexpected contents'
dohcvtec said:
But if I follow those steps, this means fresh new install of the os which is basically the same as RUU install. Or you nent something else? Thanks
P. S. I just fully unrooted my phone so now it is exactly the way you described above but the new update still doesn't install. It gives me this error and I don't understand why: 'system parition has unexpected contents'
Click to expand...
Click to collapse
hi.a poor understanding of English and how to correctly put on this site files. I had the same problem. phone-htc__a07 no rooted android 6.0 twrp recovery. OTA updates do not come to android 7.0. write step by step what did was changed the cid to BS__US001,mid on 0PJA11000.restored twrp backup http://forum.xda-developers.com/one-m9/development/one-m9-4-14-617-6-stock-root-twrp-backup-t3518149 then came the notice about the ota updates until they 4.19.617.1 but I have not installed the same as yours.https://drive.google.com/drive/folders/0BwrbLN0SdCTgQ2NseVMtdDhXV3c?usp=sharing I flashed these recovery and firmware and after that everything was installed.try. flash a twrp backup of course is not necessary if you already is 7.0 skip this step...
Hello,
Reporting back.
So what I did was, I took the RUU, flashed RUU, then updated to the newest update with no problem. Had no issues restoring my phone exactly how it was before to flash the RUU. Phone restored automatically from google account. The only thing which didn't restore was my wallpaper (like I care about it ). So that's it. Thank you very much for your help.
Best Regards
dohcvtec said:
Hello,
Reporting back.
So what I did was, I took the RUU, flashed RUU, then updated to the newest update with no problem. Had no issues restoring my phone exactly how it was before to flash the RUU. Phone restored automatically from google account. The only thing which didn't restore was my wallpaper (like I care about it ). So that's it. Thank you very much for your help.
Best Regards
Click to expand...
Click to collapse
couldn't tell what ruu was flashed? and what was your cid and mid?
asar201 said:
couldn't tell what ruu was flashed? and what was your cid and mid?
Click to expand...
Click to collapse
The RUU that I flashed is the official version from HTC website. Flashed it through laptop. CID BS_US001 MID 0PJA11000
dohcvtec said:
The RUU that I flashed is the official version from HTC website. Flashed it through laptop. CID BS_US001 MID 0PJA11000
Click to expand...
Click to collapse
thanks for inform ))))
I just wanted to add to the list of install methods. Here is what I attempted.
All attempts with MID 0PJA11000:
Rooted 4.14.617.6 with TWRP recovery and CID BS_US001 - OTA failed (doesnt hurt to try )
Flashing RUU 4.14.617.6.exe with CID BS_US001 - OTA failed
Flashing RUU 4.14.617.6.exe with CID 11111111 - OTA failed
Flashing RUU 4.14.617.6.zip with CID 11111111 - OTA failed
After the above line and changing the CID to BS_US001 - successful
It appears you must run an ruu.zip to accept the OTA no matter what. Strange the exe's will not work. It also appears the master CID no longer works. Surprisingly I was able to change the CID after running the .zip install and still accept the OTA with no problems.
asar201 said:
100% working method. keep these conditions and everything is working and updated - unlocked cid BS__US001 S-OFF mid 0PJA11000. then install from sd card 0PJAIMG nougat download the update OTA 4.19.617.1 and everything is fine to install without errors!!!!!!!!!!!! check for yourself!!!!!
Click to expand...
Click to collapse
asar201 I did want to ask and make sure, did you use double __ in your CID or just one _?
BrownEye02 said:
I just wanted to add to the list of install methods. Here is what I attempted.
All attempts with MID 0PJA11000:
Rooted 4.14.617.6 with TWRP recovery and CID BS_US001 - OTA failed (doesnt hurt to try )
Flashing RUU 4.14.617.6.exe with CID BS_US001 - OTA failed
Flashing RUU 4.14.617.6.exe with CID 11111111 - OTA failed
Flashing RUU 4.14.617.6.zip with CID 11111111 - OTA failed
After the above line and changing the CID to BS_US001 - successful
It appears you must run an ruu.zip to accept the OTA no matter what. Strange the exe's will not work. It also appears the master CID no longer works. Surprisingly I was able to change the CID after running the .zip install and still accept the OTA with no problems.
asar201 I did want to ask and make sure, did you use double __ in your CID or just one _?
Click to expand...
Click to collapse
Hello...a double underline!!! you and all who can help spread the link twrp backup, installed the OTA to 4.19.617.1. those who are not from Russia in the file, replace gps.conf data on your country,because in my backup it changed to ru.pool.ntp.org for a quick search of satellites in twrp recovery without installing a root file Manager copy the modified gps.conf (system\etc). p.s. Change CID (only if S-OFF) fastboot oem writecid BS__US001 reboot fastboot Change MID (only if there is S-OFF) fastboot oem writemid 0PJA11000 fastboot reboot. there's also posted the stock recovery and firmware. if you wish to flash from sd card file rom.zip folder 4.14.617.6 RUU rename 0PJAIMG.zip and copy to sd card restart your device in download mode. don't know what else to add... ))) if you have any questions...write. https://drive.google.com/drive/folders/0BwrbLN0SdCTgQ2NseVMtdDhXV3c?usp=sharing