Database Develop

[Q] Can't enter recovery mode

Hey, so I unlocked the bootloader, and then fastboot flash recovery cwm.img
When I do this, the I get the message "Downloading ... and Flashing recovery ..." but thats about it, however on my PC it says sending OKAY and writing OKAY, finished.
then, I fastboot reboot but when I try to enter recovery mode there's just and image of a dead android with an (!) on red.
i'm getting desesperate, any help would be apreciated!!
thanks in advance!

theblackout said:
Hey, so I unlocked the bootloader, and then fastboot flash recovery cwm.img
When I do this, the I get the message "Downloading ... and Flashing recovery ..." but thats about it, however on my PC it says sending OKAY and writing OKAY, finished.
then, I fastboot reboot but when I try to enter recovery mode there's just and image of a dead android with an (!) on red.
i'm getting desesperate, any help would be apreciated!!
thanks in advance!
Click to expand...
Click to collapse
Some days ago, i had the same problem as you: after unlocking bootloader in recovery mode there was a dead android with a red (!).
Using this tool by lebobo http://forum.xda-developers.com/showthread.php?t=2281224 made nothing: also dead android.
I solved it flashing by RSD a stock rom 4.1.2. After the flashing recovery didn't work as before but now using lebobo tool I adeed CWM recovery and it works fine. From CWM using tool i passed to TWRP recovery and it also works fine.

theblackout said:
Hey, so I unlocked the bootloader, and then fastboot flash recovery cwm.img
When I do this, the I get the message "Downloading ... and Flashing recovery ..." but thats about it, however on my PC it says sending OKAY and writing OKAY, finished.
then, I fastboot reboot but when I try to enter recovery mode there's just and image of a dead android with an (!) on red.
i'm getting desesperate, any help would be apreciated!!
thanks in advance!
Click to expand...
Click to collapse
Other people are also having this same issue, read here, solution for that member was the one provided in post #10...
Good luck!
.

theblackout said:
Hey, so I unlocked the bootloader, and then fastboot flash recovery cwm.img
When I do this, the I get the message "Downloading ... and Flashing recovery ..." but thats about it, however on my PC it says sending OKAY and writing OKAY, finished.
then, I fastboot reboot but when I try to enter recovery mode there's just and image of a dead android with an (!) on red.
i'm getting desesperate, any help would be apreciated!!
thanks in advance!
Click to expand...
Click to collapse
The image you get is the prior, to access the Recovery of stock .... so do not be flashing while the recovery
Follow this post, I made ​​some months and just upgraded.
Send to Fastboot mode Visual (Audio in Spanish sorry)
http://forum.xda-developers.com/showthread.php?t=2220242
Install CWMR or TWRP Easy
http://forum.xda-developers.com/showthread.php?t=2166646
I hope you serve, greetings and good luck :fingers-crossed
Enviado desde mi XT890

