Database Develop

[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!

error flashing with fastboot

my phone is moto g2 xt1068
i flash it with fastboot very much because after 3 days restarting and hang in boot but after flash it is work for 3-5 days
now i want to flash it but have this error fastboot
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.979s]
writing 'partition'...
FAILED (status read failed (Too many links))
finished. total time: 1.778
please help me
thanks

Do you have twrp?
Have you tried flashing twrp if you don't have it installed?
Which ROM are you flashing?
It looks like you don't have enough space if I'm reading that error correctly
We need to know so we can help you

what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks

This is stock firmware, yes?
Are all your Moto G drivers up to date?
There are a number of different ways to install depending on the package type.
Some packages are flashable zips. Needs Twrp (Team Win Recovery Project)
Some are sideload packages installed via Fastboot.
Some are OTA packages (OTA, over the air) installed via phone update.

amir58hz said:
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
Click to expand...
Click to collapse
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!

bejunk said:
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
Click to expand...
Click to collapse
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks

amir58hz said:
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
Click to expand...
Click to collapse
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!

bejunk said:
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
Click to expand...
Click to collapse
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ

amir58hz said:
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
Click to expand...
Click to collapse
Thx. But i need a picture of bootloader screen, see my picture!
-> hmm in your case i would try it now with formatting internal completly.. But even better would be full formating, so when you have TWRP:
- format Internal storage
- then tick system + data + cache and format them.
- You have to reflash stock then OR (i recommend) try it with a custom rom, like you said allready tried stock many times...
To install custom rom, get these files
ROM: https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-15-1-t3786749 get latest build
GApps: https://opengapps.org/ choose ARM -> 8.1 -> nano version
put everything in sdcard or storage (after wiping it)
Then in TWRP -> factory reset in wipe menu -> install ROM zip -> install GApps -> reboot. 1st boot can take some time. Test & report.
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck

bejunk said:
Thx. But i need a picture of bootloader screen, see my picture!
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
Click to expand...
Click to collapse
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW

amir58hz said:
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
Click to expand...
Click to collapse
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:

bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
Thanks very much
I dont have custom rom can you advise me to download it
I flashed it if is not have problem is very good but it crash and dont work i send here my problem
Thanks again good luck

bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
hi man
after one day mobile is work true thanks alot

after 3 days restart phone but then stop in black page
now flash again
what is my problem?

amir58hz said:
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
Click to expand...
Click to collapse
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)

bejunk said:
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
Click to expand...
Click to collapse
No i flash it with same my frimware
Now for flashing with custom rom it need download rom android8?

i have this error in wipping and installing rombut instal it
my error is:
e:recv error on uevent
But now flashed to 8.1 android
Thanks

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

MI9 can't boot and stucked in fastboot

Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings

Try another recovery and if it failed try full flash latest stable rom

Well, I have been warning so many times that use any TWRP in MI9:
1. format data partition
2. reboot TWRP and then enter twrp. Make twrp mount data partition
3. wipe everything BUT please keep system partition only
4. reboot twrp and then enter twrp again
5. Now wipe system partition and then flash any rom you want
6. reboot
How to save your phone now ? Please try fastboot ROM and use miflash app to save your phone !
Kris
ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse

@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...

Some questions here:
1. Is Redmi K20 CN the same as Mi9T?
If yes, that twrp is correct and the best one
2.After flashing twrp, can you enter twrp by general
method : power + volume up to enter twrp?
If yes, I think the problem is coming from your data
partition. Please format your data partition first and
then reboot to Twrp again. Then copy your rom in your
phone and then wipe cache/ dalvik cache/system. Next
to flash rom. Always Remeber not to reboot your
phone if you haven't flashed rom under twrp after
flashing system partition.
Kris
Ardysan said:
@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...
Click to expand...
Click to collapse

Thank you Kris!

Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .

Failykun said:
Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .
Click to expand...
Click to collapse
This is what I had to do both times this happened.

I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?

RebornCheiko said:
I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?
Click to expand...
Click to collapse
As i understand, you wiped system and then restarted? And now you can enter only fastboot?
When you wipe system you must flash a ROM without restart or after restart, only fastboot available. TWRP version has nothing to do with this.
Now you must use mi flash or adb and fastboot utility. Download fastboot version of ROM, then open archive and flash it using mi flash or flash_all.bat script. flash_all_lock.bat will also lock your bootloader and mi flash has that option too, so check twice what option you choose
After flashing ROM you can flash TWRP again and it will be available, because by flashing ROM you restored system

