Related
Hey guys,
recently joined this place and its awesome. So many things you can learn...
Ok onto the issue - I was gifted a Micromax A092 a few days back. Qualcomm quad core processor, 1GB Ram, Jelly Bean 4.3.
Well after rooting it somehow (total nightmare - there are a couple of guys in another thread I have been posting in out here, who are still unsuccessfully trying to root theirs) and installing SuperSU and enabling USB debugging, I have hit a brick wall with fastboot mode. The Vol down + Power button combo gets me to the logo screen where it stays till I am forced to pull the battery out to reboot.
Phone does get detected under Device Manager while its stuck on the logo screen and I can install drivers to get it to show up as Android ADB Interface/Android ADB Composite Interface but fast boot refuses to detect it even though adb does when connected normally and executes all commands properly.
Well here's a list of things I have tried:
15 seconds ADB Installer - check
Minimal ADB and fastboot - check
Android SDK with google drivers and unnecessary packages - check
Universal naked drivers - check
Modding the inf files with my devices hardware id's - check
Pdanet+ driver installation method - check
Mobrobo/Mobogenie - check
Manual driver installation - check
Different USB cables - check
Few other random hacks - check
Later gave adb sideloading a shot hoping I could flash a custom recovery onto it via command prompt. No dice there either. Being unable to flash anything means I am still rocking "android system recovery 3e" as my recovery mode which in turn means the dreaded signature verification failed message trying to install 3rd party apps in recovery and sideload mode. I have also tried installing a couple of these custom recovery modes via .bat files but I guess its failing due to the same damn signature verification reason.
Now I know all phones don't ship with fastboot mode but given that this phone was released just a couple of months back and 2 year old inferior phones from Micromax have said feature gives me hope that maybe there indeed exists a way to flash it.
Also got this .dat file from somewhere for apparently flashing my phone with a stock ROM :
@ECHO off
adb reboot bootloader
echo for not erase modemst1 and modest2
rem fastboot flash partition gpt_both0.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash rpm rpm.mbn
fastboot flash sdi sdi.mbn
rem fastboot flash fsg fs_image.tar.gz.mbn.img
rem fastboot flash modemst1 dummy.bin
rem fastboot flash modemst2 dummy.bin
fastboot flash modem NON-HLOS.bin
echo for not erase bt and wifi information
rem fastboot flash persist persist.img
fastboot flash cache cache.img
fastboot flash usbmsc usbdisk.img
fastboot erase splash
fastboot flash splash splash.img
fastboot -S 256M flash system system.img
fastboot flash recovery recovery.img
fastboot -S 256M flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Seeing a lot of fastboot commands in there make me slightly optimistic if might have a fastboot mode after all?
So anyways what am I missing here? Or does the phone not have fastboot mode at all? Coupled with the fact that the asinine default recovery mode won't allow me to load custom apps via side load, what other options do I have? Is fastboot a prerequisite for flashing?
Really frustrated...a little help please guys...thanks.
PS: What is the difference between bootloader and fastboot mode? I can get my phone into bootloader mode via the necessary adb command but it's still stuck at the logo screen so don't know what to make of it.
Hello,
I have been updating my cyanogenmod 12s using the nightlies for a while now.
While I was updating with the update on the 18th, my phone got stuck at the 'upgrading apps' step and keeps repeating the upgrade for hours.
I accidentally then wiped the phone completely in TWRP while trying to restore the phone.
I lost the backups and OS. The warning saying 'No OS installed' shows up when I try rebooting.
My PC does not show the phone when I connect it via USB. I have nothing on TWRP to install either.
Can anyone please suggest how I should proceed?
Thank you,
Abhi2488
1. If you can boot into fastboot, just download stock CM11S fastboot package (you wont have trouble find it, just search forum) and simply flash it with fastboot, one by one partition.
I will just qoute some instructions from oneplus forum:
"Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help."
2. If you allready have custom recovery installed, you can try to flash any custom rom from OTG USB disc (you need OTG cable or OTG adapter and USB fat32 formatted disc where you will copy some custom firmware).
help me please my device is stuck on fastboot mode after i flashed magisk through twrp recovery
Realme has just release its flashtool to flash there ofp firmware through fastboot. Just try it. and post result.
Note: This require bootloader to unlock
Flashtool Link:
https://download.c.realme.com/flash/Flash_tool/realme_Flash_Tool.zip
Firmware Link:
https://combinefile.com/index.php?a=downloads&b=file&c=download&id=42977
i flash rmx and vbmeta. then my phone is restarting and restarting. how can i fix it?
fastboot boot loop
after i flash twrp and vbmeta. my realme 5 didnt stop restarting to fastboot. cant open my realme 5. someone can help me?
Please help us sir
Same problem system wipe ho gya mere se glti se fastboot loop restarting restarting
Same problem happening with my realme 5i device
anshkumar7651 said:
Same problem system wipe ho gya mere se glti se fastboot loop restarting restarting
Click to expand...
Click to collapse
My phone is bricked and it just opening in fastboot mode.I 've accidentally wiped everything.when ever I turn on my phone it just stuck on boot loader.when I flash custom it reboots to fastboot menu again.please help
ryaniceday said:
i flash rmx and vbmeta. then my phone is restarting and restarting. how can i fix it?
Click to expand...
Click to collapse
Did you find any solution ?
Prateekzxr said:
Did you find any solution ?
Click to expand...
Click to collapse
Yes I have Successfully cam out of fastboot loop
akashar.rai said:
Yes I have Successfully cam out of fastboot loop
Click to expand...
Click to collapse
So how did you get out of there
Rafet18 said:
So how did you get out of there
Click to expand...
Click to collapse
Bro ! In my case, first I have flashed vbmeta and then OrangeFox recovery. Than it get out from loop and booted to OrangeFox recovery and I successfully flashed the LOS ROM using Orangefox.
---------- Post added at 05:56 AM ---------- Previous post was at 05:10 AM ----------
HI, Do anyone knows How to use banking/payment apps (Google pay, Airtel pay UPI etc) on LOS 17.1. Do Magisk able to bybass Google safety net check as I read that google have made it Hardware based and It checked bootloader. Magisk now Unable to bypass it.
USER7812 said:
help me please my device is stuck on fastboot mode after i flashed magisk through twrp recovery
Click to expand...
Click to collapse
Hi, if your still trying to unlock your phone on lock mode somehow i manage to flash my phone with realme 5 rom by going to there website since im a new user i suggest going to google just type "realme rom" and find the website that says Software Update - realme (India) and click on it now you need to have installed twrp previously at least once i think use your volume key to access the title until it changes to "Restart to bootloader" then when it restart at soon it open hold volume down + and power button at the same time until TWRP loads if not try it again or find any other way to get to TWRP when you installed the .ozip you got from the link i gave you note please select and download the current version your phone has like realme 5 if your phone is realme 5 or realme 6 if your phone is realme 6 after you download it transfer the .ozip to your phone if you cant access the phone on your pc or laptop go to installation on your twrp select the rectangular bars i forgot there name but find the one where you can select which storage your twrp will use if you manage to transfer the .ozip file then please proceed to press it then flash it even tho it might take a while wait for it if it ask you to reboot then reboot it if the phones brings you back to twrp go and go press wipe and press format data type yes then slide the arrow bar and reboot your phone and you can know access the phone.
P.S.
Sorry for bad english and sorry if the post was to long i had to put every details so people like me who knows nothing about flashing, ROM, or just having multiple failed attempts of trying every corner of youtube and google to find the fix for it for me i spend half a day and a sleepless night trying to figure out to fix this and not to mention the multiple downloads and mini heart attack you get just to see if the file you download or the tutorial your watching will even work and if you manage to root your phone already i suggest going back to settings opening developer option again then turning off OEM because for me thats the main reason of the bootloop or getting your phone brick so please what ever you do turn off OEM before you restart your phone or the root file or app requires a reboot because once you restart your phone or if it shut downs theres a high chance your phone will go back to bootloop or brick again for my experience and sorry for the long P.S so again im sorry
P.S.S
I hope some expert tech guy can see this and find a better solution for realme phone risky flashig or bootloop and also brick i too.
P.S.S.S
nothing just wanted to say that
Congratulations Friends: I Have a Solution:
extract the download file (in down) and click the folder address bar and input (cmd) and hit enter.
come to the command center and copy the pest
1.
fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase metadata && fastboot erase vbmeta && fastboot erase system && fastboot erase vendor && fastboot erase userdata && fastboot reboot-bootloader
2.
fastboot flash recovery recovery.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader
*** After Using Upper Code then install the official flash file from Realme official website.
Download and Extract
https://drive.google.com/file/d/1VMAAZoioBN3YGlV6xqd43iXGmFiWVGg3/view?usp=sharing
Then go to recovery mode
then you can install UI/IOS RealMe Official Recovery
after installation don't restart just go back and wipe to formate then restart mobile
Select 1st one. just. don't select need English...
Thanks, Everyone Enjoy...
Contact:
AndroFixer
AndroFixer. 13 likes. All the assets you need, in one place: Logo, Business Card, Intro, Product Promo, Animated Logo Text,
www.facebook.com
nharafat said:
Congratulation Friends: I Have a Solution:
extract download file (in down) and click the folder address bar and input (cmd) and hit enter.
come to the command center and copy pest
1.
fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase metadata && fastboot erase vbmeta && fastboot erase system && fastboot erase vendor && fastboot erase userdata && fastboot reboot-bootloader
2.
fastboot flash recovery recovery.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader
Download and Extract
https://drive.google.com/file/d/1VMAAZoioBN3YGlV6xqd43iXGmFiWVGg3/view?usp=sharing
Then go to recovery mode
then you can install UI/IOS RealMe Official Recovery
after install from don't restart just go back and wipe to formate then restart mobile
Select 1st one. just. don't select need English...
Thanks, Everyone Enjoy...
Contact:
https://www.facebook.com/n4zmulha
Click to expand...
Click to collapse
Bro..My device is rebooting to fastboot way fast even before any operation to be completed. How can I stop those infinite bootloops?!
nharafat said:
Congratulation Friends: I Have a Solution:
extract download file (in down) and click the folder address bar and input (cmd) and hit enter.
come to the command center and copy pest
1.
fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase metadata && fastboot erase vbmeta && fastboot erase system && fastboot erase vendor && fastboot erase userdata && fastboot reboot-bootloader
2.
fastboot flash recovery recovery.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader
Download and Extract
https://drive.google.com/file/d/1VMAAZoioBN3YGlV6xqd43iXGmFiWVGg3/view?usp=sharing
Then go to recovery mode
then you can install UI/IOS RealMe Official Recovery
after install from don't restart just go back and wipe to formate then restart mobile
Select 1st one. just. don't select need English...
Thanks, Everyone Enjoy...
Contact:
https://www.facebook.com/n4zmulha
Click to expand...
Click to collapse
Genius! It worked .
Yeah! Same thing has happend to me.
After i first do it worked perfectly fine but after i formated it. It went back to it's initial stage and after trying again and again it hasn't changed yet!.
But thanks to the original author it was a great help to know that my phone isn't bricked!
Realme 5/5i/5s PH | Cloud
☁️ This is where I put some stuffs about Realmeme Trinket except roms!! ☁️ Want to forward here your files? Just mention @dangCJ or @eun0115 😉 Stay up-to-date with us! 👉 Our Group: @realme5seriesph 👉 Our Channel: @Rm5PHUpdates
t.me
Realme 5/5i/5s PH | Cloud
☁️ This is where I put some stuffs about Realmeme Trinket except roms!! ☁️ Want to forward here your files? Just mention @dangCJ or @eun0115 😉 Stay up-to-date with us! 👉 Our Group: @realme5seriesph 👉 Our Channel: @Rm5PHUpdates
t.me
nharafat said:
Congratulation Friends: I Have a Solution:
extract download file (in down) and click the folder address bar and input (cmd) and hit enter.
come to the command center and copy pest
1.
fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase metadata && fastboot erase vbmeta && fastboot erase system && fastboot erase vendor && fastboot erase userdata && fastboot reboot-bootloader
2.
fastboot flash recovery recovery.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader
Download and Extract
https://drive.google.com/file/d/1VMAAZoioBN3YGlV6xqd43iXGmFiWVGg3/view?usp=sharing
Then go to recovery mode
then you can install UI/IOS RealMe Official Recovery
after install from don't restart just go back and wipe to formate then restart mobile
Select 1st one. just. don't select need English...
Thanks, Everyone Enjoy...
Contact:
https://www.facebook.com/n4zmulha
Click to expand...
Click to collapse
Hey! Thanks for the help.
Can you help me with this scenario:
The phone I'm working on was stocked in the logo. I cannot access it's fastboot mode. It is always stocked at realme logo whenever I press volume up + power, or volume down + power.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When to use?
-> If first time custom recovery installation is messed up because forgot to intall vbmeta_disabler in Recovery.
-> If you messed up and now stuck on fastboot mode and cannot go to recovery or system.
-> When your device is automatically rebooting to fastboot every 10-15 seconds.
-> Can also be used if you get a boot destroyed screen on trying to reboot to system and recovery.
How to use?
-> Download your vbmeta.img file of your device and put it inside your ADB or Platform Tools folder
-> Open CMD in ADB (You know it)
ADB commands :
Type "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" (Don't press enter yet)
->Connect Usb to PC and long press device's volume down and power button to go to fastboot mode ( In some cases Fastboot mode remains only for few seconds)
->When you see fastboot mode in your Smartphone then you press ENTER in your PC
->If you see "success" in cmd then you can reboot to your custom recovery
Links for Realme 5 vbmeta: https://t.me/r5notes/12
nharafat said:
Congratulation Friends: I Have a Solution:
extract download file (in down) and click the folder address bar and input (cmd) and hit enter.
come to the command center and copy pest
1.
fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase metadata && fastboot erase vbmeta && fastboot erase system && fastboot erase vendor && fastboot erase userdata && fastboot reboot-bootloader
2.
fastboot flash recovery recovery.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader
Download and Extract
https://drive.google.com/file/d/1VMAAZoioBN3YGlV6xqd43iXGmFiWVGg3/view?usp=sharing
Then go to recovery mode
then you can install UI/IOS RealMe Official Recovery
after install from don't restart just go back and wipe to formate then restart mobile
Select 1st one. just. don't select need English...
Thanks, Everyone Enjoy...
Contact:
https://www.facebook.com/n4zmulha
Click to expand...
Click to collapse
Nope…
I had a functional TWRP and by doing exactly what you wrote I just ended up destroying the recovery mode.
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, then hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Final reboot:
Code:
fastboot reboot
7. If everything worked your phone should now boot into OxygenOS.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To check current slot:
Code:
fastboot getvar current-slot
To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. This will wipe your device! Reboot to the bootloader and run:
Code:
fastboot -w
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Edit: script attached. I've (unfortunately) had the opportunity to test it and fix all the bugs. So it works. You will need to have fastboot.exe accessible in your system PATH to run it.
Slikkster2k said:
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. Reboot to the bootloader and run:
Code:
fastboot -w
This will wipe your device!
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot bootloader
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Click to expand...
Click to collapse
That would be helpful indeed. Would this script run on mac as well?
Not unless there's a version of PowerShell for macs (there is for Linux, but I don't know if it's compatible).
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
AxelM said:
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
Click to expand...
Click to collapse
I used 11.2.2.2.LE25AA as I said in the original post (this is the global variant, which matches my device). I am not sure if this works for cross-flashing, or if it's possible to cross-flash an Indian phone to EU. Have you tried restoring the Indian ROM? Does that work?
You're getting an actual boot loop? The error I was getting (and the reason I had to restore) was the phone booting to the bootloader or fastbootd (depending on the slot I tried) instead of Oxygen, because it couldn't mount the user partition due to encryption. In fastbootd an error was reported (I forget the exact one) which made me suspect it was a partition mounting issue. At no point was my phone actually boot looping, even during partial/failed flashes.
I've never encountered the error with fastboot -w, but I only did that on my phone once. From some searching online, it can be caused by an old version of the platform tools, so did you download the latest version?
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
AxelM said:
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
Click to expand...
Click to collapse
Glad to hear you got it working!
PowerShell script added to second post. Totally untested, but I tried to make it as idiot proof as possible.
Slikkster2k said:
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Reboot back into the bootloader:
Code:
fastboot reboot bootloader
7. You should now be able to continue booting normally by pressing the power button.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
Click to expand...
Click to collapse
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
toyanucci said:
That would be helpful indeed. Would this script run on mac as well?
Click to expand...
Click to collapse
Windows offered now to add to MAC - https://support.apple.com/en-us/HT201468
toyanucci said:
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
Click to expand...
Click to collapse
Thanks, updated OP.
ok i kind of bricked my phone using this and i need a little help PLEASE?
Ok i tried the fist 2 steps 1. fastboot -w than the first list of commands using cmd with admin rights it worked...i think but it did load everything without issues...now i go to do the "fastboot reboot fastboot"
and now my phone is stuck on a black screen with nothing and i just hear the chime windows makes when you disconnect and reconnect a device..... and in the Device manager this comes up for 10 seconds than goes away for 5 than comes back NON STOP
i cant adb i cant do anything please help !
I'm not sure if this will help you, but I had a lot of issues initially running this. First off you need to use the Oneplus drivers, I don't think the qualcom driver will work the same way. I could be wrong, but that's what I did. Secondly, you need to force install the driver because Windows doesn't like it.
Here are the steps I took.
1. Uninstall any old drivers.
2. Install the newest Oneplus Drivers from here https://oneplususbdrivers.com/
3. Extract the zip file and run the installer like normal
4. Once the installer finishes, you'll need to reboot your machine and bring up the Startup settings (hold down shift and reboot (keep holding down shift until you get a screen with options)) Then click advanced and startup settings and hit restart after that. Once the machines starts up, on the first boot you will have a bunch of options. Choose option 7 "disabling driver signature enforcement" mode.
5. Once Windows launches and you login, go back into the device manager and follow these steps:
right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.
----------------------------------------
The above should get your drivers working properly in all modes (adb, fastbootd, bootloader, normal)
One other issue that I ran into when I was using the powershell script was that I was seeing intermittent errors. After trial and error I realized that Windows was picking up a different version of fastboot. I was initially using the minimal adb/fastboot files, but if you compare those to the ones listed in the first post in the "SDK Platform Tools", they are very different from each other, so you need to make sure you use the SDK Platform Tools version. The minimal ADB/Fastboot version will NOT work.
After I got those 2 things ironed out, the powershell script ran without a hiccup and my phone is stock and booting without an issue.
I know I'm late to respond to this thread, but I hope someone finds this information helpful!
Mine keeps trying this and it isn't running and or rebooting into Fastbootd when the script is ran. Should I just try and invoke this manually? I've tried that as well an I'm seeming to get errors left and right with no resolve.
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Good work
toyanucci said:
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Click to expand...
Click to collapse
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
ilikepie___ said:
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
Click to expand...
Click to collapse
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
toyanucci said:
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
Click to expand...
Click to collapse
I’ll give it a shot, yeah it doesn’t do anything. Can’t see a display or anything on the screen.
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
nimbussecond said:
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Dauksza72 said:
Accident... Don't know how to delete it now...
Click to expand...
Click to collapse
Dauksza72 said:
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Click to expand...
Click to collapse
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
nimbussecond said:
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
Click to expand...
Click to collapse
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Dauksza72 said:
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Click to expand...
Click to collapse
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
nimbussecond said:
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
Click to expand...
Click to collapse
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Realized I typed flash product_a/b instead of boot_a and boot_b... SORRY. Total oversize. Delete product , flash boot
Dauksza72 said:
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Click to expand...
Click to collapse
For some reason I can't get into FastbootD, it gives the error FAILED (remote: 'Unknown command') fastboot: error: Command failed. I tried searching up stuff, removing the passcode, switching USB ports and more but I couldn't get the screen to pop up. What can I do about this?
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Dauksza72 said:
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Click to expand...
Click to collapse
So I tried flashing stock recovery and I seem to get a similar error to when I flash the magisk patched file and I've tried deleting partition and flash through regular fastboot, but it didn't work either (error in the image). I might be doing something wrong since I'm still very new to this, but I also tried downloading TWRP since I know that's another way to root and it lead to the same problems as well (bootloader) is-logical whatever I'm trying to do not found. I also tried LMSA (Lenovo Rescue and Smart Assistant) to see if there was something wrong with my phone, but it made no difference. I might consider an alternative rooting method, let me know what's the best option. You don't have to brick your wife's g7, but either way I appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Are you sure the g7 Play has a separate recovery partition? It may be part of the boot partition... Instead of flashing the modified image to a/b just try
./fastboot flash boot "modimg".img
Dauksza72 said:
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Click to expand...
Click to collapse
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run.
Are these the files you have?
Post a screenshot of the flashfile.xml or servicefile.xml
nimbussecond said:
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run. View attachment 5295077
Click to expand...
Click to collapse
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Spaceminer said:
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Thanks, that's where I was headed with this.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Dauksza72 said:
Thanks, that's where I was headed with this.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Click to expand...
Click to collapse
I did a lot of dev work for this phone. I had to help.
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).
nimbussecond said:
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).View attachment 5295529View attachment 5295531View attachment 5295533
Click to expand...
Click to collapse
Install magisk manager, patch your boot.img as "recovery". Flash the patched boot.img. Use the volume buttons while in the bootloader menu to select recovery, and hit the power button. Open magisk and it should be rooted. If it needs additional setup allow it.