Develop Bugs

Having trouble flashing ota after returning to stock.

Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks

You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).

redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img

rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.

redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297

redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.

rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?

redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...

rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.

rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2

ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...

rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?

rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.

ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?

Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !

Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help

Cant get ROM to boot.

I tried upgrading to 7.1, and have tried 3 different ROM's. I even tried going back to 6. Every single ROM told me error code 7 when I tried to flash it. I went about fixing that. So then I was able to flash the ROM and GApps. But then when it goes to boot into the OS all it does is hang on the white Asus screen, reboot, and go back to the white Asus screen. It does that 3 times then goes into recovery. I even tried fixing it with ZE551ML_Modder V3.3. I am running TWRP-3.0.2-0-Z00A.img. This is a Z00A as well. Any help would be greatly appreciated. Thank you.

jaed.43725 said:
I tried upgrading to 7.1, and have tried 3 different ROM's. I even tried going back to 6. Every single ROM told me error code 7 when I tried to flash it. I went about fixing that. So then I was able to flash the ROM and GApps. But then when it goes to boot into the OS all it does is hang on the white Asus screen, reboot, and go back to the white Asus screen. It does that 3 times then goes into recovery. I even tried fixing it with ZE551ML_Modder V3.3. I am running TWRP-3.0.2-0-Z00A.img. This is a Z00A as well. Any help would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Did you upgraded the bootloader? I would just retrace steps, if not factory reset and try again.

lordpipa said:
Did you upgraded the bootloader? I would just retrace steps, if not factory reset and try again.
Click to expand...
Click to collapse
The bootloader is the recovery right? (At least thats what I always thought). If so then I am running the newest TWRP for it.

http://theflamingskull.com/zenfone2.html
Upgrade your bootloader following the instructions on the .zip package.
This will upgrade your bootloader and flash a compatible TWRP recovery.

lordpipa said:
http://theflamingskull.com/zenfone2.html
Upgrade your bootloader following the instructions on the .zip package.
This will upgrade your bootloader and flash a compatible TWRP recovery.
Click to expand...
Click to collapse
I did all that. Now I am stuck with CM Recovery. I tried using the tool to get TWRP back but its not working. I have to figure out how to push TWRP using ADB.

In modder, return to stock option , flash stock recovery and boot img.
Unlock bootloader in modder, just incase.
Flash twrp, root in modder ..reboot to twrp...install 7.1 and pico gapps

I finally had to go to Ubuntu, run ADB as SU and ADB Sideload an older version of Cyanogenmod. Not a single factory image would work. And not a single one of those Android 7 ROM's would work. They are all broken. I would like to see real proof of one working. That little escapade cost me a lot of time. So until someone comes out with a real CM14 version for the Z00A do not attempt to boot one.

jaed.43725 said:
I finally had to go to Ubuntu, run ADB as SU and ADB Sideload an older version of Cyanogenmod. Not a single factory image would work. And not a single one of those Android 7 ROM's would work. They are all broken. I would like to see real proof of one working. That little escapade cost me a lot of time. So until someone comes out with a real CM14 version for the Z00A do not attempt to boot one.
Click to expand...
Click to collapse
You may have really misunderstood the processes and yes they are allover the place.
i am running CM14.1 lots of people are !
What you probobaly have is LP based CM 13 on WW-4.20 blah blah.165
Then there was a CM13 with MM blobs based on WW-4.21 blah blah .135 MM
I think where you have gone wrong is not unlocking bootloader in 5 LP and upgrading bootloader and unlocking.
if you are on .165 - you could flash stock recovery for .165 -- upgrade to .184 -- unlock bootloader and upgrade to MM then unlock bootloader in MM with modder
Then use the modder to install 7.1 14.1 CM
But judging by the probs you have haD already - just leave it alone :good:

What is WW?

jaed.43725 said:
What is WW?
Click to expand...
Click to collapse
WW is world wide
CN china
JP japan
relating to stock FW from official site .
You know what you are doing re using ubuntu to adb but have the procedure all messed up.
Would you like to get to MM and 7.1 CM14.1 and have a windows PC ? ?
Post a screen shot of build number info you are presently on :good:

Network issues

Hello guys,
I am using two different networks in my mobile and it was working properly when i had 4.0.3 OS version. The network stopped working after installing 4.1.1 official version. Now i would like to go back to the older version. Kindly let me know the steps to go back to the official version 4.0.3 from 4 1.3 latest official update.
Regards
Sobhan

