Database Develop

Oh no! Used CF and having problem (Your device is corrupted)...urgent

Hi,
I used CF Auto root and it didnt complet the process!
I just had some alert...which was quicly disappeared:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i boot into Bootloader I can see that:
"Device is UNLOCED Status code: 3"
I read that in order to resolve that, I should be in bootloader mode(which I can do)
and Flash system, boot, recovery.
But i just DO NOT know how...!
I even dont know which files to download?
I dont know on which android version i was.
Please help me...
Thank you!

I just did this last night. Easy fix. Follow these steps. Put all the factory image files in the platform-tools folder and run these steps in a command prompt. Let me know if you need more details. I went from never rooting a phone to loading 6.0.1 in about two hours. Which I would stay away from for now due to the battery bug. Stick with 6.0.0.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481/page62
The CF autoroot does not work for Marshmallow. Something needs to be done on this forum or lots of people are going to temporarily brick their phones.

Thanks!
Can you please look at the attached screenshor and tell me if needed files?
I extract factory image 6.0.0 (MRA58X)...
Now:
1) Which files i should copy to platform-tools folder?
2) Can I flash at the same time also SuperSU & TWRP
After i copy the file/files to platform-tools folder , is that what i should do?
1) Boot into bootloader mode.
2) Open command prompt from platform-tools .
3) Type in the command prompt window these 6 commands (1 by 1):
- fastboot erase system
- fastboot flash system system.img
- fastboot format cache
- fastboot flash cache cache.img
- fastboot flash recovery recovery.img
- fastboot reboot.
##############################
Thank you so much!

fastboot flash twrp recovery, reboot to recovery and flash roms from there

I really need your help...
Followed this:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Clicked on the flash-all
But it tell me:
'fastboot' is not recognized as an internal or external command...."
How come?
Please - need your help.
Thank you!

TWRP downloaded and copied to:
C:\\adt-bundle-windows-x86\sdk\platform-tools
Renamed it to: twrp.img

put twrp .img in same folder as fastboot:
fastboot flash recovery NAMEOFIMAGE.img
that's all

Is it ok?
After waiting long to see any process in the cmd windows or in the device (nothing), This is what i get:
Maybe something is wrong with the driver?
How can i knwo (when i connected the n6 in the first time everything looked right with the driver)

you have unlocked your bootloader? you have booted to bootloader when trying fastboot?

In the bootloader i can see:
Device is UNLOCKED, Status Code: 3
I booted into by holding VOL down+power.

You are going to have to fight through it like I did till I can get back to my laptop and help. Everyone that knows what they are doing do not understand you don't know what dgbrjkgbj efvkjdfougndfj nnufiv vsibhan andighbdfiv are. The lingo is the killer in learning all this stuff. There is no plain easy to understand guide to all this which is why I have stayed away from it for so long. Every technical area has users who break it down to the most basic level. This is the exception.

@Clay
I really having difficulties understanding your main gaol with your replay.
I am sure that there is a solution to this problem.
I just need someone to explain me what is wrong here...

never seen that error about size. can't help you with that.

Trying to get someone that can help you understand that you need it broken down in more simple terms. Where to get the image from. What to do with it, when to do which step.
---------- Post added at 03:44 PM ---------- Previous post was at 03:24 PM ----------
Download the factory image from here.
https://developers.google.com/android/nexus/images?hl=en
Extract the .tgz file then the .zip file and put all the files in the platform-tools folder. You might need winrar to extract the .tgz file.
Then run the sequence below from a cmd prompt pointed to the platform-tools folder.
1) Boot into bootloader mode.
2) Open command prompt from platform-tools .
3) Type in the command prompt window these 6 commands (1 by 1):
- fastboot erase system
- fastboot flash system system.img
- fastboot format cache
- fastboot flash cache cache.img
- fastboot flash recovery recovery.img
- fastboot reboot.