I had the same problem.
Try to flash vbmeta.img via fastboot (fastboot --disable-verity flash vbmeta vbmeta.img) and then flash recovery then boot recovery.
Or try to flash boot.img (fastboot flash boot boot.img) then flash recovery.

ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse
I got you chief. Make sure you have adb and fastboot installed.
No you don't need Mi flash tool for this. All you need is a computer.
Go to fastboot mode, plug in your device and expand cepheus.tgz file you downloaded. Link below
https://xiaomifirmwareupdater.com/
Now open the folder. You have the flash_all files in there. Any .bat file is for Windows only. Any .sh files are for Mac and Linux.
Make sure the device is recognized in fastboot via cmd or terminal
WINDOWS ONLY: Open Command prompt and drag flash_all.bat into the cmd window and press enter
MAC/LINUX: Open terminal and drag flash_all.sh into the terminal window and press enter.
This part requires some patience. Wait until everything is finished.
Reboot using power button and it should be back to normal.

[SOLVED] Xiaomi Mi 9 stuck in fastboot mod

Hello everyone!
I have a huge problem with my Mi9 and I need your help.
I tried to install magisk, but once I flashed it any version of magisk (19.3, 20 etc...) the phone was rebooting in recovery mod insted of rebooting normaly. I have the version 10.2.30 PFAEUXM.
I've downloaded this ROM (zip) and extracted it. I then flashed the boot.img file thanks to the command "fastboot flash boot boot.img" but the phone stay stuck in fastboot mod and can't restart anymore!
I tried to re-flash the entire ROM via "fastboot flash system ROM.zip" but it didn't work. I also tried to flash TWRP-3.3.1-0601 via command "fastboot flash recovery TWRP-3.3.1-0601.7z".
I hope you guys will be able to help me...
Thanks in advance and have a good day.

tom1909 said:
"fastboot flash system ROM.zip" "fastboot flash recovery TWRP-3.3.1-0601.7z"
Click to expand...
Click to collapse
О_о
Seeing this i must ask you how flashed magisk? fastboot flash boot magisk.tgz ?)))) And how you even managed to boot to recovery?

g_seva said:
О_о
Seeing this i must ask how flashed magisk? fastboot flash boot magisk.tgz ?)))) And how you even managed to boot to recovery?
Click to expand...
Click to collapse
First, thanks for your answer
I tried to flash magisk.zip by TWRP
I tried to reboot in recovery mod by "vol+" + "power" and "adb reboot bootlaoder, but it doesn't work, it is written "error: no devices/emulators found"
"fastboot reboot" reboot my device in fastboot mod. But when i try "adb devices" it's written "List of devices attached"

tom1909 said:
First, thanks for your answer
I tried to flash magisk.zip by TWRP
I tried to reboot in recovery mod by "vol+" + "power" and "adb reboot bootlaoder, but it doesn't work, it is written "error: no devices/emulators found"
"fastboot reboot" reboot my device in fastboot mod. But when i try "adb devices" it's written "List of devices attached"
Click to expand...
Click to collapse
By fastboot flash recovery TWRP-3.3.1-0601.7z you flashed twrp in archive i didn't know it even possible You must extract the archive and in archive must be file "twrp name".img or recovery.img. Then you can flash TWRP with fastboot flash recovery recovery.img or for example fastboot flash recovery twrp-3.3.1-42-cepheus-mauronofrio.img.
If after this you will manage to boot into twrp, you can flash a ROM in TWRP using install option. I don't know what you did before so before flashing ROM wipe cache/dalvik cache and format data all this in TWRP. After flashing ROM you can flash magisk, same as ROM.
If you can't enter TWRP, you must download fastboot ROM, extract it and flash it via Mi flash. Don't use flash all and lock or you will lock your bootloder.

