Develop Bugs

[Q] LG G3 Stuck on fastboot! [FIXED!!!!!]

I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:

itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
573v3 said:
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
Click to expand...
Click to collapse
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.

MWGiants said:
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
Click to expand...
Click to collapse
congrats. it is good to know it is fixable

That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk

That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk

Hakem said:
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Click to expand...
Click to collapse
Fastboot boot laf.img
But beware this doesnt work for D855. His LS980 has a unlocked bootloader

Ok thanks
Verstuurd vanaf mijn HTC One_M8 met Tapatalk

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means

bikrame said:
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
Click to expand...
Click to collapse
Hi, sorry for the late reply. I hope you've already fixed it, but if you're still having this problem then let me explain. "laf.img" is the "download mode" partition. The reason you can't use twrp.img (which is a recovery partition image) is because you're "too far gone" so to speak and not even at the point to try and get into recovery. You need to restore download mode first. If you have fastboot properly working (not going to explain that, look it up, there is plenty of info about that on here and other sites), then you can do what I did. (Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work, I cant tell you about that because I don't have one and haven't played around with one). Anyway, if you have fastboot working properly (read my first post about how it can be working as long as the phone is responsive, even if you don't get back the "devices comman", you may need to play around with the drivers to get this to work) then you need to obtain an laf.img from somwhere. I found a complete set of .img's for my model somewhere (don't remember if it was on this site or somewhere else). It took a lot of searching, but I'm sure you can find one. Once you have that and the working fastboot then run the command "fastboot boot [location of your laf.img]laf.img"
GOOD LUCK!!!

itsbighead said:
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's interesting...do you have any idea why that would be? Is it a locked bootloader like someone else mentioned? (I don't know much about the D855 model, never got to play with one). Maybe there is a workaround we can come up with...

itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
I realized the problem with the mismatched aboot after the fact... ironically it all worked out because after all of this I am now back to the original kitkat and can just root and flash as you said lol.

Complete Fix Guide
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965

Can you please post where you got your laf file? I have the same problem :crying:

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
can you please help. adb shows my device and fastboot wont. when i type in fastboot devices it doesnt show anything. tried to run commands but it always gets stuck on waiting for device..

MWGiants said:
(Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work,
Click to expand...
Click to collapse
What to do with D855 than, my friend have D855 and it's stcked in fastboot mode, doesn't allow to flash anything?

lg g3 f410 stuck at fastboot
i tried the solution it didnot work. phone accepts the cmds but remain stuck at fastboot any other method?

G3 bricked and fastboot commands not working! HELP

My G3 had TWRP + CM and I want to flash its stock rom...
For some reason, Download Mode wasn't starting and every time I ended up in fastboot (flashing laf and aboot didn't help either).
So, I decided to erase everything and again clean flash them one by one using fastboot.
Now, here is the problem:
No fastboot command is working! It just hangs at executing the command....
For example, when running 'fastboot erase recovery', it shows
Code:
erasing 'recovery'...
and nothing happens! No response, nothing. The same for flashing, rebooting, ... I have to halt (ctrl+C) every time I enter a command.
The only thing that works is
Code:
fastboot devices
which shows my device with a question mark.

Had the same issue yesterday (after using Fulimics 6.5), my root seemed to be gona, I was stuck in recovery, no backup (what an idiot I am...), can't flash anaything, sideload not working...
I had to come back on stock with the KDZ method : http://forum.xda-developers.com/showthread.php?t=2785089
But you are saying your download mode isn't working ? That's really strange, Volume Up and then insering USB, mainting volume UP until the phone goes into download mode ?

But you are saying your download mode isn't working ? That's really strange, Volume Up and then insering USB, mainting volume UP until the phone goes into download mode ?
Click to expand...
Click to collapse
Yes, this all started because download mode wasn't coming up. I press volume up, insert USB and then it goes straight to fastboot:
Code:
[470] Fastboot mode started
[560] - reset -
[560] - partcharge -
[660] fastboot: processing commands
(numbers are different each time)
I think I saw the download mode icon for a second before this but not sure.

flomenol said:
My G3 had TWRP + CM and I want to flash its stock rom...
For some reason, Download Mode wasn't starting and every time I ended up in fastboot (flashing laf and aboot didn't help either).
So, I decided to erase everything and again clean flash them one by one using fastboot.
Now, here is the problem:
No fastboot command is working! It just hangs at executing the command....
For example, when running 'fastboot erase recovery', it shows
Code:
erasing 'recovery'...
and nothing happens! No response, nothing. The same for flashing, rebooting, ... I have to halt (ctrl+C) every time I enter a command.
The only thing that works is
Code:
fastboot devices
which shows my device with a question mark.
Click to expand...
Click to collapse
Don't worry bro.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
It seems a little bit tricky.but always works.

