Develop Bugs

Root + twrp + bootloader unlock + twrp flashable stock rom - marhsmallow

If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.

Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?

Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.

Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.

I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!

slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....

Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.

I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?

Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's

Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?

famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's

Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.

famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.

Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?

famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.

Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".

famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )

Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.

find device storage corrupted your device is unsafe now

Im using MI 6 since last two weeks i am facing Error "find device storage corrupted your device is unsafenow" and already it’s been reset two times!
the wifi is not enabling and some of sensors are also not working i am in very big trouble
the bootloader is locked and i am not able to flash the official stock ROM
i have tried to download latest package from update and installed but not get success
I've seen many tutorials to solve this problem, but the thing is I've to unlock bootloader! My phone bootloader is still locked
What should i do now!
Experts please help me to sort out my problem!
Thank you.

I've heard xiaomi phone can use 'fastboot oem edl' even if it is not unlocked.
Maybe you can search something about that.
Hope that helps.

Good point. I have the same problem. I will try edl mode.

i am also getting this, have you solved?
---------- Post added at 11:48 AM ---------- Previous post was at 11:07 AM ----------
Reflashed using edl, problem still continues.

Edit, posted in wrong topic

You can try to use XiaomiTool and flash your phone with instead..
Check if your device is still encrypted, if not, that's likely the reason why it tells You storage is unsafe.

Is it solved? The same problem
Help

I had same issue. I unlocked bootloader, flashed twrp format data and then flash xioami eu and it works.
If you want to flash Global or other official you have to use miflash and tgz rom. If you, after flashing, see a corrupted memory try from fastboot the command:
fastboot format userdata

I also have this problem, but my status is strange. I use Xiaomi Flash Tool to flash the offical rom 10.3.4. When I boot to system, I get the error message, "find device storage corrupted your device is unsafe now". I flash the newest rom 10.4.3 from miui.eu, everything is good....><"
When I get this error, I have tried to enter fastboot mode and enter the command, "fastboot format userdata", but it's not work.
Have anyone also this problem and solution?

Were you able to find a solution?
imrankhp said:
Im using MI 6 since last two weeks i am facing Error "find device storage corrupted your device is unsafenow" and already it’s been reset two times!
the wifi is not enabling and some of sensors are also not working i am in very big trouble
the bootloader is locked and i am not able to flash the official stock ROM
i have tried to download latest package from update and installed but not get success
I've seen many tutorials to solve this problem, but the thing is I've to unlock bootloader! My phone bootloader is still locked
What should i do now!
Experts please help me to sort out my problem!
Thank you.
Click to expand...
Click to collapse
I have the same problem in my Mix2 having followed the instructions to move from the now stopped Global Developer ROM to the Global Stable. I followed the directions carefully and after unlocking the bootloader, flashed using the fastflash method choosing to lock the bootloader again. On starting up the phone, I have all the problems you describe, including no way of signing into my Mi account to reflash the phone. [email protected] have been contacted but their suggestions have not addressed the fundamental problem of the corruption also blocking my ability to log into the Xiaomi account to unlock the bootloader.
This has been a very good phone but now!!!
Did you find a way to unllock the bootloader? It seems to be a problem for quite a few people and it would be helpful to know if it is still worth trying to rescue the phone.
Thank you in advance. You described the problem very clearly,
Chris

On xiaomi mi 9t I installed
Code:
davinci_eea_global_images_V10.3.12.0.PFJEUXM_20190801.0000.00_9.0_eea_1d38ae0ec5
and
davinci_global_images_V10.3.11.0.PFJMIXM_20190802.0000.00_9.0_global_ea6683ef55
two times . device storage corrupted every time
3rd time installed davinci_global_images_V10.3.11.0.PFJMIXM but logged in with miaccount during first configuration and error is gone..

i have this problem in redmi note 8, after trying xiaomi.eu rom, i have flashed stock rom again via twrp and now i have that error.
is it solved already?

I have removed the problem, but I don't know the root cause. I install third rom and rollback to miui eu rom, then the problem is disappeared.
1. Install OmniRom(clean dalvik, cache, and internal).
2. Install magisk to root OS(clean dalvik, cache, and internal).
3. Boot to os and reboot to twrp.
4. Reinstall xiaomi.eu_multi_MI6_V10.3.1.0.OCACNXM_v10-8.0.zip.
5. Boot to OS and I find the problem is fixed.
mfpower86 said:
i have this problem in redmi note 8, after trying xiaomi.eu rom, i have flashed stock rom again via twrp and now i have that error.
is it solved already?
Click to expand...
Click to collapse

