Develop Bugs

red triangle while trying to update OTA lollipop while on TWRP...

Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376

jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.

flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.

jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!

jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.

If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).

redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.

flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.

redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.

flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.

redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.

flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.

So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2

[rooted] H815 can't OTA update because of TWRP

Hi folks,
Almost everything is in the subject.
I'm absolutely convinced I'm not the first one to experience this, but I can't find any thread about it ...
My LG G4 H815 is rooted with TWRP installed. I've got the OTA notification for a V20d-JAN-15-2016 (actually running V10d-EUR-XX).
I can download and initiate the update, but my phone reboots in TWRP (instead of bootloader I suppose ?) and the update hangs here.
Is there a way to go through this ?
Thx
Diego

Narsil said:
Hi folks,
Almost everything is in the subject.
I'm absolutely convinced I'm not the first one to experience this, but I can't find any thread about it ...
My LG G4 H815 is rooted with TWRP installed. I've got the OTA notification for a V20d-JAN-15-2016 (actually running V10d-EUR-XX).
I can download and initiate the update, but my phone reboots in TWRP (instead of bootloader I suppose ?) and the update hangs here.
Is there a way to go through this ?
Thx
Diego
Click to expand...
Click to collapse
Once you put a custom recovery on your device or make any other system changes it blocks the ota from being installed and even if the ota went through (which it can't) you'll lose root , you should already know this information ...
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
Oh and p.s when you rooted your phone you should of gone in the settings and unticked for the system to check for updates automatically , if you didn't do that then do it now ...

Xceeder said:
Once you put a custom recovery on your device or make any other system changes it blocks the ota from being installed and even if the ota went through (which it can't) you'll lose root , you should already know this information ...
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
Oh and p.s when you rooted your phone you should of gone in the settings and unticked for the system to check for updates automatically , if you didn't do that then do it now ...
Click to expand...
Click to collapse
You're right I should, but I never faced this limitation on my prior phones (nexus/samsung/moto), so I didn't !
But I'm still confident there is a solution !

If you have twrp, you should flash the v20d flash files, offered in the general section the g4 forum
Sent from my LG-H815 using Tapatalk

ObiDanKenobi said:
If you have twrp, you should flash the v20d flash files, offered in the general section the g4 forum
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Didn't find any flashable v20d file in the forum. Did I miss something?

Narsil said:
Didn't find any flashable v20d file in the forum. Did I miss something?
Click to expand...
Click to collapse
Sure did. Very easily found.
http://forum.xda-developers.com/showthread.php?t=3301366

LG Bridge is a solution
Narsil said:
Hi folks,
Almost everything is in the subject.
I'm absolutely convinced I'm not the first one to experience this, but I can't find any thread about it ...
My LG G4 H815 is rooted with TWRP installed. I've got the OTA notification for a V20d-JAN-15-2016 (actually running V10d-EUR-XX).
I can download and initiate the update, but my phone reboots in TWRP (instead of bootloader I suppose ?) and the update hangs here.
Is there a way to go through this ?
Thx
Diego
Click to expand...
Click to collapse
You can use LG Bridge app to update your phone as long you use original LG rom.
No need to create account even, unless you want to use backup feature.
EDIT: You will need to root the phone again after the update is finished (bootloader remains unlocked).

Confirming above for H815 EU rooted and bootloader unlocked, coming from v20D.
The notifications to update were really annoying me so i bit the bullet...
Update via LG bridge - all apps and data retained, but lost root and TWRP.
Followed this guide (again!) to install TWRP and gain root (scroll down til you find the relevant bit), hooray.
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Make sure to use newest SuperSU (v2,76 currently)
Now just got to remember how i disabled the annoying boot sound!

Guys when will people learn if your rooted or twrp you should never attempt to ota best case scenario it wont update worst case other than bricks is hard bricks and or even on unlockable bootloader is complete loss of root. some device manifactueres even went as far as blocking boooader unlock. And unablity to downgrade.
Never ota wait for modified updates. This has always been one of the first rules of rooting next to backups backups backups!!!

obo789 said:
Confirming above for H815 EU rooted and bootloader unlocked, coming from v20D.
The notifications to update were really annoying me so i bit the bullet...
Update via LG bridge - all apps and data retained, but lost root and TWRP.
Followed this guide (again!) to install TWRP and gain root (scroll down til you find the relevant bit), hooray.
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Make sure to use newest SuperSU (v2,76 currently)
Now just got to remember how i disabled the annoying boot sound!
Click to expand...
Click to collapse
can you specify what are the relevant bits? Because one of the steps in rooting says "fastboot oem unlock (this wipes ALL data!!)", and I really don't want to do that again :angel:

Reinstall twrp (instructions use old twrp, I used newer 3.0.2 version)
fastboot boot twrp-2.8.7.1-h811.img
6. For perm TWRP: In TWRP hit Install > Images... (bottom right corner) > select TWRP.img on ext sdcard > select "recovery" > swipe.
Click to expand...
Click to collapse
Then flash supersu, done!

hey, it seems it worked like a charm, no data lost, very fast, so I am VERY pleased. Thanks a lot, really!

[Q] Root for H812 (Bell) Running Marshmallow?

Hey everyone,
I have searched for quite a while and simply couldn't find a root method for my Canadian G4 running Marshmallow. If there is none, is it possible to downgrade? It doesn't seem to me like there is any root for any model running Marshmallow
Thanks,
Dan

Root is not available for the H812 on Marshmallow. Yes, you can downgrade to Lollipop and install root. However, you would lose all your data if you do this.
Check these posts for steps on flashing Lollipop back on your device:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803

sleepy_76 said:
Root is not available for the H812 on Marshmallow. Yes, you can downgrade to Lollipop and install root. However, you would lose all your data if you do this.
Check these posts for steps on flashing Lollipop back on your device:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
I can't find a link for Bell H812 20E. I don't mind downgrading from MM to LP.

h812 Marshmallow Root
magickarle said:
I can't find a link for Bell H812 20E. I don't mind downgrading from MM to LP.
Click to expand...
Click to collapse
Hi everyone,
I have been searching high and low for a proper method to root this otherwise useless device. Does anyone have a guide that actually works for them to obtain root on Bell LG G4 (h812) on Marshmallow?
I will downgrade if necessary, data loss is not an issue at this point.
I am also wanting to use alternate ROM if any are available for this device.
ON a separate note, is there another model of the LG G4 that is interchangable with the h812 that I can safely use it's ROMs and Root method, or does it HAVE to be specifically for the h812 model?
Thank Kindly!!

905jay said:
Hi everyone,
I have been searching high and low for a proper method to root this otherwise useless device. Does anyone have a guide that actually works for them to obtain root on Bell LG G4 (h812) on Marshmallow?
I will downgrade if necessary, data loss is not an issue at this point.
I am also wanting to use alternate ROM if any are available for this device.
ON a separate note, is there another model of the LG G4 that is interchangable with the h812 that I can safely use it's ROMs and Root method, or does it HAVE to be specifically for the h812 model?
Thank Kindly!!
Click to expand...
Click to collapse
The only way to root LG G4 on MM (for now) is to downgrade it to LP and then copy over a rooted image using DD command.

Thanks. Would you know where I could find a proper guide for bell h812? It's my daily driver ....

frolovvl said:
The only way to root LG G4 on MM (for now) is to downgrade it to LP and then copy over a rooted image using DD command.
Click to expand...
Click to collapse
So once you downgrade to lolipop and root, how can you bring it back to marshmellow?

Check this out and read EVERYTHING carefully ...
905jay said:
Thanks. Would you know where I could find a proper guide for bell h812? It's my daily driver ....
Click to expand...
Click to collapse
Check this out and read EVERYTHING carefully (EVERYTHING you need is there) ... [Canadian Guide] - Complete Source for the LG G4 H812. Linux VM/Root/Tools&Files: https://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Once done: then check this out for a custom recovery - [LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all locked G4 devices:
https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
- use version 3 Beta 4 first, linked in post # 193: for me it has been the most stable:
Enjoy
S.
---------- Post added at 07:33 PM ---------- Previous post was at 07:19 PM ----------
BIG_BADASS said:
So once you downgrade to lolipop and root, how can you bring it back to marshmellow?
Click to expand...
Click to collapse
Use LGUP - NEW (https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803), re-install the stock Lollipop rom (kdz) you used (before flashing the rooted image you used to get root), then ... upgrade again with LGUP - NEW with the appropriate MM kdz (you can check here for that): https://lg-firmwares.com/lg-h812-firmwares/
Suggest you read the Canadian Guide referenced above, thoroughly as well.
S.
PS - Remember the Thanks button.

sdembiske said:
Check this out and read EVERYTHING carefully (EVERYTHING you need is there) ... [Canadian Guide] - Complete Source for the LG G4 H812. Linux VM/Root/Tools&Files: https://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Once done: then check this out for a custom recovery - [LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all locked G4 devices:
https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
- use version 3 Beta 4 first, linked in post # 193: for me it has been the most stable:
Enjoy
S.
---------- Post added at 07:33 PM ---------- Previous post was at 07:19 PM ----------
Use LGUP - NEW (https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803), re-install the stock Lollipop rom (kdz) you used (before flashing the rooted image you used to get root), then ... upgrade again with LGUP - NEW with the appropriate MM kdz (you can check here for that): https://lg-firmwares.com/lg-h812-firmwares/
Suggest you read the Canadian Guide referenced above, thoroughly as well.
S.
PS - Remember the Thanks button.
Click to expand...
Click to collapse
Thank you, this is just what I have been looking for. But do I need to install a custom recovery tool such as TWRP or CWM before I root it? Because the bootloader on the H812 is locked so who knows what flashing might do.

BIG_BADASS said:
So once you downgrade to lolipop and root, how can you bring it back to marshmellow?
Click to expand...
Click to collapse
There's no way to get it back to MM unless you in-root it and use OTA. Unfortunately on all G4 except European variant bootloader is locked and LG doesn't want to open that for us.
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
BIG_BADASS said:
Thank you, this is just what I have been looking for. But do I need to install a custom recovery tool such as TWRP or CWM before I root it? Because the bootloader on the H812 is locked so who knows what flashing might do.
Click to expand...
Click to collapse
As you noticed, the BL is locked. Without unlocking it you'll not be able to install either custom recovery on H812.

You are WRONG ...
frolovvl said:
There's no way to get it back to MM unless you in-root it and use OTA. Unfortunately on all G4 except European variant bootloader is locked and LG doesn't want to open that for us.
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
As you noticed, the BL is locked. Without unlocking it you'll not be able to install either custom recovery on H812.
Click to expand...
Click to collapse
Read the post regarding TWRP-in-Fish, it allows a custom recovery WITH a locked bootloader and has been tested by me on my H812, ReeS86 (who led the way on the H812) and many others with different models with locked bootloaders - do not proclaim what you do not know. You CAN restore back to MM by re-installing the stock Lollipop KDZ with LGUP - NEW and then, using LGUP - NEW again, upgrade back to MM stock provided you have the right KDZ. You cannot however, install a custom rom, as yet. It is being worked on, however, by steadfasterX, first on unlocked bootloaders, then on locked bootloaders ... with a little luck and a lot of his hard work we will have the ability at that point
Do your homework before making proclamations, please!
S.
---------- Post added at 10:59 PM ---------- Previous post was at 10:41 PM ----------
BIG_BADASS said:
Thank you, this is just what I have been looking for. But do I need to install a custom recovery tool such as TWRP or CWM before I root it? Because the bootloader on the H812 is locked so who knows what flashing might do.
Click to expand...
Click to collapse
No, No ... no - please read the posts in the links thoroughly ... you install TWRP-in-FisH AFTER u have got a rooted system image installed. YOU WILL NOT (repeating ad nauseam) BE ABLE TO INSTALL A CUSTOM ROM (at this point any way, until we have a successful efidroid port to a locked LG G4), as you will still have a locked bootloader. You will simply have a way to get back to where you have gotten to at any point in time and if you suffer a hardware bootloop you will be able to get back to where u were once your phone is repaired. And please note, if and when in TWRP (from the TWRP-in-FisH install), it asks you if u want to install TWRP, do not respond Yes - you will brick as it tries to install to your stock recovery partition which cannot be done with a locked bootloader.
Just read all the posts thoroughly, please.
Good Luck,
S.

Thank you Sir! you're right, you can install a body without a head...
sdembiske said:
Read the post regarding TWRP-in-Fish, it allows a custom recovery WITH a locked bootloader and has been tested by me on my H812, ReeS86 (who led the way on the H812) and many others with different models with locked bootloaders - do not proclaim what you do not know. You CAN restore back to MM by re-installing the stock Lollipop KDZ with LGUP - NEW and then, using LGUP - NEW again, upgrade back to MM stock provided you have the right KDZ. You cannot however, install a custom rom, as yet. It is being worked on, however, by steadfasterX, first on unlocked bootloaders, then on locked bootloaders ... with a little luck and a lot of his hard work we will have the ability at that point
Do your homework before making proclamations, please!
S.
---------- Post added at 10:59 PM ---------- Previous post was at 10:41 PM ----------
No, No ... no - please read the posts in the links thoroughly ... you install TWRP-in-FisH AFTER u have got a rooted system image installed. YOU WILL NOT (repeating ad nauseam) BE ABLE TO INSTALL A CUSTOM ROM (at this point any way, until we have a successful efidroid port to a locked LG G4), as you will still have a locked bootloader. You will simply have a way to get back to where you have gotten to at any point in time and if you suffer a hardware bootloop you will be able to get back to where u were once your phone is repaired. And please note, if and when in TWRP (from the TWRP-in-FisH install), it asks you if u want to install TWRP, do not respond Yes - you will brick as it tries to install to your stock recovery partition which cannot be done with a locked bootloader.
Just read all the posts thoroughly, please.
Good Luck,
S.
Click to expand...
Click to collapse
:crying:

Honor 7X EMUI 8 Oreo Download Link

Hi guys,
I'm using Honor 7x BND-AL10C675 (Indian). I wanted to get back to stock as emui 8 stable rolled out. I was running emui 8 beta and I was stuck so I flashed the stock recovery, re locked bootloader, and downloaded the EMUI 8 update.app file from "Huawei firmware finder". Now, I created the "dload" folder in sd card and pressing both volume buttons and power button, I tried to install the firmware.
It says "The update failed" at 5% and I tried it many times. Maybe it's a mismatch or incompatible. Now, I can't go back to my twrp backup as stock recovery was installed. I can't flash recovery or rom using fastboot as it requires unlocked bootloader. To unlock bootloader, I need to enable "OEM UNLOCK" in settings and I can't boot into system as everything is wiped when I relocked the bootloader. So I'm basically stuck.
The only things I can do now is to install the stock firmware using the dload method. However, I need the right update.app file so I can install using install the firmware. I can't use Nougat file as I guess we can't go back to Nougat from Oreo. So I need EMUI 8 firmware BND AL10C675.
I can't find it anywhere, so Could someone miraculously post a download link or the file here? What should I be doing?

Thetpcguy said:
Hi guys,
I'm using Honor 7x BND-AL10C675 (Indian). I wanted to get back to stock as emui 8 stable rolled out. I was running emui 8 beta and I was stuck so I flashed the stock recovery, re locked bootloader, and downloaded the EMUI 8 update.app file from "Huawei firmware finder". Now, I created the "dload" folder in sd card and pressing both volume buttons and power button, I tried to install the firmware.
It says "The update failed" at 5% and I tried it many times. Maybe it's a mismatch or incompatible. Now, I can't go back to my twrp backup as stock recovery was installed. I can't flash recovery or rom using fastboot as it requires unlocked bootloader. To unlock bootloader, I need to enable "OEM UNLOCK" in settings and I can't boot into system as everything is wiped when I relocked the bootloader. So I'm basically stuck.
The only things I can do now is to install the stock firmware using the dload method. However, I need the right update.app file so I can install using install the firmware. I can't use Nougat file as I guess we can't go back to Nougat from Oreo. So I need EMUI 8 firmware BND AL10C675.
I can't find it anywhere, so Could someone miraculously post a download link or the file here? What should I be doing?
Click to expand...
Click to collapse
you need this?
http://pro-teammt.ru/firmware-database/?firmware_model=BND-AL10+8.0.0.320&firmware_page=0

Thats' so fast!! I really thank you for coming at rescue for a fellow XDA member. Thanks for the link and I couldn't find the link myself really. Do you have any idea which file I should download? there is one full Ota MF and other two are just Ota MF. Maybe full Ota mf? I guess I downloaded the firmware from the app from these guys or website only on my android phone. I will do it now on my laptop now. Let's hope it works!! Thanks again

mrmazak said:
you need this?
http://pro-teammt.ru/firmware-database/?firmware_model=BND-AL10+8.0.0.320&firmware_page=0
Click to expand...
Click to collapse
Thats' so fast!! I really thank you for coming at rescue for a fellow XDA member. Thanks for the link and I couldn't find the link myself really. Do you have any idea which file I should download? there is one full Ota MF and other two are just Ota MF. Maybe full Ota mf? I guess I downloaded the firmware from the app from these guys or website only on my android phone. I will do it now on my laptop now. Let's hope it works!! Thanks again

mrmazak said:
you need this?
http://pro-teammt.ru/firmware-database/?firmware_model=BND-AL10+8.0.0.320&firmware_page=0
Click to expand...
Click to collapse
I downloaded it but the update failed again. I guess the file is not the right one for this model but I don't know why it's listed as the right model. I thought I could install stock Emui 8 Rom by downloading from "firmware finder" so I just locked myself out of all the options now. Such a shame

Thetpcguy said:
I downloaded it but the update failed again. I guess the file is not the right one for this model but I don't know why it's listed as the right model. I thought I could install stock Emui 8 Rom by downloading from "firmware finder" so I just locked myself out of all the options now. Such a shame
Click to expand...
Click to collapse
I'm not positive on the correct DLOAD method
I think you extract the update.zip to dload folder on sdcard.
The whole zip package, not just the update.app

Thetpcguy said:
I downloaded it but the update failed again. I guess the file is not the right one for this model but I don't know why it's listed as the right model. I thought I could install stock Emui 8 Rom by downloading from "firmware finder" so I just locked myself out of all the options now. Such a shame
Click to expand...
Click to collapse
Did you do this guide?
https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240

I followed all the steps and I guess it's more complicated for me. I was stuck with an older build number although I changed different ROMS. Maybe because of that the update doesn't authenticate and fails to install the firmware. I don't know but also it maybe that the firmware isn't for my exact model. I just don't know and my phone is as good as bricked and I"m taking it to service centre.
What's more hurting is that, I Locked myself out of all the options. I mean I have the bootloader unlock code, Twrp backup but I just went through a one way route so confidently that it would work and I locked bootloader, flashed stock recovery. It's such a shame that HUAWEI DOESN'T RELEASE THE STOCK FIRMWARE EVEN AFTER ALMOST 6 MONTHS OF THE HONOR 7X RELEASE. If they had the stock firmware available just like Xiaomi, I wouldn't have had all this trouble.
I don't know why no one raises the voice. I really hate Huawei for this and I'll make sure I won't recommend these phones to anyone.

Thetpcguy said:
I followed all the steps and I guess it's more complicated for me. I was stuck with an older build number although I changed different ROMS. Maybe because of that the update doesn't authenticate and fails to install the firmware. I don't know but also it maybe that the firmware isn't for my exact model. I just don't know and my phone is as good as bricked and I"m taking it to service centre.
What's more hurting is that, I Locked myself out of all the options. I mean I have the bootloader unlock code, Twrp backup but I just went through a one way route so confidently that it would work and I locked bootloader, flashed stock recovery. It's such a shame that HUAWEI DOESN'T RELEASE THE STOCK FIRMWARE EVEN AFTER ALMOST 6 MONTHS OF THE HONOR 7X RELEASE. If they had the stock firmware available just like Xiaomi, I wouldn't have had all this trouble.
I don't know why no one raises the voice. I really hate Huawei for this and I'll make sure I won't recommend these phones to anyone.
Click to expand...
Click to collapse
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...?
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
Thetpcguy said:
I followed all the steps and I guess it's more complicated for me. I was stuck with an older build number although I changed different ROMS. Maybe because of that the update doesn't authenticate and fails to install the firmware. I don't know but also it maybe that the firmware isn't for my exact model. I just don't know and my phone is as good as bricked and I"m taking it to service centre.
What's more hurting is that, I Locked myself out of all the options. I mean I have the bootloader unlock code, Twrp backup but I just went through a one way route so confidently that it would work and I locked bootloader, flashed stock recovery. It's such a shame that HUAWEI DOESN'T RELEASE THE STOCK FIRMWARE EVEN AFTER ALMOST 6 MONTHS OF THE HONOR 7X RELEASE. If they had the stock firmware available just like Xiaomi, I wouldn't have had all this trouble.
I don't know why no one raises the voice. I really hate Huawei for this and I'll make sure I won't recommend these phones to anyone.
Click to expand...
Click to collapse
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...

srvm1983 said:
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...
Click to expand...
Click to collapse
Phone is sold as a scrap for 2000 RS (30$ approx) There was no way to revive it after losing that fastboot and getting that above said error state.

Is there any safe method to update MEE7S using global rom yet?

I'm using RN5 chinese edition, but currently I'm using global stable rom.
I've just read that the new update will brick chinese phones running global stable rom. Is there any way to avoid the brick / recover from such thing?

Where did You read that ?
As far as i know, as long as you have unlocked bootloader you can install global mui on chinese device. Just leave your bootloader unlocked

Do not update before you unlocked the Bootloader.
Unlocked first then update.
If you see the problem (stuck in recovery mode).. You must flashing china rom first via fastboot metode. Then flash global rom...
I have tested. (Mee7s)

MikiGry said:
Where did You read that ?
As far as i know, as long as you have unlocked bootloader you can install global mui on chinese device. Just leave your bootloader unlocked
Click to expand...
Click to collapse
This is the article I read: Article

ruditremonti said:
Do not update before you unlocked the Bootloader.
Unlocked first then update.
If you see the problem (stuck in recovery mode).. You must flashing china rom first via fastboot metode. Then flash global rom...
I have tested. (Mee7s)
Click to expand...
Click to collapse
I see that you have MEE7S, which is the exact same device as the one I use.
So, did you succeed on upgrading the first time? Please tell me more. Do you use fastboot method (bypassing ARB first with dummy image or not) or how?

My Redmi Note 5 Bricked after MIUI 10 update
MikiGry said:
Where did You read that ?
As far as i know, as long as you have unlocked bootloader you can install global mui on chinese device. Just leave your bootloader unlocked
Click to expand...
Click to collapse
My phone gave me an option to update and it downloaded the image and then asked to restart so I did like have done in the past for v9 incremental updates.
It download the new ROM and I accepted the Restart Phone. After restarting I got a warning message at the bottom of the screen in red "This MIUI version can't be installed on this device" and the options are:
1. Reboot, which just brings me back to this same screen on startup.
2. Wipe Data. This goes through a wipe storage but it doesn't make any difference and just brings me back to the same screen after a restart.
3. Connect with MIAssistant. With MiPCSuite installed, it doesn't connect and just hangs.
Chatting to Mi Support, they tell me they don't recognise the phone even though I provided the IMEI number and the fact it is less than 1 year old. I bought it off Ebay new unused.
So now I have a bricked useless phone. Well done Xiaomi

@moby17
Can you boot your phone into fastboot mode ?
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
gamalkevin said:
This is the article I read: Article
Click to expand...
Click to collapse
Well.That"s new
This article has a one flaw. Were those devices officialy unlocked or fake-unlocked ?

Well it goes into Fastboot screen but just sits there.
MikiGry said:
@moby17
Can you boot your phone into fastboot mode ?
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
Well.That"s new
This article has a one flaw. Were those devices officially unlocked or fake-unlocked ?
Click to expand...
Click to collapse
Well it goes into Fastboot screen but just sits there. I remember it did one update when it was still MIUI 9 something earlier this year and right after that an annoying message would show up a few times a day near the top saying it wasn't an official Rom. I just touched on close and it would carry on working fine. The update to MIUI 10 was in settings, system update section.
Since then someone recommended flashing it back to v9 and using MI's rom flash app MiFlash I'm in the process of flashing it now. The small green progress bar has gone all the way to the end but in Result column it is still showing "Flashing". after 2 hours. Not sure if it's completed or not, will leave it alone for another few hours before rebooting it.

moby17 said:
Well it goes into Fastboot screen but just sits there. I remember it did one update when it was still MIUI 9 something earlier this year and right after that an annoying message would show up a few times a day near the top saying it wasn't an official Rom. I just touched on close and it would carry on working fine. The update to MIUI 10 was in settings, system update section.
Since then someone recommended flashing it back to v9 and using MI's rom flash app MiFlash I'm in the process of flashing it now. The small green progress bar has gone all the way to the end but in Result column it is still showing "Flashing". after 2 hours. Not sure if it's completed or not, will leave it alone for another few hours before rebooting it.
Click to expand...
Click to collapse
Is your device a chinese version with global rom and fake-unlocked bootloader ?
Which rom are you trying to flash ? China or Global ? ARB 4 or ARB 3 ?

MikiGry said:
Is your device a chinese version with global rom and fake-unlocked bootloader ?
Which rom are you trying to flash ? China or Global ? ARB 4 or ARB 3 ?
Click to expand...
Click to collapse
What is fake-unlocked bootloader exactly? Currently I have it unlocked (from what I know), and am on MIUI global before the latest update. Probably ARB 4.
I'm low-key hesitant to upgrade, because I don't want to wipe my phone in case anything bad happen, and worse, bricking.

I'm in the UK and it was a Global Rom.
gamalkevin said:
What is fake-unlocked bootloader exactly? Currently I have it unlocked (from what I know), and am on MIUI global before the latest update. Probably ARB 4.
I'm low-key hesitant to upgrade, because I don't want to wipe my phone in case anything bad happen, and worse, bricking.
Click to expand...
Click to collapse
I wouldn't upgrade it if I were you, you might brick it too.
I'm trying to flash it with a rom, any rom would do to get it back to a working condition but I haven't been able to flash it. I'm using MiFlash, I've tried China, Global, both newer 10 versions and the 9 without success.
I'm not sure what you mean by ARB 3 and 4.
There seems to be 2 types of ROMs available to down load. One for MiFlash
i.e whyred_global_images_9.6.20_20190620.0000.00_9.0_global_006620721b and the 10.x version which has 1 folder called Images and a list of .bat files
flash_all.bat
flash_all_except_data.bat
flash_all_lock.bat and a dozen more files.
and another miui_HMNote5Global_9.6.20_9d5e732488_9.0 and Chgina rommiui_HMNote5_V10.3.1.0.PEICNXM_38eb804e2b_9.0
with
Folders Firmware-Update, META-INFO and compatabily.zip
a boot.img file and another 6 files. For instance system.new.dat.br, system.patch.dat

gamalkevin said:
I see that you have MEE7S, which is the exact same device as the one I use.
So, did you succeed on upgrading the first time? Please tell me more. Do you use fastboot method (bypassing ARB first with dummy image or not) or how?
Click to expand...
Click to collapse
I have try upgrading from ota & flash rom via twrp but stuck in mi logo.
Then i trying flash china rom first (10.3.4.0 stable oreo) via fastboot method, let it booting and flash global rom (10.3.1.0 stable pie) via fastboot method too.
Succeed, no stuck in mi logo..

ruditremonti said:
I have try upgrading from ota & flash rom via twrp but stuck in mi logo.
Then i trying flash china rom first (10.3.4.0 stable oreo) via fastboot method, let it booting and flash global rom (10.3.1.0 stable pie) via fastboot method too.
Succeed, no stuck in mi logo..
Click to expand...
Click to collapse
Okay. Thanks for the information.