Help htc butterfly s , iam an expert in android but i failed :(

hii ...
i have HTC butterfly s phone is boot looping ,,,
issue :
when entering OS i can see the lock screen for 3 seconds then reboot.
solutions tried :
1- tried to wipe from TWRP recovery when it reaches /data >>> reboot.
2- tried to install another ROM without wiping >>>> reboot
3- tried to install CWM recovery , it says completed in fastboot (CMD) but recovery is not changing.
4- tried to lock the boot loader again , it says no such file or directory .
5- tried to boot in safemode but i see the lock screen for 3 seconds then reboot
iam stuck ... please help
thank you

hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295

GAVANA said:
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
Click to expand...
Click to collapse
hi .. thanks for reply ,,,
i downloaded stock rom 2.21 and tried to flash it from recovery when it tries to install the rom when it reaches to writing /data phone reboots
you mean something else ?
thanks ...

i want to add one thing ,,,
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s

hwoarang626 said:
i want to add one thing ,,,
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device, saludos
http://forum.xda-developers.com/showthread.php?t=2730482 .
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
Click to expand...
Click to collapse
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device
regards
http://forum.xda-developers.com/showthread.php?t=2730482

its the same ,,, i tried to install the recovery you gave me but it did not install the recovery , Iam still stuck with a recovery that is not doing anything .
thanks

one more point ,,, i noticed that my /system is empty ...

hwoarang626 said:
one more point ,,, i noticed that my /system is empty ...
Click to expand...
Click to collapse
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key

xXminiWHOOPERxX said:
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping

hwoarang626 said:
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
Click to expand...
Click to collapse
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key

xXminiWHOOPERxX said:
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?

hwoarang626 said:
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
Click to expand...
Click to collapse
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk

xXminiWHOOPERxX said:
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards

mr_wehbe said:
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
Click to expand...
Click to collapse
There is no RUU for this phone, as far as I know. The closest thing to RUU is flashing everything by hand, but this seems to have failed in this case, unfortunately.

Fastboot Recovery? Getting g.co/ABH Error On Boot

I flashed the Android Wear 2.0 OTA update and now the watch won't boot. I get the "Device Software Can't Be Checked For Corruption" error and it's telling me to go to g.com/ABH.
It won't go into recovery mode, but will go into fastboot mode. I grabbed the stock images from here, and flashed the stock boot, system, and recovery imgs, but the error persists.
https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Am I screwed? Or is there something I could do to recover?
Thanks.

Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk

Wait for about 10 seconds when the warning appears. The watch will continue it's boot after 10 secs.

TonySuperPony said:
Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Click to expand...
Click to collapse
I thought I had initially. I hadn't turned the watch on for a while, but decided to get it set up yesterday when I saw news of the 2.0 update hit. It originally had the first firmware on it and wouldn't update to 2.0 (adb would fail to find the watch).
So, I flashed MWF76 from the link in my earlier post. And that worked properly -- the watch booted normally, set up the apps, the right build number was showing, etc.
When that was done I tried to flash the 2.0 update again. And this time the watch was being recognized properly with adb. The flash procedure seemed to go without a hitch, but I got the g.co/ABH error on first boot.
And if you let the watch sit for 10 seconds, it only boots into Fastboot mode. You can't enter recovery. If you try to enter recovery with the vol-down+power button combo, you see recovery for a split second and then it goes right to fastboot.
At the moment it appears the bootloader is locked again.

Still experimenting. Hoping someone with more knowledge may be able to help.
Fastboot oem unlock reports that the bootloader is already unlocked.
Tried flashing all of the IMGs in MFW76 and these flash successfully:
boot
system
recovery
modem
asusfw
But when trying to flash these, the flash fails because it says the bootloader is locked. Trying fastboot oem unlock again reports the bootloader is unlocked, but still can not flash these...
devinfo
factory
misc
modemst1
modemst2
oem
splash
Tried fastboot flashing unlock_critical, and the watch shows part of a message, but I can't see if there's anything to do on...pressing the top or bottom buttons changes the color of the bg.

Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.

yilun said:
Go into bootloader, unlock bl, flash everything and then reboot back into bootloader and lock it.
Click to expand...
Click to collapse
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?

re: flashable AW 2.0 zip file
BigWopHH said:
Thanks for the help -- tried this and still no luck.
Since I can't get into recovery mode and use adb to try reflashing 2.0, would it be possible to create a flashable .ZIP file from the 2.0 update that can be flashed from Fastboot mode?
Click to expand...
Click to collapse
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!

Misterjunky said:
Here is the OTA flashable android wear 2.0 zip file
which you can flash in FASTBOOT.
https://android.googleapis.com/pack.../9ff6d27ebfc20bf885f21ce9386c4b16018a7eff.zip
Good luck, have a great day!
Click to expand...
Click to collapse
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"

re: adb sideload
BigWopHH said:
That's the same file that's been shared repeatedly; it requires flashing in recovery mode using adb. If you try to flash this with fastboot, you get an error that says "update package xxx.zip has no andriod-info.txt"
Click to expand...
Click to collapse
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!

Misterjunky said:
Your right, this file is not fastboot compatible. (my error)
This is what I used and flashed when I upgraded to v2.0 Android Wear.
To flash this you need to use ADB SIDELOAD filename.zip.
OR if you can boot into twrp you can install it from there too.
Good luck, have a great day!
Click to expand...
Click to collapse
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.

BigWopHH said:
That's exactly what I had done initially and what ultimately bricked the watched. Can't boot into any recovery, unfortunately. Just boots directly to Fastboot mode.
Click to expand...
Click to collapse
I'd try to get the watch running 1.5 first via fastboot.

See my post in the other thread linked here, specifically my edits.
I did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata"

I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?

re: not booting properly
AndyKir said:
I have the same issue. Zenwatch 3 just boots to Fastboot Mode after manual update to Android Wear 2.0 . I can`t enter recovery mode and try to reflash it.
Do you have any ideas, what should I do?
Click to expand...
Click to collapse
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!

Misterjunky said:
You need to flash stock kernel in fastboot before you can do anything else.
( FASTBOOT FLASH BOOT BOOT.IMG )
Here is the the link to the stock Android Wear 1.5 boot.img
https://www.dropbox.com/s/dudeyq9rjsrag2i/boot.img?dl=0
(The boot.img is the kernel)
If worse comes to worse, you need to flash full android wear stock 1.5 firmware to get your watch working.
Here are the full instructions how to go back to go back to stock android wear v1.5 firmware.
This link also contains the download link for the full android wear original stock v1.5 firmware:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
First simply try to flash the boot.img in fastboot and reboot the watch before flashing the stock 1.5 firmware.
::: fastboot flash boot boot.img :::
Good luck, have a great day!
Click to expand...
Click to collapse
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.

AndyKir said:
Thank you for your reply, but it doesn`t help!
I have got the same issue as the topicstarter had. Flashing to the STOCK firmware doesn`t do anything. It stills shows Getting g.co/ABH Error on Boot and after 10 seconds it goes to Fastboot mode.
Click to expand...
Click to collapse
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.

Misterjunky said:
Your bootkoader is unlocked...
After using fastboot before reboot you need to lock the bootloadet by using.the command below.
FASTBOOT OEM LOCK
Then you can boot successfully ..
The error message you saw is normal if you have not locked your bootloader.
Good luck.. Have a great day.
Click to expand...
Click to collapse
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?

re: fastboot bootup
AndyKir said:
Sorry but this doesn`t help.
My watches are booting only in Fastboot mode.
So i do next steps:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot oem lock
fastboot reboot
After reboot, watches still boots straight in Fastboot mode.
Maybe I should flash something from AW 2.0 to repair the watch ?
Click to expand...
Click to collapse
You must have flashed the wrong boot.img (which is the kernel)
Make 100% sure that you are flashing the correct kernel and
don't issue the command "fastboot format userdata".
All you need is:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
then oem lock bootloader
What was the exact filename of the ziip file
which had the 3 IMG files in it?
Here is the link for the zip file which contains the correct IMG files in it:
https://www.dropbox.com/s/tz9bg5fggpfn2q6/swift_partition_dump_part1_MWG68.zip?dl=1
unlock bootloader, flash the three img files, lock bootloader
and issue this fastboot command: " fastboot reboot "
Don't flash anything else and don't format anything...
Good luck, have a great day!

Misterjunky, thank you for your replies!
I`ve downloaded your files from Dropbox, put it in c:\adb\correct\ folder, and run next commands in PowerShell
PS C:\adb> fastboot oem unlock
...
(bootloader) The bootloader is already unlocked!
OKAY [ 0.006s]
finished. total time: 0.007s
PS C:\adb> fastboot flash boot C:\adb\correct\boot.img
target reported max download size of 262144000 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.038s]
writing 'boot'...
OKAY [ 3.222s]
finished. total time: 4.263s
PS C:\adb> fastboot flash recovery C:\adb\correct\recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.043s]
writing 'recovery'...
OKAY [ 3.150s]
finished. total time: 4.195s
PS C:\adb> fastboot flash system C:\adb\correct\system.img
target reported max download size of 262144000 bytes
erasing 'system'...
OKAY [ 1.134s]
sending sparse 'system' (254201 KB)...
OKAY [ 8.468s]
writing 'system'...
OKAY [ 26.695s]
sending sparse 'system' (149469 KB)...
OKAY [ 5.016s]
writing 'system'...
OKAY [114.570s]
finished. total time: 155.890s
PS C:\adb> fastboot oem lock
...
(bootloader) Locking bootloader...
(bootloader) Device Locked!
(bootloader) Locking bootloader done!
OKAY [ 0.023s]
finished. total time: 0.024s
PS C:\adb> fastboot reboot
rebooting...
finished. total time: 0.008s
PS C:\adb>
After reboot, I still in Fastboot mode - nothing is changed.

Can't flash vendor.img but i have TWRP [What to do ?]

Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much

I need help :'(

I had that.
Phone was completely dead, needed a new board.

chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?

benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.

benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!

You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.

benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??

Question TWRP write FAILED (remote: partition doesn't exist)

Hi guys
I can't install twrp on my Redmi Note 10 pro Chinese Variant phone
i opened the boot loader means it's unlocked now
But when I try to install twrp using adb tool I receive this message
FAILED (remote: partition doesn't exist)
the file i have only is TWRP-3.5.1-sweet-Nebrassy-1 and TWRP-3.5.1-sweet-Nebrassy- 2
i have tried by using a new cable, another PC, different USB ports
every time i face this error
thank you

asadattari12 said:
Hi guys
I can't install twrp on my Redmi Note 10 pro Chinese Variant phone
i opened the boot loader means it's unlocked now
But when I try to install twrp using adb tool I receive this message
FAILED (remote: partition doesn't exist)
the file i have only is TWRP-3.5.1-sweet-Nebrassy-1 and TWRP-3.5.1-sweet-Nebrassy- 2
i have tried by using a new cable, another PC, different USB ports
every time i face this error
thank you
Click to expand...
Click to collapse
Follow the guide:
https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs section up to step 13. Ignore step 8, 9 and 12
Use the TWRP file you have, the TWRP-3.5.1-sweet-Nebrassy- 2.img for step 13.

flash file ( fastboot rom) to be placed in deskyop and try . mi flash tool support only file on desktop folder

pl1992aw said:
Follow the guide:
https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs section up to step 13. Ignore step 8, 9 and 12
Use the TWRP file you have, the TWRP-3.5.1-sweet-Nebrassy- 2.img for step 13.
Click to expand...
Click to collapse
same error appears with this tool too

mathan7 said:
flash file ( fastboot rom) to be placed in deskyop and try . mi flash tool support only file on desktop folder
Click to expand...
Click to collapse
file is already on desktop

First
Code:
fastboot reboot bootloader
Then do the steps again.
Show screenshots of the program what error you get.

pl1992aw said:
First
Code:
fastboot reboot bootloader
Then do the steps again.
Show screenshots of the program what error you get.
Click to expand...
Click to collapse
what i found later that i was using twrp for sweet code, later i was known that the code for my phone is Chopin, and Twrp file for Chopin is not available, so i am trying to do root without custom recovery

asadattari12 said:
what i found later that i was using twrp for sweet code, later i was known that the code for my phone is Chopin, and Twrp file for Chopin is not available, so i am trying to do root without custom recovery
Click to expand...
Click to collapse
First you need to go back to MIUI.
fastboot reboot bootloader
then flash your phone device official MIUI fastboot ROM (China).
Do not choose anything with lock option.

pl1992aw said:
First you need to go back to MIUI.
fastboot reboot bootloader
then flash your phone device official MIUI fastboot ROM (China).
Do not choose anything with lock option.
Click to expand...
Click to collapse
flashing is done with orignal rom, Phone is OK now, how can i root it without custom recovery?

asadattari12 said:
flashing is done with orignal rom, Phone is OK now, how can i root it without custom recovery?
Click to expand...
Click to collapse
Installation
The Magic Mask for Android
topjohnwu.github.io
If the official way don't work, then you have to wait until someone figure out how to root.
You phone doesn't even belong to here. No forum for you phone yet.
So you may need to find Chinese forum to see if they can root it.

asadattari12 said:
file is already on desktop
Click to expand...
Click to collapse
firet flash fatboot
fastboot flash bootloader fastboot.img
then try flash tool

asadattari12 said:
Hi guys
I can't install twrp on my Redmi Note 10 pro Chinese Variant phone
i opened the boot loader means it's unlocked now
But when I try to install twrp using adb tool I receive this message
FAILED (remote: partition doesn't exist)
the file i have only is TWRP-3.5.1-sweet-Nebrassy-1 and TWRP-3.5.1-sweet-Nebrassy- 2
i have tried by using a new cable, another PC, different USB ports
every time i face this error
thank you
Click to expand...
Click to collapse
you are using a TWRP for RM Note 10 pro global(codename is: sweet), The China Version is based on MTK CPU, it's codename is :chopin. There still no available TWRP for chopin.

fxxkingchopin said:
you are using a TWRP for RM Note 10 pro global(codename is: sweet), The China Version is based on MTK CPU, it's codename is :chopin. There still no available TWRP for chopin.
Click to expand...
Click to collapse
Does OrangeFox REC is TWRP ? When I input .\fastboot flash boot recovery.img in CMD, everything seems alright. But when I reboot my RedMi Note 10 Pro, the screen is looping in black &RedMi logo. What should I do?

GilbertWong said:
Does OrangeFox REC is TWRP ? When I input .\fastboot flash boot recovery.img in CMD, everything seems alright. But when I reboot my RedMi Note 10 Pro, the screen is looping in black &RedMi logo. What should I do?
Click to expand...
Click to collapse
Try directly after flashing recovery via Fastboot:
Press buttons volume+ and power so long as you see the logo and feel vibration.
Now recovery ofox should start again and should be stable

Laptapper said:
Try directly after flashing recovery via Fastboot:
Press buttons volume+ and power so long as you see the logo and feel vibration.
Now recovery ofox should start again and should be stable
Click to expand...
Click to collapse
I did it according to your instruction. I press buttons volume+ and power , but nothing happens. My phone kept black. What should I do?

GilbertWong said:
I did it according to your instruction. I press buttons volume+ and power , but nothing happens. My phone kept black. What should I do?
Click to expand...
Click to collapse
You've flashed twrp via Fastboot without any glitches or not?
So you stay after flashing in Fastboot, if you press then the buttons as long as you see logo and feel vibration then the recovery should start

Laptapper said:
You've flashed twrp via Fastboot without any glitches or not?
So you stay after flashing in Fastboot, if you press then the buttons as long as you see logo and feel vibration then the recovery should start
Click to expand...
Click to collapse
I think I flashed OrangeFox image correctly.
CMD result is below .
D:\APPs\_Utility\AndroidRootTools\platform-tools>.\fastboot flash boot recovery.img
Sending 'boot_b' (34024 KB) OKAY [ 0.788s]
Writing 'boot_b' OKAY [ 0.063s]
Finished. Total time: 0.976s
FastBoot feedback in phone screen is below.
USB Transferring...
USB Transmission OK Time:0 s Vel: 45MB/S
After I quitted FastBoot and reboot , the screen was looping in black & RedMi logo.
Anything I did wrong?

GilbertWong said:
I think I flashed OrangeFox image correctly.
CMD result is below .
D:\APPs\_Utility\AndroidRootTools\platform-tools>.\fastboot flash boot recovery.img
Sending 'boot_b' (34024 KB) OKAY [ 0.788s]
Writing 'boot_b' OKAY [ 0.063s]
Finished. Total time: 0.976s
FastBoot feedback in phone screen is below.
USB Transferring...
USB Transmission OK Time:0 s Vel: 45MB/S
After I quitted FastBoot and reboot , the screen was looping in black & RedMi logo.
Anything I did wrong?
Click to expand...
Click to collapse
Not quitting Fastboot, remove cable and press the buttons together until vibration

GilbertWong said:
I think I flashed OrangeFox image correctly.
CMD result is below .
D:\APPs\_Utility\AndroidRootTools\platform-tools>.\fastboot flash boot recovery.img
Sending 'boot_b' (34024 KB) OKAY [ 0.788s]
Writing 'boot_b' OKAY [ 0.063s]
Finished. Total time: 0.976s
FastBoot feedback in phone screen is below.
USB Transferring...
USB Transmission OK Time:0 s Vel: 45MB/S
After I quitted FastBoot and reboot , the screen was looping in black & RedMi logo.
Anything I did wrong?
Click to expand...
Click to collapse
You're not using RN 10 Pro global, it must be RN 10 Pro 5g (codename chopin), a.k.a. Poco X3 GT, which is A/B device. Global one is not A/B device.
Do not continue any further before risking bricking your device.

x3r0.13urn said:
You're not using RN 10 Pro global, it must be RN 10 Pro 5g (codename chopin), a.k.a. Poco X3 GT, which is A/B device. Global one is not A/B device.
Do not continue any further before risking bricking your device.
Click to expand...
Click to collapse
Yes，it is chopin. So chopin can not be rooted?