Database Develop

flash which ROM ?

Hello, my watch R has 5.1.1 (LDZ22D) stock ROM and it has some problems. I tried factory reset, still not ok. I would like to try flashing again the stock ROM. I have found this thread: http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 , i downloaded boot.img, recovery.img and system.img, checked SHA1 but i don't know which version should i try? 5.1.1 (LDZ22D), 5.1.1 (LCA44B), 5.0.2: ??? Are there limitations for downgrade / upgrade ?
And as a guide to flashing...
1. i start watch, swype 11 to 5, so now in fastboot mode i connect to PC, the PC detect the watch as what ?
2. adb devices and if watch is detected i continue.
3. fastboot flash boot boot.img
4. fastboot flash recovery recovery.img
5. fastboot flash system system.img
6. restart
is that ok ?
How long does it take to flash each of those imgs ?
thank you

intersectRaven said:
Notes/FAQ:
1.) I re-mkbootimg-ed them since I'll be uploading 2 x 20+MB files if I didn't. Still has the same SHA1 checksums as the ones being checked by stock ROM so it's safe to flash.
2.) If you're confused on how to download click on the box marked in this pic.
3.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
4.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the 5.0.1 images above.
*only for 5.0.1 since I didn't make a system image for 4.4W.2 or below
Click to expand...
Click to collapse
took that from the link you posted, just conect the watch to the dock while in fastboot mode, search for 15 second adb/fastboot installer, after installing that and the computer detects your watch just follow those steps using cmd and navigating to the directory where the files are at first, remember to install fastboot and adb system wide on the 15 second adb installer

when in fastboot mode the watch is not detected:
C:\Users\user>adb devices
List of devices attached
when i chose "recovery" in fastboot mode (android robot on back with door open and red exclamation mark) i get:
C:\Users\user>adb devices
List of devices attached
410KCHserialnr888 sideload
but the watch says he waits "adb sideload <filename>"
what i am doing wrong ? something else had to be done ?
thank you

you can use adb to boot watch on bootloader, but it is not needed since you can boot into fastboot already, problem is the watch is not detected on fastboot mode, try finding some drivers or something, what i usually do is download cydia impactor and select usb then let it do the driver stuff for me, quote me next time so i can get notified when you respond

[No More Errors] [Fastboot Rom Flashing] [Direct Method]

Hi all,
Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error . I tried many things but no luck. Then i followed direct method and that worked. Following is the procedure.
Note:
1. This will erase all your data and internal storage so better you backup them first.
2. I'm not responsible if anything goes wrong with your device.
Requirement:
1. Minimal ADB and Fastboot
2. Fastboot rom
3. Mi Pc Suite (for drivers, you can skip if already installed drivers)
Preparing:
1. Install Mi Pc Suite.
2. Install Minimal ADB and Fastboot.
3. Extract fastboot rom anywhere.
4. Copy all the files from images folder to the directory where Minimal ADB And fastboot is installed.
for example C:\Program Files (x86)\Minimal ADB and Fastboot
Procedure:
1. Connect your phone to pc in fastboot mode,
your Pc will install some drivers automatically.
2. Go to Minimal ADB and Fastboot directory .
3. Hold shift and right click.
4. Click open command window here.
5. Enter fastboot devices command.
If you see your device name in list of devices attached in command window then your good to go.
6. Now enter the following commands given below one by one in sequence.
fastboot flash partition gpt_both0.bin
fastboot flash tz tz.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash tzbak tz.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hypbak hyp.mbn
fastboot erase boot
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot reboot
Or
Simply put Flash All.bat (Attached Bellow) in Minimal ADB and Fastboot directory and double click on it (No need to enter those commands). Your Devices will reboot automatically when flashing done.
congrats
Hit thanks

It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.

did you place all the files in minimal adb and fastboot folder?
gabika1941 said:
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
Click to expand...
Click to collapse
did you place all the files in minimal adb and fastboot folder? And what you mean by using several different rom package? This method is only for fastboot rom made for redmi 2 only. Make sure your phone is detected by PC in fastboot mode with command fastboot devices.
I have tested this method three times without any errors. You are surely doing something wrong.

screenshot
gabika1941 said:
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
Click to expand...
Click to collapse
Can you attach a screenshot of your minimal adb and fastboot folder here. Also attach screenshot of your cmd window when you face error.

rkmadotra said:
Can you attach a screenshot of your minimal adb and fastboot folder here. Also attach screenshot of your cmd window when you face error.
Click to expand...
Click to collapse
i have a similar problem :
C:\Xiaomi\wt86047_pro_images_6.3.25_20160307.0000.16_5.1_cn_ee14351bfb\images>fastboot.exe flash partition gpt_backup0.bin
target reported max download size of 268435456 bytes
sending 'partition' (16 KB)...
OKAY [ 0.005s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.018s
C:\Xiaomi\wt86047_pro_images_6.3.25_20160307.0000.16_5.1_cn_ee14351bfb\images>
Click to expand...
Click to collapse
I have a 2014813 , was using a moded 2014811 rom on it. Kept crashing wanted to reflash , and installed TWRP on it , that said can't mount partitions and now i can't flash neider the 811 or the 813 roms to it . Just keeps saying error writing to partition . I can attach a screenshot of the Miflash tool if it helps. And above is the Command prompt error.

Pushing just 5 img files didn't worked for me and was stuck on MI logo, but pushing all files was reviving my phone!
Thank you very much for this method!

sir, my Redmi 2 is bricked
when I am trying to flash this the error messages is coming like
cannot load " gpt_both0.bin".
like these and so on. when I am using flash all.bat same messages is coming and then after erasing boot the phone reboots with black screen .
sir please help me
your help will be highly appriciated.
[email protected]

My phone stucks on Mi logo what will do

yeah!!!!!!!!!!!! after trying many other methods like recovery through adb ,command prompt,mi flash tool,mi pc suit...... i downloaded atleast 4-5 roms to just confirm that whether flash tool has some problem or the ROMs..........but if something worked after constantly trying many things in past three days it is this method.......seriously...
FYI this is the way i used it and u should probably use the same way
-> download MI flash tool (google it)
->install(in C
->download any compatible ROM for ur phone
->open :- C:\Program Files\Xiaomi\MiPhone\Google\Android
->paste all the contents of image folder from the ROM into this android folder
->then download this Flash All.bat from here and extract it...
->put your phone in fastboot mode ->connect it via usb
->then double click your Flash all.bat file-> give it some time->once finished ur device will start automatically
->after 10 mins or so disconnect ur phone from pc ... give it 4-5 mins , ur phone will be out of bootloop and u will be awarded with a new MIUI

Yes! It worked for me as well.
Thanks for your steps.
(FYI this is the way i used it and u should probably use the same way
-> download MI flash tool (google it)
->install(in C
->download any compatible ROM for ur phone
->open :- C:\Program Files\Xiaomi\MiPhone\Google\Android
->paste all the contents of image folder from the ROM into this android folder
->then download this Flash All.bat from here and extract it...
->put your phone in fastboot mode ->connect it via usb
->then double click your Flash all.bat file-> give it some time->once finished ur device will start automatically
->after 10 mins or so disconnect ur phone from pc ... give it 4-5 mins , ur phone will be out of bootloop and u will be awarded with a new MIUI )
and it worked good.
My Mi Account was locked and could not connect to internet at all.
I had tried using Flash tools, PC suite - Flash methods and nothing worked. I had spend more time to fix my mobile in all these ways.
But this method is awesome. Only took around 15 minutes to completely flash my mobile.
After flashing the mobile, I am able to connect to internet and I have also created a new Mi-Account and linked my G-Mail account to it.
Am super happy now.
Thanks a lot.
However I would wish to add another details to the above setps:
The Flashall.BAT too needs to be extracted and copied into the same folder where the contents from ROM's Image folder were copied.

awesome bro thankyou very much.it's working absolutely well:good::good:

Tried a similar method and got my redmi2 prime hard bricked. Can someone tell me the test points in the device 2014818?

Thanx This works for me. successfull to flash my redme 2
Simply put Flash All.bat (Attached Bellow) in Minimal ADB and Fastboot directory and double click on it (No need to enter those commands). Your Devices will reboot automatically when flashing done.
congrats
Hit thanks[/QUOTE]

Will this work for Redmi note 3 Snapdragon??

Hello
I am stick in bootloop with my Redmi 3 (after trying Flashify).
Tried the above method with high hopes, as I have been trying everything else also with no luck.
I have downloaded a ROM for my device of course.
It all seems to go well until I launch the Flash_All.bat
Then the DOS commands are executed in 5 to 10 secs, and my devices reboot, but in a bootloop again
I got a breif view at the DOS commands, and it basically, at several lines says somthing, like: "failed to write, device is locked"
see attached sreen shot
does this mean my problem has no solution and I can simply throw away my device?
Thanks

rkmadotra said:
Hi all,
Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error . I tried many things but no luck. Then i followed direct method and that worked. Following is the procedure...
Click to expand...
Click to collapse
You solved my problem :good:

Thank you buddy..... This method works

Fastbooting method did not bring back my stock model number that is hm2014818. It changed to 2014817 when i flashed miui 8 64bit rom for redmi 2. Now i am not able to go back to my original model number even by fastboot method. Any help please??

will the flash all.bat support on other mi device's??

stuck at erasing user data
flashing stuck at flashing userdata

[Guide][TWRP 3.1] How to Flash TWRP 3.1 on Lenovo ZUK Z2 Pro

The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx

MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.

bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.

I've tried again on Chrome,IE and Firefox but still get Decrypt message.

Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit

Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.

fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.

Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp

Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.

People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.

MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.

which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.

jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.

Hello, this works fine very thx, but you have recent/new mix version?

Mi A2 Can't flash anything via fastboot (bootloader unlocked, oem critical too)

When I flash TWRP
It shows me this
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
PS C:\adb>
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
Code:
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
PS C:\adb>
I try to use another way
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot getvar current-slot
getvar:current-slot FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
PS C:\adb>
But without fastboot devices
Code:
PS C:\adb> fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
PS C:\adb> fastboot flash boot_b recovery.img
sending 'boot_b' (41314 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
-------------------------------------------------------------
UPDATE!!
I just use a USB2.0 Port (USB HUB)
and I got the problem solved!!!!

You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......

bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(

same problem here , please help anyone

cs853120 said:
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(
Click to expand...
Click to collapse
reset your phone once then try........also try to unlock your boot loader & see if you can flash the stock rom from the official website......make sure that the entire rom file is in a folder on your desktop.......for some reason MI flash does not like long system paths.....

cs853120 said:
When I flash TWRP
It shows me this
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
I try to use another way
But without fastboot devices
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
Click to expand...
Click to collapse
Hi there.
I have the same problem. Can't do anything with my phone on any USB 3.0/3.1-Port on my Ryzen desktop (works neither on Win10 nor Linux Mint). I have to use my old Win8.1 Intel laptop and there everything works flawlessly but only on the USB 2.0 port. I used the same tools/commands/Mi-drivers but it only works on the laptop. Tried different drivers for MB/USB-host controller and different cables but to no avail... Connecting the phone and mtp works but no adb/fastboot.
I read on different threads that other people have the same problem with other hardware setups but most of them were able to fix it with MB drivers from the manufacturer instead of the Windows ones. Maybe that could work for you.
For now I keep the laptop around for flashing my A2....

whenever you get "press any key to shutdown" on fastboot it's because of the usb port, use usb 2.0

I have the same problem , and change to 2.0 USB Ports works! Thanks!

Did you found a solution?

Please help. Facing exact same issue. Tried all USB ports on my PC. Switched between Ubuntu and Win10. All to no avail.

It's a USB 3 problem. I had it too in my laptop. You gotta find a USB 2 port, maybe in another PC. Good luck.
Sent from my Mi A2 using XDA Labs

i was also fasing same problem so what is did is
fastboot flashing unlock_critical
then
fastboot oem edl
and flashed stock

Mi A2 Boot loop
The first thing you'll want to do here is extract the factory images archive that you downloaded from your manufacturer's website. For that part, I'd recommend using 7-Zip, as it's free and works with most archive formats , move all of the contents of the archive to the platform-tools folder inside of your ADB installation directory, then open an ADB Shell window in this folder.
Flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders.
there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
//
fastboot flash boot <boot image file name>.img
//
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
//
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
//
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
//
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
//
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
//
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
//
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot
/
Thanks to Android gadget hacks .
P.S : Including today , it was 22nd time that i rooted , enabled camera2api .. but i think till know its useless .

After dealing with this issue for a long time I found that using a USB hub solved it for me.
This is the one I'm using: https://es.aliexpress.com/item/USB-...342.html?spm=a2g0s.9042311.0.0.1d6e63c04tJJe6
Hope this helped!

the same problem
have tried all USB port, unfortunately, no success

Hi everyone,
Today I have a big problem
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks

HELP
bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
Can you help me with my thread?? Thank you!

Same error.

Download TWRP and TWRP installer
DONT CONNECT YOUR PHONE!!
Put your phone in Fastboot
in cmd type
fastboot boot twrp.img (twrp name instead of twrp.img)
Then when you see <Waiting for Device> connect your phone !
Check if it's working.
This was fix for me, when I was unable to even boot into recovery.
Once you boot into recovery, wipe everything, flash twrp zip, and error should be gone

Hey guys,
same issue here but i don't have any usb2.0 port on my laptop now. Any workaround? Totally sure that i used fastboot + usb3.0 on Sony, LG, Samsung ROMs with no hassles whatsoever. Is this only happening with Xiaomi?
Cheers

I bricked my OnePlus 7 Pro (was stuck and fastboot) and how I fixed it

Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.

Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk

vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done

All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.

I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!

Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!

Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.

vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!

vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.

i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd

nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/

vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power

I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?

I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:

moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk

Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?

Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?

Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk

Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...

I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse