Related
TWRP 2.8.5.0 YotaPhone 2 recovery imageAfter the bare bones modded stock recovery for YotaPhone 2 it's time for something more advanced. The TeamWin Recovery Project 2, or TWRP2 is just that: a fully fledged, graphical, touch enabled, custom recovery.
This recovery image for YotaPhone 2 is still an alpha version, so expect some rough edges. Which leads me to:
Disclaimer
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device. You are likely to void your warranty by doing so, and on a bad day you might even damage or brick your device.
What is it?
It's a recovery image for YotaPhone 2 based on TWRP2 custom recovery, and the stock kernel from Yota Devices. You can boot it ad-hoc, or flash it permanently to the recovery partition. Use it to root, install software, make backups, update ROMs etc.
What can you do with it?
- adb root & shell access
- All TWRP 2.8.5.0 functionality (except MTP)
- install update zips (signed with testkeys (e.g. SuperSU), Yota Devices software, and also unsigned zips like Xposed framework.
- You can sideload packages, but also install them from internal storage (e.g. Download folder)
- make partition backups
- root your device
What can it NOT do?
- In this recovery image the MTP functionality of TWRP is disabled, it doesn't play nice with YD's kernel.
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0
- Some technical confidence to cope with quirks that come with an alpha version
- USB cable with a PC or laptop on one end
Steps overview:
NOTE: I used less detail in this post than the previous recovery thread, please look there for more detail.
1) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
2) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
3) Unlock the bootloader if you haven't done so before (read warning below!)
4) Download recovery image: recovery_twrp_yd201_alpha2.img
5) boot or flash the recovery image
Unlocking bootloader:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
See stock recovery thread for unlock steps
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
You should see a black screen with a tiny white: downloading...
b) Boot the recovery image:
Code:
fastboot boot path/to/recovery_twrp_yd201_alpha2.img
Alternatively, flash the recovery image (overwriting the stock recovery):
Code:
fastboot flash recovery recovery_twrp_yd201_alpha2.img
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly. TWRP has it's own logfile that you can copy to (virtual) SD card, and access from there.
Kernel sourcecode:
In this recovery image is Yota Device's version of the Linux kernel v3.4.0 for YotaPhone 2. Yota Devices are required by the GPLv2 license to release the source code for this kernel, but so far they haven't taken that step or even shown intention to do so as far as I know. The YotaPhone firmwares and also this recovery image are in effect violating the GPLv2 license if the situation does not change. Attempts to contact Yota Devices on the subject through support, press departement, and an attempt to contact Yota Device's management, have gone pretty much unanswered as of writing. I'm hoping they're just busy making great devices instead of being unwilling.
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info & credits::
TWRP2 is created and maintained by TeamWin. Please donate through their site if you enjoy their work!
Recovery image for YP2: SteadyQuad
Version: alpha2 based on TWRP 2.8.5.0 with Yota Devices kernel (1.39 EU1)
Thanks to: TeamWin for TWRP, @Dees_Troy for hints for getting it up and running, @Jeopardy for testing, @Chainfire for SuperSU and lastly Yota Devices for a great device.
Linking to this recovery image:
Please don't link directly to the download image, link to this post instead. That way users can get the most recent version and any updated info. (It's an alpha version after all)
Created: 2015-06-23
Last Updated: 2015-06-24
SteadyQuad said:
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Click to expand...
Click to collapse
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Yeah, I got the same boxed response and replied that it was not relevant, and explained why. Their SDK (for app development) has nothing to do with the kernel sourcecode, and at the moment their developer pages do not mention anything about kernel sources. I think that their support page tickets are handled by an external company (quicksupportlink.com), that is dependent on Yota for definitive answers, and they're probably instructed to send this reply. At least Yota will get reports from them, with hopefully lots of requests for kernel source. On the press page there's email addresses of 2 press ladies, you could try those too (as I did).
So nice to see this! Looking forward to trying, once mine comes.
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
zencooler said:
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
Click to expand...
Click to collapse
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Jeopardy said:
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Click to expand...
Click to collapse
Hi again,
Soory for the mistake (I just replied not for the first post). Once again sorry SteadyQuad and congrats for you again!
Jaopardy, thanks for the quick info and confirmation it works on 1.44 EU firmware! It's a good news
Regards!
Jeopardy said:
...Yotaphone 2 kernel's source code...
Click to expand...
Click to collapse
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
elatllat said:
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
Click to expand...
Click to collapse
Thanks, this archive was already known, it contains a kernel snapshot of end of june 2015. I put it on github with some small adjustments to make it build initially. (and it actually boots
I've also put up an initial device and vendor tree there, although both are pretty far from complete/correct at this point.
BTW @elatllat where did you get the link from?
SteadyQuad said:
...where did you get the link from?
Click to expand...
Click to collapse
I did a xda forum search and found that link, this thread, and thought I should link them up.
(as it's not widely known)
so anyone tried xposed??
varun.gid said:
so anyone tried xposed??
Click to expand...
Click to collapse
Yeah. It works as expected. No problems for me.
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
adamo86 said:
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
SteadyQuad said:
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
Click to expand...
Click to collapse
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
adamo86 said:
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
May be my phone is dieing?
Sent from my YD201 using Tapatalk
SteadyQuad said:
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
Click to expand...
Click to collapse
Your right my phone is bust does anyone have yota contact details
Sent from my YD201 using Tapatalk
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
zute333 said:
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
I got rid of it I tried everything downgraded wiped data etc clean install then did ota still freezes after a while. I did clean install of Rom twice. I think the screen is dying or something inside it is loose because the epd started off as freezes then moved to very light grey instead of black and would refresh but old pics and widget would be visible and it started to flicker from one side then it would start to work after a while then fade again etc. When these freezes happened I would get a blue screen when phone was rebooted and it would slow device down then reboot it self until the screen got unfrozen. I noticed even after installing rom new the screen would some time be frozen. It's only sometimes the screen would be reseted if I did a new installation.
I will miss my yotaphone. I will be getting a nexus 6p or v10.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
This method successfully worked for me & @lysm bre (Thanks to him for the guiding)!
Your phone will be unencrypted after folllowing this guide and successfully rooted too if I didn't mention that
To flash ROMs in future you have to disable encryption so this method will make you ready for that too
Here is my video in which I explained in detailed and I've done all the steps from beginning! So you can follow this guide too here- https://youtu.be/mUq1xdJ-7-E
To Boot into Bootloader mode use command adb reboot bootloader or hold power and volume down button once its switched off!
I'll modify & beutify the guide in future so stay tuned for that!
1] Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
6] Boot into TWRP & select allow modifications !
7] Goto Wipe & select format data !
8] After that is done, reboot into system without rooting& skip through setup again!
9] Now if you check the encryption status of your phone (Settings -> Security - Encrypt phone), it won't be encrypted anymore as it'll give you the option of encrypting it, which means it currently isn't encrypted.
10] Now transfer the SuperSU zip file in the internal storage of the phone, reboot into TWRP, and flash SuperSU!
BOOM! You have successfully rooted with encryption disabled.! Congratulations!
Just a reminder that for video explanation watch this- https://youtu.be/mUq1xdJ-7-E
Downloads-
Modified boot.img- http://bit.ly/1MVtrNr Thanks to @Chainfire ONLY FOR build no mdb08i as of now! Do not flash on any other build!
TWRP recovery image- https://dl.twrp.me/bullhead Thanks to @Dees_Troy
SuperSU zip- https://download.chainfire.eu/743/SuperSU Thanks to @Chainfire
Modified boot images for all nexus devices- http://bit.ly/modifiedbootimages Thanks to @Chainfire
Thanks for posting! Unfortunately the link for the modified boot image is broken.
johnpwu said:
Thanks for posting! Unfortunately the link for the modified boot image is broken.
Click to expand...
Click to collapse
Updated! Here- http://bit.ly/1MVtrNr
Else you can always download the boot.img file from here- http://bit.ly/modifiedbootimages [Select "bullhead" for Nexus 5X]
Thanks!
Thank you OP and @lysm bre, great job. Might I suggest that you include the build number in your instructions as you have clearly stated in your video. I watched it and it was very helpful to learn that your boot image was from a specific build number. Thanks again
Might be worth mentioning it's build specific (only for mdb08i currently) and will save someone the time I wasted figuring that out [emoji14]
Sent from my Nexus 5X using Tapatalk
Hayth said:
Might be worth mentioning it's build specific (only for mdb08i currently) and will save someone the time I wasted figuring that out [emoji14]
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
just flash that build number then flash the modified version, thats what i did and its working fine ( i came from build number MDA89E)
hawkins95 said:
just flash that build number then flash the modified version, thats what i did and its working fine ( i came from build number MDA89E)
Click to expand...
Click to collapse
I was thinking of doing that but wasn't sure if the builds are region specific and could affect something I wasn't aware of?
Sent from my Nexus 5X using Tapatalk
Hayth said:
I was thinking of doing that but wasn't sure if the builds are region specific and could affect something I wasn't aware of?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Im in the uk and it is working great for me, im rooted and my data is working, just make sure to flash normal version from google first because when i did it with the modified version is came up with some weird bootloop image. and im pretty sure MDBO8I is an update everyone is getting saw a few articals saying it was.
Worked for me!! Thanks a million!:good::good:
hawkins95 said:
Im in the uk and it is working great for me, im rooted and my data is working, just make sure to flash normal version from google first because when i did it with the modified version is came up with some weird bootloop image. and im pretty sure MDBO8I is an update everyone is getting saw a few articals saying it was.
Click to expand...
Click to collapse
Cool, that's good to know I saw those articles too but as they made reference to enabling band 12 in the US I wasn't sure. I've wiped and restored my phone that many times today I'm going to give it a few days to see if the OTA comes through [emoji14]
Sent from my Nexus 5X using Tapatalk
Thanks. Was too lazy to properly make a post about it. Good work on the video!
Thanks you! How's the device after you have disabled the encryption? I guess faster.....
Can someone verify two things?
Finger print reader is functional
Android Pay is working, by actually making a purchase successfully
EDit: figured that one out...
johnpwu said:
So this is not a complaint about the OP's awesome work, and sorry if I should start a new thread, but I just got a message I've never seen before attempting to unlock the bootloader...
Click to expand...
Click to collapse
Before attempting to unlock the bootloader, go into developer options and tick the option "OEM Unlocking"
xtentual said:
Before attempting to unlock the bootloader, go into developer options and tick the option "OEM Unlocking"
Click to expand...
Click to collapse
Thanks, just figured it out about 15 seconds before you posted.
*deleted* replied to wrong thread
Trinity86 said:
Thanks you! How's the device after you have disabled the encryption? I guess faster.....
Click to expand...
Click to collapse
This. Can someone please comment on performance after disabling encryption?
xtentual said:
Can someone verify two things?
Finger print reader is functional
Android Pay is working, by actually making a purchase successfully
Click to expand...
Click to collapse
I can confirm the Finger print reader is working
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)
*Update 7/30: On my 6P, I found that the original kernel with this mod was using pretty much 1.5 cores, instead of all 4. People with the 5X were also reporting this, so I modified the images to utilize all 4 cores better. It helps performance a lot (able to beat stock 6P in some Antutu marks now, and play intensive games), try it out if you haven't yet!
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/26 - EX kernel for Android O uploaded.
8/22 - Android O working, boot.img and source uploaded.
8/08, 2nd Change - Added boot.img for 48C firmware (August security patch).
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img for 1 core, just to see if it would work for devices that didn't work with the 4 core image.
7/30, 2nd Change - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/30 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP, and added Marshmallow images.
7/23- Created this fix, stock boot.img, twrp, and EX kernel added.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 5X with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice.
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: with the new universal EX zip, you don't have to flash the modified boot.img now, you can just flash TWRP, and then flash the EX zip, and everything should work.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from Android O DP6: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. As a bonus, it also disables forced encryption. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware (August security patch): Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 47Z, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03, for Android O: Download | Mirror. EX kernel for Android Oreo, modified to use 4 cores. You must flash it over the 4 core boot.img for it to work.
EX kernel version 4.12, universal zip: Download | Mirror. This zip is modified to use only 4 cores, and it will also apply the speed fix. Flash this in TWRP. I highly recommend you flash this, as it improves device performance notably, and disables forced encryption. This kernel should work with almost any other ROM, and it applies the core utilization mod from the first image, thanks to AnyKernel.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Here it is: Download | Mirror
For Marshmallow:
Boot.img from the latest 6.0.1 20K firmware: Download | Mirror. This boot.img is modified to use only 4 cores, and is modified to utilize those 4 cores more effectively. Untested as of now.
Ex kernel version 1.2.0 for Marshmallow: Download | Mirror. This is the latest EX kernel for marshmallow, it will keep the core utilization mod from the above image, and should work on almost any other ROM, thanks to any kernel. Untested as of now.
*Source Code:
Source for 4 core Android O DP6: Source.
*Tested custom ROMS/kernels
you should be able to use almost any ROM with a stock based kernel, just flash the EX zip over it.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as people request more, so stay tuned.
Flash a custom ROM. Once again, I will upload more as people request more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@xls654, He found out how to get Android O working with 4 cores.
*FAQs:
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are you have a different problem.
Does EX kernel have the new speed fix? - Yep, the EX kernel zip should apply the 4 core fix, and the speed fix. It should also work with almost any ROM, including stock.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Didn't work
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
TheIronLefty said:
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
Click to expand...
Click to collapse
Awesome! Glad to hear it.
XCnathan32 said:
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
Click to expand...
Click to collapse
Yeah Twrp is not working.
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Gonna try this
Sent from my EVA-L09 using Tapatalk
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
This works, thanks. First time I've been able to boot my 5X in months.
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
I uploaded a custom TWRP image and EX kernel zip. Try flashing the modified TWRP, and then flashing the modified EX kernel, and see if that works.
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
ragdoll96 said:
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Click to expand...
Click to collapse
X-calibar said:
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Click to expand...
Click to collapse
I updated the OP with a modified EX kernel, and some tweaks to make your device faster, check it out to see if it helps your device.
stipo42 said:
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
Click to expand...
Click to collapse
My first time took around 10 minutes to boot I think, if it takes over 20 minutes, reboot your device and reflash, and if that fails, update your firmware to the latest version.
stipo42 said:
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
Click to expand...
Click to collapse
Are you upgrading from stock firmware or a custom rom? This boot.img is for the latest 7.1.2 build. Unless you have files that you can't afford to delete, I would recommend reflashing your stock firmware with the latest version.
flar2 said:
This works, thanks. First time I've been able to boot my 5X in months.
Click to expand...
Click to collapse
Awesome! I just want to say how much I love your kernel, it makes this fix much more viable.
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
stipo42 said:
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
Click to expand...
Click to collapse
default_password didn't work for me, I just clicked cancel when it asked for the encryption, and then I factory reset the device through TWRP. If you have important files you can't delete, you can try just flashing EX Kernel, as I don't think EX needs to access the /data partition.
Update 2 : Seems I was able to just cancel out of the password prompt. Flashed Elemental X and it looks like its booting!
Awesome job my friend, you fixed the (temporarily) unfixable. I'll play around with this for a few days and report back.
Thanks!
XCnathan32 said:
So I found a bootloop fix for the Nexus 6p here, and some users reported having the same problem with their Nexus 5X.
I do not own a Nexus 5X, but I made a modified boot.img the same way I made the modified 6P image. It simply disables the big cores, as that's what was preventing the 6P from booting.
Please report if this works/does not work for you, that way I can get a good sample size to determine how effective this is.
Disclaimer: I have not tested this, I uploaded this image so testers could flash it and report if it works or not. If your device breaks/spontaneously combusts after flashing this, you accepted that risk.
Edit: A few people have reported this working, so it should be safe.
N2G47Z_4Cores.img, this image is based on the latest 7.1.2 firmware for the Nexus 5X, modified by me to only use 4 cores. 4 reported working, 2 reported not working.
To flash it: you must have an unlocked bootloader and fastboot on your PC. Boot your device into bootloader, and then run the command fastboot flash boot N2G47Z_4Cores.img Hopefully, your device will now boot up.
TWRP3_1_1_5X.img, modified to use only 4 cores, will get working TWRP on your device. Not tested yet
To flash, navigate to the folder where it is downloaded, make sure you have fastboot installed, and then run this command: fastboot flash recovery TWRP3_1_1_5X.img.
EX4_10_5X.zip, Elemental X kernel V4.10 for android 7.1.2, modified to use only 4 cores, I highly recommend you flash this, as EX kernel is faster, and you can overclock to the little cluster to make up for some speed. Not tested yet.
To flash, copy the zip to your device, then flash it in the modified TWRP, just go through the AROMA installer as usual. Changing the BIG cpu frequency in the installer will not change anything, as the cores are disabled.
Additional notes:
Root worked on my 6p by flashing the regular SuperSu zip just as normal. None tested for 5X yet
To improve performance slightly:
Disable animations in developer options, it helps a lot.
Overclock little cores with EX kernel, I have mine set to 1632 MHz and everything is working fine so far.
Set CPU governor to performance (or some aggressive governor), with the BIG cores disabled, the battery is already much better, so using a better performance governor shouldn't be a problem for battery life.
Doing a fresh flash of the firmware/factory reset can help a lot too.
Fast custom roms can also help.
Roms that me/other users have found working with this fix:
Pure Nexus worked well for me on the 6p, insane battery life and very little lag. If you are going to flash a rom, be sure to flash the modified EX kernel over it.
If you find a rom that works with this fix, tell me, and I'll put it here.
Credits:
@rchtk, his post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
Feel free to ask me for help, If you have a favorite ROM/Kernel that you want to use, tell me and i'll modify it to use 4 cores.
Please click thanks if I helped you, it means a lot to me
Click to expand...
Click to collapse
Hey man I tried this method, and I can confirm that this works! Although it is slow, it's better than nothing I truly do appreciate your efforts. SCREW LG
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013
kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!
Confirmed G version received.
kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.
kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?
Script to fix the Nexus 5X / Nexus 6P Bootloop problem
Credits
99% credit goes to @squabbi for teaching how to patch files yourself and @XCnathan32 for discovering the fix itself.
1% for me for making the script .
DISCLAIMER
THIS PROCESS WIPES ALL YOUR DATA (unless your bootloader is already unlocked) AND PROBABLY YOUR WARRANTY TOO! USE WITH CAUTION! I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
THIS PROCESS WILL MAKE YOUR PHONE SLOWER (6P 2 times slower, 5X 1.5 times slower)! PLEASE USE ONLY AS A LAST RESORT!
PLEASE CONTACT YOUR WARRANTY TO TRY AND GET A REPLACEMENT BEFORE PROCEEDING!
What does the fix do?
The problem with those phones are the cores of the Cortex A57, and they need to be disabled.
What should you do?
Before proceeding, make sure you have OEM Unlocking enabled on your device, or the flashing won't work!
1. Download the zip below
2. Extract the zip
3. Extract the boot.img from the image you've downloaded (the script explains how to do it if you don't know how) to the folder you've downloaded
4. Open "Script.bat"
You should also download a factory image from this link (unless you live in Japan, don't download the Softbank versions, and unless you live in Australia, don't download the Telstra versions):
6P - https://developers.google.com/android/images#angler
5X - https://developers.google.com/android/images#bullhead
The script itself was not tested, but the method did work on my 5X so it should work.
If you have any requests, you can comment them here, and maybe I'll add them. One day.
I do plan on adding TWRP, Elemental X and Magisk patching one day, and if there will be many requests that day will come earlier.
Links to original posts and videos
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
https://youtu.be/PhObuifEp3Y
I get error of adbwinapi...What can I do? (N5X)
Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
R3tro7 said:
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
Click to expand...
Click to collapse
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Yea, it did that for me too and then booted
Mehr_DaD said:
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Click to expand...
Click to collapse
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
R3tro7 said:
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
Click to expand...
Click to collapse
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Click to expand...
Click to collapse
I'm glad to hear! If you could please "Thank" the post, it will be much appreciated. For your question, I haven't used my script on my phone, I've just followed the steps in @squabbi 's video, and then I've decided to create an automated script (which is the script in this thread) to patch it automatically. Which basically means, yes, I have flashed a BLOD "workaround" patch.
Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Click to expand...
Click to collapse
Still frozen?
R3tro7 said:
Still frozen?
Click to expand...
Click to collapse
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Mehr_DaD said:
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Click to expand...
Click to collapse
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
R3tro7 said:
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
Click to expand...
Click to collapse
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Mehr_DaD said:
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Click to expand...
Click to collapse
Please try to do what I've said
R3tro7 said:
Please try to do what I've said
Click to expand...
Click to collapse
Flashed the March ROM again. Used the script and it successfully installed. On the first boot it stuck on those 4 circles. Sounds like cooling down is the only answer. I can't use my phone constantly :/
Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
theBeachBoy said:
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
Click to expand...
Click to collapse
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
R3tro7 said:
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
Click to expand...
Click to collapse
the script worked.
Now should I flash TWRP 4 core recovery (edit seems so) and use the AK injector or not needed?
What is Elemental X?
p.s. Thanks!
theBeachBoy said:
the script worked.
Now should I flash TWRP 4 core recovery and use the AK injector or not needed?
p.s. Thanks!
Click to expand...
Click to collapse
I'm glad it worked. There is no need to flash TWRP and use the AK injector as you've already flashed a 4 core boot image. If you want, you can flash 4 core TWRP, but that's optional.
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
theBeachBoy said:
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
Click to expand...
Click to collapse
I did a quick search and some website said try resetting the phone. If that doesn't work, try to flash a factory image to make it bootloop again, and try the script. If all of that doesn't work I suggest asking @XCnathan32 or @squabbi because they probably understand it better than me.