Develop Bugs

[Q] So I have the B508 system...but I need the international version!

Hello! I bought a P6 very recently, but it turns out that its stock system is based on the Chinese local store, not Google Store! This is a very big problem as I am a Canadian user, and I have many apps and personal information that's associated with my Google account.
The current version of my p6 is B508 after the kitkat update. So can anyone please shed some light on how I can replace it with an international rom? I see so many versions flying around and I don't know where to start anymore...step by step guidance would be greatly appreciated, as I'm a noob with custom roms.
Thank you all in advance!

kesun said:
Hello! I bought a P6 very recently, but it turns out that its stock system is based on the Chinese local store, not Google Store! This is a very big problem as I am a Canadian user, and I have many apps and personal information that's associated with my Google account.
The current version of my p6 is B508 after the kitkat update. So can anyone please shed some light on how I can replace it with an international rom? I see so many versions flying around and I don't know where to start anymore...step by step guidance would be greatly appreciated, as I'm a noob with custom roms.
Thank you all in advance!
Click to expand...
Click to collapse
Look here, bottom post http://forum.xda-developers.com/ascend-p6/general/huawei-p6-u06-chinese-rom-help-t2864228

osstis said:
Look here, bottom post http://forum.xda-developers.com/ascend-p6/general/huawei-p6-u06-chinese-rom-help-t2864228
Click to expand...
Click to collapse
I tried to boot into the bootloader by both methods (pressing volume down + power button, and from the command line), but both method got me stuck on the white screen with orange WO logo. Is this a common problem? How do I get around it?
ie. The device shows up when i go adb devices, so this part is fine at least.

kesun said:
I tried to boot into the bootloader by both methods (pressing volume down + power button, and from the command line), but both method got me stuck on the white screen with orange WO logo. Is this a common problem? How do I get around it?
ie. The device shows up when i go adb devices, so this part is fine at least.
Click to expand...
Click to collapse
Changing from b508 is little irritating process, but it's possible ,, first you've to downgrade to b132 ,,,then you can upgrade to kit Kat versions,,,, directly you can't change from b508 to international kit Kat versions,,

kesun said:
Hello! I bought a P6 very recently, but it turns out that its stock system is based on the Chinese local store, not Google Store! This is a very big problem as I am a Canadian user, and I have many apps and personal information that's associated with my Google account.
The current version of my p6 is B508 after the kitkat update. So can anyone please shed some light on how I can replace it with an international rom? I see so many versions flying around and I don't know where to start anymore...step by step guidance would be greatly appreciated, as I'm a noob with custom roms.
Thank you all in advance!
Click to expand...
Click to collapse
I find B508 is way better than international kitkat roms. For google play, go to the Huawei app store app and then search for google play and install it. or alternately download google play apk file and install it.

kesun said:
I tried to boot into the bootloader by both methods (pressing volume down + power button, and from the command line), but both method got me stuck on the white screen with orange WO logo. Is this a common problem? How do I get around it?
ie. The device shows up when i go adb devices, so this part is fine at least.
Click to expand...
Click to collapse
I believe that "white screen with orange WO logo" it's in your case a bootloader mode so type "fastboot flash recovery {here type your stock recovery file name.img} after that, force update.app (P6 Unicom EMUI2.0) (power and both volumes) make sure you got update.app in sd/dload folder and then just update to B132.
Your recovery file should be placed in adb folder

osstis said:
I believe that "white screen with orange WO logo" it's in your case a bootloader mode so type "fastboot flash recovery {here type your stock recovery file name.img} after that, force update.app (P6 Unicom EMUI2.0) (power and both volumes) make sure you got update.app in sd/dload folder and then just update to B132.
Your recovery file should be placed in adb folder
Click to expand...
Click to collapse
So I decided to give fate a shot, and went straight with your method (started copying the first .app file to the SD and update it). It worked! So it seems like my device's bootloader was already unlocked? Anyways, I followed your method seeing that the first step was successful, and now I have the international kitkat with full working Google Store! My deepest gratitude to all of you!
@warea: I actually had the Google Play services installed, but it would simply crash on me after I entered my account, just before the policy page showed up. I reset the phone multiple times, went with all the methods I could find about getting Google Play to work with the Chinese version, but I couldn't...Which makes sense, because it's likely forcefully blocked to avoid conflict on interest. That's my guess though!

Uhmm That's weird, I have no problems with google services at all. I've changed official roms B132, B125, B510, B512. B634 a multiple times and Google always works. Which Rom you are running now? In my case B132 is best one, I will wait for another KitKat release as for now all KitKat seems to be a little sluggish for me.

Hi.
I'm in similar situation as kesun (OP) was: I'm running B508 right now and I want to install the international version B512. Google Play Store was installed, but it also crashes everytime I open it and it can't be fixed with any of the suggestions found online (downloading newer version, updating Google Play Services, clearind data and cache, etc.)
I know that in order to install B512 I have to first install B132, but I recently discovered that the bootloader in my phone is locked, does that prevent me to doing this? If so, how do I unlock it?
Thank you all in advance.

Can anyone please give me a hand here? I've been told that the bootloader doesn't have to be unlocked to install official firmware, so I gave it a try.
The methods described here involve flashing EMUI 2.0 (which I already have, do I need to flash it again?, can I do that with bootloader locked?), then installing the B132 firmware and them the B512.
I encountered a problem when installing B132 via local update. It says "Huawei SD card update failed", then it does a couple of steps and gives a big FAILED.
I remind you the my bootloader is locked. I suspect this is the problem. I'm currently running 4.4.2 with B508.
Sent from my HUAWEI P6-U06 using XDA Free mobile app

Try the suggested method and install the emui 2.0 even though you already have it, because I know few months ago people had problem reverting back to jb without the update. Then you can try to install the B132.
Sent from my P6-U06 using xda app-developers app

Thank you. I'll try that then.

There is a downgrade update.app for EMUI 2.0 just search here on XDA otherwise you will not be able to downgrade.

taaeem said:
There is a downgrade update.app for EMUI 2.0 just search here on XDA otherwise you will not be able to downgrade.
Click to expand...
Click to collapse
Thank you, taaeem. Would hat cause the error I described ("Huawei SD card update FAIL")? or there could be other reasons for that?

Adrianrff said:
Thank you, taaeem. Would hat cause the error I described ("Huawei SD card update FAIL")? or there could be other reasons for that?
Click to expand...
Click to collapse
Yes this would cause such a error message, there could be a different problem but I don't think that.
Search for EMUI 2.0 downgrade

taaeem said:
Yes this would cause such a error message, there could be a different problem but I don't think that.
Search for EMUI 2.0 downgrade
Click to expand...
Click to collapse
Thanks again, mate.
EDIT @taaeem, sorry for the hassle, but I have a few more doubts.
Is it important which version of the firmware and which Android version i'm coming from? I'm running B508 right now, which is a KitKat firmware. Can I just flash a 4.2 firmware (B132) from a 4.4 firmware? I've seen many post talking about flashing some other stock recovery in order to being able to go from B50x to B132 and then to B512. Do I need to have bootloader unlocked for this? If you culd just go through the steps quickly I'd appreciate it greatly.
Thanks in advance

Adrianrff said:
Thanks again, mate.
EDIT @taaeem, sorry for the hassle, but I have a few more doubts.
Is it important which version of the firmware and which Android version i'm coming from? I'm running B508 right now, which is a KitKat firmware. Can I just flash a 4.2 firmware (B132) from a 4.4 firmware? I've seen many post talking about flashing some other stock recovery in order to being able to go from B50x to B132 and then to B512. Do I need to have bootloader unlocked for this? If you culd just go through the steps quickly I'd appreciate it greatly.
Thanks in advance
Click to expand...
Click to collapse
No need of other stock recovery just download the downgrade update.app and put it on your dload folder and update. Than put B132 update.app in the dload folder IMPORTANT delete the other file before.
And then update again and that should work.

taaeem said:
No need of other stock recovery just download the downgrade update.app and put it on your dload folder and update. Than put B132 update.app in the dload folder IMPORTANT delete the other file before.
And then update again and that should work.
Click to expand...
Click to collapse
All done!

Will say Update FAILED if USB cable is plugged in, must UNPLUG usb cable for stock recovery to update successfully.

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

RETUS Nougat Firmware Package?

I've been searching high and low for a full nougat firmware package for the RETUS model... and i cant find one. Has anyone else found one?
I know there are OTAs out there, I'm looking for an FXZ that can be used with fastboot.
filefactory, mirrors.lolinet, etc... seem to have most 7.0 firmware packages EXCEPT for RETUS which only have 6.0 packages.

I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.

Jimi Mack said:
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Click to expand...
Click to collapse
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.

FanDroid09 said:
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
Click to expand...
Click to collapse
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?

chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
What did you do to root? Unlock bootloader then what?

chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.

EspElement said:
What did you do to root? Unlock bootloader then what?
Click to expand...
Click to collapse
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
FanDroid09 said:
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
Click to expand...
Click to collapse
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.

Does anyone know where to get the latest either RETAIL or RETUS stock firmware with the May 1st security update? NPN25.137-24.4

chris23445 said:
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Click to expand...
Click to collapse
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader

EspElement said:
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
Click to expand...
Click to collapse
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.

chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
Is it worth after all?

chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
I've been there done that that's for sure. I just bricked one of my Moto Z plays last week doing what you were about to do.

StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.

tpx00 said:
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
Click to expand...
Click to collapse
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh

EspElement said:
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
Click to expand...
Click to collapse
Ya I'm about to go pick up a nexus 6 from craigslist until mine comes back from Motorola.

Updating BND-L21 To Stable Stock Oreo / Any Daily Driver Oreo Custom Rom

Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?

mimminou said:
Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
Click to expand...
Click to collapse
My opinion is there is little to no need to backup nougat. Because there is a "roll-back" firmware available and also when you upgrade to Oreo the partition table gets changed , so the twrp backup will not work anyhow.
To make ylur update, if ota is not working, then search for and use "hwota".

mrmazak said:
My opinion is there is little to no need to backup nougat. Because there is a "roll-back" firmware available and also when you upgrade to Oreo the partition table gets changed , so the twrp backup will not work anyhow.
To make ylur update, if ota is not working, then search for and use "hwota".
Click to expand...
Click to collapse
Thank you ... i made sure to look up every way possible to upgrade and yet didn't find HwOTA until you told me about it, lots of interesting stuff to learn on the tool !
i'll give it a try whne i get back home ! thanks again
EDIT : i just noticed that you are the op of the guide i followed , very detailed and well explained !

