Like many people here, I was eager to get onto Android 7 but the issue I faced was the fact that I got a branded phone and a long wait till I officially get the Android 7 update. Looking through this forum I was very put off on manually updating it to Android 7 with so many threads about bricked phones. However, the urge to get onto Android 7 was too great so ultimately, I decided to do my research and just do it. I am not new to flashing and custom roms but I am new to Huawei but I had confidence that I will recover if I do brick my new P9. In the end (after a few bricks and a couple of mild heart attacks), I got there and to get there, I needed to grab information from multiple threads. So I have decided to put together this guide so people have a singular guide to debrand and get onto Android 7. Below are steps and threads I took to debrand my C34 to C432 and update it to B361.
What listed below is what I did to get onto Android 7, this may or may not work for you so use this guide at your own risk.
Using this Guide - Please read through this guide BEFORE attempting it. There is a lot of large files to download so I recommend that you download everything you need before you make a start and a fast and reliable internet is strongly recommended.
Prep Work
- Backup all your data because your phone will get wiped.
- Make sure you have the stock recovery already flashed and make sure your phone is not rooted (may not be necessary but this was the state my phone was in).
- Get yourself a bootloader code from Huawei. Go to http://www.emui.com/en/plugin/hwdownload/download, you will need to create a Huawei ID if you haven't already done so. Click on the Unlock Bootloader link and fill out the form, you should get a bootloader code almost instantly after submitting the form.
- Download and install HiSuite (http://consumer.huawei.com/minisite/HiSuite_en/index.html).
- Download the SRK Tool from here: https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2
Now lets make a start.
1. Download and flash the dload-huawei-p9-eval09-eva-b136.zip from this thread: https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818. Instructions on how to flash this is in the first post. After flashing, you should be on the L09C900B136 firmware. NOTE: If it boots up to a white screen asking you to enter password, reboot into recovery by holding volume up when you powering up your phone, do a wipe partition and factory reset. You may need to reboot your phone a number times before the phone boots up correctly.
2. After flashing and booting into the L09C900B136 firmware, you will need to unlock your bootloader and install TWRP. You can use the SRK Tool to do this, please have a look at this thread (https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2) and watch the video on how to do this. NOTE: You only need to unlock bootloader and install the TWRP recovery.
3. After your phone has been unlocked with TWRP recovery installed, download oeminfo-huawei-p9-eval09-c432.zip from this thread: https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903 and flash it via TWRP. To get into TWRP, power off your phone and go into recovery by powering up your phone while holding volume up.
4. Once you flashed the oeminfo file via TWRP, power off your phone and repeat step 1. So you need to flash the dload-huawei-p9-eval09-eva-b136.zip file again via the dload method (power on the phone while holding volume up and volume down). NOTE: When you flash this firmware again, it will lock your bootloader (Fastboot will tell you that the phone is unlocked but I assure you, your bootloader is locked) and restore to stock recovery.
5. Once your phone has booted back up, go into the phone settings and you should see that your phone is now on the EVA-L09C432B136 firmware. To test that the firmware is working as intended, go into the phone settings and go into Updater, updater should pick up the B182 firmware and you should be able to update it to B182 without an issue.
UPDATE: A number of people has reported that they are getting the B166 update instead of B182, if this happes, do a wipe partition and a factory reset after updating to B166. When you get back in, you should be able to update to B182 via Updater in the Settings menu. If this method does not work, you can manually update to B182 by following the steps here: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
6. After your phone has rebooted and you are on the B182 firmware, you need to now update the firmware to B361 via Huawei Updater 2.0 using this guide: https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2.
After all that is done, you should now have a debranded UK C432 P9 running EMUI 5.0.
Special thanks to @paulobrien, @somboons and @KrAzYtHeBoY for their guide, tools, files and video to make this update possible.
Props to you sir. I will try this when I get back. I don't have any doubts now after reading this guide.
Does debranding will affect warranty of the device? Mine is quite new.
zoold3vil said:
Does debranding will affect warranty of the device? Mine is quite new.
Click to expand...
Click to collapse
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Z-Blade said:
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Click to expand...
Click to collapse
Thanks for the feedback!
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
halliday77 said:
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
Click to expand...
Click to collapse
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Z-Blade said:
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Click to expand...
Click to collapse
Legend. Appreciate the reply - it was tough to find experienced Aussies on the same starting build/carrier.
Now I just wish I hadn't wasted the time going for the Asia Pacific variant!
Will get stuck into it this evening.
Thanks!
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Nawor81 said:
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Click to expand...
Click to collapse
How did you get onto that build? Have you tried following the guide I put up?
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Z-Blade said:
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Click to expand...
Click to collapse
That's not the news I wanted to hear! I guess I'll keep this guide in mind and do some more research, hopefully find someone in love with Huawei that might be able to assist. Thanks
SmartPhonesFan said:
Hi z-blade I flashed B136 but it didn't put icons and themes back .. I flashed B182 and STILL didn't put icons and themes back
BUT only B166 gave me proper theme and icons back.. ! After that I flashed I had to flash B182 and so on.. B166 is the key important
Click to expand...
Click to collapse
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
---------- Post added at 02:42 AM ---------- Previous post was at 02:34 AM ----------
Z-Blade said:
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Click to expand...
Click to collapse
Broken themes/icons seem to be caused by missing assets in the /CUST/ partition. I managed to get around it on my broken C900 firmware by separately flashing the /hw/normal/ package specific to the build. These can be found in the filelist.xml in the [WAREHOUSE] post - but you need to change the URL manually to grab the file.
SmartPhonesFan said:
So B361 will? Didn't know that.. Didn't want to risk it it took ages to download.. I had 3 folders in B136 but I flashed it via dial pad options.. Not 3btn..maybe if I would flash via 3btn it will give it back then and I wouldn't need B166..
Cannot be bothered.. It's done now..
Nougat best..
Click to expand...
Click to collapse
It makes no difference if you use the 3 button method or via the dial menu, both does exactly the same thing. I am only assuming that Themes could be installed when I flashed B361, I was not paying attention to the apps that was installed but I think this may be the case because I believe the Theme app was updated for EMUI 5.0, again all assumptions here.
Can I jump directly from b136 to b361?
Thanks in advance.
halliday77 said:
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
Click to expand...
Click to collapse
It's from Vodafone unfortunately
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
trouble2000 said:
Can I jump directly from b136 to b361?
Thanks in advance.
Click to expand...
Click to collapse
No you cant, you need to get to B182 before flashing B361.
d_mouse81 said:
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
Click to expand...
Click to collapse
Try wiping partition and a factory rest and see if you get the B182 update. If not, you can download the B182 update and flash it via dload but if that does not work, you can try doing it via the Hisuite and Updater method.
Related
I flashed TWRP and unlocked bootloader, I am on mha-l29c636b158. How can I return to completely stock? I want to receive updates via ota because I read that there is a new update to fix the touch screen not being responsive. Or is there a flashable stock zip update I can flash?
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page31
Jaimesco12 said:
I flashed TWRP and unlocked bootloader, I am on mha-l29c636b158. How can I return to completely stock? I want to receive updates via ota because I read that there is a new update to fix the touch screen not being responsive. Or is there a flashable stock zip update I can flash?
Click to expand...
Click to collapse
I spent that past two days rooting and flashing the one rom I could. Had to ignore some Chinese. I am USA 567B167. Got into trouble a number of times. This phone is funky compared to all the rooting I have done. I booted into erocovery, downloaded stock 2GB, wiped and was back to current stock without issue. It bootlooped if I didn't hard reset and wipe cache.
gm007 said:
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page31
Click to expand...
Click to collapse
Will I be able to receive otas?
rndchef said:
I spent that past two days rooting and flashing the one rom I could. Had to ignore some Chinese. I am USA 567B167. Got into trouble a number of times. This phone is funky compared to all the rooting I have done. I booted into erocovery, downloaded stock 2GB, wiped and was back to current stock without issue. It bootlooped if I didn't hard reset and wipe cache.
Click to expand...
Click to collapse
So you just booted to erecovery and from there it automatically downloaded the stock firmware?
You can return stock by use dload update.
Jaimesco12 said:
So you just booted to erecovery and from there it automatically downloaded the stock firmware?
Click to expand...
Click to collapse
yes. I did it twice. that is how many times I got into trouble and was the only solution. It worked great as it gives you the ability to log into wifi with a keyboard present to put in the password, then downloads the stock current rom and flashes it. You have to format data and wipe cache yourself.
Miss Wugfresh root tool. Get you out of any trouble.
It says getting package info failed in erecovery
rndchef said:
yes. I did it twice. that is how many times I got into trouble and was the only solution. It worked great as it gives you the ability to log into wifi with a keyboard present to put in the password, then downloads the stock current rom and flashes it. You have to format data and wipe cache yourself.
Miss Wugfresh root tool. Get you out of any trouble.
Click to expand...
Click to collapse
any ideas?
Jaimesco12 said:
any ideas?
Click to expand...
Click to collapse
Erecovery only work for Chinese firmware.
Use the guide above and yes you can receive ota.
I also received the same message. Getting into recovery was inconsistent for me even with TWRP. Sometimes it would do the auto downloaded and fail thing and other times it would go into TWRP. You need to get where you have three choices and pick erocovery and push the start button. This brings up the restore ability. Worked perfect on the USA model.
rndchef said:
I also received the same message. Getting into recovery was inconsistent for me even with TWRP. Sometimes it would do the auto downloaded and fail thing and other times it would go into TWRP. You need to get where you have three choices and pick erocovery and push the start button. This brings up the restore ability. Worked perfect on the USA model.
Click to expand...
Click to collapse
Do you say that you recovered your phone from erecovery? For usa model?
gm007 said:
Do you say that you recovered your phone from erecovery? For usa model?
Click to expand...
Click to collapse
Yes. Twice. Once to get off of HRT rom that was wonky and another to remove root because I lost Google apps. All accidents and was grateful to discover erecovery put me back on the current B167 version stock.
rndchef said:
Yes. Twice. Once to get off of HRT rom that was wonky and another to remove root because I lost Google apps. All accidents and was grateful to discover erecovery put me back on the current B167 version stock.
Click to expand...
Click to collapse
Are you sure ur not using a paid service?
That's a good news, that was only possible for Chinese firmware,hope they extend it to all regions.
gm007 said:
Are you sure ur not using a paid service?
That's a good news, that was only possible for Chinese firmware,hope they extend it to all regions.
Click to expand...
Click to collapse
Completely positive. It happened by accident because I got in a bad place with HRT rom. Came out completely stock and current when no upgrade need. Then I rooted stock and somehow lost gapps including keyboard. Did it again and back to stock. All in erecovery. No other programs or files. It did a 2.5GB download, flashed in Emui and rebooted like when I bought it.
rndchef said:
Completely positive. It happened by accident because I got in a bad place with HRT rom. Came out completely stock and current when no upgrade need. Then I rooted stock and somehow lost gapps including keyboard. Did it again and back to stock. All in erecovery. No other programs or files. It did a 2.5GB download, flashed in Emui and rebooted like when I bought it.
Click to expand...
Click to collapse
Sorry for the no noob question: I just got my mate 9 and unlocked bootloader and rooted it. Recovery is TWRP 3.0.2-2.
Where do i find this erecovery? Couldn't see any download option in TWRP and even Google didn't know that term. Could anybody please explain step by step how to revert to stock (for the only sake of getting OTAs) once the phone has unlocked bootloader and is rooted using the method from xda with modified boot.img?
Or is it even possible to take OTAs while being rooted with system read only? On my previous phone, the Asus Zenfone 2 this was possible.
Thanks a lot
itenos said:
Sorry for the no noob question: I just got my mate 9 and unlocked bootloader and rooted it. Recovery is TWRP 3.0.2-2.
Where do i find this erecovery? Couldn't see any download option in TWRP and even Google didn't know that term. Could anybody please explain step by step how to revert to stock (for the only sake of getting OTAs) once the phone has unlocked bootloader and is rooted using the method from xda with modified boot.img?
Or is it even possible to take OTAs while being rooted with system read only? On my previous phone, the Asus Zenfone 2 this was possible.
Thanks a lot
Click to expand...
Click to collapse
Connect ur phone to usb,and boot ur phone while holding volume up.
Please report back if erecovery recovered ur phone.
gm007 said:
Connect ur phone to usb,and boot ur phone while holding volume up.
Please report back if erecovery recovered ur phone.
Click to expand...
Click to collapse
Thanks for the quick answer. Let me clearify what I understood : this erecovery is available only on the PC?
So basically I wait in rooted state until I receive the next OTA, don't take it but switch off the phone.
Then connect it to the PC and boot it up by holding the volume up + power key.
Then what happens exactly?
Sent from my MHA-L29 using Tapatalk
itenos said:
Thanks for the quick answer. Let me clearify what I understood : this erecovery is available only on the PC?
So basically I wait in rooted state until I receive the next OTA, don't take it but switch off the phone.
Then connect it to the PC and boot it up by holding the volume up + power key.
Then what happens exactly?
Click to expand...
Click to collapse
Booting the phone while plugged and with volume up will take you to erecovery on ur phone.
There you connect to wifi and the firmware get downloaded into ur phone
gm007 said:
Booting the phone while plugged and with volume up will take you to erecovery on ur phone.
There you connect to wifi and the firmware get downloaded into ur phone
Click to expand...
Click to collapse
Ah ok, this erecovery is still available on my phone even if I already flashed a custom recovery, right?
Then after downloading the firmware, erecovery will flash it and overwrite root and lock my bootloader again, correct?
Sent from my MHA-L29 using Tapatalk
what is the official update for my phone it is BLL-L22 and it is now on b160 (marshmallow)
i have installed the b360 but it has few issues such as 1) no update app 2) build no is tester not official no and so on
yoko89 said:
what is the official update for my phone it is BLL-L22 and it is now on b160 (marshmallow)
i have installed the b360 but it has few issues such as 1) no update app 2) build no is tester not official no and so on
Click to expand...
Click to collapse
It may be because you flashed it manually. And unless we have rollback package for your model you may not be able to rollback to MM. Are you planning to install custom ROM or want to be on stock rom only.
Updater is not there means tou wont get OTA bit test build wont impact anything.
You may need to flash the oeminfo of your model as well.
shashank1320 said:
It may be because you flashed it manually. And unless we have rollback package for your model you may not be able to rollback to MM. Are you planning to install custom ROM or want to be on stock rom only.
Updater is not there means tou wont get OTA bit test build wont impact anything.
You may beed to flash the oeminfo of your model as well.
Click to expand...
Click to collapse
I forgot to update oeminfo now i am updating to 370 as it is the latest and will update oeminfo
yoko89 said:
I forgot to update oeminfo now i am updating to 370 as it is the latest and will update oeminfo
Click to expand...
Click to collapse
Good luck. If need help just post it with details. We will try as much as we can
shashank1320 said:
Good luck. If need help just post it with details. We will try as much as we can
Click to expand...
Click to collapse
Updated successfully using firmware finder
yoko89 said:
Updated successfully using firmware finder
Click to expand...
Click to collapse
I knew from the first post that it was Firmware Finder's fault!! Now your build number is correct?
RedSkull23 said:
I knew from the first post that it was Firmware Finder's fault!! Now your build number is correct?
Click to expand...
Click to collapse
Yes
yoko89 said:
Yes
Click to expand...
Click to collapse
Ok perfect
yoko89 said:
Yes
Click to expand...
Click to collapse
Hide IMEI.
Also, updater in setting visible? How about FM, manager, theme etc?
shashank1320 said:
Hide IMEI.
Also, updater in setting visible? How about FM, manager, theme etc?
Click to expand...
Click to collapse
Yes every thing is working more tha fine
yoko89 said:
Yes every thing is working more tha fine
Click to expand...
Click to collapse
That is cool. Few reported one or the other things missing
Bll-l22c636 b160 to nougat
shashank1320 said:
That is cool. Few reported one or the other things missing
Click to expand...
Click to collapse
Hi.
Bought gr 5 '17 yesterday. Running MM.
I want to update to Nougat, cant find my build number in firmware finder list.
Fb group admin (also member here...) suggested to download a B 370 package.
I want to ask will it work for B160?
Also, any link to step by step instructions for update? Sorry, non tech person here...
Note: if i click to dl a package from Firmware finder, it shows dl as a zip file. Once download is complete, then what?
Thanks in Advance.
GR5_17 said:
Hi.
Bought gr 5 '17 yesterday. Running MM.
I want to update to Nougat, cant find my build number in firmware finder list.
Fb group admin (also member here...) suggested to download a B 370 package.
I want to ask will it work for B160?
Also, any link to step by step instructions for update? Sorry, non tech person here...
Note: if i click to dl a package from Firmware finder, it shows dl as a zip file. Once download is complete, then what?
Thanks in Advance.
Click to expand...
Click to collapse
Give me your exact current build number
shashank1320 said:
Give me your exact current build number
Click to expand...
Click to collapse
Thank you for your reply.
Build number : BLL-L22C636B160
GR5_17 said:
Thank you for your reply.
Build number : BLL-L22C636B160
Click to expand...
Click to collapse
I would advise to wait for official OTA (as you got the phone yesterday) but if you really want to do it-
Download this- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
and this http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Flash first file and boot to system. Then 2nd and boot.
You need to use dload method as below
Unzip 1st file and extract the package. You will get few files including update.app.
Few suggest to use only update.app file but I would advise, based on my personal experience for all dload method I tried, use all the files.
Create a folder dload under SD card and copy all the files to this folder.
Power off the phone. Remove USB cable, if connected.
Press volume up+volume down keys and simultaneously press power button (3 keys together)
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Repeat the same with 2nd zip file.
Good luck. Happy Flashing.
shashank1320 said:
I would advise to wait for official OTA (as you got the phone yesterday) but if you really want to do it-
Download this- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
and this http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Flash first file and boot to system. Then 2nd and boot.
You need to use dload method as below
Unzip 1st file and extract the package. You will get few files including update.app.
Few suggest to use only update.app file but I would advise, based on my personal experience for all dload method I tried, use all the files.
Create a folder dload under SD card and copy all the files to this folder.
Power off the phone. Remove USB cable, if connected.
Press volume up+volume down keys and simultaneously press power button (3 keys together)
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Repeat the same with 2nd zip file.
Good luck. Happy Flashing.
Click to expand...
Click to collapse
Thank you very much for the detailed instructions and links.
I think I will take your advice and wait for OTA update.
As mentioned, I am not too 'tech' and am worried might do the wrong thing.
Is it normal for my build # not to have nougat update yet?....
I will bookmark this post and report back in a week. Hopefully I will have an update by then.
Thank you again shashank1320
GR5_17 said:
Thank you very much for the detailed instructions and links.
I think I will take your advice and wait for OTA update.
As mentioned, I am not too 'tech' and am worried might do the wrong thing.
Is it normal for my build # not to have nougat update yet?....
I will bookmark this post and report back in a week. Hopefully I will have an update by then.
Thank you again shashank1320
Click to expand...
Click to collapse
You welcome. Welcome to XDA and tech stuff.
Yes it is normal. Update may pop up anytime. Have you inserted the SIM yet? If not, putting the SIM may help. Also it may take upto a week for your phone to register and get update.
Regards,
Shashank
shashank1320 said:
You welcome. Welcome to XDA and tech stuff.
Yes it is normal. Update may pop up anytime. Have you inserted the SIM yet? If not, putting the SIM may help. Also it may take upto a week for your phone to register and get update.
Regards,
Shashank
Click to expand...
Click to collapse
Thank you for your Welcome Shashank I hope to learn alot from the XDA Forum and you, since this is my 1st Android phone o).
I had not inserted the SIM before, since I'm still learning how the phone works and was playing around with the GR 5 17 without the SIM.
I have inserted the SIM and just like you said; I got an update from the Settings menu.
I am downloading update : BLL-L22C636B360 as we speak.
I am worried since I read on this thread that it might have some problems....
I will post an update once completed.
I am excited to learn more about Android from the XDA Forum, and how I can keep my GR 5 17 in the best condition.
Thank you again for your support Shashank. Stay Well
GR5_17 said:
Thank you for your Welcome Shashank I hope to learn alot from the XDA Forum and you, since this is my 1st Android phone o).
I had not inserted the SIM before, since I'm still learning how the phone works and was playing around with the GR 5 17 without the SIM.
I have inserted the SIM and just like you said; I got an update from the Settings menu.
I am downloading update : BLL-L22C636B360 as we speak.
I am worried since I read on this thread that it might have some problems....
I will post an update once completed.
I am excited to learn more about Android from the XDA Forum, and how I can keep my GR 5 17 in the best condition.
Thank you again for your support Shashank. Stay Well
Click to expand...
Click to collapse
Don't worry, download and install it. If there is any issue you may download further updates. There will few more if your model has it. I got a phone couple of days back amd got 3 updates(different model though)
shashank1320 said:
Don't worry, download and install it. If there is any issue you may download further updates. There will few more if your model has it. I got a phone couple of days back amd got 3 updates(different model though)
Click to expand...
Click to collapse
I have downloaded the B360 update. As you mentioned, I have received another update and am now on : Build number ~: BLL-L22C636B384 , EMUI : 5.0.1, Android : 7.0
Things seem to be working fine for now.
I wanted to ask you about any good Dark theme for the GR5-17.
Do you suggest from the Huawei themes (built in) or from :EMUI theme factory? (an app I dl from PlayStore.
Thank you, Stay Well
Hmm, so I'm going to try and bring root to these devices but first I need current stock firmware. So the issue I've run into, and this is the first time I've come across something like this... is that there doesn't seem to be any stock fw downloads available online. There are some extremely sketchy websites that try to get you to pay for low_ship firmwares but I don't like that.
How do we get current stock downloads for our devices if nothing has been released? I need SM-J727R4 J727R4TYU1AQD4 stock firmware for Galaxy J7 US Cellular...
EDIT:
Managed to get this phone rooted and everything was working great. Flashfire may have borked my System partition when I was doing backups, don't know how. But now I'm bricked until I can get firmware. Sent an email to Samsung, we'll see what they say.
Do you if the phone it comes unlocked ? Im interested in getting one
Sorry, Im on US Cellular but Im not sure that it is. I dont even know how to find out.
By the way, the firmware thankfully has been released. You can find it at SAMMOBILE and samsung-firmware.
Hi. Please, if root will be done - will it also work on European languages? Well thank you.
What is your exact model number, is it SM-J727R4?
LeviathaninWaves said:
What is your exact model number, is it SM-J727R4?
Click to expand...
Click to collapse
J727R4 US Cellular Check ESN A
tono4224 said:
Hi. Please, if root will be done - will it also work on European languages? Well thank you.
Click to expand...
Click to collapse
tono4224 said:
J727R4 US Cellular Check ESN A
Click to expand...
Click to collapse
Root should work great for you.
Stock stock ROM J727R4TYU1AQD4_J727R4USC1AQD4_USC Precisely J727R4TYU1AQJ3_USC1AQJ3_USC_U.S_Cellular_7.0. Please, can anyone use TWRP and superSU to root? Well thank you.
tono4224 said:
Stock stock ROM J727R4TYU1AQD4_J727R4USC1AQD4_USC Precisely J727R4TYU1AQJ3_USC1AQJ3_USC_U.S_Cellular_7.0. Please, can anyone use TWRP and superSU to root? Well thank you.
Click to expand...
Click to collapse
There isn't an official TWRP release for this phone, but the SMJ727P is an exact match to the SMJ727R4 in hardware. Use the TWRP for that device, wipe your data partition to remove encryption, then without rebooting flash the Magisk 14 zip for root. SuperSU works but has some problems. You will lose all your data but this is what I did and it works well.
Now that goes without saying, if things go wrong I'm not responsible.
Please help. Everything is like me, but after the SuperSU v.2.79-SR3 is introduced and the following restart is still running: Verification failed. Well thank you.
Prize. J727R4 works on the Slovak and on the network. I want to share my experience.
1. Start uninstall without restart, all 5 items (Odin3_v3.12.10) Build number: NRD90M. J727R4TYU1AQJ3. After the restart process, we select a flashlight.
2. Release the rest without restart, insert twrp_3.0.3-1_sm-j727p_17517. After we start without restart, we select the flashlight.
3.Downloads without reboot. insert J727P-SR3-SuperSU-v2.79-SR3_rooted_boot_AQB9. after we pick the flashlight.
4. Trojhmat home, power, + set wipe-Gawlik.chase.data and select restart system in the menu. After the ratcheting and learning is the phone root and unlock.
Maybe I have to close this topic.
Hello all,
Does anyone have a vendor.img file for US variant BLN-L24? I am attempting to get back to stock, and I have the boot, recovery, and system files, but my update.app seems to not have vendor.img for some reason. Any help on this is much appreciated.
Hi, a reason because your update.app wouldn't have the vendor.img could be that you're trying to extract the vendor from the wrong update package; which one you used? The vendor is present only in the biggest update.zip file around 1,64GB; are you sure you didn't tried to extract it from one of the other two packages (update data full public/update data hw region code)? The vendor is present only in the package labeled with FULL, and not in normals OTA that you receive through system update. Write me up here your build number for extended, and I'll provide you a download link for a package that will surely contain the vendor.img for BLN-L24
Thanks for the reply. I actually downloaded a new update.app last night that contained the necessary vendor.img.
I now have the issue that when I attempt to go back to stock via dload, my install will get to 5%, fail with a red exclamation point in the middle of the screen, and then only give an option to reboot.
From reading the rolling back to stock thread, it appears my version of update.app just may not be working correctly for dload. I have no clue what build number I was on previously, but it should be the latest update that was available as of a week ago. If you can direct me to a valid working update.app for this variant (BLN-L24), that should get me back to stock. Thanks again for any help.
You should try dload with the latest build available here for BLN-L24Cxxx that has "PV" at the end of the package name http://pro-teammt.ru/firmware-database/ (can't know code region so except if there is only one variant, like C583 for example, be careful on which package you download) i suppose that you could be on this USA variant, but i can't ensure it http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v103272/f1/full/update.zip
RedSkull23 said:
You should try dload with the latest build available here for BLN-L24Cxxx that has "PV" at the end of the package name http://pro-teammt.ru/firmware-database/ (can't know code region so except if there is only one variant, like C583 for example, be careful on which package you download) i suppose that you could be on this USA variant, but i can't ensure it http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v103272/f1/full/update.zip
Click to expand...
Click to collapse
Thanks for the link. I will double check when I get home later and try to use dload again.
TurtlePwr82 said:
Thanks for the link. I will double check when I get home later and try to use dload again.
Click to expand...
Click to collapse
You're welcome dude. Let me know if you can solve that out.
RedSkull23 said:
You're welcome dude. Let me know if you can solve that out.
Click to expand...
Click to collapse
So attempting to use the two latest updates available on that site for a basis, I did attempt to use the update.app from each one to attempt install, and get an error message each time when installing package (fail at 5%). At this point, I'm not sure where exactly the fault lies. Just wanted to give you an update.
TurtlePwr82 said:
So attempting to use the two latest updates available on that site for a basis, I did attempt to use the update.app from each one to attempt install, and get an error message each time when installing package (fail at 5%). At this point, I'm not sure where exactly the fault lies. Just wanted to give you an update.
Click to expand...
Click to collapse
I'm sorry that you still are in trouble. I never had luck using dload too, i tried 3 times but I remember that time ago, the thing about using the package with PV at the end was still unknown, so maybe that was the fault. I'll look for users who owns a BLN-L24 to call in cause, in way to ask them to provide a vendor.img for your build and solve this.
RedSkull23 said:
I'm sorry that you still are in trouble. I never had luck using dload too, i tried 3 times but I remember that time ago, the thing about using the package with PV at the end was still unknown, so maybe that was the fault. I'll look for users who owns a BLN-L24 to call in cause, in way to ask them to provide a vendor.img for your build and solve this.
Click to expand...
Click to collapse
Thanks for the help. I've pretty much gone to my backup phone at this point, though I am still trying to fix this one. I thought I had a breakthrough in getting back to stock last night, but upon boot the EliteRom without sound was still flashed. If I could get sound on the EliteRom when I flash it I could live with the phone. I did see that was a reported problem apparently with some of the rooms (loss of sound and video playback).
It's almost as if maybe the custom kernel can no longer be wiped from the phone once it is flashed, and I think that may be where my issue is stemming from, as I have attempted all update.apps from the most recent through to 7/31, all of which fail at 5% through dload, though flashing in fastboot for everything else goes smoothly. I will continue to try to work on it, or just sell the phone. Thanks again for all of your help, it is much appreciated.
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.
BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.