sobhan06 said:
Hello guys,
I am using two different networks in my mobile and it was working properly when i had 4.0.3 OS version. The network stopped working after installing 4.1.1 official version. Now i would like to go back to the older version. Kindly let me know the steps to go back to the official version 4.0.3 from 4 1.3 latest official update.
Regards
Sobhan
Click to expand...
Click to collapse
Wipe System and the rom flash should do the trick.

Puddi_Puddin said:
Wipe System and the rom flash should do the trick.
Click to expand...
Click to collapse
Nope. Tried everything. Tried lineage OS, tried installing the 4.1.1 newly by wiping the data/system. Tomorrow planning to go back to 4.0.3 to check the issue is related to mobile or OS.

Back to global stable

Hello.
I have a bootloader unlocked, twrp and a custom rom (now its havoc) and I had Xiaomi.eu too.
There is any way to back to global miui without brick my phone?
Thank you.

will not brick the device.
There are two ways to install MIUI for you:
1) Use MI Flash to install the Stock-ROM through fastboot (you will have the option to lock the bootloader or not, and you will lose the TWRP)
2) Download the ROM that is installed by Recovery and install as any ROM. (You will not miss the TWRP)

1thomas said:
will not brick the device.
There are two ways to install MIUI for you:
1) Use MI Flash to install the Stock-ROM through fastboot (you will have the option to lock the bootloader or not, and you will lose the TWRP)
2) Download the ROM that is installed by Recovery and install as any ROM. (You will not miss the TWRP)
Click to expand...
Click to collapse
It's so simple as that? I will not have any problem about anti-rollback?

I have restore using old backup nothing lose using redwolf with arb enabled. No need reflash.

nunomsgodinho said:
It's so simple as that? I will not have any problem about anti-rollback?
Click to expand...
Click to collapse
this only happens between ROMs MIUI .. example: being at MIUI 10.2 and returning to MIUI 10.1

1thomas said:
this only happens between ROMs MIUI .. example: being at MIUI 10.2 and returning to MIUI 10.1
Click to expand...
Click to collapse
But I have a friend that said that bricked her phone because tried to put a oreo rom after having a pie rom!

nunomsgodinho said:
But I have a friend that said that bricked her phone because tried to put a oreo rom after having a pie rom!
Click to expand...
Click to collapse
he may have done something wrong, it happens, but if you do it right you will not have the bricked device.

First rom with arb v4 was 9.5.19, so u can install anything from this to latest 10.2.0.1 (imo best choice). You cant brick phone unless you try to flash older roms.

1thomas said:
this only happens between ROMs MIUI .. example: being at MIUI 10.2 and returning to MIUI 10.1
Click to expand...
Click to collapse
Wrong information... One can easily install any ROM between 9.5.19 to 10.2.1
Use fastboot method to return back to global stable
---------- Post added at 08:14 AM ---------- Previous post was at 08:12 AM ----------
nunomsgodinho said:
But I have a friend that said that bricked her phone because tried to put a oreo rom after having a pie rom!
Click to expand...
Click to collapse
Probably she flashed older version of Oreo ROM (below 9.5.17 version)
And MIUI based on android pie is around the corner for our device.. After installing android PIE miui ROM there is no chance to install Oreo based miui ROM

How can i downgrade binaries?

I want to go from 9 to 7 because i accidentally installed an android 11 rom, is that possible?

Nubidubi23 said:
I want to go from 9 to 7 because i accidentally installed an android 11 rom, is that possible?
Click to expand...
Click to collapse
So far as I know, you can't downgrade the Binaries. But still u can manage to find someway to leave A11 and back to whatever A u want since customs ROMs ( based on stock ) are seems enough

LinhBT said:
So far as I know, you can't downgrade the Binaries. But still u can manage to find someway to leave A11 and back to whatever A u want since customs ROMs ( based on stock ) are seems enough
Click to expand...
Click to collapse
Hi, thanks for answering. I found an A9 rom for my phone, but when i flash it in TWRP 3.6.1 A11 it gets stuck in bootloop. Tried flashing multidisabler afterwards and wiping it but still nothing. Any ideas?

Nubidubi23 said:
I want to go from 9 to 7 because i accidentally installed an android 11 rom, is that possible?
Click to expand...
Click to collapse
Nope

Nubidubi23 said:
Hi, thanks for answering. I found an A9 rom for my phone, but when i flash it in TWRP 3.6.1 A11 it gets stuck in bootloop. Tried flashing multidisabler afterwards and wiping it but still nothing. Any ideas?
Click to expand...
Click to collapse
Flashing Custom Recovery and/or ROOT on A50 is quite different with few extra steps. Do the searching in our forum, u'll find the information u need.
P/S : Always read carefully ROM's Install Instructions, it cover all the info u may need!