Hi,
Cant see any tgz file there...unless you meant to a ZIP file(image-shamu-mra58x) ??
Here are the files: (it's a screenshot)
http://forum.xda-developers.com/attachment.php?attachmentid=3587442&stc=1&d=1450972618

The .tgz file is the original file you download from this site. The factory image.
https://developers.google.com/android/nexus/images?hl=en
Extract the .tgz file, then the .zip file that extracts from the .tgz file, place all those files in the platform-tools folder then run the sequence above.

place all those files in the platform-tools folder
Click to expand...
Click to collapse
Do i need to take only the files that created from the extracted zip file?

Do i need to take only the files that created from the extracted zip file?

I don't know what twrp is yet, so you'll have to get help from someone else on that one.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
I put everything in the platform-tools folder. As long as you have the files mentioned in the fastboot steps you should be good.

@Clay
As we can't post images by this kind of commants, pleas see bellow the attached image.
I extracted it correctly?
Thanks!

[ROM][MIUI][4.4.X] Stock Kitkat MIUI 6 fastboot ROM flashing guide for Redmi 2

After xiaomi decided to push an update of miui with lollipop, they decided to change partitions and firmware is new too which is bad (as it causes bootloop) if you want to switch to Cyanogenmod 13 which has got official support recently.
So its good to get back on kitkat MIUI to switch to Cyanogenmod.
Let's get started!
THINGS YOU'LL NEED:
1. ADB and Fastboot tools: http://d-h.st/oFLb
2. Stock MIUI kitkat ROM: http://bigota.d.miui.com/V6.7.1.0.K...ICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
3. 7zip (Probably the best file manager) http://www.7-zip.org/download.html
4. Drivers: http://d-h.st/a5kA
How to install drivers: Download and extract the above zip contents in a folder. Right click on My Computer > Manage > Device Manager. If your drivers are not installed correctly, it will show as unknown device in device manager. Right click unknown device > Click update driver software > Browse and select the extracted folder. If warning is shown, ignore it and proceed.
5. Patience and some brain xD :silly:
INSTALLATION:
Windows 7/8/8.1 is recommended
1. Extract the adb and fastboot tools in folder on your desktop named Redmi 2.
2.Download and extrack the fastboot ROM in the same folder too. Use 7zip software here to extract it.
3.Now move mouse to empty space in folder and while pressing shift, press right click. A menu will open. Select " open command prompt here" option. A command prompt window will open.
4.Power off your phone. Let it vibrate. Press and hold "Volume down and power" buttons until it enters fastboot mode.
5.Connect the phone to PC/Laptop in fastboot mode itself. Let the OS install drivers, make sure you have working internet connection.
6.Type the following command:
Code:
fastboot devices
Fastboot will return serial number of device(It can be any number don't worry if it looks weird). Click button below to see screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.If a blank space is returned, make sure drivers are installed correctly and phone is connected correctly.
8.If everything is okay, type the following commands one after another when previous process is complete.
I have shown a example for flashing recovery image below. Likewise you have to proceed for others.
Code:
1.fastboot flash boot boot.img
2.fastboot flash system system.img
3.fastboot flash userdata userdata.img
4.fastboot flash recovery recovery.img
5.fastboot flash cache cache.img
9.After this is completed, type the last command:
Code:
fastboot reboot
10.DONE.
Your phone will now boot in MIUI kitkat and you are ready to flash the official CM13!
Follow this guide for CM13:http://forum.xda-developers.com/redmi-2/how-to/rom-install-official-cyanogenmod-13-t3374589
HIT THANKS AND FEEL FREE TO ASK QUESTIONS HERE.

bootloader isn't locked, only partitions change bro

I flashed the images via fastboot and got bootloop...........

PROdelision said:
I flashed the images via fastboot and got bootloop...........
Click to expand...
Click to collapse
Device variant?
Did you try cm13? Try and tell.
Sent from my 2014818 using Tapatalk

is this how to the same with if i use MiFlash?

sennayan said:
is this how to the same with if i use MiFlash?
Click to expand...
Click to collapse
Yes. I'll try to update this with screenshots etc today.
Sent from my 2014818 using Tapatalk

Is this working with 2014813?

frosty234 said:
Is this working with 2014813?
Click to expand...
Click to collapse
It should.
Sent from my 2014818 using Tapatalk

noobpremium said:
It should.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
I made it with 2014813, and now I am stuck at boot with MI logo.
What can I do?

bisato said:
I made it with 2014813, and now I am stuck at boot with MI logo.
What can I do?
Click to expand...
Click to collapse
Flash twrp and go for cm13 :good:
Sent from my 2014818 using Tapatalk

I was now able to once Start after installing "your" twrp. I wiped data etc, but now it gives me error 7.
Edit: solved by once again flash twrp IMG through twrp itself. THX noobpremium

Device variant: 2014811, a.k.a. Wt88047, a.k.a. Redmi 2 WCDMA
I exactly followed your post and flashed the images via fastboot and got a bootloop.
Then used fastboot to install & boot a twrp-3.0.0-0-wt88047-20160309.img and proceed to install a cm-13.0 NIGHTLY-wt88047 ROM and, again, got a bootloop

plasticdoc said:
Device variant: 2014811, a.k.a. Wt88047, a.k.a. Redmi 2 WCDMA
I exactly followed your post and flashed the images via fastboot and got a bootloop.
Then used fastboot to install & boot a twrp-3.0.0-0-wt88047-20160309.img and proceed to install a cm-13.0 NIGHTLY-wt88047 ROM and, again, got a bootloop
Click to expand...
Click to collapse
Did you follow cm13 guide properly?
Did you wipe system partition
Sent from my 2014818 using Tapatalk

Hey so, I'm running HM2014811 redmi 2 on lollipop miui. I've followed your article, but when i try to flash system.img, fastboot comes up with an error (remoteata too large). So what should i do.

Luke T. Kirk said:
Hey so, I'm running HM2014811 redmi 2 on lollipop miui. I've followed your article, but when i try to flash system.img, fastboot comes up with an error (remoteata too large). So what should i do.
Click to expand...
Click to collapse
First erase data partition with this command:
Code:
fastboot erase userdata
And then flash userdata again
Edit: Maybe you'll need to erase system partition too and flash again.
Sent from my 2014818 using Tapatalk

noobpremium said:
First erase data partition with this command:
Code:
fastboot erase userdata
And then flash userdata again
Edit: Maybe you'll need to erase system partition too and flash again.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Nope, It's still saying 'remote: Data too large" on trying to flash either system.img or userdata on fastboot
Any other suggestions?

Luke T. Kirk said:
Nope, It's still saying 'remote: Data too large" on trying to flash either system.img or userdata on fastboot
Any other suggestions?
Click to expand...
Click to collapse
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.

plasticdoc said:
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
Click to expand...
Click to collapse
Super thanks. I'll add it to OP for ubuntu guys. I have ubuntu too but i dont use it for flashing [emoji14]
Sent from my 2014818 using Tapatalk

plasticdoc said:
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
Click to expand...
Click to collapse
Thank you, i'll try it out. I should have included the fact that im running os x. So yes, i'll execute the flash all from terminal.

"flash_all.bat" will work alternative of typing commands manually? (2014818)

HELP: Bricked P20 Pro - "Getting package info failed"

Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
My Model : CLT-L29C432
Please help..
I have placed down here some more info from fastboot which may could help,,
*****************
PS C:\adb> fastboot oem get-product-model
(bootloader) CLT-L29
OKAY [ 0.004s]
Finished. Total time: 0.005s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.004s
PS C:\adb> fastboot oem get-build-number
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.004s]
Finished. Total time: 0.004s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.020s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.005s]
Finished. Total time: 0.006s
PS C:\adb>
*******************

