Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Do a Google search for sideloading ota images. It's actually pretty easy. I'm unlocked running a rom so I can't give you a step by step off the top of my head.
nissan skyline said:
Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Click to expand...
Click to collapse
The instructions are on the download page for the OTA and I have pasted them below. You don't need an unlocked bootloader and there is always a chance that something could go wrong when flashing your phone but this method seems pretty safe.
To update a device using one of the OTA images below, you need the latest adb tool. You can get it from the Android SDK Platform-Tools package, which you can download here.
Don't forget to either add adb to your PATH environment variable or change into the directory containing the executable.
Also be certain that you've set up USB access for your device, as described in Run Apps on a Hardware Device.
To apply an OTA update image:
Download the appropriate update image for your device below.
Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
With the device powered on and USB debugging enabled, execute:
adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device instead, and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
For security, you should disable USB debugging when the device is not being updated.
Were you able to sideload the OTA? I tried on the 8th but got an error -- footer error. I'm on 7.1.1 and attempted to load N6F27E.
Adb sideload
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Here is a link to gdrive with ota zips. Not reall great at this. So, hopefully you can download. I have not experienced any of the issues you have. None https://drive.google.com/drive/folders/0B1PLXsZI0UyjTGJEVDFaRy1ITms?usp=sharing
Liftkit said:
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Click to expand...
Click to collapse
https://developers.google.com/android/ota
Edit:I see that this URL already appears in the first post. Hmmm...
Sideloading the OTA is by far the simplest way of upgrading. You keep everything - data, apps, etc. You lose root, but that's easy to reinstall.
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
NCtwin said:
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
Click to expand...
Click to collapse
OTAs are complete packages. You can sideload the latest one directly.
Maybe that's why I keep getting an error when trying to use Wug to update. I'll do the sideload option and see what happens. Thanks a lot.
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
pckarma112 said:
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
Click to expand...
Click to collapse
what is your build #
Liftkit said:
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
what is your build #
Click to expand...
Click to collapse
Take a backup and then sideload N6F27H, Jul 2017. You lose nothing, you boot back into pretty much what you had before, but with security enhancements and a few minor feature improvements.
And before you do any more, read my first sentence again.
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is getting no more updates, ever. This sucks, it all sucks, luckily we can say "F all that" and do whatever we want with this device, provided you follow this guide.
I am making this guide because I want to condensate every single thing I know about this device in one single thread. One big guide to help all of you out installing custom ROMs. Without this, you would have to do research along multiple threads, often with conflicting information, and what's even worse, DEAD LINKS! There's nothing more frustrating than finally finding the solution to your problem, just one download away, just to be greeted by a dead link, and you would need to scout for another file that may or may not work... ugly stuff.
So, the point of this is to bring up to date info so you can make this device rock. This guide assumes you have Huawei's EMUI 4.0 installed which runs on Android 6.0. I'm also assuming you have your bootloader locked, and I will explain how to unlock it FOR FREE. No need to pay to some shady site in order to access what effectively belongs to you.
These are the requirements for this guide:
Code:
#USB cable
#A PC
#Some charge on the device to ensure nothing goes wrong
#An SD Card
#Patience
Before beggining, a quick disclaimer:
Code:
#It's not my objective to break your device, however there's always a risk when doing these kind of things.
#When you follow this guide's steps your are accepting the risks and are taking full responsiblity for whatever may happen to your device.
#Don't blame me for breaking your stuff if that happens, all I'm listing here worked for me, and should work for you.
#I won't be babysitting anybody to help solve their specific problems, don't PM me asking me why X doesn't work.
#I am unaware if this works in other versions of this device, but I'm positive this works on both ALE-L23 and ALE-L21
#If you have a "CAM-XXX" device, it's highly likely this works for you too, but as with everything, TRY AT YOUR OWN RISK.
#YOU HAVE BEEN WARNED!
Ok, so let's begin. As the title says, the guide is applicable to any custom ROM. However, I will be installing Lineage OS 14.1 which runs on (almost stock) Android 7.1.2. Regardless, the final step where we install the custom ROM is interchangable, and you can use whichever you please.
This process WILL wipe all of your data (except SD card). Make sure to make a backup of everything you want to save (app configs, photos, videos and whatever else).
1. DOWNGRADING TO ANDROID 5
As you may know, Huawei has stopped providing bootloader unlock codes for very stupid reasons. This has led to many unable to unlock their bootloader and having to pay for third party apps in hopes they don't get scammed. There are some trustworthy sites where you can get these at a fee tho (mainly DC Unlocker at 4 bucks), so if you want to pay up to avoid having to downgrade to Android 5, you can do so. However, I understand that you may not want to pay at all, I didn't want to either.
To get the bootloader unlock code, we need root, and to get root, we need Android 5. Why? Because getting root in Android 6 requires us to flash some zips, and for that we need TWRP, and for that we need an unlocked bootloader, everyhing closes up very nicely. So, we have no choice but to downgrade.
An SD card is not needed for this process, but it is going to be required at a later point, so why not use it now too?
NOTE: It may be a good idea to make a factory reset at this point, to avoid issues. For that, do the following:
Turn your phone off.
Boot the phone by holding the power button and the volume up button at the same time.
Wait untill the Huawei logo appears, then let go of both buttons.
You should be in recovery mode, navigate with the volume keys to the "Wipe data/factory reset" option.
Select it with the power button and wipe everything.
Reboot the device with the option in the menu.
Once the device has booted up, follow the guide.
Alright, once that's done, connect your phone to the PC to transfer some files:
NOTE: There's two Stock Android 5s downloads ("HW_Android_5_Transition.zip" and "HW_Stock_Android_5.zip"). One is a transition package, as the name implies, and the other is Huawei's EMUI 3.1 in all of it's glory. What's the difference? The transition package is a much smaller file that is designed to downgrade the phone from EMUI 4.0 (Android 6) to EMUI 3.1 (Android 5). If you are running EMUI 4.0 (which should be the case) then you can use the transition package which will take less to download. If you have another version (i.e. EMUI 4.1) you should use "HW_Stock_Android_5.zip". However, the latter is the safe bet. If you are not sure which one to use, use "HW_Stock_Android_5.zip". The process is exactly the same for both packages.
Extract the "UPDATE.APP" file from "HW_Stock_Android_5.zip" or "HW_Android_5_Transition.zip".
Navigate to your phone's internal memory or SD card (whichever you want to use) and locate a folder called "dload". If there's not one, create it.
Put the "UPDATE.APP" file inside of the "dload" folder.
Turn your phone off.
Once it's off, press the power button and the two volume buttons until you see the Huawei logo.
That should make the phone recognize the "update" and start flashing it. Once it finishes, it will try to boot by itself, so pressing those 3 buttons was your last input until the phone boots into Android 5. It will take a long time for it to both finish and boot, don't be afraid, the phone is not bricked. If you think the phone is indeed bricked because it has been stuck at the logo screen for way to long (longer than an hour) then proceed to the "Unbricking" section of this guide. However, it's highly unlikely that this will happen, as Huawei checks the file before flashing it, so if it's incompatible with your device it should not do anything and boot again into Android 6 with everything untouched.
2. ROOTING ON ANDROID 5 AND EXTRACTING BOOTLOADER UNLOCK CODE
Once you are in Android 5, we will need to root the device. Download KingRoot (proved to work) or another one click root app of your choice. I'm aware of KingRoot's bad reputation because of the spyware accusations, but the phone will be wiped anyway and we are sure it works, so it doesn't really harm at all. If you still don't want to use it, check with other apps, I haven't done so myself so I don't know what else works.
Once your phone is rooted, we will need to use the terminal for the first time. We will need to setup ADB and Fastboot, if you already have that, skip this step.
Extract the "platform-tools" folder from the zip and place it somewhere nice.
Shift right click on a blank space INSIDE of the "platform-tools" folder.
Select "Open command window here".
This should be enough to get ADB working, but we need to make some config on the phone itself too.
Go to Settings -> About Phone
Look for a line that says "Build Number" and tap it multiple times.
When the message saying "You are now a developer" pops up, go back and enter the new "Developer Options" menu.
In there, look for an option called "USB Debugging" and turn it on.
Connect the phone to your PC via USB cable.
A message should have popped up on the phone asking for permission to use USB Debugging, tap on "Always allow from this PC" and then on "Allow".
NOTE: If the message doesn't pop up, you can try a number of things. I prefer to tap the "Revoke USB debugging authorizations" button to ensure that no PC is authorized, so the message must pop up at some point. Once you revoked authorizations, disconnect and connect the phone again, if you still don't see it, try to select MTP as the transfer protocol. If not, then PTP, if you still don't see it install Hi Suite on your PC and open it, it should pop up now.
Once you have everything working, type the following in the terminal in your PC:
Code:
adb devices
If you see a serial number there, that's your phone, and that means everything is set up correctly (make sure you don't have any other device attached to your PC, or you could confuse the two and make bad stuff happen for that other device). If you don't see it, make sure USB Debugging is enabled. You can try to use different cables if you still have problems. Now type:
Code:
adb shell
And then:
Code:
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
KingRoot (or the app you used to root) should prompt you (in your phone) if you want to give ADB root access, make sure to allow it to make this work. This should give you your unlock code. SAVE IT INTO A TXT FILE AND COPY THAT FILE TO ALL OF YOUR PCS, ALL OF YOUR CLOUD ACCOUNTS AND ALL OF YOUR MOBILE DEVICES.
(Maybe the terminal gets stuck at this point, press CTRL + D (or C) to get it unstuck).
Seriusly tho, it didn't happen to me, but it is a possibility that your Bootloader can re lock after doing some of the things that follow, in which case you will need to unlock it again, and if you don't have that code... it's back to square one.
3. GOING BACK TO ANDROID 6
Now that we have done all that we wanted on Android 5, it's time to go back. The process is exactly the same.
Extract the "UPDATE.APP" file from the "HW_Stock_Android_6.zip" file and move it to the dload folder (SD card or Internal).
Turn off your phone and turn it on again with all three buttons pressed.
Wait.
???
Profit.
So, we're back on Android 6. Why did we go back you may ask? Why did we not just flash our precius custom ROM? Well, for once, this gives people the chance to stay on EMUI if all they wanted was to unlock the bootloader and maybe root on Android 6 (which I will explain how to do too, in case you want to). Another, more important reason, we need Android 6 to install the B895/B896 update, which is a requirement for any custom ROM (mainly Android 7.0+) if you don't want any problems with your SIM card (and others that may arise).
4. UNLOCKING BOOTLOADER AND FLASHING TWRP
Now, we need to turn on USB Debugging again, and to allow our PC... again. Do so, and check that everything is right with:
Code:
adb devices
If that's the case, then type the following:
Code:
adb reboot bootloader
Your phone will reboot, and you should see a white screen with a wasted android above a green text saying "PHONE LOCKED". If that's the case, take a moment to say goodbye to that green text, because it will soon turn very red. We will need to unlock the bootloader with the code you got from the previous steps, for that type the following:
Code:
fastboot oem unlock ****************
In place of the "****************" you must enter your code, of course. And that was it, now the green text is replaced with a red "PHONE UNLOCKED". This are good news. Now, we need to flash our custom recovery if we want to do anything fancy with the device. For that, extract the "recovery.img" file from the "TWRP_3.1.1.zip" file and paste it into the same folder where all of the ADB files are located (where "adb.exe" is). Now type:
Code:
fastboot flash recovery recovery.img
This will flash TWRP into your device, hooray! Now type:
Code:
fastboot reboot
And your device should turn back on, today is a bright day my son. Now you must take a decision, do you want to flash a custom ROM and get very nice and fancy features or do you want to stay with what you have? If you prefer Huawei's EMUI 4.0, then follow to the next step. If you want to flash custom ROMs, then skip the next one.
5. ROOTING ON ANDROID 6 (OPTIONAL)
I don't know why you would prefer EMUI over... anything else really, but it's your call. I'll tell you how to root it so you can at least take some advantage of it. You see that file called "HW_Android_6_Root.zip"? Extract it, inside there will be... another folder called Root... huh? Redundant. Anyway, inside of that there should be two zips. 1.zip and 2.zip. You will need to place the folder called "Root" inside of your SD card or your internal storage. Then, go back to the terminal and type:
Code:
adb reboot recovery
You should reboot into TWRP, isn't it nice? Anyway, we have to flash some zips! Go to "wipe" first and wipe the "Cache" partition and the "Dalvik" partition. Once that's done, go to install and navigate to the Root folder your placed... well, you know where. Select 1.zip and flash it, once it's finished reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. Once the phone has rebooted (it will take longer because of the cache and dalvik wipe), repeat the process but flash 2.zip this time, reboot and your phone should be rooted. This is the end of the line for you now, as you don't want to make anything else to the phone. However, you can go to the final chapter where I explain how to install Xposed framework, if you want more customization. EMUI doesn't like Xposed very much, so there's little you can do with it, but it's something I guess.
6. INSTALLING THE B895/B896 UPDATE
So, you followed the power user path, the one we all really want deep down. That's cool, I respect you. We gotta use that custom recovery we just flashed, but first we need to transfer some files into our phone's memory. We need to install an update to the phone, for which you need Android 6 (that you should already have anyway). There's two different updates, B895 and B896. As you may guess, B896 is newer. However, any of these two will (or rather should) work without issues. I personally used B896, but some people claim B895 is more stable. I can't find a difference really, but the process is the same regardless of which you choose. Once you have made that decision, move "B895_update.zip" or "B896_update.zip" to your phone's internal storage or SD card AS IS (don't extract it). Then type into the terminal:
Code:
adb reboot recovery
You should be in TWRP now. Go to wipe and select the "Cache" and "Dalvik" partitions ONLY, then wipe them. Once that's done, go to install and flash your update of choice. Once finished, reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. The boot should take longer than usual because of the "Cache" and "Dalvik" wipe... and because of the update too. Once booted, you should be in EMUI 4.1. Go to settings and into "About Phone". In there, look for a field called "IMEI". If you see a number, that means you did everything properly, if you see "unkown" or nothing at all, then that means you lost your IMEI... which means you will have connectivity issues. To fix this, you will need to do a full wipe (so, boot into recovery (we lost TWRP due to the update) and then go to wipe, in there select everything except SD card) and follow the steps again starting from 3, this time flashing the other update (so if you flashed B895, flash B896 this time and vice versa)).
Now, this last step we made has wiped our custom recovery... so sad. We have to flash it again, but we are almost finished!! Now it's time for you to move the custom ROM you want to your SD card (SD card is mandatory, as we will wipe internal storage). You should also move your custom ROM of choice. If you want root, also move the "SuperSUv82.zip" file.
OPTIONAL:
If you want Gapps, that means the Google apps, so PlayStore, Google services and such (and you really should want them, as Android without PlayStore is kinda rough), then you need to download them separately.
So, go to the Gapps website and select the pacakge you want. You NEED to choose the ARM64 platform, the android version depends on the ROM you are flashing, so check which version it runs, and the package itself is personal preference. Here you can see a comparison of each package, detailing what each one contains so you can make a decision. The aroma package is kinda bugged, I would avoid it. Choose wisely, as flashing another Gapps package once you have flashed a different one can and most likely will cause issues. If you want my opinion, I would stick to the nano package. It offers the basic Google functionality and allows you to download other Google apps you may need/use with the PlayStore once you are booted up.
Once you choose your package, move it to your phone's SD card along with the ROM and the SuperSU zip if you want it.
Check that USB Debugging is still enabled, and then type:
Code:
adb reboot bootloader
Once into the bootloader, flash the custom recovery once again with:
Code:
fastboot flash recovery recovery.img
Then:
Code:
fastboot reboot
Once booted up again, type:
Code:
adb reboot recovery
And now it's time to drop the bomb, say bye bye to EMUI, and say hello to... whatever it is you are installing.
7. FLASHING YOUR CUSTOM ROM OF CHOICE
MOST CUSTOM ROMS REQUIRE AN LTE CAPABLE SIM IN ORDER TO HAVE CELLULAR NETWROK WORKING CORRECTLY, THIS DEPENDS ON A ROM TO ROM BASIS, DO YOUR RESEARCH BEFORE FLASHING
Once in TWRP, go to wipe and check every box, I'm serius, check everything except the SD card. Once that's finished, the moment of glory has come. Go to install and flash your ROM. It will take a while, and when that's done reboot. The phone should boot into your ROM. If you want either Gapps or SuperSU, make a quick setup and enable USB Debugging again, then reboot to recovery with:
Code:
adb reboot recovery
Once in TWRP, go to install and flash the Gapps package and the SuperSU zip (in that order) if you want it. Reboot. That should be it! You are done!
8. UNBRICKING
I don't know why, but with all the flashing and the testing I've done you would have thinked that I should have suffered of a brick state at least once... that was, luckily, not the case. I haven't suffered a single brick. I don't know if I'm extremely lucky or if this phone is tremendously resilient, but the case is I haven't had any issues of this kind.
However, I can understand that it is a possibility, so if this happens to you my best advice is to do the following: Boot into recovery mode (either stock or TWRP depending on where in the whole process you got stuck), make a full wipe and apply the update from "HW_Stock_Android_6.zip" with the dload folder and the three buttons method. That should get it unstuck, if not... try the same with the "HW_Stock_Android_5.zip" 's "UPDATE.APP".
9. INSTALLING XPOSED FRAMEWORK (OPTIONAL)
What? A custom ROM is not enough for you? Getting freed from EMUI is not enough? Well fear not then, because there's one last step for the true power user, for that man who thinks that everything is not enough, the good old Xposed Framework *queue fireworks and trumpets.
So, you need to install the Xposed Installer apk. Get it from here, and ONLY THERE. I once installed an apk from another source... ended up being adware, not fun. The apk is at the very bottom of the thread. You will also need the framework itself, get it from here.
Get the latest (arm64) version for your ROM. This depends on what Android version it is running on:
Code:
SDK21 = Android 5.0
SDK22 = Android 5.1
SDK23 = Android 6.0
SDK24 = Android 7.0
SDK25 = Android 7.1
SDK26 = Android 8.0
SDK27 = Android 8.1
You should also get the uninstaller in case things go south.
Once you got the files, install the apk on your phone. Open the app once. Transfer the framework and the uninstaller into your SD or internal storage. Boot into TWRP recovery and install the framework, reboot the device.
NOTE: Android 6.0 takes about 20 mins to boot, wait about an hour before deciding that it's bricked. Android 7.1.2 took me about 2 mins. I'm unaware of the boot times of other versions, but be aware that it can take LONG. If you think it really got bricked, boot into TWRP again and flash the uninstaller. That should get it unstuck and you can either try again or leave it as is.
----------------------------------------------------------------------------
Well guys, that's all I got, quite a big write up huh? I don't really have nothing else to say, just remember that what you are doing here is at your own risk and I don't want anybody blaming me for the bad things that can happen. I will proceed to leave you with the download links so you can try this yourself. I'm currently running Lineage OS 14.1 which features Android Nougat 7.1.2 on my Huawei P8 lite ALE-L23, I've never been happier to be free from the manufacturer's ROM.
DOWNLOADS
(The B895 and B896 update's links are not mine)
Huawei's Stock Android 5:
Android Filehost
Mediafire
Huawei's Android 5 Transition:
Android Filehost
Mediafire
Huawei's Stock Android 6:
Android Filehost
Mediafire
Huawei's Android 6 Root:
Android Filehost
Mediafire
EMUI 4.1 (B895):
Android Filehost
EMUI 4.1 (B896):
Android Filehost
Platform-Tools:
Android Filehost
Mediafire
TWRP 3.1.1:
Android Filehost
Mediafire
Gapps:
Open Gapps
SuperSU:
Android Filehost
Google Drive
Hi,
I didn't understand what do you mean whan you write: Once booted, you should be in EMUI 4.1. If you retained your IMEI, you are in good path, if not... then do a factory reset (wipe everything) and repeat the steps starting from 3.
Could you explain it better?
Thank you
ilmatte said:
Hi,
I didn't understand what do you mean whan you write: Once booted, you should be in EMUI 4.1. If you retained your IMEI, you are in good path, if not... then do a factory reset (wipe everything) and repeat the steps starting from 3.
Could you explain it better?
Thank you
Click to expand...
Click to collapse
Yes, it's basically this: If you go into the "About Phone" section you will see that there's a field detailing your IMEI. I won't lie, I don't know exactly what it is, but it's a unique number for every phone and has something to do with your cellular network connection.
If you messed up at some point, you can lose your IMEI (i.e. you won't see it in that field or it will say "unknown" or something of the sort). If that happens, then it means you did something wrong, and proceeding in this state will make you have problems with your connection. The signal would be really unstable and it would be practically unusable.
To make a simpler check, if you have a cellular network connection, and can make calls and send/receive SMS on EMUI 4.1, then you won't have any problems.
Ah ok it wasn't so clear but I know what an imei is luckily it didn't erase it in my case. Anyway, I don't know how to thank you bro! You saved my life. I beleived to be screwed when I learned that Huawei stopped releasing the bootloader unlock code. How stupid they are. I blamed them through the customer support. I'm running lineage now! Kiss my ass Huawei!
ilmatte said:
Ah ok it wasn't so clear but I know what an imei is luckily it didn't erase it in my case. Anyway, I don't know how to thank you bro! You saved my life. I beleived to be screwed when I learned that Huawei stopped releasing the bootloader unlock code. How stupid they are. I blamed them through the customer support. I'm running lineage now! Kiss my ass Huawei!
Click to expand...
Click to collapse
Glad to hear I helped! Mind dropping a thank on the main thread? Hope you enjoy your phone
Thanks <3 -notes
Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/
Look for a line that says "Compilation Number" and tap...
Click to expand...
Click to collapse
Step 2. second point 2. Change to "Build Number"
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
Click to expand...
Click to collapse
Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
t
Thanks for your work.
BelisTT said:
Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/
Step 2. second point 2. Change to "Build Number"
Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
t
Thanks for your work.
Click to expand...
Click to collapse
Thanks for pointing this stuff out, I'll make those changes you suggested and try to fix some typos too. So, what I gather from what you told me about that Android 5 thing is that in order to correctly flash the update I'm providing you NEED to be in Android 6, right? Whereas with the one you are providing me it should boot into Android 5 regardless of what you currently have. If that's the case, I'll include both and tell people of the distinction between the two so they can use the one they want/need (after all, the transition package is much smaller and easier to download). I'll download the package and upload it to Android Filehost along with everything else. I think I'll keep the mediafire downloads as a mirror. I'll get to that, thanks.
tralph3 said:
.... in Android 6, right? Whereas with the one you are providing me it should boot into Android 5 regardless of what you currently have.
Click to expand...
Click to collapse
Yes, exactly. Thanks for curating this additional download, good idea.
Does this also work for the PRA-LX1 version?
I have Android 8.0 on it and absolutely no idea what EMUI version or eben the firmware version.
I want to put crDroid on this phone because EMUI ... you know, it's bad.
Otherwise: I am ok with paying these 4€ if this payed unlock works.
WHICH of all these DC Unlocker Apps do I need for getting the unlock code?
Badoolo said:
Does this also work for the PRA-LX1 version?
I have Android 8.0 on it and absolutely no idea what EMUI version or eben the firmware version.
I want to put crDroid on this phone because EMUI ... you know, it's bad.
Otherwise: I am ok with paying these 4€ if this payed unlock works.
WHICH of all these DC Unlocker Apps do I need for getting the unlock code?
Click to expand...
Click to collapse
DON'T TRY ANY OF THIS. All of what I've detailed is for the P8 lite 2015, your phone is a different 2017 version that's basically another completely different phone with the same name, because Huawei doesn't know how to namr their devices. You have a different chipset, doing anything of what's described here will most likely brick your phone. With that said, maybe the bootloader unlock method works IF YOU FIND ANOTHER WAY TO ROOT YOUR PHONE. DON'T ROLL BACK TO ANDROID 5 WITH THE FILES I'M PROVIDING PLEASE.
This forum is dedicated to P8 lite 2015, you can see there's a different forum for 2017. Good luck.
Hello, I have ALE-L21 with EMUI 4.0.3 - MM 6.0 - version B633 and i can not downgrade to android 5, phone says : update failed, or stuck on 5%. could someone help me please ?
I tried a lot of stock ROMs, 5.0 , 6.0 etc, nothing worked for me.
Thanks,
Ax1qwer said:
Hello, I have ALE-L21 with EMUI 4.0.3 - MM 6.0 - version B633 and i can not downgrade to android 5, phone says : update failed, or stuck on 5%. could someone help me please ?
I tried a lot of stock ROMs, 5.0 , 6.0 etc, nothing worked for me.
Thanks,
Click to expand...
Click to collapse
Are you using the stock package or the transition package? If you are using the transition package, try stock.
I tried both, with no success. And many others.
I tried to update via internal storage and SDcard too, with no success.
If phone is connected to pc, updating stuck on 5%, if not connected to PC, update fails.
Ax1qwer said:
I tried both, with no success. And many others.
I tried to update via internal storage and SDcard too, with no success.
If phone is connected to pc, updating stuck on 5%, if not connected to PC, update fails.
Click to expand...
Click to collapse
Did you wipe all of your data with the stock recovery? If nothing works then I could suggest you to try to apply the downgrade with sideload. (Boot into recovery and select to apply update from adb, then you type adb sideload <filename>)
I'm clueless on why it doesn't work on your device, it should.
Also, you can try to flash the stock android 6 rom first, that's an older emui version (4.0). If you can flash that, then maybe you can flash android 5 after it.
i have tried intalling both the 5.0 stock roms but it always fails at 5%. i got ALE-L21C02B896 with emui 4.1 and android 6.0. i've been trying different guides but all lead me to dead ends. please help
thanks in advance
Wazu786 said:
i have tried intalling both the 5.0 stock roms but it always fails at 5%. i got ALE-L21C02B896 with emui 4.1 and android 6.0. i've been trying different guides but all lead me to dead ends. please help
thanks in advance
Click to expand...
Click to collapse
I have the exact same firmware(ALE-L21C02B896) that you have and I also cant downgrade to android 5.0 using any of the tutorials that I found in XDA Furum.
razorfancy said:
I have the exact same firmware(ALE-L21C02B896) that you have and I also cant downgrade to android 5.0 using any of the tutorials that I found in XDA Furum.
Click to expand...
Click to collapse
Yeah it very frustrating, please let me know if you find a way and ill do the same.
Wazu786 said:
Yeah it very frustrating, please let me know if you find a way and ill do the same.
Click to expand...
Click to collapse
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
tralph3 said:
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
Click to expand...
Click to collapse
I tried your Huawei's Stock Android 5, Huawei's Android 5 Transition and Huawei's Stock Android 6 and all failed to install giving error at 5 percent.
tralph3 said:
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
Click to expand...
Click to collapse
i tried android 6 also and it also failed at 5%, please is there anything else i can try?
I went to check for system updates today and my pixel initially started to download the latest patch and then after a couple of seconds went straight to telling me that there is no update available. Anyone else have this issue and/or successfully update to the March 2020 OTA via the process below?
Updating Phone Once Rooted:
- Check for device updates, when found:
- Tap uninstall in 'Magisk Manager'
- Tap restore images
- install OTA (do not reboot)
- Back to magisk, tap install > select install to inactive slot
- When magisk installed, press the reboot button in it. It'll force to the other slot AND you'll be updated AND rooted
I assume I should be able to go under 'System' -> 'Advanced' and get the OTA under 'System Update'. I've already disabled 'Automatic system updates' under 'Developer Options'. Just making sure google is somehow not blocking the update on rooted devices and that the above steps are correct. Thank you in advance!
Found similar thing on reddit here.
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, the initial boot may take quite a while. I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take a regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just be patient and let the phone complete the process.
Click to expand...
Click to collapse
sic0048 said:
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Click to expand...
Click to collapse
Thanks for the reply! I'm very used to sideloading/dirty flashing the updates, was hoping to use the Magisk method . Seems like google is getting smarter with their updates. I am guessing the current inability to see the OTA is due to the updates with google pay and google wanting to ensure banks it is safe.
I just finished sideloading March's OTA and patching the boot.img and everything seems to work, just a bit more effort than leveraging Magisk.
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
I experienced same exact thing. Looks like it saw the update at first then after a few seconds reverted to No updates available. About to try uninstalling Magisk, if no bueno, then gonna just sideload.
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Gooch4130 said:
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Click to expand...
Click to collapse
Yes I disabled automatic updates. It didn't do it automatically, I clicked the check for update button. Normally when I do that it says there's a download available and then I know to check online for the flash file. This time it updated without stopping.
FAILED (remote: Failed to write to partition Not Found)
what i am doing wrong ????
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Boot loader is unlocked...
10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)
this version i did ota update
i am from germany.
okay, i found a way to root, but how is it with safety net fix ???
anyone an idea ???
Deleted
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
It installed the OTA for me too, now I'm afraid to restart my phone.
mattcoz said:
It installed the OTA for me too, now I'm afraid to restart my phone.
Click to expand...
Click to collapse
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
I successfully rooted the March update, using the boot.img method.
Spookymyo said:
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
Click to expand...
Click to collapse
I rooted with boot.img method, as well
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
I got it rooted. It ended up taking a factory reset. It must have been some file interfering with the process. Once I reset my phone the rooting process went without incident.
As I'm searching for a more Phone based update wy, I'm thinking about to use maybe the Implemented OTA Process, but download the OTA-File manually... But for that We must know,how the OTA process is working. Did someone know:
- Where the update stores the download fine (I found a OTA and a OTA_Packge directory in the /Data/ folder)
- is there maybe a setting or information which must be injected somewhere (maybe a txt file)
- after that the ota update could then maybe started by hand
Has someone informations on that? If maybe someone where the ota still works and stil has root could check the files and places?
Chris.C said:
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
Worked like charm!! Thanks!! :good:
Click to expand...
Click to collapse
I unlocked the bootloader, sideloaded the August 2020 OTA and flashed the patched boot image. Kept bootlooping, then I restored to the original, booted in, installed Magisk Manager and then flashed the patched image again. Just leaving this here in case it helps someone.
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Why you so eager that you can't wait a few days?
It's available now.
it has been up for about 5 hours
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
Layoffs, poor employee morale, and Google moving away from innovation and a move to deplete resources from projects/divisions that are not returning enough profit.
If you've ever had to deal with Google customer "service" for any technical issues before, you already know why. Sometimes you get lucky and find a unicorn of a tech to help, but it's usually an infuriating mess dealing with them.
But, to be honest, I'd rather have a delayed update than a rushed and buggy update. Quality control is important.
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
After all we are all just humans ... they sure have their reasons
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
No problems here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
Rooted, Kirisakura Kernel, Apr. update. All good here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it???
The mobile phone system is running normally.
Click to expand...
Click to collapse
Assuming you're rooted, that message is normal and can be ignored.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored.
Click to expand...
Click to collapse
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored I am root and magisk on my device..
Click to expand...
Click to collapse
Lughnasadh said:
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
Click to expand...
Click to collapse
I refresh init_boot.img or prompt this message.
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
ozyk100 said:
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
Click to expand...
Click to collapse
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
simplepinoi177 said:
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for that explanation, I'll read up on it from the provided link.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
I had the same issue, but everything works normally without any issues. I regularly flash custom roms and factory images, so if you still want to fix this issue, restore a factory image using the Android flash tool.
Any info on whether the fingerprint scanner is being fixed or at east bettered with this?