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.

UPDATE.......full OTA .... does not work with TWRP

Hello,
my Pixel XL came from T-Mobile Germany.
I am in TWRP alpha2 and SR4-SuperSU-v2.78-SR4.
My Pixel XL is on NDE63H.
I logged the OTA download process used the link in there and got now the 68MB small OTA.zip.
Can I use TWRP and this small update OTA to update to NDE63U,
or do I need to use the large 850MB OTA file from the google develope site to do so -> marlin-ota-nde63u-56d5b07a.zip?
I think I will loose root by using the large one, but will I loose TWRP as well?
My preference would be to use the small one, but will it work via TWRP and will I loose root as well or will this only update the necessary files?
Any help is highly appreciated.
mancman

I haven't tried it on the pixel, but on my previous Nexus device (N6), the small OTA would fail if the devices was rooted or had any changes to the system partition - that's because the small OTA was an incremental update, and was checking to see if the system partition was modified in any way before applying the OTA.
The full OTA would work - but you would lose the root/TWRP. Reinstalling TWRP is just a fastboot command away, so why is that a big deal?

Hello jj14,
I tried it.
First within TWRP and then by sideload and both failed with the same error.
I first needed to get a newer version of adb, but it failed as said above as well via sideload.
See error message here in the attached picture.
Any hint?

As far as that error, it means the binary update files are missing. That could be because the structure of OTA's changed. Without seeing the OTA I cannot say for sure. I would post that screenshot in the twrp thread and ask @Dees_Troy what he thinks.

Hello Scott,
thanks for your answer.
I wrote Dess a message.
Attached 2 screenshots which show what is in the zip from the OTA file and one for the comparison to a Nexus 10 zip,
you see that the update-binary is missing, so Goggle has changed things here as you postulated.
Thanks,
mancman

I assume you are trying to sideload the full OTA file. If so, what error did you get using the ADB sideload? (yes, you will need the newest version of ADB - download from the Google developers site). TWRP is still very new, so there may still be some bugs to address - Dees is pretty good about quick updates/fixes though.

I may be wrong here but shouldn't you flash back stock recovery before applying stock ota ??

B367 Update available for US variant (BLN-L24)

The security patch is updated to Jan. 1, 2018. "Integrates Google security patches for improved system security"

I still do not get it

jamesxantt said:
I still do not get it
Click to expand...
Click to collapse
Try the system update from the HiSuite. I didn't get it from the phone system update but the update became available in the HiSuite software (PC).

galapagos said:
Try the system update from the HiSuite. I didn't get it from the phone system update but the update became available in the HiSuite software (PC).
Click to expand...
Click to collapse
Thanks ?

I'm gonna take a big guess and say I'll lose root if I do this.
Edit: Can't update. Have TWRP. Don't have stock boot file for my US Honor 6X. No available links in the sticky forum either.

AidenSurvival said:
I'm gonna take a big guess and say I'll lose root if I do this.
Edit: Can't update. Have TWRP. Don't have stock boot file for my US Honor 6X. No available links in the sticky forum either.
Click to expand...
Click to collapse
These are the files needed for the update (B366 version):
https://mega.nz/#F!7clljDYQ!DjUTltO2GOHfBlHDndmCvQ
After the update, just flash TWRP and root again. None of your settings or apps/data will be affected (unless you've something that changes system files such as xposed framework - this can be resolved by reinstalling exposed zip)

galapagos said:
These are the files needed for the update (B366 version):
https://mega.nz/#F!7clljDYQ!DjUTltO2GOHfBlHDndmCvQ
After the update, just flash TWRP and root again. None of your settings or apps/data will be affected (unless you've something that changes system files such as xposed framework - this can be resolved by reinstalling exposed zip)
Click to expand...
Click to collapse
the update don't lock the bootloader?

Alex19Gam said:
the update don't lock the bootloader?
Click to expand...
Click to collapse
Nope, I never had to. If the update re-locks the bootloader, your data partition will be wiped. As said above, the update does not affect your data (as also noted by Huawei's update info which says "This update will not erase your personal data, but we recommend that you back up any important data before updating.").

Got it! But I saw B368 on Firmware Finder.
Sent from my HUAWEI BLN-L24 using XDA Labs

I got B367 on Saturday via notification. I'm the only one of three in the family thus far to get it, so it's definitely a slow roll out. I was super excited when I realized it also magically fixed my lagging camera-startup issue. :good:
That is, until today, when I realized I still had a massively lagging camera. Sigh...
Please tell me we'll soon get Oreo AND a camera fix.

Flash stock software update through TWRP?

First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.

ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.

sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.

ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.

This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs

Question Steps to root

I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!

I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303

It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)

leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.

ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)

leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?

ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.

ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!

Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?

i need fastboot driver for win 64

Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route

can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?