Hi, i flashed a bad boot file and my phone is stuck on bootloader, i tried to get into edl but it's still stuck.
my bootloader is unlocked and i have access to download mode and i can run commands via fastboot. the problem is i can't remember what whas my android version (just got the phone yesterday, i think it's 8.1)
any idea how to get the phone working (any solution is good: back to stock or whatever)
oh, and i don't have root access if it's relevant.
thanks!
If you can access fastboot you can try
Code:
fastboot oem edl
And connect your phone to a PC and use MiFlash to flash the stock clean rom that you can download here
If it doesn't work, since you have access to fastboot you can extract images from here and flash them via fastboot by running the following commands from the same location of the images :
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
first of all - thank you!
i tried with miflash and it didn't work. when i flash an img file it's flashing it too fast, almost like it didn't do anything, and then it is stuck again.
about the second solution - how can i exctract img files from the file you gave me? there is a bin file in there and no img...
[edit]: it didn't flash because the folder name has spaces, now it's working. thanks!
b.t.w: do you know if there is another twrp for a2 lite then the one here ? because this is what started the problems..
I used to be like that when I was trying root by magisk
your device has update security september or aug ?! to see in setting - about
you can find original boot.img of update secrutiy your device (in topic:magisk update ota) to re-flash and reboot ... everything will be fine
Sent from my Mi A2 Lite using XDA Labs
I flashed stock rom and it's all good now. thanks!
if anyone has working twrp for a2 lite (not the one that published here unoffical)- it would help me.
As far as I know, the one you posted is the only version of TWRP for now. But the official TWRP for the Redmi 6 Pro (that is exactly the same device as ours but with dufferent partitions and MIUI ROM) has been released so fortunately the official build will be availbable for the A2 Lite soon
(btw, if ever needed again, the payload.bin file also needs to bé unpacked with a tool named "payload dumper" for example)
wrong. delete
Related
How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.
Anutter226 said:
How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.
Click to expand...
Click to collapse
What happens with the flash-all.bat file?
delete
airmaxx23 said:
What happens with the flash-all.bat file?
Click to expand...
Click to collapse
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.
Your fastboot is likely too old and can't read the pixel partitions. Make sure your Google drivers and fastboot files are up to date and try again.
Sent from my Pixel XL using Tapatalk
Anutter226 said:
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.
Click to expand...
Click to collapse
I have used the flash all script several times and it works flawlessly.
Nevermind..
kiddiosky said:
Nevermind..
Click to expand...
Click to collapse
Mate somehow i too need the manuall commands Did you solved the problem/?
Hi, I reflashed stock 10.0.2.0 and wifi stopped working. Can't turn on. Reflashed again and again and tryed with patched_boot.img but still not working.
Reflashed all images manually with fastboot and now working again. I used ./flash_all.sh to flash.
blue4 said:
Hi, I reflashed stock 10.0.2.0 and wifi stopped working. Can't turn on. Reflashed again and again and tryed with patched_boot.img but still not working.
Click to expand...
Click to collapse
Same issue Will you write me how you did it?
otobeker said:
Same issue Will you write me how you did it?
Click to expand...
Click to collapse
I unpacked stock firmware and copied all images to fastboot's folder and flashed.
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash keymaster keymaster.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib cmnlib.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash mdtp mdtp.img
fastboot flash aboot aboot.img
fastboot flash sbl1 sbl1.img
Problem solved.
blue4 said:
I unpacked stock firmware and copied all images to fastboot's folder and flashed.
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash keymaster keymaster.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib cmnlib.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash mdtp mdtp.img
fastboot flash aboot aboot.img
fastboot flash sbl1 sbl1.img
Problem solved.
Click to expand...
Click to collapse
Hi, I had upgraded my Mi A2 Lite to Pie and the had Twrp installed and Rooted it with Magisk. Tried installing multiple treble ROMS, all had issues, last one had the wirless feature not working, so I gave up and went back to stock using a twrp backup that I have created before ... to my surprise wifi was still not working on stock !! Can you please let me know how you solved it and where did you obtain that stock ROM??
SOLVED: https://youtu.be/yubl_JTEyJw
Code:
flash-all.bat
@echo off
title Mauronofrio Fastboot Rom Flasher :P
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash reserve reserve.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash LOGO LOGO.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.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 system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
pause
Hello! I am having a lot of issues after trying to push a beta update: I couldnt find the zip in the root directory, or more accurately I couldnt place the zip into the root directory, I tried multiple file managers with most recent MAGISK, sooooo
I unpacked the JAR and payload.BIN file using payload_dumper and tried to install the System, Boot, Vendor, and Recovery partition: I couldnt find Radio within the payload.
OnePlus7TOxygen_13.W.08_OTA_008_all_2009072104_5a77f7db9358487c.zip
Sure enough, when it rebooted, i didnt have radio comms: so I tried doing a system wipe from the recovery partition: but now I am in a permanent bootloop after reboot.
I have tried reflashing the most recent stable update using the same method
OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_77d64cd32274479a
but still no luck. I am trying the MsmDownloadTool V4.0
and cant seem to see my device in the connected devices screen: I see "COM3 N/A Waiting for device"
So at this point, I dont know what to do and would greatly appreciate any help I can get
Thank you
derrickl1990 said:
Hello! I am having a lot of issues after trying to push a beta update: I couldnt find the zip in the root directory, or more accurately I couldnt place the zip into the root directory, I tried multiple file managers with most recent MAGISK, sooooo
I unpacked the JAR and payload.BIN file using payload_dumper and tried to install the System, Boot, Vendor, and Recovery partition: I couldnt find Radio within the payload.
OnePlus7TOxygen_13.W.08_OTA_008_all_2009072104_5a77f7db9358487c.zip
Sure enough, when it rebooted, i didnt have radio comms: so I tried doing a system wipe from the recovery partition: but now I am in a permanent bootloop after reboot.
I have tried reflashing the most recent stable update using the same method
OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_77d64cd32274479a
but still no luck. I am trying the MsmDownloadTool V4.0
and cant seem to see my device in the connected devices screen: I see "COM3 N/A Waiting for device"
So at this point, I dont know what to do and would greatly appreciate any help I can get
Thank you
Click to expand...
Click to collapse
When you tried to find the ota in root directory did u rename jar file to .zip
SOLVED
https://youtu.be/yubl_JTEyJw
snoopy1e11 said:
When you tried to find the ota in root directory did u rename jar file to .zip
Click to expand...
Click to collapse
Yes, I extracted the jar to a zip, but It failed to copy to the root directory every time
hay i flashed the open beta android 12 on my le2123
i noticed thet i dont have root so i trying download twrp and flash magisk.zip
i boot the phone into fast boot and run this commend
"fastboot boot twrp.img"
and then i flash magisk
the phone refuse to boot normal
i able to boot it to fastboot, what should i do now?
i convart to payload of the open beta via payload dumper and i have now a lot of .img file
should i flash them 1 by 1?
there is any order of doing that?
edit:
first i sorry for my bad english
i finally boot up the phone by first download stock rom and extract the .bin file into payload dumper (i found it on xda)
after that i flash allmost any of the output img the phone came to liva again.
(i have to download the fastboot from android sdk, the minimal adb and fastboot not incloude the specific command of "reboot fastboot.
the command boot the phone into fastbootd (new to me, i never heard about it))
this is the command i use if any one here do my mistake
1. fastboot -w (this will erease anything on the phone)
2.now you need to flash the following img
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
3. now use this command to reboot the fastboot into fastbootd
fastboot reboot fastboot
4. Flash the remaining files
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
5. finnaly use this command to reboot your phone into stock rom
fastboot reboot
i really hope this will halp anyone who stuck on the same situation as me
credit to other forum for the flash guide
How to Root Android 12 via Magisk patched boot.img (without TWRP)
In this tutorial, we will show you the steps to root your Android 12 device via Magisk patched boot.img, without using TWRP Recovery.
www.droidwin.com
FizzyAps said:
How to Root Android 12 via Magisk patched boot.img (without TWRP)
In this tutorial, we will show you the steps to root your Android 12 device via Magisk patched boot.img, without using TWRP Recovery.
www.droidwin.com
Click to expand...
Click to collapse
i'll do it after i get my phone boot, you have any idea what should i do now? im stuck on fastboot
msm tool
awesome
but not all thats need to flash stock
FizzyAps said:
awesome
but not all thats need to flash stock
Click to expand...
Click to collapse
so for the next time, how to flash stock?
i was on 12 beta and back to 11 so i flash all the files
elad0elad said:
so for the next time, how to flash stock?
i was on 12 beta and back to 11 so i flash all the files
Click to expand...
Click to collapse
On 12 you can actually downgrade using the updater app they provi
Or
I have a fastboot script .bat flash the essential that are need to flash
FizzyAps said:
On 12 you can actually downgrade using the updater app they provi
Or
I have a fastboot script .bat flash the essential that are need to flash
Click to expand...
Click to collapse
The phone refuse to boot so I can't use the app...
I'll be glad If you can send the script
After not receiving any OTA updates since I bought my phone last year, I decided to VPN to Britain and let it download from there.
To keep this short, I don't like the changes RealUI 3.0 has made and I'm wondering what the easiest way to go back is.
Some searching shows me there's a rollback package for the 3360 model, but I'm concerned it may have detrimental effects for my 3363 device.
Any advice would be appreciated.
Edit: I tried a handful of things and ended up bricking the device. Fastboot is the only thing I can get to load.
My current situation is that the phone only boots into fastboot mode. I've tried running the opporealme ofp flash tool a few times with "RMX3363GDPR_11_C.08_2022062322010228.ofp", but it doesn't seem to help.
Not sure what changed, but after more tinkering I've got back into android on RMX3363_11_C.08
cobatts said:
My current situation is that the phone only boots into fastboot mode. I've tried running the opporealme ofp flash tool a few times with "RMX3363GDPR_11_C.08_2022062322010228.ofp", but it doesn't seem to help.
Not sure what changed, but after more tinkering I've got back into android on RMX3363_11_C.08
Click to expand...
Click to collapse
how you did it, my device only boots in fastboot mode
I don't really know. I just ran the flash tool several times in different active slots and trying to change them afterwards. sometimes it would hard lock during the slot change, but one time it worked.
but now my cell service is extremely spotty and I'm looking to replace the phone entirely. If anyone smarter than me wants to buy a gt master in almost perfect physical condition, hit me up (us only though)
for any who is bricked use this and u will be good to go
extract all from the DOWNLOADED FIRMWARE using mct_ofp_extractor
copy all adb fastboot and adb files in that folder
open cmd in that folder
paste all given below commands there
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.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 engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.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 system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
finally fastboot reboot
i don't know why i don't have the sames files when i do extract from ofp so this lot of this command don't work anymore