Related
Does ADB and fastboot install automatically with the HTC drivers or must it still be downloaded separately and installed? I have the adb file and trying to obtain s-off (using moonshine) but having issues doing so. I tried following a guide online however I believe it was written with windows 7 in mind.
My goal is to root and install the Google Edition 4.3 android then flash a custom kernel. Any guides would be great. My last phone was an HTC evo 4g LTE and it's been a new laptop and new version of windows ago since I went through the process. I'm completely behind playing catch up.
Thanks!
Duck
This is the website I used: http://htc-one.wonderhowto.com/how-...wrp-root-google-play-edition-htc-one-0148146/
A couple things to note (from my experience following this tutorial):
-The first time I fastboot flashed TWRP, it didn't stick. I had to do it again, and then it stuck.
-When I rebooted to system from TWRP and let it root me using the SuperSU installer, that didn't work using Google Play or the TWRP option, probably because I was on 4.3. You have to manually flash the supersu zip file in TWRP from the thread on XDA.
Hope that helps!
EDIT: regarding you driver situation, I'm on Windows 8 and all I had to do was plug it in and it downloaded the necessary drivers automatically. I believe I have HTC Sync Manager installed, but it's not running, and wasn't running when I was going through that tutorial.
EDIT 2: Looks like I read your post wrong,.. I thought you had the GPe. Nonetheless, that tutorial may help you.
I don't think ADB or Fastboot are pre-installed nor are they packaged with sync manager. You have to download them either as part of the SDK or from XDA. Personally, I download the whole package as it's far easier to keep updated.
Sent from my HTC One using xda app-developers app
If you google koush Dutta windows 8 adb drivers you will find a bunch of places to download universal adb/fastboot drivers.. I have had Iuck using those ..
Sent from my HTC One using Tapatalk 4
jkel777 said:
This is the website I used: http://htc-one.wonderhowto.com/how-...wrp-root-google-play-edition-htc-one-0148146/
A couple things to note (from my experience following this tutorial):
-The first time I fastboot flashed TWRP, it didn't stick. I had to do it again, and then it stuck.
-When I rebooted to system from TWRP and let it root me using the SuperSU installer, that didn't work using Google Play or the TWRP option, probably because I was on 4.3. You have to manually flash the supersu zip file in TWRP from the thread on XDA.
Hope that helps!
EDIT: regarding you driver situation, I'm on Windows 8 and all I had to do was plug it in and it downloaded the necessary drivers automatically. I believe I have HTC Sync Manager installed, but it's not running, and wasn't running when I was going through that tutorial.
EDIT 2: Looks like I read your post wrong,.. I thought you had the GPe. Nonetheless, that tutorial may help you.
Click to expand...
Click to collapse
Thanks for the link I'll try that out. I tried the method he linked to at the beginning of his post but he tells you to edit the user "path" which I don't have under windows 8.
Thanks a bunch I'll post an update!
Sent from my HTC One using Tapatalk 2
ToiletDucky said:
Thanks for the link I'll try that out. I tried the method he linked to at the beginning of his post but he tells you to edit the user "path" which I don't have under windows 8.
Thanks a bunch I'll post an update!
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Let us know if it works! Since that tutorial is for the GPe, unlocking the bootloader for your Sense version is a little different. But once you achieve an unlocked bootloader, I believe the rest of his tutorial is the same for both devices.
hey i tryed a lot of Guides but still doesnt work. Dont know why...
On windows 7 its no ptoblem but on windows 8..gosh... driver signature --> off diferent drivers from different guides everything...
New Windows 8 installation ---> Nope
I have to use the pc from my parents to flash xD very annoying
I know a couple people asked for a guide and I didn't see anything concise had been posted (Mods feel free to remove if it's a duplicate.). Things are still a bit fresh, but this should be a short list of steps to perform the upgrade of your Nexus 7 (2012) WiFi to Lollipop.
As with other guides, I make no expressed or implied warranties - you break it, it's on you.
This is how I was able to get Lollipop working on my own Nexus 7 (2012). I was coming from a rooted factory image of 4.4.4.4 which was the previous most-recent factory image released by Google for this device. I like my device as bone stock as possible and wanted to upgrade and keep it that way.
I assume the following:
You know how to use both adb and fastboot and have already configured your system to use these utilities.
You have already performed an oem unlock on your device.
That out of the way, on to the guide...
It goes without saying, but I'll call it out anyway... Take a backup of your current device setup. Most likely this is within your custom recovery or TiBu. If your not familiar with how to do so, consult the help pages for those apps.
Download & unpack the requisite files
LRX21P factory image from Google.
CF-Auto-Root from Chainfire.
OPTIONAL Only if you're upgrading from a version of Android prior to the JWR66Y Android 4.3 factory image, download the KRT16S factory image from Google.
Start by rebooting your device to the bootloader.
Code:
$ adb reboot bootloader
OPTIONAL If you have ignored my assumption and haven't already done so, now would be the time to oem unlock the bootloader
Code:
$ fastboot oem unlock
Run the following commands to prep your device to install Android L. NOTE:This will erase your device
Code:
$ fastboot erase cache
$ fastboot erase recovery
$ fastboot erase system
$ fastboot erase userdata
OPTIONAL If you are upgrading from a version of Android prior to the 4.23 bootloader release which was originally released along with the Android 4.3 JWR66Y factory image, then you will need to upgrade the bootloader also. The bootloader included in the Android L factory image is not correct and will fail to install. Your best bet is to download the KRT16S factory image from Google and use the bootloader-grouper-4.23.img file from that factory image. Be sure whatever version of the bootloader-grouper-4.23.img file you use has the correct md5sum.
Code:
$ md5sum nakasi-krt16s/bootloader-grouper-4.23.img
df53028033c9eccf4fe5ba7bc198ce24 nakasi-krt16s/bootloader-grouper-4.23.img
$ fastboot erase boot
$ fastboot flash bootloader nakasi-krt16s/bootloader-grouper-4.23.img
Now, install the actual Android L system
Code:
$ fastboot -w update image-nakasi-lrx21p.zip
Your device will automatically reboot at this point and when it does, you will be running Android L (5.0) 100% stock and WITHOUT ROOT. This boot usually takes a very long time (~5-10 minutes) as it's performing the initial setup of the OS. When the device is back up fully, you will have to go through the setup steps as if it were a new device. Once that's done, proceed to the next step.
Now that Android L is freshly-installed, not only have you lost root, but you've also lost the Developer Options menu and the USB Debugging option contained therein. So, before we proceed, we need to enable Developer options & USB Debugging in the settings menu so that adb & fastboot will work recognize the device. Again, if you have any experience with running adb & fastboot, you will know how to do this. The process is exactly the same as with previous versions, so there should not be any surprises here.
Go to the Settings menu and scroll down to and tap on "About Tablet"
On the next screen tap on the "Build Number" field seven (7) times and you'll be presented with a message of "You're now a Developer!"
Hit the back "triangle" and go into the Developer Options menu and turn on USB Debugging.
Just be sure to accept the key on your device when you connect it to your computer.
Now, we can use adb to reboot the device so we can apply the CF-Auto-Root patches and SuperSU from the bootloader
Code:
$ adb reboot bootloader
Once in the bootloader you will need to apply the cf-auto-root. Use the following command.
Code:
$ fastboot boot image/CF-Auto-Root-grouper-nakasi-nexus7.img
NOTE: Windows users have reported that the file is in the same directory so just double-check the path to the file.
This will boot the device onto a custom kernel, install the kernel fix to allow root and also install the latest beta version of SuperSU (2.20) for Android L.
You will now end up with a device running Android L with root. I did not mention at any point about installing a custom recovery. These steps will remove a custom recovery, so if you want to install that, you will need to consult the instructions for your custom recovery of choice. I usually use the CM instructions for installing CWM as they're easy to find. This is not strictly necessary for root. Similarly, my main purpose for rooting was to use Titanium Backup. The current production version of TiBu doesn't support Android L, but the TiBu team has released a test version for L via their twitter feed. Here's a direct link or you can go to their twitter feed for more info...
Questions? Comments? Did I miss something? Let me know.
EDIT: Seems that the performance has really gone down over the past few days. Not really sure what the cause of the performance degradation is but it's quite severe. I noticed last night after having left it plugged in all night that the device wouldn't even turn on or took an inordinately long amount of time (many minutes) to wake from sleep. As it stands I attempted to play a game that's slightly intensive and after a short period of time the device got really hot and started really having performance issues to the point where it rebooted on it's own. Further, I noticed a number of things aren't working that probably should... Bluetooth & "Battery Saver" mode are the first two that come to mind.
Anyone else experiencing similar issues?
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
petenatas said:
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
Click to expand...
Click to collapse
Would you mind pointing me to it?
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
jasoraso said:
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
Click to expand...
Click to collapse
added
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
Click to expand...
Click to collapse
Not sure about on Windows, but on Linux when I unzipped the root zip file, there was a directory layout as such...
Code:
cf-auto-root/
cf-auto-root/image/
cf-auto-root/image/CF-Auto-Root-grouper-nakasi-nexus7.img
cf-auto-root/root-linux.sh
cf-auto-root/root-mac.sh
cf-auto-root/root-windows.bat
cf-auto-root/tools/
cf-auto-root/tools/AdbWinApi.dll
cf-auto-root/tools/AdbWinUsbApi.dll
cf-auto-root/tools/fastboot-linux
cf-auto-root/tools/fastboot-mac
cf-auto-root/tools/fastboot-windows.exe
In any case, you were able to find it. Should be pretty obvious which file I'm referring to...
apocope said:
Would you mind pointing me to it?
Click to expand...
Click to collapse
Added a link in the paragraph at the end.
Yes!
I needed my root. (The stock kernel underclocks like crazy, making the tablet nearly unusable.)
Thanks for the guide brother. You are awesome
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
A very very very very usefull guide!!!!
All working fine!!!!
Thanks!!!!!!!
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
OMG corrupted bootloader AGAIN.
GOOGLE what's wrong with you???
Thanks for the guide! Works fantastically on my aging N7.
Short rundown video by me on YouTube here:
Does it wipe internal storage?
abobobilly said:
Thanks for the guide brother. You are awesome
Click to expand...
Click to collapse
:good:
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
Click to expand...
Click to collapse
:good::good:
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
Click to expand...
Click to collapse
I made a mistake on the version number that I listed in my instructions. When I did my N7, I had originally just tried flashing SuperSU via the standard zip file method. The most recent version of SuperSU available in the SuperSU XDA thread is/was 2.19, so I just assumed that it was the same version being used in the CF-Auto-Root. But as you correctly point out, the process installs 2.20 not 2.19. I updated the version number in the guide. Thanks.
ToucherCD said:
Does it wipe internal storage?
Click to expand...
Click to collapse
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
Added a link to the KRT16S factory image which contains a proper bootloader-grouper-4.23.img file that you could use.
jetsaredim said:
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
Click to expand...
Click to collapse
Hi. Good job on the guide. Very detailed. That's good.
Thanks for the tip with booting CFautoroot img. I was wandering why superSU 2.16 was not working and was looking for modified karnel all morning.
BTW. I know it's not recommended, even my Tapatalk signature says it
but I didn't wipe user data while upgrading. See my post here with details.
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Can I just ask about the bootloader?
I'm seeing alot of users reporting there's an issue within the bootloader that is included on the LRX21P image for Grouper, I performed a clean flash yesterday and flashed the leaked image for grouper, I haven't had any single issue flashing all of the images, even bootloader that came from the lollipop image doesn't seem to cause an issue.
Btw, everyone's suggesting to flash the bootloader from JB & KK on this lollipop build, is there any impact on the performance of why's that recommended to flash the old bootloader?
And I didn't really expect this but lollipop made it worst to run on this device! Even if it's a 2012 device, why's that it can't handle lollipop smoothly? I can't even drop the status bar down at a rate of 60fps as promised by Google, can't even swipe the screen smoothly and it's freezing as hell! It feels like something's wrong with this build.
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
JovieBrett said:
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
Click to expand...
Click to collapse
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Natakranta said:
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Click to expand...
Click to collapse
Yup, I all agree of what have you said. I tried ext4, f2fs etc etc, none of them improves the N7's performance or at least the stock one has the best performance and stability for me.
Heard alot of users blaiming about the tegra chip for this, they said that tegra chips are getting worst every year and if all of these are true, I have doubts about Nexus 9's performance since even the one of the famous 'Android Police' senior editors have found that there are unusual freezes and glitches from the device itself, idk if that happened on the latest build for N9.
The 2011 device I'm currently comparing to is an Xperia Mini, snapdragon chip with 1Ghz single core, 512MB of RAM, I'll look away from tegra based devices...
Btw, do you have an N7 2013? I'm planning to buy one this December to replace my 2011 device. Can I trust this 2013 model with snapdragon processor? I always trust these snapdragon based devices.
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not iirc <71.08 shouldn't be flashed onto 71.08 existing BL right or was it 71.10 ?? (idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all. Heard a few CM roms had BL packed into ROMs and the updte to 5.1.x + lower BL caused hardbrick, a.k.a bootloop + noTWRP with Fastboot lockedout ).
So here's my to-do list sorry to post this long but seems like this is start for me....Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & Nexus 6 information....
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - MultiROM working guide on 5.1.1 plus M latest release anyone, will try the official thread tho, any info on whre to start would be awesome !!
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful posts/threads that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Ashtrix said:
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not(idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all). So here's my to-do list sorry to post this here but seems like this is start for me.Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & a few Nexus 6 information, any useful links would do the job.
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - Does MultiROM work on 5.1.1 plus M latest release ?
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful links that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Click to expand...
Click to collapse
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
AlkaliV2 said:
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
Click to expand...
Click to collapse
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Ashtrix said:
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Click to expand...
Click to collapse
I'm pretty sure mFastboot is made directly for a Verizon variant, but since the Nexus 6 is unlocked and your Verizon SIM card dictates the network you are on, I would say stick with normal Fastboot for your flashing endeavors. Good luck and read twice, flash once :good:
Edit: Quick side note, love the avatar. Good choice.
Thankyou :highfive:
Just did an OEM unlock and wierdly after that, the bugdroid loading doesn't end at all. Did an factory img flash of 5.1.1 Shamu-LMY48Y and booted in less than a min Lol.
And yes the fastboot is working, wow things are definitely wierd with Shamu (volume normalization, mFastboot previous xperience, bootloader bricks...seems like Qcom fixed that after CM brickbug and no one can help the manual bricking) but I'm ok with all these , just love this device, massive, powerful and sexy looking piece
EDIT :
Well everything's going fine but this bugdroid loading doesn't seem to be fixed at all, after bootup 23Gb was there so I did a format and again stuck, this time around I tried using TWRP to flash (CM12.1)after doing fastboot commands - fastboot format userdata, cache. Now it says unable to flash on so&so data partition, So formatted from the OS and now MTP says generical heirarchial. I don't remember any device with that format...
EDIT 2 : Device won't boot with that bugdroid formatting the Data partition. Needs to be fastboot flashed else stuck there forever again same 23Gb bootissue if I do that & Using fastboot format userdata command it formats into the 64GB - 54Gb available space but with TWRP It fails to flash - the same error, can't flash on data parition. So repeat fastboot and it's a damn cycle. Will try to flash MM if it won't then. I may have to return again...OMG
EDIT 3 : http://forums.androidcentral.com/go...ys-formatting-data-yellow-text-any-ideas.html
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-formatting-data-t2737793
EDIT : Tried MM and after 10 mins formatted succesfully now gotta try a ROM or any, hope its fine !!
Again the GH FS is back with MTP and doesn't flash at all with TWRP. If I go for a re-lock and it it fails to boot with formatting properly...then bam nothing but a bricked Nexus !!
TWRP did the format but the device is messed up, sliptscreen issue..
I'm going to return this, enough of the hassle had me messed up totally :crying:
Seems like 6P seems better than having all these issues. Or wait for the 2016 device...
EDIT : Sorry for the GH format seems like it's normal, but the flashing issue is too wierd..
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
scryan said:
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
Click to expand...
Click to collapse
I know this issue, just a factory reset fixed this thing on my old N6 that I had for 2 days, but this takes too much of time to format....Just had TWRP do the job and flashed the Temasek but ALAS !! Splitscreen issue.
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?
Disclaimer: By attempting this I accept no responsibility for any consequences or repercussions or perceived consequences or repercussions of using this guide or any of the files in it. I'm simply a n00b trying to make things easier for the next guy because this was quite a process and my phone was "bricked" for several days before i found the solution so this is more a "how i did it, maybe it will work for you" guide then most of these guides by guys with a lot more experience than me. If you run into something crazy I didn't run into, ill likely not be able to help you.
With that being said after 3-4 days of struggling, this is what was working TODAY, 6-3-2022
Now that the disclaimer is out of the way, here's a further warning... THIS WILL ONLY WORK FOR THE NORD N100 Metropcs Variant (BE2015) BE82CF. You WILL have issues if you try this on another N100! Furthermore, this will leave you stuck on OOS 10.5.8 (android 10) rooted with no way (that I could find) to update further. If that's not ok with you, well then this guide isn't for you.
PLEASE READ THE WHOLE GUIDE BEFORE BEGINNING TO AVOID MAKING MISTAKES OR MISSING STEPS/NOTES!
So normally we would unlock the bootloader and then install magisk and take our boot.img from the firmware we are on and patch it and flash the patched boot img and then we would be done.... HOWEVER there's not a lot of newer firmware floating around for this phones variant.... so first, a step backwards before we continue.
0) Before you start make sure you have everything you want to keep backed up one way or another because this will wipe your phone several times over and you will lose everything that you don't backup!
1) Flashing OOS 10.5.8 using MSMDownloadtool.exe so that our boot.img will match our current version
So the newest firmware I could find that I could VERIFY belonged to this exact variant was 10.5.8 (android 10). However i was on the newest firmware which was android 11. The boot.img wouldn't match so this could likely brick my device
So first i used the firmware i found to go back to an older firmware that i got from here [OPN100][OOS METRO BE82CF] Unbrick tool to restore your device to OxygenOS
and in case a newer version is posted in the future here's the direct link from this post OOS 10.5.8
I used the included MSMDownloadTool but had trouble connecting until i used my motherboard USB port AND uninstalled the qualcomm driver that was already installed and installed the one i got from this post: Qualcomm HS-USB QDLoader 9008 Drivers: Download & Install
After i finally connected it took me just about 4 minutes to flash the new firmware. Once again you have a fresh clean install. Setup everything really quickly in OFFLINE mode. This is for 2 reasons, one is speed but the other is to stop the auto update of the system firmware! Before enabling internet. enable developer mode and uncheck Automatic System Updates
NOTE: For some people it will make more sense to do this next part first so they aren't stuck on an old firmware for a week while waiting for an unlock token, but regardless if you do these steps first or not they still need to be done here as well since flashing firmware with MSMDownloadTool relocks the bootloader if it was unlocked already.
This is already going to be long so for sake of shortening it im putting these steps here instead
2) Switch the OEM UNLOCK toggle in dev options
We have to flip the OEM Unlocking option in developer options. But it's greyed out! I myself did this the time consuming way but theres two methods, ONLY CHOOSE ONE
2.1a) Its greyed out because you're carried locked. You can get this ungreyed by waiting 6 months and using the stock carrier unlock app named "unlock." You can do this quite easily using this app and following the prompts.
2.1b) There's a way to skip the carrier unlock, after all we dont want to switch carriers just unlock the bootloader. This was found the best way: by accident. Someone made a one plus debloat script and the people that were running it found out that the"unlock bootloader" came unlocked afterwards. It's a neat little script, i ended up running it myself. I found somewhere in my searches the exact command in the script that did it but i can't remember exactly and can't find the post that identified the one command.
I BELIEVE it's one of these three:
com.qualcomm.qti.remoteSimlockAuth
com.qualcomm.qti.uim
com.qualcomm.qti.uimGbaApp
The most obvious one seems to be the remoteSimlockAuth. TBH i only added that because it seemed so obvious. I believe it's actually one of the other two, but i'm just not sure. You could try removing those three only and see if it works. Worse come to worst, run the whole script from this post: One Plus Pure Debloat
NOTE: If you are going to run the whole debloat script make sure to install a keyboard FIRST or you will be stuck without one! Or remove com.google.android.inputmethod.latin from the list.
2.2) No matter which way you completed it (using step 2.1a or 2.1b), the OEM Unlocking toggle in developer option will be usable now. Enable it. While you're in developer options, make sure usb debugging is on because you will need it for the next part. Make sure to plug your phone in and when the rsa key fingerprint pops up, choose "always allow from this computer"
3) Unlocking the bootloader
This part is pretty standard with no serious deviations. I followed this guide from step number 3 on: How to unlock bootloader for OnePlus smart Phone
When you get to step 5 they don't mention it but it takes about a week to get the unlock token.
The only real thing i changed for all of this pretty straightforward guide was when they say the command is fastboot flash cust-unlock <unlock_token.bin> ... Well the bin is called unlock_code.bin so i ended up using fastboot flash cust-unlock unlock_code.bin instead.
Once you finish and your phone restarts, set up the phone quickly in offline mode just to get through it again. Before enabling internet. enable developer mode and uncheck Automatic System Updates. While you're in developer options, make sure usb debugging is on because you will need it further on. Make sure to plug your phone in and when the rsa key fingerprint pops up, choose "always allow from this computer"
4) Decrypt the .OPS firmware file from step 1 to get the boot.img
The next part seemed very complicated but really wasn't. We need to decrypt the .OPS firmware file to get the boot img out of it. I used Oppo Decrypt
There were some changes I needed to make in this section which ended up working, i don't know if the issue was a newer python version or what but if following the readme from the github doesn't work as-is for you, try this instead.
4.1) install python for windows from the official website Python Official Site
4.2) Navigate to the python install directory. C:\Users\%username%\AppData\Local\Programs\Python\PythonXXX\ is the default directory, with %username% being your account username, and XXX being the current python version without the .'s For me this was C:\Users\Kaladin\AppData\Local\Programs\Python\Python310\
Now launch a command prompt from this location.
4.3) Run the command pip3 install -r requirements.txt and if it complains about anything not being updated run that command next to update everything.
4.4) Move a copy of bengal_14_O.04_201221.ops from step 1 into the python310 folder and then run the command opscrypto.py decrypt bengal_14_O.04_201221.ops and wait for it to finish. You can now close the CMD window. You will find the boot.img we need in the "extract" folder in the same directory. Put your phone in file transfer/MTP and move just the boot.img over to your phone or however you want to get this done, do it.
5) Install magisk and root by patching the boot.img and then flashing the patched boot.img
Now we just follow these steps starting at step 2.3 from this guide How to Root OnePlus Nord N100 using Magisk [No TWRP Required]
The only thing that seemed wrong here is in step 3.4 they say to run the command fastboot devices and not only is this not needed but wont work here. If you want to make sure you're connected, use adb devices here instead or reboot to fastboot first before running fastboot devices (so after step 3.5 before step 3.6 instead of step 3.4).
Then, in step 3.6 we have an A/B partition systems, so we need to use the first command only, fastboot flash boot boot.img ... ignore the second part about non A/B Partition systems. Flashing the wrong command here could probably brick your device.
Follow the rest of the guide.
One additional thing i needed to do to obtain root after rebooting was to again open Magisk Manager and click install and choose "Direct Install (recommended)" this time (instead of select file and patch it). When the process is done, reboot your phone and then once it restarts you will be able to download a root checker app off the play store and verify root.
Yay! It was a long journey, but we are done!
NOTE: Magisk has a way to install OTA updates while keeping root by half uninstalling Magisk and reverting to the stock boot.img before allowing the OTA update, then you would reinstall Magisks patched boot.img to the other partition before restarting but i wasn't able to get this to work myself. I will give you the tutorial here though just in case but for me it auto restarted as soon as the OTA update finished installing and updated me to the newest firmware which removed my root and made it so that i had to start this whole process all over again from step 1 (minus the wait time for the carrier unlock and the unlock token of course). So up to you if you want to try this out.
For now i'm just happy to be rooted on a stock rom even if it is a little old. Hope this helps someone out =)
SPECIAL THANKS FOR ALL THE PEOPLE WHO WROTE THE GUIDES, TUTORIALS, AND PROGRAMS USED THAT I LINKED TO! I WOULD HAVE BEEN LOST WITHOUT THESE AND ALSO WITHOUT GOOGLE TO FIND THEM!
any chance you could upload the patched and unpatched boot.img?
dabman710 said:
any chance you could upload the patched and unpatched boot.img?
Click to expand...
Click to collapse
Sure, but i don't know enough to know if you should use the patched one or not. I think you should use magisk and patch yourself.... But ill include it anyways Boot.img from bengalm_14_O.04_201221 it may be totally safe im just not sure. but the boot.img is unaltered.
AesopRock127 said:
Sure, but i don't know enough to know if you should use the patched one or not. I think you should use magisk and patch yourself.... But ill include it anyways Boot.img from bengalm_14_O.04_201221 it may be totally safe im just not sure. but the boot.img is unaltered.
Click to expand...
Click to collapse
i didnt try using your patched boot.img, but the unpatched one worked perfect for me after patching myself. saves everyone a few steps too by having that available. thank you
So even though i debloated all one plus things i could find and kept autoupdate automatically in dev settings turned off , my phone still pushed an update and i lost root.... Unless someone knows how to fix this, CFW may be our only hope of keeping root, at least for this variant