Jahanzaibawan said:
Don't worry bro.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
It seems a little bit tricky.but always works.
Click to expand...
Click to collapse
That seems a little extreme. I prefer not to meddle with the hardware if I could find a software solution... (hopefully!)

flomenol said:
That seems a little extreme. I prefer not to meddle with the hardware if I could find a software solution... (hopefully!)
Click to expand...
Click to collapse
I had the same situation because I flashed the wrong tot.it is the best solution.I spent almost 3 weeks and just the given worked.

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks

Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.

BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked

Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem

droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.

BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...

after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool

LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....

try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash

Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.

Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?

I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.

I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?

droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?

Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]

How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?

had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again

Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.

Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse

Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

Device unable to boot: Error - mdtp image is corrupted.

So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system (It doesn't even work, actually). :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: fastboot write command failed (no error). If there is a fix, please reply. I would be crying if it works.

Did you flash both _a and _b partitions?

Pixeloyco said:
So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system (It doesn't even work, actually). :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: fastboot write command failed (no error). If there is a fix, please reply. I would be crying if it works.
Click to expand...
Click to collapse
Just flash stock back via fastboot and MiFlash and flash custom ROM again with their instructions followed.
And BTW, use offain's TWRP for flashing custom ROMs (most).

Majaque said:
Did you flash both _a and _b partitions?
Click to expand...
Click to collapse
Yes I did, but it always shows the error "write command failed(no error)" during the flashing process.

RFD80M-75679 said:
Just flash stock back via fastboot and MiFlash and flash custom ROM again with their instructions followed.
And BTW, use offain's TWRP for flashing custom ROMs (most).
Click to expand...
Click to collapse
Ok, so I did that. But I accidentally selected flash_all_lock.bat instead of flash_all.bat.... Now it's stuck in a bootloop.

Pixeloyco said:
Ok, so I did that. But I accidentally selected flash_all_lock.bat instead of flash_all.bat.... Now it's stuck in a bootloop.
Click to expand...
Click to collapse
Try wipe data/cache from stock recovery. If no luck, then try the EDL short circuit test point method and reflash stock ROM again with MiFlash. If all fails, go to service center.
Test point EDL needs very short wire (or tweezers), your regular USB cable and Qualcomm Drivers. Disconnect battery before short circuit the test points.
Test Point video tutorial: https://www.youtube.com/watch?v=BrEyAEXid_o
Test Point Location Diagram: https://gsm5g917658702.files.wordpress.com/2019/02/edl-testpoint-xiaomi-mi-a2lite.png

Question Soft brick RMX3363GDPR

Hello,
I am sorry to bother you with this stupidity but i soft bricked (stuck in fastboot) my Realme GT Master Edition (RMX3363GDPR).
The phone is unlocked but i am unfamilear with flashing this phone and it's partition system.
Anyone can help me? I tried flashing with RealmeOppo flash tool but it or hangs or tells me it's succeeded but it's clearly not. It stays on fastboot mode.
Thanks in advance

pieterrees said:
Hello,
I am sorry to bother you with this stupidity but i soft bricked (stuck in fastboot) my Realme GT Master Edition (RMX3363GDPR).
The phone is unlocked but i am unfamilear with flashing this phone and it's partition system.
Anyone can help me? I tried flashing with RealmeOppo flash tool but it or hangs or tells me it's succeeded but it's clearly not. It stays on fastboot mode.
Thanks in advance
Click to expand...
Click to collapse
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel5-Tiramisu-Beta2.1%20-%20KAVHT4FFWN/Pixel5-Tiramisu-Beta2.1-AB-Tiramisu-20220527-NipponGSI.img.gz/download
extract the .gz to become a .img, with 7zip or whatever,then rename it to system.img, put to c drive not under any folder, then execute fastboot command:
fastboot flash system C:\system.img
if fail then replace with
fastboot flash system_a C:\system.img
and
fastboot flash system_b C:\system.img
then
fastboot -w
fastboot reboot
if you are really lucky it will boot up into system
do at your own risk

Thank for your reply. How is Pixel5 firmware compatible with Realme GT Master Edition?

NVM, fixed it already.

pieterrees said:
Thank for your reply. How is Pixel5 firmware compatible with Realme GT Master Edition?
Click to expand...
Click to collapse
ported (added compatibility) for generic android 9 or higher devices
pieterrees said:
NVM, fixed it already.
Click to expand...
Click to collapse
glad you fixed it

LR7875 said:
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel5-Tiramisu-Beta2.1%20-%20KAVHT4FFWN/Pixel5-Tiramisu-Beta2.1-AB-Tiramisu-20220527-NipponGSI.img.gz/download
extract the .gz to become a .img, with 7zip or whatever,then rename it to system.img, put to c drive not under any folder, then execute fastboot command:
fastboot flash system C:\system.img
if fail then replace with
fastboot flash system_a C:\system.img
and
fastboot flash system_b C:\system.img
then
fastboot -w
fastboot reboot
if you are really lucky it will boot up into system
do at your own risk
Click to expand...
Click to collapse
I did all that on the phone but the phone is on fastboot ????????? What is the solution please?

nighetspy said:
I did all that on the phone but the phone is on fastboot ????????? What is the solution please?
Click to expand...
Click to collapse
Fastboot does not properly recognize your device?
Try fastboot reboot fastboot before executing the commands

LR7875 said:
Fastboot does not properly recognize your device?
Try fastboot reboot fastboot before executing the commands
Click to expand...
Click to collapse
(remote: 'Partition not found') fastboot error please help me

nighetspy said:
(remote: 'Partition not found') fastboot error please help me
Click to expand...
Click to collapse
Tried system, system_a and system_b?

LR7875 said:
Tried system, system_a and system_b?
Click to expand...
Click to collapse
yes The problem is still there

nighetspy said:
yes The problem is still there
Click to expand...
Click to collapse
GSI on Super Partitions
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error...
forum.xda-developers.com

LR7875 said:
GSI on Super Partitions
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot flash <PARTITION> <FILENAME>. ......... Nothing new

pieterrees said:
NVM, fixed it already.
Click to expand...
Click to collapse
Could you please tell me how you fixed it, dealing with the same issue

battus said:
Could you please tell me how you fixed it, dealing with the same issue
Click to expand...
Click to collapse
I also want to know how this problem was solved

Allright,
I had a GDPR version of the firmware. I soft bricked my phone by accident. Then I flashed
Code:
RMX3363export_11_A.04_2021080317040000.ofp
and then it was an export version.
I found other ofp's but they didn't work (alltough for me..)
After i successfully flashed my phone i had update issues so i flashed
Code:
RMX3363export_11_A.09_2021122118530211.ofp
This works and a couple of hours later i even get the Realme UI 3.0 update. (this was my goal before i bricked my phone )
I used this tool:
Code:
OppoRealme-OFP-Flash
Beware, if you flashed your phone and it does not work, try changing your Slot in Fastboot.
If you don't have the correct slot (or the new software is flashed onanother slot, it will keep rebooting to fastboot)
I hope my explanation helps. I was desperate and spent three days fixing my phone. When i succeeded i tried to flash the same file from my laptop. This didn't work.I don't know why.
Good luck

pieterrees said:
Allright,
I had a GDPR version of the firmware. I soft bricked my phone by accident. Then I flashed
Code:
RMX3363export_11_A.04_2021080317040000.ofp
and then it was an export version.
I found other ofp's but they didn't work (alltough for me..)
After i successfully flashed my phone i had update issues so i flashed
Code:
RMX3363export_11_A.09_2021122118530211.ofp
This works and a couple of hours later i even get the Realme UI 3.0 update. (this was my goal before i bricked my phone )
I used this tool:
Code:
OppoRealme-OFP-Flash
Beware, if you flashed your phone and it does not work, try changing your Slot in Fastboot.
If you don't have the correct slot (or the new software is flashed onanother slot, it will keep rebooting to fastboot)
I hope my explanation helps. I was desperate and spent three days fixing my phone. When i succeeded i tried to flash the same file from my laptop. This didn't work.I don't know why.
Good luck
Click to expand...
Click to collapse
How long does it take to flash after this? fastboot --set-active=a ؟؟؟؟؟؟؟؟؟؟؟

I just flashed the ofp, after that i tried to reboot.
Then it didn't work and the device booted back into fastboot. After that I did
Code:
fastboot --set-active=other
and after that
Code:
fastboot reboot
and then it worked.
Maybe a vague tip: when you flashed it correctly and you are on the wrong slot it takes longer to boot into fastboot then when your device is bricked. Then you can change slots and (for me) that did the trick.
Good luck

How long does it take for this to end?
fastboot --set-active=other ؟؟
؟؟

a couple of seconds. When it takes forever try rebooting fastboot and try changing slots again or flash again (on another computer).

pieterrees said:
a couple of seconds. When it takes forever try rebooting fastboot and try changing slots again or flash again (on another computer).
Click to expand...
Click to collapse
What region is your phone used ؟
It works fine with you? RMX3363_11_A.09_2021122118530211.ofp ؟؟