Database Users

Help, bootlooped! Locked bootloader.

Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?

ok shot in the dark here. I had a boot loop until I flashed the flashable vendors zip
I got it in this thread:
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
Give it a whirl if you haven't already.
Found this in the Pure Nexus Project thread, so props to them for providing this.

-MotoNexus- said:
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
Click to expand...
Click to collapse
Thanks, the problem is I can't find a way to sideload anything or move a file over. Everything results in a myriad of errors.

tigercranestyle said:
at worst, you would have to invoke the flash-all command via adb once you extracted the couple of times that you have to. directions are on google's factory image site.
may not be the answer that you were looking for, but it always feels great having a clean device to work with. i mean as it stands, you would have to set everything back up on whatever rom anyway if you somehow got out of the problems you were having. you would spend more time doing that instead of just going the factory image route.
toolkits are fun, but learning your way around them is even more so.
Click to expand...
Click to collapse
I'm gonna check the flash all,I've never done that before. I think that would be all the images in the tgz factory image? Anything to get my phone back yeah, I just need it working again.
-UPDATE- I tried the flash all batch in the system image and I tried the flash all batch command and neither work.

Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!

Melamunna said:
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Click to expand...
Click to collapse
I have already done the advance wipe and the format data, I just tried again and my computer will not read it as storage with MTP enabled.
Thanks though!

tigercranestyle said:
after extracting the tgz file, it should become a tar file. after extracting that tar file, it should become the six files listed below. these files should be in platform-tools to start from scratch.
bootloader-angler-angler-02.45.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mmb29m.zip
radio-angler-angler-02.50.img
once they are, open command line in that directory (platform-tools) and then "flash-all" should work. if it doesn't make sure you post the error that you're getting on your computer so that others can help.
Click to expand...
Click to collapse
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?

-MotoNexus- said:
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
Click to expand...
Click to collapse
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.

The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.

tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.

just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas

akellar said:
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
Click to expand...
Click to collapse
Are you telling me that I'm bricked?
I have no way of transfering files to the devices, it won't read as anything to transfer files and ADB won't sideload anything.

tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
Neither am I , I just got back from a trip. I have the fastboot exe adb exe mfastboot exe the ADB api files, and the ROMs I tried to sideload along with all the images I pushed to the device.
Originally I had the bootloader unlocked, like I said I was being a fool blindly following a tutorial to get back to stock and I locked it too soon.
Yeah, I tried flash-all flash all and flash flash-all / flash flash all

dontbeweakvato said:
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
Click to expand...
Click to collapse
Okay I unzipped that folder and put all the files in the fastboot folder, I still get the same error. The thing that scares me here is I can use the batch file now and it just gives me an error saying it can't flash because it's bootloader is locked.

Soulfly3 said:
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
Click to expand...
Click to collapse
They are default unchecked, hence the reason I can't unlock the bootloader again. I said it in my first post, I was being a fool following some guide to get back to stock and ******* up a step.

rift999 said:
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
Click to expand...
Click to collapse
Is there not a way to fix the sideload? Or a way to get my computer to read it as a media devices so I can transfer files or something? It's always worked with previous phones but my computer reads the 6P differently. (even when it was working)

Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.

akellar said:
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
Click to expand...
Click to collapse
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.

-MotoNexus- said:
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
Click to expand...
Click to collapse
Can't help too much personally, but you might give this a shot:
http://forum.xda-developers.com/showpost.php?p=64317181&postcount=20
Sent from my Nexus 6P using XDA Free mobile app

So I just got it............!!!!! I have spent a total of 16 hours with videos, forums and trial and error. When I was going back the 5th around time messing with drivers I turned my ADB driver into a USB composite because I had no idea I could and instantly I was able to file transfer!!!! Problem solved, I have my ROM on now.
Thank you all for your help! I am so sorry I derped at this, I have been doing this a long time and just got sloppy.

Cant install TWRP-MATA_2 error: cannot load 'C:\ADB\recovery.img': No such file or...

I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help

There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.

MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:

MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.

fastboot flash boot_a/boot_b yourTWRP.img
The above command worked for me. Use boot_a or boot_b depending on what you have. In addition use a separate type C cable to your PC instead of stock type C cable and remove all USB accessories plugged in the PC. I know its crazy but working with this phone may require you to do some unexplainable stuff.

MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP

TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.

droidstyle said:
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
Click to expand...
Click to collapse
I am semi new to this community, so I am unsure if it's doing this because I am rooted or not but I've got twrp permanently installed... So from my understanding Slot a can hold your os and slot b basically hold your twrp you just need to remember when you need to switch back.... How I installed was fast booted twrp to slot a, then in twrc switched to slot b to install rom, then switch back to slot a and did a reboot to recovery... Boots into twrp, I switched back to slot b to flash gapps, then restart system... Once inside os and everything is set up if you are rooting reboot to bootloader and flash the patched boot. Img with fastboot on pc... Then reboot system... Now when you want to use twrp all you have to do is reboot bootloader, fastboot to switch to slot a, and then boot recovery... Then Twrp will load then switch to slot b and you are good to go!

barteringram said:
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
Click to expand...
Click to collapse
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise

A_Pac1 said:
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
Click to expand...
Click to collapse
Worth a try I guess but I am maintaining a solid connect to my PC and all other commands seem flawless. My problem has evolved now. I have installed twrp but now the touchscreen wont work.

rignfool said:
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
Click to expand...
Click to collapse
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?

MackHoncho said:
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
Click to expand...
Click to collapse
It's not persistent as in it won't survive the flashing of the stock boot.img.

MackHoncho said:
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
Click to expand...
Click to collapse
I had the same issue with using an older version of Mata TWRP... You need to install TWRP-MATA_11

Solved
My Windows 10 machine isnt set to show file extensions.
was trying to fastboot twrp-11 as I named it; recovery.img
fastboot wanted recovery.img.img
please laugh hardily

aer0zer0 said:
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!

vonstarr said:
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
Click to expand...
Click to collapse
So op6t is easier (I just bought one)
Fastboot boot nameoftwrp.img
It'll boot twrp without flashing it to the phone. Makes life easier. Mata doesn't have this option.

[How to] Fix 'sensors and camera not working', restore IMEI, etc. (Stock Pie)

At some moment when playing with Magisk modules, I've got Android crash, after which sensors (Accelerometer, Gravity, etc.) and Camera stopped working.
Obviously, somehow persist partition data got corrupted and must be reflashed. I believe, that flashing persist via fastboot is not supported, so I reflashed it via ADB, and got everything working.
What we'll need to flash persist partition:
1. Mi A2 with unlocked bootloader and critical partitions, on stock Pie 10.0.2.0 to 10.0.7.0, connected to an USB 2.0 port in PC MB; USB debugging and MTP file transfer enabled;
2. Working copy of ADB / Fastboot installation
3. image of persist partition, can be found in each stock fastboot image
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
4. twrp-3.3.1-5-jasmine_sprout-unofficial.img, copied to ADB / Fastboot installation directory
https://forum.xda-developers.com/mi-a2/development/recovery-mi-a2-jasminesprout-t3941096
Note: even if TWRP boots with black screen, this method should work as we'll not control process on Mi A2, instead we'll use ADB commandsthis TWRP is reported to work with all variants of MiA2 screen panels.
5. Attached command file "flash_persist.cmd", unZIPped to ADB / Fastboot installation directory.
Instruction:
Run "flash_persist.cmd" from CMD shell or Explorer (probably admin rights needed?).
Command file execution will be paused several times, waiting for ADB and fastboot commands execution.
Please read CMD window output, check that phone is being switched to needed mode and/or ADB/Fastboot commands succeed.
In case something goes wrong, press Ctrl^C and terminate batch job.
After 1st reboot from TWRP, reboot once more by standard means.
Update:
- attached f"lash_persist_V2.zip" using "twrp-3.3.1-5-jasmine_sprout-unofficial"

my mi a2 is in ARB4, I can only use MIUI, could you tell me how do I get the persist file, could also explain where TWRP comes in since the command is made by ADB?

Aerobatic said:
At some moment when playing with Magisk modules, I've got Android crash, after which sensors (Accelerometer, Gravity, etc.) and Camera stopped working.
Obviously, somehow persist partition data got corrupted and must be reflashed. I believe, that flashing persist via fastboot is not supported, so I reflashed it via ADB, and got everything working.
What we'll need to flash persist partition:
1. Mi A2 with unlocked bootloader and critical partitions, on stock Pie 10.0.2.0 to 10.0.7.0, connected to an USB 2.0 port in PC MB; USB debugging and MTP file transfer enabled;
2. Working copy of ADB / Fastboot installation
3. image of persist partition, can be found in stock fastboot image
http://en.miui.com/download-353.html
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
4. twrp-3.2.3-0-jasmine_sprout.img, copied to ADB / Fastboot installation directory
https://dl.twrp.me/jasmine_sprout/
Note: even if TWRP boots with black screen, this method should work as we'll not control process on Mi A2, instead we'll use ADB commands.
5. Attached command file "flash_persist.cmd", unZIPped to ADB / Fastboot installation directory.
Instruction:
Run "flash_persist.cmd" from CMD shell or Explorer (probably admin rights needed?).
Command file execution will be paused several times, waiting for ADB and fastboot commands execution.
In case something goes wrong, press Ctrl^C and terminate batch job.
After 1st reboot from TWRP, reboot once more by standard means.
Click to expand...
Click to collapse
I don't understand either why is twrp involved. I'm at stock 10.0.12 ROM, with unlocked bootloader and usb depuration turned on. Should I get the persist.img from the Fastboot image of 10.0.12? I only see the link to an unofficial one which I don't know in which way is different to the official one...

marcushg said:
I don't understand either why is twrp involved..
Click to expand...
Click to collapse
ADB.exe is sending requests to phone. Usual ROM cannot evaluate these requests, while TWRP is specially developed to perform actions specified by ADB requests.

Thanks for the reply. Now what I'm not sure is if flashing persist.img will delete my original IMEI and Bluetooth and WiFi Mac address. I don't want to lose them.

[/COLOR]
marcushg said:
Thanks for the reply. Now what I'm not sure is if flashing persist.img will delete my original IMEI and Bluetooth and WiFi Mac address. I don't want to lose them.
Click to expand...
Click to collapse
This happens to me, camera and sensors are not working. the solution for this is to flash persist.img from original and official rom. you can get that on miui official website. there you can get the persist.img and flash it on TWRP in Mi6X version not the jasmin_sprout. I have try and tested and sensors and camera on my Mi A2 is working now. Blaming myself by deleting the persist! and persist_back up at the twrp. Not to worry by lost imei and etc. mine is all working fine.

how can i do this on android 10? I say that because twrp is not available for android 10. I have problem with frond camera. it return at secondary back camera. please help me

tnt-4- said:
how can i do this on android 10? I say that because twrp is not available for android 10. I have problem with frond camera. it return at secondary back camera. please help me
Click to expand...
Click to collapse
TWRP_4pda_verison works for me in 9 and 10 stock crypted. See link in item 4 of OP instruction.

Aerobatic said:
TWRP_4pda_verison works for me in 9 and 10 stock crypted. See link in item 4 of OP instruction.
Click to expand...
Click to collapse
sorry i am noob. please give me the link

tnt-4- said:
sorry i am noob. please give me the link
Click to expand...
Click to collapse
'OP' in these forums is mostly used in 2 meanings:
- 'OP' refers to the person who Originally Posted this thread;
- 'OP' refers to the Opening Post in this thread.
So, " See link in item 4 of OP instruction" means:
- scroll page up to the beginning (or go to the beginning of 1st page of a thread, here we still have 1 page);
- then read it carefully;
- find item 4:
4. twrp-3.3.1-5-jasmine_sprout-unofficial.img, copied to ADB / Fastboot installation directory
https://forum.xda-developers.com/mi-...prout-t3941096
Click to expand...
Click to collapse
Do I need to go through alphabet or google search course also? no offence, cheer up!

Aerobatic said:
'OP' in these forums is mostly used in 2 meanings:
- 'OP' refers to the person who Originally Posted this thread;
- 'OP' refers to the Opening Post in this thread.
So, " See link in item 4 of OP instruction" means:
- scroll page up to the beginning (or go to the beginning of 1st page of a thread, here we still have 1 page);
- then read it carefully;
- find item 4:
Do I need to go through alphabet or google search course also? no offence, cheer up!
Click to expand...
Click to collapse
thanks for all. i will try to do it beacause the front camera is very usefull.

Persist.img flash via flashed_persist.cmd or flash with twrp??

tnt-4- said:
Persist.img flash via flashed_persist.cmd or flash with twrp??
Click to expand...
Click to collapse
Read OP carefully and try to Google about ADB, TWRP, etc. to understand the process. Why should we do your homework instead of you?
In brief, again and again:
1. TWRP is needed to be booted into phone, as it is the only valid means to perform ADB requests from PC.
2. TWRP has no options to reflash /persist partition from its UI
3. /persist partition image is flashed into phone from PC using ADB commands, so:
3.1. PC is to be prepared (drivers installed, latest platform-tools with ADB unpacked and tested to work, persist.img unpacked and copied into platform-tools directory)
3.2. phone is to be prepared (successfully connected via USB and then booted into TWRP with command from "flash_persist.cmd").
4. "flash_persist.cmd" is just Windows::CMD command file, helping to make ADB / fastboot / ADB requests from PC to phone/TWRP in correct order, and with intermediate checks of successful connection / mode switching: rebooting into bootloader (ADB command), booting into TWRP (fastboot command), and then reflashing /persist (ADB command)
You can read it, e.g. in Notepad, and try to understand what it should make, Googling for Windows::CMD commands and ADB commands descriptions.

Aerobatic said:
Read OP carefully and try to Google about ADB, TWRP, etc. to understand the process. Why should we do your homework instead of you?
In brief, again and again:
1. TWRP is needed to be booted into phone, as it is the only valid means to perform ADB requests from PC.
2. TWRP has no options to reflash /persist partition from its UI
3. /persist partition image is flashed into phone from PC using ADB commands, so:
3.1. PC is to be prepared (drivers installed, latest platform-tools with ADB unpacked and tested to work, persist.img unpacked and copied into platform-tools directory)
3.2. phone is to be prepared (successfully connected via USB and then booted into TWRP with command from "flash_persist.cmd").
4. "flash_persist.cmd" is just Windows::CMD command file, helping to make ADB / fastboot / ADB requests from PC to phone/TWRP in correct order, and with intermediate checks of successful connection / mode switching: rebooting into bootloader (ADB command), booting into TWRP (fastboot command), and then reflashing /persist (ADB command)
You can read it, e.g. in Notepad, and try to understand what it should make, Googling for Windows::CMD commands and ADB commands descriptions.
Click to expand...
Click to collapse
I understand that. I have unlock bootloader and criticals. Then i need run twrp.img on cmd to boot twrp. Then?? Sorry for my questions i am afraid for my phone. I dont want to destroy it with any fault step

tnt-4- said:
I understand that. I have unlock bootloader and criticals. Then i need run twrp.img on cmd to boot twrp. Then?? Sorry for my questions i am afraid for my phone. I dont want to destroy it with any fault step
Click to expand...
Click to collapse
Then read everything I wrote and understand what you are going to do.
Again: read text in "flash_persist.cmd" and make sure you understand each line in it.
At this I stop helping you, I'm to make my work, I'm really busy.

Aerobatic said:
Then read everything I wrote and understand what you are going to do.
Again: read text in "flash_persist.cmd" and make sure you understand each line in it.
At this I stop helping you, I'm to make my work, I'm really busy.
Click to expand...
Click to collapse
i've done it but my front camera still not working. when return it returned at secondary. :crying:
Then i disassembly my phone and disconnect my camera. I open my phone again and did the same thing. Finally i reconnect the camera and it works!! Thanks fo all Aerobatic

Would this work on a V11.0.6.0.QDIMIXM?
Also, where can I find the persist files for it?

valp88 said:
Would this work on a V11.0.6.0.QDIMIXM? Also, where can I find the persist files for it?
Click to expand...
Click to collapse
Yes, it should, if this is really /persist corruption issue, and not HW problem. Diagnostics can be made running tests in engineering mode or with 3rd-party apps like AIDA64: if most or at least several sensors are misbehaving or disfunctional, this is the direct prompt to reflash /persist.
As for your question, It is always recommended to read the OP:
Aerobatic said:
3. image of persist partition, can be found in each stock fastboot image
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
Click to expand...
Click to collapse
Latest variant of persist.img for A10 can be found in unofficial repack of 11.0.8.0 OTA, link was published in https://forum.xda-developers.com/showpost.php?p=82370929&postcount=42.
Funny fact, but someone wrote in these forums that he solved his problem with corrupted /persist (being on Pie?) using image from the 1st official fastboot image for Oreo (V9.6.9.0.ODIMIFE, link in the thread pointed to in OP and above.)

Will it work with WIfi problems in MIUI for Mi A2
I'm using Custom Rom named as Derpfest and i had also flashed MIUI 11 but my wifi doesn't works in MIUI while it works perfectly for Derpfest.

steps please?
tnt-4- said:
i've done it but my front camera still not working. when return it returned at secondary. :crying:
Then i disassembly my phone and disconnect my camera. I open my phone again and did the same thing. Finally i reconnect the camera and it works!! Thanks fo all Aerobatic
Click to expand...
Click to collapse
Can you describes the steps... yo disassembly and disconnect the camera module, and then? you power it on?

My moto g5 plus is bricked and is stuck at fastboot mode

I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....

Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You need to install fastboot in pc and then flash the device to make it work.
You can prefer this thread
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633

Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.

debdeep98 said:
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
Click to expand...
Click to collapse
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.

Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
K.. install adb(https://www.androidfilehost.com/?fid=745425885120698566 ). If you had installed moto assistant then you'll have the drivers. If not then google motorola drivers and install them(http://www.motorola.com/getmdmwin ).
Once it's done. Open the folder where adb is installed.
Hold shift and right click>open command promt here.
At this point boot into the bootloader on your phone (fastboot mode).
On cmd type fastboot devices.
If your device is detected then it will show on screen.
If you get to this part.
Start flashing thru fastboot.
Get the files from google( or https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL)
Instructions to flash are in xda.
If you get failed to flash: security version downgrade then you're probably flashing an older firmware. Download the latest.
If you get failed to flash: preflash validation failed then there's not much you can do. Or atleast i don't know a solution to that.

its not detecting my device
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem

Anubhav074 said:
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Click to expand...
Click to collapse
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.

riyan65 said:
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
Click to expand...
Click to collapse
yeah i tried that but when it is not verifying my phone when i select id (which is xt 1686) it says that phone can not be verified try again.i have tried every given id but it is refusing to accept my device.

Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
Here's a guide to flash stock firmware.
Try the linked Mini ADB & Fastboot, if your device isn't recognised try to connect it to another usb port or use another usb cable.
Are you sure that you're in fastboot mode when you type the commands?
Read the guide carefully.
You need:
Latest signed stock firmware:
Europe (RETEU):
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
India (RETIN):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flashallO.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
Mini ADB & Fastboot
https://drive.google.com/file/d/1lLYfimKN1U5CJ9cfpTCkhtMiuG8EfXBZ/view?usp=sharing
1) Download the 8.1.0_OPS28.85-17-6-2 Indian firmware (it's the last one for the Moto G5+ (potter).
2) Install Mini ADB & Fastboot (best place is the root directory of C:/ or how the partition/hard drive is named where your OS resists), not in program files or another folder.
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
NOTE: If the command window appears for a brief moment then disappears, device drivers may not be installed. Ask again then.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
Sent from my Moto G5 Plus using XDA Labs

Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help

Anubhav074 said:
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Click to expand...
Click to collapse
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log , you can do that in TWRP->advanced->copy log, if TWRP is installed.
Try to flash the firmware and immediately after that grab a log and attach it here.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log, you can do that in TWRP->advanced->copy log, it will be stored in your internal storage.
Try to flash the firmware and immediately after that grab the log (with TWRP file manager) and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.

Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.

Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
debdeep98 said:
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Click to expand...
Click to collapse
That´s what I´ve said. If you would have TWRP you would be able to send a recovery.log but all you want to do is to flash a signed fastboot firmware. That´s possible without TWRP or unlocked bootloader, just by fastboot. Unzip the indian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
into your Mini ADB & Fastboot folder, place the flashallO.bat there too and double-click it, everything in fastboot mode as described before.
What happens when you do that? Are the commands executed in the command window of your Windows PC?
Can you make a screenshot of it? The guide I posted has everything you need in it, you have to tell me what happens when you try to flash the unzipped firmware.
Just to be clear, the firmware and everything has to be on your PC, not your moble device!

i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
View attachment batch.txt

Anubhav074 said:
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
Click to expand...
Click to collapse
Ok, that doesn't look to good.
The whole process is failing right at the start when the device is trying to build the partition table.
Have you tried different USB cables and ports?
Imo there are only two possible solutions:
Your device isn't working with fastboot correctly or its a hardware failure, the eMMC (the internal SD) may be corrupted. As your device is locked and hasn't been modded in any way this is the most plausible scenario also because it crashed out of the blue.
The only thing you can try yet is to use a different ADB and Fastboot tool, this one for example:
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
If all that changing of ports, cables and tools doesn't help you have to bring your device to a service center, they will most probably change the motherboard which isn't a cheap repair so if your device isn't under guarantee anymore you have to consider it it's worth the money.
Good luck!
Sent from my Moto G5 Plus using XDA Labs

So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center

Anubhav074 said:
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Click to expand...
Click to collapse
I think you've done everything that's possible.
The device wasn't rooted,modded,unlocked or something.
It showed the failure out of the blue.
You tried different fastboot tools, cables, ports and the correct firmware.
I asked someone with more knowledge about your log and the whole case and he is thinking the same as I do.
So the chance for a software problem is really small. I told you everything I know, maybe a service center has more options for software checks but as far as I know they use the good old Lenovo Motorola Software Assistant.
So I would recommend to go there and ask (before they do anything) what you have to pay if your eMMC is broken. Here in Germany they always change the whole motherboard, the costs are about the half of the price you paid for the device here.
If your still under guarantee it's a different story.
I'm sorry, I told you everything I know and I flashed my Moto G5+ several times.
My opinion is that the device has a hardware failure and visiting the service center is the only thing you could do now.
I really would like to give you better news.
Sent from my Moto G5 Plus using XDA Labs

Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks

phone crazy said:
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
Click to expand...
Click to collapse
Read this thread. You can flash signed Motorola firmware like discribed. If you don't want to lose your data you can try to omit the "erase user data" command. Just delete it out of the flashallO.bat.
https://forum.xda-developers.com/g5...ked-stuck-fastboot-mode-t3996599/post80792213
Sent from my Moto G5 Plus using XDA Labs

PLZ help me out TWRP install issues

im a XDA pleb im sorry but before i junk my ph-1 which i love to death i want to flash it to something spicy, i got the bootloader unlocked started to get twrp going then thats where it all went bad. 1. im feb 2020 update latest 2. fastboot is kinda working, i see my phone flash the img to slot a not slot b which im on and well says either file size too large or another error i can pull it all up. one error i got through my attempts i seen my bootloader was out of date update for a/b ? but some direction would BE MUCH appreciated !?!? also maybe a suggestion on a rom thats works best thats de-googled?

im even willing to pay a little bit to help me over discord or something, really would like to de-google my ph-1 hit things past my knowledge

TDIfrogman said:
im even willing to pay a little bit to help me over discord or something, really would like to de-google my ph-1 hit things past my knowledge
Click to expand...
Click to collapse
If you like the rom without Google, then there're only two right now far I know: LineageOS and crDroid
To install LineageOS, you don't need TWRP, because LineageOS has its own recovery image, you must follow exactly their instruction for installation.
Here's the link for LineageOS: https://download.lineageos.org/mata
To install crDroid, you need TWRP, at first, you must go back to Jan stock since Feb stock rom has issue with using TWRP.
Also, you need special TWRP image patched that gives you touch otherwise you need USB dongle with mouse to use TWRP. I can give you that TWRP if you need.
Here's the link for crDroid: https://forum.xda-developers.com/t/...microg-volte-wireguard-crdroid-v6-13.4129739/
Good luck!

TDIfrogman said:
im a XDA pleb im sorry but before i junk my ph-1 which i love to death i want to flash it to something spicy, i got the bootloader unlocked started to get twrp going then thats where it all went bad. 1. im feb 2020 update latest 2. fastboot is kinda working, i see my phone flash the img to slot a not slot b which im on and well says either file size too large or another error i can pull it all up. one error i got through my attempts i seen my bootloader was out of date update for a/b ? but some direction would BE MUCH appreciated !?!? also maybe a suggestion on a rom thats works best thats de-googled?
Click to expand...
Click to collapse
You can download that special TWRP image from Telegram channel
Essential Nostalgia Chat
and memes.
t.me

chanh2018 said:
If you like the rom without Google, then there're only two right now far I know: LineageOS and crDroid
To install LineageOS, you don't need TWRP, because LineageOS has its own recovery image, you must follow exactly their instruction for installation.
Here's the link for LineageOS: https://download.lineageos.org/mata
To install crDroid, you need TWRP, at first, you must go back to Jan stock since Feb stock rom has issue with using TWRP.
Also, you need special TWRP image patched that gives you touch otherwise you need USB dongle with mouse to use TWRP. I can give you that TWRP if you need.
Here's the link for crDroid: https://forum.xda-developers.com/t/...microg-volte-wireguard-crdroid-v6-13.4129739/
Good luck!
Click to expand...
Click to collapse
this is what i get after trying to flash recovery
target didn't report max-download-size
sending 'boot' (25741 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s

TDIfrogman said:
this is what i get after trying to flash recovery
target didn't report max-download-size
sending 'boot' (25741 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Click to expand...
Click to collapse
What rom did you try to flash?

chanh2018 said:
What rom did you try to flash?
Click to expand...
Click to collapse
the one on there site you linked , also tried sideloading the .zip and got Signature verification failed , no where to click continue just failed with error 21

TDIfrogman said:
the one on there site you linked , also tried sideloading the .zip and got Signature verification failed , no where to click continue just failed with error 21
Click to expand...
Click to collapse
Ok, here's the steps that I do to install custom rom (not LineageOS):
1. Make sure Essential driver is installed in computer
2. Make sure to use the latest adb package from Essential (or from Android)
3. Make sure your phone is unlocked boot loader
4. Make sure your phone is in Jan stock rom
5. Make sure to turn off finger print log in and password
6. Copy TWRP installer .zip and Rom to phone
7. Boot phone to boot loader and flash boottwrp.img
8. In TWRP, in Wipe, in Advanced Wipe, select Dalvik/ ART Cache, System, Data (DO NOT select Internal Storage), and Swipe to Wipe
9. Now still in TWRP, in Install, install ROM (first), after ROM installation is done, do not reboot, install TWRP installer .zip
10. Reboot phone.
11. DONE

that's the thing i have Feb 2020 on it, how do i go back now ?

TDIfrogman said:
that's the thing i have Feb 2020 on it, how do i go back now ?
Click to expand...
Click to collapse
Download original Jan stock rom
- Unzip it to your computer
- Put phone in boot loader
- From command prompt, goto unzip folder and run flashall.bat
- Sit back and let the batch file running installation process
- When it's done, just reboot, and you'll be back to Jan stock

chanh2018 said:
Download original Jan stock rom
- Unzip it to your computer
- Put phone in boot loader
- From command prompt, goto unzip folder and run flashall.bat
- Sit back and let the batch file running installation process
- When it's done, just reboot, and you'll be back to Jan stock
Click to expand...
Click to collapse
ok so it hangs on first command might be my cable ? im gonna run and go grab a better one and try that switching ports too

TDIfrogman said:
ok so it hangs on first command might be my cable ? im gonna run and go grab a better one and try that switching ports too
Click to expand...
Click to collapse
Make sure your path of adb is working, or quick solution is to copy these 4 files into your unzip folder and run flashall.bat
You can find these 4 files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe

chanh2018 said:
Make sure your path of adb is working, or quick solution is to copy these 4 files into your unzip folder and run flashall.bat
You can find these 4 files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Click to expand...
Click to collapse
i couldnt find a single cable in town, its not the best cable either no damage just kinda cheap i left my anker at my friends house
im pretty sure my path is ok using the essential drivers and adb/fastboot "platform-tools_r30.0.5-windows" i tried moving those files over same thing hangs at
fastboot flash nvdef_a nvdef
Sending 'nvdef_a' (310 KB)
but i can see it with fastboot devices

TDIfrogman said:
i couldnt find a single cable in town, its not the best cable either no damage just kinda cheap i left my anker at my friends house
im pretty sure my path is ok using the essential drivers and adb/fastboot "platform-tools_r30.0.5-windows" i tried moving those files over same thing hangs at
fastboot flash nvdef_a nvdef
Sending 'nvdef_a' (310 KB)
but i can see it with fastboot devices
Click to expand...
Click to collapse
Did you enable USB debugging in Developer options?

chanh2018 said:
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
yes dev options on , usb debug on

- Un plug USB cable from phone
- Goto Setting - About phone - Build number, tap on Build number (don't remember how many, maybe 5 or 7 times) until Developer Options is enable
- Goto System - Developer Options and turn on Android debugging (or USB debugging...I forgot)
- Connect USB cable back to phone, you will see a message popup asking to allow, enable it.
- Now from command prompt, in that unzip folder (assume you already have those 4 files copied), type: adb reboot bootloader
- Let see if your phone can goto bootloader
- If it does, continue to issue command flashall

TDIfrogman said:
yes dev options on , usb debug on
Click to expand...
Click to collapse
Ok, I'm not sure it's the cable or the adb path.
If you're positive about adb path, then your cable is bad.
You can try another version of adb (version 1.4.3)
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com

chanh2018 said:
Ok, I'm not sure it's the cable or the adb path.
If you're positive about adb path, then your cable is bad.
You can try another version of adb (version 1.4.3)
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Click to expand...
Click to collapse
i just uninstalled the essential driver/adb , using the universal everything now and i get this
fastboot flash nvdef_a nvdef
fastboot: error: cannot load 'nvdef': No such file or directory and more , but my phone reboots seems to be adb/driver issue

tried the auto install now it doesnt see my phone at all, found this user same issue but i cant follow what he did to fix it
https://www.reddit.com/r/essential/comments/8vi0nt

TDIfrogman said:
i just uninstalled the essential driver/adb , using the universal everything now and i get this
fastboot flash nvdef_a nvdef
fastboot: error: cannot load 'nvdef': No such file or directory and more , but my phone reboots seems to be adb/driver issue
Click to expand...
Click to collapse
Did you copy those 4 files to unzip rom folder?
If you did, then you can run fastboot or adb within that folder.