I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)

Anutter226 said:
I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)
Click to expand...
Click to collapse
ATt least your TWRP is working, .. even it is useless.. looking forward for solution..

alfrqan said:
Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this .
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
Please help..
Click to expand...
Click to collapse
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.

You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches

After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)

I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn

KennyDumah said:
I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn
Click to expand...
Click to collapse
So you should just flash stock boot.img to be able to boot to os again....

Anutter226 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.

side_flip15 said:
You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches
Click to expand...
Click to collapse
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..

dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
Sounds interesting. will give it a try.

side_flip15 said:
So you should just flash stock boot.img to be able to boot to os again....
Click to expand...
Click to collapse
I download several update.zips and up pack them and so far i could not find this file in :boot.img:

dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
can i know which TWRP you have used here?

YellowSnowman23 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I have tried this without success. I used to flash imgs by "fastboot flash system xxx.img"

alfrqan said:
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..
Click to expand...
Click to collapse
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.

side_flip15 said:
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.
Click to expand...
Click to collapse
I tried a lot of them.. but still not able to boot into TWRP

alfrqan said:
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.
Click to expand...
Click to collapse
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]

alfrqan said:
can i know which TWRP you have used here?
Click to expand...
Click to collapse
Always unofficial, it's the most functional

Update>>
I have visited Huawei service center in Madrid and they said "there is no way to repair it, you have to change the motherboard". This is ridicules and I dont believe that.

YellowSnowman23 said:
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]
Click to expand...
Click to collapse
hey,
I have downloaded and extracted many official and found the following files unzip file (update.zip):
for system: SYSTEM.img
command: fastboot flash system SYSTEM.img
Result: error: cannot load 'SYSTEM.img'
For RECOVERY_RAMDISK: RAMDISK.img
command:
Result:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16384 KB)...
OKAY [ 0.369s]
writing 'recovery_ramdisk'...
OKAY [ 0.140s]
finished. total time: 0.509s
conc. still not booting only fastboot commands,,,,,,

Question Flashing Factory Images

I am trying to flash 11.0.0 (RD2A.211001.002, Oct 2021) factory image in windows using the flash-all bat file. I updated my fastboot drivers in windows update and downloaded the latest platforms tools from google's website. I get this error while running the bat file.
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 3.254s
Press any key to exit...
Any idea as to why?

Do you have your platform-tools folder in your PATH Variables?

kingofnice said:
Do you have your platform-tools folder in your PATH Variables?
Click to expand...
Click to collapse
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?

On Windows 10, type in the search bar "system environment variables" and open that settings menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click on Environment Variables...
Edit
Add the location to your folder. Press Ok and Apply if you need.
Now try your adb and fastboot commands from a new command prompt window. They should be working from any directory you are using command prompt in.
I think that is why your flash failed, though I don't know. It sounds like it couldn't connect because it couldn't utilize fastboot to find a device/partition.
Test "fastboot devices" and if you see your device try flashing again. Also, "fastboot -w update image-xxx-xxx.zip" is in the flash-all bat. remove "-w" to stop it from wiping data. That's your call as you might need a fresh install.

Klimon5 said:
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
Click to expand...
Click to collapse
Did that help at all?

kingofnice said:
Did that help at all?
Click to expand...
Click to collapse
I ended up using Windows 10 to adb sideload the most recent android 11 OTA zip from google. I performed a factory data reset in recovery after I booted into the update first. I then was able to unlock the bootloader, re-enable the oem unlocking setting in dev options, & install the official lineage os recovery and rom for barbet. I will try your steps and see if I can flash a factory image. When I had my nexus 6p, I removed the -w prefix and immediately rebooted into recovery to factory data reset. It then booted just fine. For me I think that my platforms tools for Ubuntu are out of date.
I ran this command on my ubuntu machine.
$ adb version
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5ubuntu2
The lineage os installation instructions warns about issues with out of date platform tools.
Install LineageOS on barbet | LineageOS Wiki
wiki.lineageos.org
"Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
I want to try this on linux manjaro on my laptop. The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.

Klimon5 said:
For me I think that my platforms tools for Ubuntu are out of date.
The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Click to expand...
Click to collapse
This is the problem. Using outdated Platform Tools causes problems. Latest release is 31.0.3, Aug '21. Many other users have run into similar problems because they were using outdated Platform Tools.

General 📌 [Shared] TWRP by skkk

A12/A13
-----------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
or
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
--------------------------------------------------------------------------------------------------------
REC VERSION
Install with TWRP or fastboot***
flash recovery_ab twrp.img(cmd)
or
./flash recovery_ab twrp.img(Power Shell)
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
---------------------------------------------------------------------------------------------------------
DOWNLOAD
REC VERSION
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/zeus/
__________________________________________________________________________________
Boot version A13
https://mega.nz/folder/7g0EUAxK#HYD-Wl65HCYKa8PiwSsLKQ
Spoiler: Change the language.

woohooo!

hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.

alpaca2333 said:
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
Click to expand...
Click to collapse
me to

alpaca2333 said:
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
Click to expand...
Click to collapse
bootloader must be unlocked
What command did you use?

NOSS8 said:
bootloader must be unlocked
What command did you use?
Click to expand...
Click to collapse
i unlocked bl, and i even had magisk installed, maybe magisk's the reason?
command i use:
fastboot flash recovery twrp-3.6.2_12-v3.8.2_A12-zeus-skkk.img

NOSS8 said:
bootloader must be unlocked
What command did you use?
Click to expand...
Click to collapse
flash recovery twrp.img
Bootloader Open

ttistvn said:
flash recovery twrp.img
Bootloader Open
Click to expand...
Click to collapse
You cant flash with this command(A/B partition)
Use this command https://forum.xda-developers.com/t/install-twrp-for-xiaomi-11t-pro.4398007/

NOSS8 said:
You cant flash with this command(A/B partition)
Use this command https://forum.xda-developers.com/t/install-twrp-for-xiaomi-11t-pro.4398007/
Click to expand...
Click to collapse
worked like charm. i was being noob. thx

Working on the a partition
Command :
fastboot flash boot_a twrp.img

Thank you very much
NOSS8​. He works

Working super fine, btw there's no system partition listed on Advance wipe. Any idea? and can i now directly flash miui recovery rom (official) using twrp?

karkiankit said:
Working super fine, btw there's no system partition listed on Advance wipe. Any idea? and can i now directly flash miui recovery rom (official) using twrp?
Click to expand...
Click to collapse
Normally yes

updated today

dont flash TWRP.
TWRP A12 flashing instructions:
1. boot your device in Fastboot mode
2. fastboot boot recovery_finename.img
This will temporary boot your device to TWRP
3. From TWRP go to Advanced and choose "Flash curent TWRP" - this will permanently install TWRP but will overwrite magisk scripts, so root will be lost.
4. Flash magisk from TWRP - this will fix root.

Very nice.....waiting for updated zip rom....

updated today

new update...very nice working..

new update 3.6.2_12-v3.9 working fine no issues as of now

trinadhchinna7 said:
new update 3.6.2_12-v3.9 working fine no issues as of now
Click to expand...
Click to collapse
Me too