mimminou said:
Thank you ... i made sure to look up every way possible to upgrade and yet didn't find HwOTA until you told me about it, lots of interesting stuff to learn on the tool !
i'll give it a try when i get back home ! thanks again
Click to expand...
Click to collapse
So i checked the HWota methode and it seemed very legitimate .... well when i tried it i even got the EMUI logo and beneath it it says Updating ... at 100 percent the phone rebooted and .... nothing happened, not even data was erased ... well actually 2 things happened :
- My bootloader was locked back and now i have stock recovery ( which is nice tbh i was looking for ways to get it back .. and i still got the unlock code so i'm good to go )
- My phone now actually notified me that there is an OTA update to Oreo and that's the thing i was looking for .... so did it work ? kind of , did i fulfill my goal ? Yes i did and Thank you so much

mimminou said:
So i checked the HWota methode and it seemed very legitimate .... well when i tried it i even got the EMUI logo and beneath it it says Updating ... at 100 percent the phone rebooted and .... nothing happened, not even data was erased ... well actually 2 things happened :
- My bootloader was locked back and now i have stock recovery ( which is nice tbh i was looking for ways to get it back .. and i still got the unlock code so i'm good to go )
- My phone now actually notified me that there is an OTA update to Oreo and that's the thing i was looking for .... so did it work ? kind of , did i fulfill my goal ? Yes i did and Thank you so much
Click to expand...
Click to collapse
Ok, so you used hwota and the fullOTA for nougat. This made bootloder lock.?
Good to know, I was not aware of that.
But good results in the end.

mrmazak said:
Ok, so you used hwota and the fullOTA for nougat. This made bootloder lock.?
Good to know, I was not aware of that.
But good results in the end.
Click to expand...
Click to collapse
i actually used the full OTA of Oreo ... that's why i said nothing happened ... it did not update even tho it brought new features like AI Lens ...
i noticed another thing ... the write recovery bat file detected that my rom was on OREO ... which wan't the case it was still androind 7.1 EMUI 5

Well i've been running Oreo since 3 days Now
Great new features to the camera and some minor battery life improvements

mimminou said:
i actually used the full OTA of Oreo ... that's why i said nothing happened ... it did not update even tho it brought new features like AI Lens ...
i noticed another thing ... the write recovery bat file detected that my rom was on OREO ... which wan't the case it was still androind 7.1 EMUI 5
Click to expand...
Click to collapse
mimminou said:
Well i've been running Oreo since 3 days Now
Great new features to the camera and some minor battery life improvements
Click to expand...
Click to collapse
Hi, how you got android Nougat 7.1?
I bought the same phone model BND L21 C432 with Nougat 7.0 and updated to 8.0.0.330 with FF app, but after that FF never works to update to new updates like 8.0.0.331 which is the latest for our device. How can I update to latest firmware or to Nougat 7.1 manually or with HWota without unlock bootloader ? (my bootloader is locked).
Any tips will be helpful, I'm new to this tipe of phone which is flashing different from my old Galaxy S5, thank you.

Actually, the latest is 8.0.0.332 from 2 days ago.

Bosket said:
Hi, how you got android Nougat 7.1?
I bought the same phone model BND L21 C432 with Nougat 7.0 and updated to 8.0.0.330 with FF app, but after that FF never works to update to new updates like 8.0.0.331 which is the latest for our device. How can I update to latest firmware or to Nougat 7.1 manually or with HWota without unlock bootloader ? (my bootloader is locked).
Any tips will be helpful, I'm new to this tipe of phone which is flashing different from my old Galaxy S5, thank you.
Click to expand...
Click to collapse
I don't think you can do much with a locked bootloader i'm sorry
i'm also not used to this new method of flashing as i used primarely samsungs before too
There is However a service to unlock your bootloader for 4€ even after Huawei shut down the unlock website ... if you can pay that's great but if you can't or you are not willing to you can always wait as somd people will figur out the way the unlock code is generated / stored

mimminou said:
Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
Click to expand...
Click to collapse
Hi, is your phone single or dual SIM?

mimminou said:
Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
Click to expand...
Click to collapse
It supposed to be officiall update, so why twrp? My phone is full stock, have the fw downloaded and still failed at 5%!

aspot72 said:
It supposed to be officiall update, so why twrp? My phone is full stock, have the fw downloaded and still failed at 5%!
Click to expand...
Click to collapse
I couldn't follow what you said but to make myself clear ... i used HwOta methode and updated to Oreo .... Hwota failed but when i booted the rom i got Ota update from settings ... how ? i still don't know maybe Hwota updated the cust partition (almost certain) so my device was eligible for update ....
Now i'm rocking LOs Beta 5 and it's working fine so far except for the secondary camera Focus thing ...

mimminou said:
I couldn't follow what you said but to make myself clear ... i used HwOta methode and updated to Oreo .... Hwota failed but when i booted the rom i got Ota update from settings ... how ? i still don't know maybe Hwota updated the cust partition (almost certain) so my device was eligible for update ....
Now i'm rocking LOs Beta 5 and it's working fine so far except for the secondary camera Focus thing ...
Click to expand...
Click to collapse
Well, to make it as clear as possible, if the update is officiall why we need twrp for update? When checking the desired ROM it's approved for installation, however when trying to update at 5% it says failed. My broadband is down, so can use my phone only, and the HwOTA is for pc

aspot72 said:
Well, to make it as clear as possible, if the update is officiall why we need twrp for update? When checking the desired ROM it's approved for installation, however when trying to update at 5% it says failed. My broadband is down, so can use my phone only, and the HwOTA is for pc
Click to expand...
Click to collapse
Oh Ok
I think you need TWRP to flash the stock recovery that has "cached code"
Basically the recovery you flash will have a specific commande to flash the stock rom from a specific directory in sd card ... this is why you DON'T change the name of any Folder / File during the HwOta flashing unless you know how to mess with Updater script file
Appart from that i still don't know any method on how to do this without PC even if Ota is approved .... i suggest you to tether your Internet to your pc ... as far as i remember Emui had that feature

mimminou said:
Oh Ok
I think you need TWRP to flash the stock recovery that has "cached code"
Basically the recovery you flash will have a specific commande to flash the stock rom from a specific directory in sd card ... this is why you DON'T change the name of any Folder / File during the HwOta flashing unless you know how to mess with Updater script file
Appart from that i still don't know any method on how to do this without PC even if Ota is approved .... i suggest you to tether your Internet to your pc ... as far as i remember Emui had that feature
Click to expand...
Click to collapse
Will give it a try, thanks.

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.