Stuck in TWRP - Xiaomi Mi A2 / 6X Questions & Answers

So basically I was installing TWRP onto my Mi A2. I installed twrp on slot b using fastboot flash boot_b twrp.img When then trying to boot into the b slot using fastboot set_active b That command wasn't recognized. I tried installing JDK and SDK manager to get the latest syntax etc. of adb/fastboot. I tried everything again and accidently typed fastboot flash boot twrp.img . This made me flash twrp to my a slot too. The new adb/fastboot syntax still didn't recognize the set_active command. So now I'm simply stuck with twrp on both my slots. I tried installing havoc-OS v2.0 for GSI. downloading the img.xz file. Extracting it and tried flashing it on slot a. But it kind of failed. This was the code:
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot flash system_b havoca2.img
target reported max download size of 536870912 bytes
sending sparse 'system_b' (524284 KB)...
OKAY [ 17.596s]
writing 'system_b'...
OKAY [ 0.001s]
sending sparse 'system_b' (524284 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 18.764s
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot reboot
rebooting...
finished. total time: 0.001s
I would appreciate some help

It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?

Stop using minimal adb, use this
https://developer.android.com/studio/releases/platform-tools
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too

If all that results in is you staying in TWRP, look at twrp and hopefully it's one of the newer versions that allows you to set the 'active slot'. Hopefully choosing the other slot and then indicating reboot in twrp will cause the device to boot normally.

AsItLies said:
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Click to expand...
Click to collapse
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.

Nebrassy said:
Stop using minimal adb, use this
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
Click to expand...
Click to collapse
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.

ncse said:
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Click to expand...
Click to collapse
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.

AsItLies said:
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
Click to expand...
Click to collapse
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update

ncse said:
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
Click to expand...
Click to collapse
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.

AsItLies said:
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
Click to expand...
Click to collapse
Now i get bootloops. Should I flash system.img too? Apprently all this fault is because you have to type .\fastboot.exe instead of fastboot in powershell.
EDIT: I flashed system.img too. It works again. Thanks for all the help!

ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
Fastboot flashing unlock_critical

Related

Issues with flashing TWRP to tablet

I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.
Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.
Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]

[Q] Recovery partition not found

It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks
sambastrakan said:
It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks
Click to expand...
Click to collapse
I am guessing the reason you are running CM11 LBL is due to the restriction imposed by a locked bootloader and not because you are choosing to miss out on all the Lollipop fun. If that's the case, I don't think you can flash a recovery via fastboot the same way you can with an UBL. You said it yourself that you have tried flashing recoveries multiple times w/o success. As far as I know, your bootloader needs to be unlocked for flashing via fastboot commands.
On the other hand if your bootloader's unlockable or you relocked it sometime in the past and forgot about it, I suppose unlocking it would do the trick. Just in case you don't know, dial up *#*#7378423#*#* and see if its unlockable.
Also what is your current recovery? I am guessing it one that came with the kernel you are using and not something you flashed separately?
Btw did you flash Williams kernel separately or did it come with the ROM? If you did flash it separately then how did you do it? Also you mentioned you flashed a kernel - did you mean via fastboot or something else like FlashTool?
No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks
sambastrakan said:
No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks
Click to expand...
Click to collapse
Since your bootloader's unlocked and your phone's probably rooted, why don't you use Rashr to flash the file? It will replace the recovery you have right now (cyanogenmod recovery?) with the one you wanna flash.
Note: This recovery stays even when you flash new ROMs so if want something else you will have to reflash via Rashr or flash stock firmware kernel with FlashTool.
Also if you switch to Lollipop, you can have dual recoveries if you follow the instructions on the Tangerine kernel thread.
http://forum.xda-developers.com/xperia-sp/orig-development/kernel-tangerine-kernel-v1-t3073297
Edit: What recovery do you have with Williams kernel right now?
Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.
akashsaini7 said:
Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.
Click to expand...
Click to collapse
It is very possible ...
Thx
Useful
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.
kojata said:
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.
Click to expand...
Click to collapse
thank you. i will have a look.
facing the same problem.. did u manage to fix it yet?
l2azoredge said:
facing the same problem.. did u manage to fix it yet?
Click to expand...
Click to collapse
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.
sambastrakan said:
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.
Click to expand...
Click to collapse
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?
l2azoredge said:
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?
Click to expand...
Click to collapse
I don't think so. what kernel are you using ? Seems your kernel ignore recovery partition....
Having the same problem after upgrading to CM 13. Any solution would be appreciated.
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
Click to expand...
Click to collapse
Thank god this nasty hack did the trick. However I placed my recovery.img inside the /system, so my command was 2- using command: dd if=/system/recovery.img of=/dev/block/mmcblk0p11
Try to flash with minimal adb fastboot.
If not,try this method: flash your recovery as boot(fastboot flash boot recovery.img), see if it works,then flash your kernel again.
Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said
IiroP said:
Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said
Click to expand...
Click to collapse
Has someone tried it already? I am afraid after installing the recovery in the boot partition and something goes wrong, that then the phone will be bricked.
Might it be the afore mentioned Kernel issue? My Xperisa XP has the kernel: 3.4.0-perf-g4c8352f-00783-gce6e17b
Thx for replies.
[EDIT]
Installing TWRP in boot partition worked fine. Let us see how it works with an Update.
The same problem
I have the same problem. Maybe Sony didn't create a recovery partition on this Phone, I unlocked it in 2016 and now i don't remember how i did this.
I only can flash boot, but afeter install system from twrp or cwm, this recovery disappear so i can't install gapps.
My experience with "Partition Not Found" is:
1.- Install Stock Rom, later of install Root
2.- Install TWRP with CMD (But the 2.8 high version, (On the internet there is a version of CMD that only makes one click and ready) Note* i Update to 3.0.1, later of install 2.8 version.
(Now update to device to Android 7, or 6, or 5)
3.- Install Rom + Gapps + Root (Note* Install Root because later u need install TWRP App)
4.- After of install rom, install TWRP App, Download and Flash Image TWRP (in the same app) on device
5.- Finally check u TWRP if all install is correct.
Saludos!
Actually i have Android 7 (Candy Rom + Fusion Kernel) with TWRP y everything is fine!

Potential brick help

So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
EDIT: Now fixed. In case anyone has a similar issue, I flashed in fastboot the stock recovery_ramdisk found in the UPDATE.APP I extracted with the Huawei update extractor, then ran fastboot -w to erase userdata and it booted successfully.
MrDanMak said:
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
Click to expand...
Click to collapse
Have you tried eRecovery?
danifilth4king said:
Have you tried eRecovery?
Click to expand...
Click to collapse
Yeah same issue with 'your device is booting now...'
MrDanMak said:
Yeah same issue with 'your device is booting now...'
Click to expand...
Click to collapse
Hmm that's not good. Maybe you've wiped/flashed over the eRecovery partition (I think it's recovery2, not recovery_ramdisk) try downloading the latest update.zip from firmware finder that matches your model number and unzip, then use Huawei update extractor to extract recovery2.img from UPDATE.APP and try flashing it through fastboot
fastboot flash recovery2 *filename*.img
Then reboot to eRecovery and see if you can recover?
This is just a guess based on what you've told me and may not work. Attempt at your own risk ?
---------- Post added at 06:24 PM ---------- Previous post was at 06:03 PM ----------
MrDanMak said:
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
EDIT: Now fixed. In case anyone has a similar issue, I flashed in fastboot the stock recovery_ramdisk found in the UPDATE.APP I extracted with the Huawei update extractor, then ran fastboot -w to erase userdata and it booted successfully.
Click to expand...
Click to collapse
Just seen your edit. Glad you got it fixed!
I have you found a solution i have the same issue?
It's the factory reset with twrp to provoque the issue...
I was able the get the same problem. I am just able to get into fastboot mode... Now I am unable to find out which files for emui 8 erecovery are needed -.- If I try to flash erecovery_ramdis.img to recovery2 just get a error which tells me partition length error.
I am mad now xD
Fixed it with just flashing every sinlge .img which I extracted out of the updater.app xD Some errors while flashing occured but it worked xD
Kaffee4Eck said:
Fixed it with just flashing every sinlge .img which I extracted out of the updater.app xD Some errors while flashing occured but it worked xD
Click to expand...
Click to collapse
***
how did you that? im trying but every single img sais something like this
fastboot.exe flash fastboot FASTBOOT.img
Sending 'fastboot' (3351 KB) OKAY [ 0.234s]
Writing 'fastboot' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.344s
Luis2k33-XDA said:
***
how did you that? im trying but every single img sais something like this
fastboot.exe flash fastboot FASTBOOT.img
Sending 'fastboot' (3351 KB) OKAY [ 0.234s]
Writing 'fastboot' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.344s
Click to expand...
Click to collapse
There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Yes but you said you flashed all the img files from the update.app, is near of 20 or 30, i only can flash, cust.img, kernel.img, recovery ramdisk and system.img but do nothing, still not booting
Kaffee4Eck said:
There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Click to expand...
Click to collapse
---------- Post added at 11:40 AM ---------- Previous post was at 11:05 AM ----------
I mean what all imgs you had flashed? i flashed cust.img kernel.img recovery_ramdis.img and system.img but didnt boot :/
QUOTE=Kaffee4Eck;78461118]There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img[/QUOTE]
download firmware
Where do iget the firmware from?
The downloads
Kaffee4Eck said:
There is no fastboot.img to be flashed.
from firmware finder dont finish downloadin or are corrupted.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Click to expand...
Click to collapse

Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error]