What's the solution?
ChrisX5 said:
I have the same problem in my Mix2 having followed the instructions to move from the now stopped Global Developer ROM to the Global Stable. I followed the directions carefully and after unlocking the bootloader, flashed using the fastflash method choosing to lock the bootloader again. On starting up the phone, I have all the problems you describe, including no way of signing into my Mi account to reflash the phone. [email protected] have been contacted but their suggestions have not addressed the fundamental problem of the corruption also blocking my ability to log into the Xiaomi account to unlock the bootloader.
This has been a very good phone but now!!!
Did you find a way to unllock the bootloader? It seems to be a problem for quite a few people and it would be helpful to know if it is still worth trying to rescue the phone.
Thank you in advance. You described the problem very clearly,
Chris
Click to expand...
Click to collapse
This is exactly the trouble I caused with my Redmi 3S Prime

I am also have the same problem in redmi 4x
, I restored perist partition it's fixed,
this error comes when revert back to stock or lower version custom Rom from Q based custom Rom.
Then I faced another problem weak network (reset the network every tower/ band changes) freeze my phone ? I don't know how to fix it? Some one please help me

imrankhp said:
Im using MI 6 since last two weeks i am facing Error "find device storage corrupted your device is unsafenow" and already it’s been reset two times!
the wifi is not enabling and some of sensors are also not working i am in very big trouble
the bootloader is locked and i am not able to flash the official stock ROM
i have tried to download latest package from update and installed but not get success
I've seen many tutorials to solve this problem, but the thing is I've to unlock bootloader! My phone bootloader is still locked
What should i do now!
Experts please help me to sort out my problem!
Thank you.
Click to expand...
Click to collapse
Well I got a solution from telegram group.
People having this problem can flash persist.img . But this worked on POCO F1 , don't know about other devices . Y'all can try and let other know.

Touch screen not working, even after factory reset

My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...

Send it back. It sounds like a hardware issue.

sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?

DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:

Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.

Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!

As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.

Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.

DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).

Again, just to be sure, you are using a USB A to C and not a C to C, correct?

DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...

krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.

Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...

DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.

Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.

DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable

Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it

I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.

I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...

DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.

Bootloader auto locks, can install TWRP but asks for password.

Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks

internetdenizen said:
Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks
Click to expand...
Click to collapse
"bootloop_after_lg_replaced_mainboard_bootloader reddit"
google it

https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
This is the droids guide you are looking for...
Hope this helps anyone else who lands here with the same issue.

First sorry my bad english. I guess you took wrong way.
I suggested safety and easy solution. TWRP needs password due to encrypted data partition.
If you can format userdata,TWRP require no password and you can flash any Rom.
I wish you success with your way.

Thank you for your reply.
I am following the instructions here; https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
I am stuck at the google logo. The bootloader is locked and I cannot unlock it because I cannot get the system up to enable developer tools and allow unlocking.
I don't really know what else to do.

The last resort
h ttps://ja.aliexpress.com/item/32846103543.html?spm=a2g0o.cart.0.0.74743c004Bny1g&mp=1
There is no longer anything that I can do for that.

I've managed to recover the phone using a combination for LGUP + tot files and sideloading an OTA from google.
I want to turn off encryption though... not sure how to do that..

Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2

Hiroki.S said:
Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2
Click to expand...
Click to collapse
I've tried to follow the reddit instructions. There are some missing files in the instructions where he links to xda-developers https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
The files are not available. Same goes with Magisk Compatible phh's SuperUser not being available
Thank you though for taking the time to try and help me

h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17

Hiroki.S said:
h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17
Click to expand...
Click to collapse
I have that boot img and tried to flash it but nothing happens.. The phh-superuser-magisk is marked as obsolete here -> https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
thanks mate

Majisk latest
Probably no problem

Hi mate,
I managed to flash TWRP. I booted into TWRP and selected to keep the system read only. I then used 'adb push' to push Magisk to the SDCARD and successfully flashed Magisk. I can boot back into the system and I have root access. Where do I go from here? I would like to install a custom ROM
thanks mate.

OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks

internetdenizen said:
OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks
Click to expand...
Click to collapse
Everyone goes through the same thing.
Cheers.

How To Guide adb doesn't discover phone but fastboot does - trying to install Lineage OS

I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.

Try fastboot commands in bootloader

yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload

Try "fastboot reboot" or "fastboot reboot bootloader"

yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.

If it's Windows your using it may be a driver issue.

yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?

johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222

heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment

johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too

heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.

bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool

heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?

i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware

heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?

johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself

can you tell me which version your phone have? IN/CN/GLOBAL/INDIA

Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above

heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America

johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos