Related
I use a Moto G4 Plus and probably a lot of you hate that unlocked boot loader message or your boot logo is white and your boot animation is black. I'm here to solve that. I have created this boot logo for myself but I'll share it anyway! If you want to see the boot logo just check the attached files! This also hides the n/a message!
ONLY FOR MOTO G4 AND G4 PLUS
Download: https://www.dropbox.com/s/9q7zuij4kc0yfmn/logo.bin?raw=1
HOW TO USE
- First, you need to have ADB and fastboot working correctly and have an unlocked bootloader plus the Motorola drivers.
- Move your logo.bin file into fastboot folder.
- Next, you need to open a command prompt or terminal window open in your folder with your fastboot files.
- Reboot your phone into bootloader mode. (Turn off then hold power button and volume down)
- Connect your phone to your computer.
- In the command prompt or terminal type "fastboot flash logo logo.bin"
- After that's finished then type "fastboot reboot"
Horray! Your logo.bin was flashed!
*Apparently someone else already made something like what I made. Credit to them but I had no idea that it existed though. I based this off of the droid boot logo and didn't intend to steal their work.
https://forum.xda-developers.com/moto-g4-plus/themes/bootlogo-white-moto-logo-black-t3542399
Just throwing this in here because the font sticks to the normal android bootlogo style.
negusp said:
https://forum.xda-developers.com/moto-g4-plus/themes/bootlogo-white-moto-logo-black-t3542399
Just throwing this in here because the font sticks to the normal android bootlogo style.
Click to expand...
Click to collapse
The font I used is the new Android logo, not the old one like that one
Does this work in nougat? NPJS25.93-14-10 EU retail
sandravictoria said:
Does this work in nougat? NPJS25.93-14-10 EU retail
Click to expand...
Click to collapse
Yes
Can someone please make a TWRP flashable zip bootlogo version of my new designed Motorola g4 plus 2019 bootlogo
https://drive.google.com/file/d/14yRSvlg0C0Bhn2S5unfJeBFklP6UlskS/view?usp=drivesdk
Long story short, I attempted to flash the first 9.0.0 factory image and now my phone is seemingly bricked. I keep getting errors that say that fastboot can't detect the current slot. When I try to manually select the slot with --set-active=a/b it returns with my device doesn't support slots. If I try to flash anything individually like the bootloader/radio cmd/powershell just sits there with the "_" underscore blinking for all eternity. TWRP is already flashed and when I try to boot to it it sits on the splash screen indefinitely. I can't fastboot boot TWRP either because I can't flash anything. Deuce's script did the same thing. I tried 3 different cables and am using a brand new computer and latest Platform Tools.
Should I contact google for a warranty replacement? I don't have the order # but that should be irrelevant I think since this phone is still under a year old.
Any ideas????
GohanBurner said:
Long story short, I attempted to flash the first 9.0.0 factory image and now my phone is seemingly bricked. I keep getting errors that say that fastboot can't detect the current slot. When I try to manually select the slot with --set-active=a/b it returns with my device doesn't support slots. If I try to flash anything individually like the bootloader/radio cmd/powershell just sits there with the "_" underscore blinking for all eternity. TWRP is already flashed and when I try to boot to it it sits on the splash screen indefinitely. I can't fastboot boot TWRP either because I can't flash anything. Deuce's script did the same thing. I tried 3 different cables and am using a brand new computer and latest Platform Tools.
Should I contact google for a warranty replacement? I don't have the order # but that should be irrelevant I think since this phone is still under a year old.
Any ideas????
Click to expand...
Click to collapse
You're posting in the original 2016 Pixel XL forum. Hopefully you didn't try to flash firmware from this device to your device.
Try running the flash-all.bat file from the correct firmware package.
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy A20 crap.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. I also don't know if this will work on other variants, as I only have these for MetroPCS, and from my understanding this will NOT obviously work for Verizon, AT&T, and Cricket phones.
I want to thank @diversenerd, and @jhjhjhjhjhjh for their hard work tinkering with the phone as I tried to figure it all out from their notes and instructions. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this, as the information wasn't quite clear in some places and I got some bootloops.
Introduction/Preparation
First, go and prepare by READING EVERYTHING IN THIS FORUM. Very important. Don't even jump into this without reading this thread here all the way to the last page: https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857 (this is so you know start to finish what worked for some might not work for this variant).
Second, unlock the bootloader. The MetroPCS variant can be unlocked by Motorola; follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). I did it in Firefox this go round and it sent the codes immediately . When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
***NOTES SO YOU DON'T FREAK OUT***
1. Every time you power up the phone after you unlock the bootloader Moto will try and make you feel like crap with a bad key error in the middle of a nice message that your phone is not to be trusted. :laugh: This is normal. Give it a minute, you havent broke it.
2. There is no custom recovery/TWRP for this variant, so read carefully so you don't delete something you might not be able to flash back later.
3. OEM Unlocking toggle switch is interesting. On my first phone it was activated once the bootloader is unlocked and greyed out to where it couldn't be accessed anymore; On the significant other's phone it is still accessible and can be toggled even with the bootloader unlocked.
Files
There is confusion in some of the threads about leaving the Sim Card/SD Card in while flashing. Yes, pull it out and flash without it. Flashing with the sim card/SD card in can cause problems flashing. I did my first phone without it, but forgot to take it out with my second and had to start from scratch. Avoid that step.
1. Get Minimal ADB and Fastboot (it's easier to use than Android SDK and smaller).
2. Download the Motorola Drivers from their site (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (This is a good thing to have to know your hardware responsibly).
4. Stock Firmware. I used XT1955-5_OCEAN_RETUS_9.0_PPO29.114-63-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml which is the US Retail software instead of MetroPCS's firmware because of the issues I was having with it straight out the box. Both of my phones flashed fine with it and you can find it here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ I used the 2nd one with success - the first one doesn't play nice with Magisk.
5. MagiskManager-v7.3.2 apk.
6.The Boot .img separately extracted from the Firmware listed in Step 4.
7. Root Checker.apk
8. Patience (and a good movie keeping you going).
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card and SD card is REMOVED from the phone. Again, this is to prevent problems in the flashing.
3. Make sure your wifi is OFF. Every time you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and immediately pushes updates galore.
4. Make sure you save Magisk and the Boot .img to your phone directly. Using the Download folder is a great place and easily accessible in Magisk. You will not be able to add files once in fastboot).
5. Make sure your developer options are activated.
6. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
7. Make sure to check CPU-Z for your hardware specs and to make sure you're avoiding potential problems.
8. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device). Once you flash, you have to constantly check USB to Transfer because it will not do it.
9. Make sure you have the STOCK CABLE that comes with the phone. This model is funky about using other cables.
10. Make sure you set your display to time out to ten minutes. If the phone screen goes to sleep mode, it may interfere with flashing.
Rooting
Here is the fun part. Please keep in mind you may get a bootloop. I did on both phones on the first try with two different methods. I was on the infamous March 1 2019 security update and still got a bootloop from the patching. The second phone I just flashed ahead of time to the new firmware and still got a bootloop until I flashed again. Expect it.
1. Go into your developer options and DISABLE Automatic Updates. This is important for later on.
2. With the phone on, install Magisk. Make sure you use the version 7.3.2 or update to it since it's the latest version at the time of this guide.
3. Say yes when your phone asks whether or not you want to install things from unknown sources. It will grant access for this application only.
4. Open Magisk Manager and turn on your Wifi. If you don't Magisk will hang at checking updates. If necessary, force close Magisk and open it up again with Wifi on. It should bring you to One Green Check Mark that Magisk Manager is Up To Date, and One Red Mark above it that says Magisk isn't installed.
5. Click install on that tab ONLY (there is no need to click install by the Green Check Mark one). Magisk will then ask you "Do You Want To Install Magisk v19.3(193000) now? and click Install again.
6. Under Select Method, navigate to the folder on the phone where you saved your boot.img file (or whatever you named it). Once you select it you will be taken to a screen where the letters are funky looking but spell FLASHING at the top. Once it patches your file, it will tell you when it's done. Should it hang or you get errors, you WILL HAVE TO REFLASH THE FIRMWARE AND START OVER.
7. When the screen tells you it's all done, plug your phone up to the computer and drag the patched img file (it should by default say magisk_patched.img) and put it in the folder with Minimal ADB and Fastboot.
8. Turn the phone completely OFF.
9. Plug your phone via USB cable into the computer.
10. Press Volume Down and Power to boot into fastboot mode.
11. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory or it won't work.
12. Type "fastboot flash boot thenameofyourrecoveryfile.img" and hit enter.
If all goes well it should flash to "a" partition, and you should see in the command prompt "image signed with key bad key" before it says done. If it doesn't take do not re-flash as it will flash to "b" partition which will definitely bootloop and ensure you have to reflash the firmware.
13. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
14. Wait for the bad key/device cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
15. Open Magisk Manager. The icons should be in green, letting you know you have root. Follow @diversenerd advice and Click Tap To Start SafetyNet Check. Make sure your Wifi is on for that check. This apparently tests to see if it can deceive Google checks and possibly install OTA (can't say I did all that, not a update junkie).
16. Install Root Checker and confirm root.
17. Disable Updates. I know this is hard for some people, but you dont know if a forced OTA update will take root away, and leave us with no option to get it back or roll back to an earlier version of Pie.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. I have no idea why it doesn't work device to device, but it doesn't. And while I thank @jhjhjhjhjhjh for giving up his original files, it was incompatible with my phone (even though we are on the same variant) and bootlooped me.
2. You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. You will lose everything datawise flashing and playing with the boot.img. My phone reset itself tinkering with flashing, every time. Don't be alarmed if it takes you through a reset.
4. I wasn't able to confirm by going into updates (couldn't find the system settings) and verifying that nothing said anything about Device Integrity Compromised. I just assumed it.
5. Magisik is TEMPERAMENTAL. So if first you don't succeed, reflash the firmware and try again.
6. You cannot just go into the Stock Rom file and extract the boot.img file, put it in the Minimal ADB file folder and flash it if it bootloops. YOU MUST REFLASH ALL THE FIRMWARE OVER.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, here's what you're going to have to do. And don't worry - it won't relock the bootloader.
1. Make a duplicate folder of Minimal ADB & Fastboot that is clean (doesn't have any boot images or any added files in it).
2. Extract the firmware to the folder where Minimal ADB & Fastboot are at on your computer.
3. Turn the phone completely OFF and back ON if you haven't done so yet. Make sure there is no Sim Card of SD card in it.
4. Press Volume Down and Power to boot into fastboot mode.
5. Plug your phone via USB cable into the computer.
6. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure all your firmware files have been extracted in the Minimal ADB directory or it won't work.
7. Cut, Copy, and Paste in Fastboot All Together the following:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
8. When it is done it will stop on fastboot reboot. Hit enter and the phone will reboot.
9. Repeat all steps in the Pre-Rooting and Rooting section to obtain root.
Hope this helps my fellow MetroPCSers. I boot looped both of my phones this evening and brought them back with this method, and eventually achieved root on the 2nd tries, respectively. Old girl is working and I got Root Explorer and Titanium Backup going full stop. At least this root was easier than on my E4, lol.:laugh:
I will try and answer questions if I can or point you in the right direction.
I believe my boot img was flashed to "b" partition and everything is fine...
do you know a way to sim unlock it?
edwardxi said:
I believe my boot img was flashed to "b" partition and everything is fine...
do you know a way to sim unlock it?
Click to expand...
Click to collapse
Make sure it is okay, because when I flashed it the first time and it flashed to "a" and it bootlooped the Moto intro, I only flashed the boot image again and it flashed to "b" and hung at the "This Device Cannot Be Trusted/Bad Key" Screen.
I have no way to test sim unlock as MetroPCS locks their sims to the phone via IMEI and don't let you hotswap them, mostly to charge you 11 bucks reactivation fee. But in theory it should be sim unlocked by flashing to a different Carrier/Retail Rom, or at least that is how in the more budget line phones it worked.
Articul8Madness said:
Make sure it is okay, because when I flashed it the first time and it flashed to "a" and it bootlooped the Moto intro, I only flashed the boot image again and it flashed to "b" and hung at the "This Device Cannot Be Trusted/Bad Key" Screen.
I have no way to test sim unlock as MetroPCS locks their sims to the phone via IMEI and don't let you hotswap them, mostly to charge you 11 bucks reactivation fee. But in theory it should be sim unlocked by flashing to a different Carrier/Retail Rom, or at least that is how in the more budget line phones it worked.
Click to expand...
Click to collapse
I have been using it for couples of days, and definitely, everything is fine:laugh:
For metro, it's controlled by their Unlock app, you can't simply flash a different rom to unlock it... used to $10 on eBay, now $40... too expensive
edwardxi said:
I have been using it for couples of days, and definitely, everything is fine:laugh:
For metro, it's controlled by their Unlock app, you can't simply flash a different rom to unlock it... used to $10 on eBay, now $40... too expensive
Click to expand...
Click to collapse
Well, on My E4 I was able to unlock it by flashing Lineage Nougat. I could put any sim in it but Metro, because they lock by IMEI. Can't speak for this one, I just jumped back to Metro from Tmobile, who was HIDDEOUS.
Maybe you might get lucky and get some Moto support from Chimera. Then for 11 euro you could unlock it with their tool. But stay on their behinds and make sure its working first.
Articul8Madness said:
Well, on My E4 I was able to unlock it by flashing Lineage Nougat. I could put any sim in it but Metro, because they lock by IMEI. Can't speak for this one, I just jumped back to Metro from Tmobile, who was HIDDEOUS.
Maybe you might get lucky and get some Moto support from Chimera. Then for 11 euro you could unlock it with their tool. But stay on their behinds and make sure its working first.
Click to expand...
Click to collapse
yeah, can't agree more, they are terrible...
@Spaceminer. This is the post I'm talking about
If you want to get rid of the bad key message at boot, you can flash the logo.bin file from the link below with fastboot. Just place the downloaded logo.bin in the minimal adb and fastboot folder, open a cmd window and type fastboot flash logo logo.bin and press enter. Next boot you should have a plain white screen with a large black moto symbol instead.
https://forum.xda-developers.com/g7-power/themes/remove-bad-key-start-boot-t3947359
Going to root mumy G7 power from metroPCS. Can anyone confirm is there a way to SIM unlock after root?
aggresive said:
Going to root mumy G7 power from metroPCS. Can anyone confirm is there a way to SIM unlock after root?
Click to expand...
Click to collapse
There is no SIM unlock per se with MetroPCS. They tie their SIMS into the IMEI of the phone you're using. So you can't just take the sim out and put it in another phone easy peasy without going through them and paying them to do it.
However, if a custom rom comes out, which will happen once we get a TWRP, you'll be able to do that probably on Lineage. But until then, there will be no confirmation.
Beetle84 said:
If you want to get rid of the bad key message at boot, you can flash the logo.bin file from the link below with fastboot. Just place the downloaded logo.bin in the minimal adb and fastboot folder, open a cmd window and type fastboot flash logo logo.bin and press enter. Next boot you should have a plain white screen with a large black moto symbol instead.
https://forum.xda-developers.com/g7-power/themes/remove-bad-key-start-boot-t3947359
Click to expand...
Click to collapse
This is correct and I have contributed my custom made logo.bin image on said thread, even though you can still see bad key its cute, lol.
i got it all rooted but now it shows i have no imei and sim status not available any suggestions do i need to flash modem or radio
626jose said:
i got it all rooted but now it shows i have no imei and sim status not available any suggestions do i need to flash modem or radio
Click to expand...
Click to collapse
try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Thanks figured it out i used the 2nd download like the op said. I didnt check to see if it was the same version i was on so it bootlooped and i flashed the whole thing so i downloaded the original firmware reflashed it that didnt work so i let it update and it came back good as new. So for anyone else doing this make sure its the same version youre on i found it on a different site just google it
626jose said:
Thanks figured it out i used the 2nd download like the op said. I didnt check to see if it was the same version i was on so it bootlooped and i flashed the whole thing so i downloaded the original firmware reflashed it that didnt work so i let it update and it came back good as new. So for anyone else doing this make sure its the same version youre on i found it on a different site just google it
Click to expand...
Click to collapse
I used the RETUS version and didn't have that problem; are you sure you didn't accidentally click the wrong version and flashed that (like a CDMA version)? At any rate, glad you got it back. Interesting you updated....I NEVER EVER EVER EVER do that because updating can break root if the manufacturer patches it.
Also, make sure you are on the OS version March1st; I didn't update my phone and used that stock.
Articul8Madness said:
I used the RETUS version and didn't have that problem; are you sure you didn't accidentally click the wrong version and flashed that (like a CDMA version)? At any rate, glad you got it back. Interesting you updated....I NEVER EVER EVER EVER do that because updating can break root if the manufacturer patches it.
Also, make sure you are on the OS version March1st; I didn't update my phone and used that stock.
Click to expand...
Click to collapse
Yep made sure to follow everything word for word pretty sure thats why it bootloops the 1st time then after you flash the whole thing it works ive looked at them and the one that matches my firmware is the last 1 with the 2nd one i had 2 unlock apps one from metro and one from tmobile idk if thats your case or something didnt flash right or dirty flashed i was wondering also if that twrp river works has anyone tried it or is there twrp for this device and is there a way to rewrite the imei using adb or some other way
626jose said:
Yep made sure to follow everything word for word pretty sure thats why it bootloops the 1st time then after you flash the whole thing it works ive looked at them and the one that matches my firmware is the last 1 with the 2nd one i had 2 unlock apps one from metro and one from tmobile idk if thats your case or something didnt flash right or dirty flashed i was wondering also if that twrp river works has anyone tried it or is there twrp for this device and is there a way to rewrite the imei using adb or some other way
Click to expand...
Click to collapse
@Geofferey has created an unofficial TWRP here https://forum.xda-developers.com/g7-power/development/port-twrp-g7-power-t3963738
Warning: DO NOT USE RIVER twrp - Our device is Ocean and River will Bootloop and possibly brick it.
We can't rewrite the imei or any of that yet - we still are working on custom roms. I've been trying to make stock roms for our variant, but unlike the old Moto I had, the new android OS has new permissions and all that with Pie and it keeps messing up on the porting.
Well after installing adaway and it not working i tried uninstall phone froze so i turned it off by holding the power button now its stuck in a bootloop idk if it finally ran out of power everytime i shut it off it kept rebooting can i recover without reflashing everything or do i have to start from scratch tia for the help
626jose said:
Well after installing adaway and it not working i tried uninstall phone froze so i turned it off by holding the power button now its stuck in a bootloop idk if it finally ran out of power everytime i shut it off it kept rebooting can i recover without reflashing everything or do i have to start from scratch tia for the help
Click to expand...
Click to collapse
I've never had that problem before, so I'll give my suggestions.
1. Try a factory restore from the Fastboot Menu. That may set everything easy peasy BUT it will wipe the phone.
2. If #1 doesn't work, then see if you can just reflash the magisk patch. That may do it.
3. If #1 and #2 don't work, then yeah, back to the drawing board.
Adaway maybe messed with Magisk; did you set the proper permissions in Adaway to give it root access? Anybody else care to weight in?
I'm not able to upload Magisk or boot.img directly to moto g7 phone from computer through Windows. I can transfer both to SD card, but doesn't allow access directly to phone file directly. Yes, bootloader is unlocked.
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
renatogui said:
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I had frozen twrp screen before but usually managed to fix just by restarting the phone and using twrp offain in adb.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
Click to expand...
Click to collapse
1- Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2- Create a new folder on your C drive and name it: adb
3- Extract & place everything from the platform-tools into your adb folder
4- Download this: https://drive.google.com/open?id=1SKIlWS-y6kNI4YIE2Sj4_9CcRJ9W0xTh
5- Extract & place it to your adb folder
6- Reboot your phone to TWRP and wipe it, then reboot to bootloader
7- Connect your phone to your PC
8- Go into the daisy_global_images_V10.0.9.0.PDLMIXM_9.0 folder and run: flash_all.bat
A window will pop up and install the stock mi a2 lite rom. Let it finish then your phone boot up. You will have to update your phone since this stock rom that I linked is a pretty old one.
Someone had a similar question in another forum, so I just copy my answer from there. If you have adb already installed you can ignore the first 3 steps.
I had frozen twrp screen a couple of times but managed to fix it by restarting the phone and re-open the powershell window in adb. I use twrp-daisy-3.2.3-0-offain.img
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
I was thinking I did not try to install stock image using MiFlash tool. I can do it if I get a windows computer available.
I saw people suggesting fastboot oem edl but I could not find a clear explanation of the procedure.
I understood that I must use MiFlash in that case too but the steps are not clearly defined and I need a windows computer anyway.
Does someone have a step by step to use fastboot oem edl?
renatogui said:
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
Click to expand...
Click to collapse
No particular reason behind 10.0.9.0 ... I just had that uploaded to my drive and when I posted this to another forum I didn't wanted to "waste" time to search for a link so I just used mine. Anyways u have to wipe your phone before installing stock rom.
The way I fixed mine is not working for you so Im afraid Im out of ideas.
Hope someone can help you out with it
thanks, anyway for your kind and quick answer.
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue. When it comes to EDL flashing:
1 - Grab the 20160401 version of MiFlash from here : https://www.xiaomiflash.com/download/ (You need this version because it's the only MiFlash version that's capable of EDL flashing, mind you, you need a Windows PC and 64-bit hardware for this)
2 - Connect the phone in fastboot mode and type this command :
Code:
fastboot oem edl
Hit enter, this will take the phone into EDL mode, which means the screen will go black and the notification LED will start blinking.
3 - Now you're in EDL mode, open the MiFlash version I mentioned and Browse to find the location the stock ROM is stored, then hit refresh so that the software can recognize the phone.
4 - Hit flash to start flashing, but remember EDL flashing is a very fragile process, so make sure you don't lose power/shutdown the app while it's doing its job. After a successful flash, the app will say it is successful. Unplug the phone and start holding the power button to reboot. If you want to lock the bootloader, make sure to hold vol down as well and go into fastboot then re-lock the bootloader with :
Code:
fastboot oem lock
5 - Voila!
Thank you marstonpear for the detailed answer.
I will try MiFlash this evening and will post the result here.
I am very glad to count with more experienced people in fixing my errors.
Hello marstonpear,
I downloaded daisy image v10.0.13.0 that was suggested in XiomiFlash how to and try to flash it.
I got the error "mismatch image and device". This is very strange. Never had this before flashing with fastboot.
Do you think I could scrambled mi A2 lite so MiFlash cannot recognize it as a mi A2 lite anymore?
The only different think I did was interrupting my first flasing try using ^C when it was frozen.
I made 2 other tries after this with no errors. The only problem was the never ending boot.
My next try will be using image v10.0.18.0, the one I had installed before all this problems begin.
renatogui said:
Hello marstonpear,
Click to expand...
Click to collapse
marstonpear said:
I'd suggest giving MiFlash a try.
Click to expand...
Click to collapse
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
coolwei1 said:
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
Click to expand...
Click to collapse
I'm sorry. I tried hard how to quote and did'nt find.:cyclops:
I am almost learning...
marstonpear said:
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue.
Click to expand...
Click to collapse
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
renatogui said:
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
Click to expand...
Click to collapse
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
renatogui said:
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
Click to expand...
Click to collapse
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Now I know the reason of mismatching. All the scripts bundled with Xiaomi_Mi_A2_Lite_V10.0.13.0.PDIMIXM_20190807.0000.00_Global_9.0_XFT are made for jasmine. I will find another image more trustworthy than this one.
marstonpear said:
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
Click to expand...
Click to collapse
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
renatogui said:
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
Click to expand...
Click to collapse
for others having the same probem I've learn in another thread that this error is issued because I did not choose the lock option below right of MiFlash tool. That is why it didn't catch the lock checkpoint. But the end of the message is not true because at this checkpoint, the flashing is already done. I simply turn the phone off and on again and the boot was normal.
Thanks for all that help me specially marstonpear.
Thread closed... until next problem.
hey, i have a completely stock 9 pro, i was texting someone and sending them pictures from the night but while i was doing that the phone suddenly crashed to the lock screen over and over again. so i just hard rebooted it since it was completely unresponsive and just crashing on the lock screen and now it will not even boot up it just shows the oneplus log and a field to put in a password and after entering the password its looking to format the phone and probably factory reset the whole device i was hoping that there would be some way to use adb to get my photos back since i didnt get a chance to save or send them and it would be a real bummer if they were gone. not enough to pay 1000s of dollar but enough that i would spend time playing with adb to recover them. im very familiar with commandline and adb but i dont know of a way to get in without unlocking the bootloader first.... any help would be very much appreciated.
Can you manage to boot into fastboot and try some things there?
Setup platform tools (let me know if you do not have it setup) and then boot into fastboot. Connect your device to your computer and try out the following commands :
fastboot getvar current-slot
If this outputs something like :
current-slot: b
Then run the following command :
fastboot --set-active=a
otherwise, run the following command :
fastboot --set-active=b
After this is done, reboot your device by running :
fastboot reboot
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
I never set bios or lockscreen passwords, or encrypt data drives. You are the one most likely to be locked out, sometimes through no fault of your own. People will steal these devices regardless if they're locked or not; physical security is the only type of security that works.
wjcrabtree said:
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
Click to expand...
Click to collapse
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
ekin_strops said:
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
Click to expand...
Click to collapse
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
You can't do a factory reset from there?
It's rare but a SEU can corrupt any part of the flash memory. It causes no physical damage but the altered memory cells will need reset.
I think the best way to recover is MSM tool for youre specific model phone.
My phone power off by it self after watching a video on a received link with whatsapp.
Nothing workt beside MSM. I factory reset, downgrade rom. flash-reflash rom's.
MSM wipe all in youre phone.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Thank you so much!!
Sorry for the slow reply, but I haven't had time to deal with the problem because of work. I'll be looking into this today.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Ho Lee Sheet! I finally got around to dedicating serious time to working on this.
I had to jack-around with it quite a bit to get Windows 11 to load the proper drivers so that the phone would be recognized, but: BOOM! BACK IN BUSINESS!
Thank you so much for the guidance.