I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好,我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img(adb >> fastboot flash system system.img中的命令)
2. boot.img(adb 中的命令,如#1,更改 img 文件的名称)直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img(选择twrp与你要安装的rom兼容)
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b

Stock on fastboot

So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.
First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.
Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.
So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.
Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.
Im just very confused were do i go from here.
Model number LM-v4059N (jydypn)
SKT_KR (Korean version)
Android 10
Device State - Unlocked
Also i know my IMEI if that helps
Cookies_crumbly said:
So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.
First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.
Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.
So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.
Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.
Im just very confused were do i go from here.
Model number LM-v4059N (jydypn)
SKT_KR (Korean version)
Android 10
Device State - Unlocked
Also i know my IMEI if that helps
Click to expand...
Click to collapse
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.
But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.
The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.
If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.
cheers
AsItLies said:
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.
But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.
The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.
If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.
cheers
Click to expand...
Click to collapse
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.
I managed to install v35 eng abl back.
Also, can you sideload download mode from Bootloader?
Cookies_crumbly said:
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.
I managed to install v35 eng abl back.
Also, can you sideload download mode from Bootloader?
Click to expand...
Click to collapse
ahhh good, then follow this link and you'll find the boot+twrp image you need.
So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.
follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.
this is abl attached.
AsItLies said:
ahhh good, then follow this link and you'll find the boot+twrp image you need.
So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.
follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.
this is abl attached.
Click to expand...
Click to collapse
Okay so im trying to understand
First i fastboot flash abl_b kor_30f (im on b part)
Then i fastboot boot twrp
Them Resart into TWRP using power down + volume down
Then go from here?
Because i get error like this should i also flash to abl_b only?
I renamed abl_b to new, and twrp to boot for easier usage
Cookies_crumbly said:
Okay so im trying to understand
First i fastboot flash abl_b kor_30f (im on b part)
Then i fastboot boot twrp
Them Resart into TWRP using power down + volume down
Then go from here?
Because i get error like this should i also flash to abl_b only?
I renamed abl_b to new, and twrp to boot for easier usage
Click to expand...
Click to collapse
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.
any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.
I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.
cheers
AsItLies said:
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.
any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.
I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.
cheers
Click to expand...
Click to collapse
I first tried loading 30f abl and got this (My active abl was in b):
C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (1024 KB)...
OKAY [ 0.024s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 0.027s
then i tried with twrp and got the same error:
C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (65536 KB)...
OKAY [ 1.384s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 1.386s
im new to this, i really need help
Cookies_crumbly said:
I first tried loading 30f abl and got this (My active abl was in b):
C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (1024 KB)...
OKAY [ 0.024s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 0.027s
then i tried with twrp and got the same error:
C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (65536 KB)...
OKAY [ 1.384s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 1.386s
im new to this, i really need help
Click to expand...
Click to collapse
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!
You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!
I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.
So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.
cheers
AsItLies said:
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!
You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!
I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.
So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.
cheers
Click to expand...
Click to collapse
Okay my goal is installing TWRP + CUSTOM ROM
Only thing working now is v35 bootloader, and download mode shows "no command" dialog.
I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.
please help me, step by step
greatly appreciated
Cookies_crumbly said:
Okay my goal is installing TWRP + CUSTOM ROM
Only thing working now is v35 bootloader, and download mode shows "no command" dialog.
I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.
please help me, step by step
greatly appreciated
Click to expand...
Click to collapse
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.
To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.
And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).
They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.
Do that, and we'll go from there. cheers
AsItLies said:
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.
To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.
And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).
They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.
Do that, and we'll go from there. cheers
Click to expand...
Click to collapse
They files you shared is for 30c, mine is 30f (Korean version).
Is it okay to use it?
Also is there a certain order do i have to go through? like boot first etc?
cheers for the helps
Cookies_crumbly said:
They files you shared is for 30c, mine is 30f (Korean version).
Is it okay to use it?
Also is there a certain order do i have to go through? like boot first etc?
cheers for the helps
Click to expand...
Click to collapse
yes, I know they are not what you currently have. But it will work to get to lgup, not to boot the device, only to get to lgup.
there's no order, I would have told you an order if there was one.
just re-read what I said. This allows you to go directly from qfil to lgup, use the key combo I mentioned.
It's at that point you can re-flash kor 30f, and start fresh.
Im still getting the same error.
C:\adb>fastboot flash abl abl_30c.img
target reported max download size of 805306368 bytes
sending 'abl' (1024 KB)...
OKAY [ 0.031s]
writing 'abl'...
FAILED (remote: unknown command)
finished. total time: 0.031s
Cookies_crumbly said:
Im still getting the same error.
C:\adb>fastboot flash abl abl_30c.img
target reported max download size of 805306368 bytes
sending 'abl' (1024 KB)...
OKAY [ 0.031s]
writing 'abl'...
FAILED (remote: unknown command)
finished. total time: 0.031s
Click to expand...
Click to collapse
you're suppose to be using qfil, not fastboot.
But how would i enter QFIL if i cannot enter 9008 mode?
why are u unable to enter 9008 mode?
AsItLies said:
why are u unable to enter 9008 mode?
Click to expand...
Click to collapse
I did now, thank you
I was just having problem clicking volume up down button so i thought it was only possible if the phone is booted.
Successfully installed the recovery files and booted into download mode.
Downloading original kdz and hopefully do all this all over again, this time backing up the files
Thank you for all your troubles, you single handedly helped me save my phone.
AsItLies said:
why are u unable to enter 9008 mode?
Click to expand...
Click to collapse
Another surprise, when i tried to install kdz on the phone, it says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la
Both refurbish and upgrade options show same result.
This is the same version that i successfully flashed before
edit: shoot, i downloaded the wrong version
Cookies_crumbly said:
Another surprise, when i tried to install kdz on the phone, it says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la
Both refurbish and upgrade options show same result
Click to expand...
Click to collapse
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
AsItLies said:
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
Click to expand...
Click to collapse
Great news, i flashed kdz using patched LGUP with custom cmd line. Now its working as intended, it shows OEM already unlocked in dev options. i patched abl_a to get magisk working ( i think my active slot is A now).
So i got root and magisk, but my goal is still have TWRP and install custom ROM.
So from what i gathered, i install v35 on abl_a, boot into fastboot, flash twrp to boot and flash orignal abl back and restard bootloader.
Or can i just flash twrp into boot_a in QFIL?
cheers

Categories

Resources