g_seva said:
By fastboot flash recovery TWRP-3.3.1-0601.7z you flashed twrp in archive i didn't know it even possible You must extract the archive and in archive must be file "twrp name".img or recovery.img. Then you can flash TWRP with fastboot flash recovery recovery.img or for example fastboot flash recovery twrp-3.3.1-42-cepheus-mauronofrio.img.
If after this you will manage to boot into twrp, you can flash a ROM in TWRP using install option. I don't know what you did before so before flashing ROM wipe cache/dalvik cache and format data all this in TWRP. After flashing ROM you can flash magisk, same as ROM.
If you can't enter TWRP, you must download fastboot ROM, extract it and flash it via Mi flash. Don't use flash all and lock or you will lock your bootloder.
Click to expand...
Click to collapse
Unfortunately, I tried to install TWRP-3.3.1-42-cepheus-mauronofrio.img. too but it doesn't work. My phone reboot in fastboot mod. :crying:
I found a fastboot rom but in 10.2.22 not in 10.2.30. I'm going to try with this, and update the rom after.
I'll tell you back soon. Thanks for all.

tom1909 said:
Unfortunately, I tried to install TWRP-3.3.1-42-cepheus-mauronofrio.img. too but it doesn't work. My phone reboot in fastboot mod. :crying:
I found a fastboot rom but in 10.2.22 not in 10.2.30. I'm going to try with this, and update the rom after.
I'll tell you back soon. Thanks for all.
Click to expand...
Click to collapse
Have you wiped system?

g_seva said:
By fastboot flash recovery TWRP-3.3.1-0601.7z you flashed twrp in archive i didn't know it even possible You must extract the archive and in archive must be file "twrp name".img or recovery.img. Then you can flash TWRP with fastboot flash recovery recovery.img or for example fastboot flash recovery twrp-3.3.1-42-cepheus-mauronofrio.img.
If after this you will manage to boot into twrp, you can flash a ROM in TWRP using install option. I don't know what you did before so before flashing ROM wipe cache/dalvik cache and format data all this in TWRP. After flashing ROM you can flash magisk, same as ROM.
If you can't enter TWRP, you must download fastboot ROM, extract it and flash it via Mi flash. Don't use flash all and lock or you will lock your bootloder.
Click to expand...
Click to collapse
I'm sorry, but I finaly didn't find a link to download the fastboot rom. I only find recovery rom .zip. Can you help me and send me a link pleeease.

tom1909 said:
I'm sorry, but I finaly didn't find a link to download the fastboot rom. I only find recovery rom .zip. Can you help me and send me a link pleeease.
Click to expand...
Click to collapse
Download Mi Flash tool pro: https://jumpmobile.ru/download/miflashpro-3-3-1212-88/?wpdmdl=286&refresh=5da2215f6f9e21570906463
Enter with your account choose "ROM packages", search for your device, and choose one of available fastboot ROMs, tap on copy and paste the download link in browser or download manager.

g_seva said:
Have you wiped system?
Click to expand...
Click to collapse
Yes, when my phone rebooted in recovery I tried to wipe system and reflash the rom. It worked but when I reinstalled magisk the bug came back

tom1909 said:
Yes, when my phone rebooted in recovery I tried to wipe system and reflash the rom. It worked but when I reinstalled magisk the bug came back
Click to expand...
Click to collapse
You sure that you reinstalled ROM after wiping system? Because if you just wiped system and flashed magisk that's the problem You must flash a ROM after wiping system without reboot or you will stuck in fastboot after reboot And there is no need in system wipe, don't touch it

g_seva said:
Download Mi Flash tool pro: https://jumpmobile.ru/download/miflashpro-3-3-1212-88/?wpdmdl=286&refresh=5da2215f6f9e21570906463
Enter with your account choose "ROM packages", search for your device, and choose one of available fastboot ROMs, tap on copy and paste the download link in browser or download manager.
Click to expand...
Click to collapse
I tried to flash the fastboot rom 10.2.15 by Miflash and it works ! I upraged this just after :fingers-crossed:
Yes, I remote system just before flash a rom but maybe I forgot.
My problem is solve ! Thanks for all (sorry for my bad english, I'm french)
How can I get my topic "Solved" ?
Cordialy

tom1909 said:
I tried to flash the fastboot rom 10.2.15 by Miflash and it works ! I upraged this just after :fingers-crossed:
Yes, I remote system just before flash a rom but maybe I forgot.
My problem is solve ! Thanks for all (sorry for my bad english, I'm french)
How can I get my topic "Solved" ?
Cordialy
Click to expand...
Click to collapse
Just add to the thread name [SOLVED]. Edit first post and then you can edit thread name.
Greetings from Israel.

This is maximum stupid. I need the xiaomi flash tool to repair it and the tool wants to verify my telephone number by sending me a code by SMS...