Database Develop

[Q] I can't boot into recovery!

I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?

top_bunk said:
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
Click to expand...
Click to collapse
You probably have SLCD screen. Then you have to use Amon_RA 1.8.0.1 recovery which is only one (as far as i know) intended for SLCD screens.

Ah okay. Is there an easy way for me to flash that? Not really comfortable with the SDK approach...
Thanks for the fast reply btw

If you don't have unlocked bootloader you have to use flash_image binary to flash new recovery because amon_ra 1.8.0.1 recovery don't show up in rom manager.
Download it from here http://cyanogen-files.carneeki.net/flash_image.zip. Put it in root of sdcard as well as 1.8.0.1 img file and in phone terminal type
1) cd /sdcard
2) flash_image recovery 1.8.0.1.img (replace with name of img file)

houmles said:
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
Click to expand...
Click to collapse
I'm getting flash_image: not found
I've double checked the file name is correct

Did you unpack the zip file? There is only one file named exactly "flash_image" so you should not getting not found error if you have that file in root of sdcard and you are at /sdcard in terminal.
Send me output of "ls -la" command from /sdcard.

----rwxr-x system sdcard_rw 17638414 2010-09-10 20:20 gapps-hdpi-20100817-signed.zip
----rwxr-x system sdcard_rw 70864056 2010-09-10 20:22 update-cm-6.0.0-N1-signed.zip
----rwxr-x system sdcard_rw 11818685 2010-09-10 21:05 FRF50-radio-4_06_00_12_7.zip
----rwxr-x system sdcard_rw 4145152 2010-09-10 23:10 recovery.img
----rwxr-x system sdcard_rw 26172 2009-10-03 18:07 flash_image

Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>

Jack_R1 said:
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Click to expand...
Click to collapse
./flash_image: permission denied

top_bunk said:
./flash_image: permission denied
Click to expand...
Click to collapse
Weird. Try:
1) su
2) cd /sdcard
3) chmod +x flash_image
4) ./flash_image recovery file.img

Well, that's because SD card isn't a good place to put flash_image. Permissions inherited from FAT32 are awkward and aren't changeable. But there's a way around it.
Do the following sequence: run Terminal, enter the following commands:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>

houmles said:
3) chmod +x flash_image
Click to expand...
Click to collapse
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.

Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
It didn't work...
Jack_R1 said:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
Click to expand...
Click to collapse
cp: not found

Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.

Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
I just thought of the same thing
Installing Astro now (it's a new phone no apps!)

Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
ah, didn't know that
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
As Jack wrote, you can only copy the file manually with some file explorer.

houmles said:
As Jack wrote, you can only copy the file manually with some file explorer.
Click to expand...
Click to collapse
It won't let me copy it... I've tried Astro and ES.

Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.

If you have adb connection you can try this:
unpack zip I sent you and recovery.img to root of c:\ for example .. then:
1) adb push c:\flash_image /data/flash_image
2) adb push c:\recovery.img /data/recovery.img
3) adb shell
4) chmod 755 /data/flash_image
5) /data/flash_image recovery /data/recovery.img

Jack_R1 said:
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
Click to expand...
Click to collapse
Lots
...but it's done! Thanks a lot for the help guys
I've gotta be up in a few hours so I don't have time to install a ROM and faff about, but hopefully it will be all good from here on in.
Cheers again!!

[Q] Galaxy S big problem.

Hi,
By my mistake i delete recovery file in system directory, and now my phone doesnt start up only wait at galaxy S logo.
What can i do?

what rom was you running.
what if the full directory of the file you deleted.
As you can push it back with adb if someone else has it.

I had froyo2.2, and directory was: system/bin/ recovery
i want to change it with diferent recovery file but i see now that file was only deleted and not replaced xD
so i am without recovery option and phone doesnt start.
I can go to download mode.

denesch said:
I had froyo2.2, and directory was: system/bin/ recovery
i want to change it with diferent recovery file but i see now that file was only deleted and not replaced xD
so i am without recovery option and phone doesnt start.
I can go to download mode.
Click to expand...
Click to collapse
if you still have the recovery file you wanted to put there.
plug your phone into the computer and try
adb devices if something pops up your in luck
move the recovery file to your tools folder (in the sdk)
then use
adb push recovery /system/bin/

i have file on phone under Download folder. how can i get it and how can i copy back file.
my phone is detected by computer and i can acess it with odin.

denesch said:
i have file on phone under Download folder. how can i get it and how can i copy back file.
my phone is detected by computer and i can acess it with odin.
Click to expand...
Click to collapse
To copy a file or directory (recursively) from the emulator or device, use:
adb pull <remote> <local>
To copy a file or directory (recursively) to the emulator or device, use:
adb push <local> <remote>
example:
adb push foo.txt /sdcard/foo.txt

ttf said:
To copy a file or directory (recursively) from the emulator or device, use:
adb pull <remote> <local>
To copy a file or directory (recursively) to the emulator or device, use:
adb push <local> <remote>
example:
adb push foo.txt /sdcard/foo.txt
Click to expand...
Click to collapse
Sry but i am noob here
when i try to connect with adb says that no device found
but odin works fine.

ok we SOLVED with new firmware.
CLOSE thread.
And big thx to iammodo

[Q] Cant flash ClockworkMod Recovery (cannot open for read: No such file or directory

When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.

First off, before someone else says it, you shouldn't start a new thread for something we already have a topic for. But anyways,
Sounds to me like recovery.img never got pushed to /data. Not sure if its a typo in your post but 'adb push recover.img/data' should be 'adb push recovery.img /data'. The space is important. On your phone use a root file explorer and go to your /data partition and see if recovery.img is there. You may need to either change permissions for /data or just put recovery.img on your sdcard and move it to /data with a root explorer.
Sent from my LG-P925 using Tapatalk

Well im sorry im new to this kind of thing, i didnt want to make anyone mad i just wanted some help and i apologize if ive ticked somone off. How would i change the permissions for the data? And could you tell me how to use the root explorer to put the recovery image in the right place? Again i appreciate any help you can offer.

Is recover.img in the same folder as adb? Because the instructions assume your recovery.img is in the same folder you are working from. So if you have to cd to your adb folder to use adb then recovery.img should be in that folder as well. Look at your cmd window, whatever directory/ folder it says you are in that is where you should put recovery.img.
If you saw a bunch of commands it means the .img did not go through your command did not work. You dont have the recovery.img in /data either put the file on your sdcard and use a root explorer to move it to /data or try the adb push again, you most likely made a typo or something.
You would put recovery.img on your sdcard through your computer. Open root explorer and navigate to your sdcard, long press on the recovery.img select move, go to/ data on the root of the phone, not the one on either sdcard it MUST be /data not /mnt/sdcard/data or anything like that once there paste file to /data and finish up in adb shell.

Alright i copied the recovery image to the /data folder and finished up in command prompt and everything worked out like it was supposed to. what was i supposed to do next to put it into cwm recovery mode? I held power, volume down, 3d button but i just went into normal recovery mode. then i went to rom manager to try and put it into cwm recovery that way but it just rebooted my phone. And when i went back into the /data folder i couldnt find the recovery image there anymore and i did a search on my root explorer and couldnt find it anywhere.

Hold vol down + 3D + power when lg logo appears release power but keep vol down +3D held down until recovery pops up. If you still don't boot into cwm try flashing recovery.img again. Do NOT use rom manager at all to install cwm on this phone.

Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.

powers.jereme said:
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
Click to expand...
Click to collapse
rm is the command to remove. So yes, recovery.img is supposed to disappear after that command. Put it back on /data and run the whole process from the CWM thread again making sure you do every step. Sounds like you may have accidentally skipped a step.
Sent from my LG-P925 using Tapatalk

Double post.

Ugh...keep selecting quote instead of edit on Tapatalk...Triple post...

Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks

powers.jereme said:
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
Click to expand...
Click to collapse
Yea just do it all again. Worst case is you flash cwm back over cwm
Sent from my LG-P925 using Tapatalk

I got it to work Urabewe was right i just needed to put the recovery image in the correct folder and everything worked perfect. Thanks guys.

Lg G flex T-mobile D959 soft bricked

Hey guys, any help you could give me with my problem would be great. Basically, i tried to flash cyanogenmod 11 unofficial on my d959 g flex and it didn't work. unfortunately, i had created backups with twrp recovery, but had cwm on at the time and no cwm backup. I try to send the stock 1.5gb zip over with adb push or adb sideload, but neither is ever successful(stops after 1gb). basically need a way to flash a twrp.zip in cwm to restore my phone recovery to twrp, then I can restore my phone using my twrp backup. Any ideas? I've got the twrp.img file that the Freedom flex app downloaded before, and found a recoveryinstaller.zip that i have put it in and have thought about flashing that to my phone, but don't want to brick it further.

I lost where you replied to what I said about the otg cable but you're halfway right.
Try this.
Download Flash_img. and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
This will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ twice.
Here is the "bumped" twrp.img
https://docs.google.com/file/d/0B2OabWtEBQcpVjZGb2ppT083OGs/edit?usp=docslist_api
Here is the flash.img that you need to extract on your PC
https://docs.google.com/file/d/0B2OabWtEBQcpcmowamtnUVY1YU0/edit?usp=docslist_api
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
If you can get into download mode try opening cmd and
Fastboot flash recovery " then drag and drop the twrp.img that I just posted the link for here with out the quotations". It doesn't matter what you name it in this case. This is the easiest way to me.

Mi Flash Error error: Not catch checkpoint (\$fastboot -s .* lock),flash is not done

Been getting this error after trying to flash to my k20 pro, removing the checkpoint just makes it instantly flash and nothing changes. Any help?

WaiAi said:
Been getting this error after trying to flash to my k20 pro, removing the checkpoint just makes it instantly flash and nothing changes. Any help?
Click to expand...
Click to collapse
I am facing same problem, but no problem there, phone boot up after flash.

Ignore it. To get it done without this error you have to lock your bootloader...

thiagodark said:
Ignore it. To get it done without this error you have to lock your bootloader...
Click to expand...
Click to collapse
Nothing happens still, just says flash done and phone stays in fastboot loop

I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.

SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
You have saved my life sir, days of surfing the internet with no solution, you have saved me a new phone.

SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thank you very very very much. ( I should stop messing with this stuff )

I also had to fiddle around until I figured it out. I don't understand why all instructions are based on the Mi Flash tool. It seems to be just a GUI for fastboot, optimized for Xiaomi devices.
If you download fastboot and set it as a PATH system variable, you can run the scripts from the rom folder with one click. Super easy and you never have to deal with the "Mi Flash tool" again.

SageDroid said:
I also had to fiddle around until I figured it out. I don't understand why all instructions are based on the Mi Flash tool. It seems to be just a GUI for fastboot, optimized for Xiaomi devices.
If you download fastboot and set it as a PATH system variable, you can run the scripts from the rom folder with one click. Super easy and you never have to deal with the "Mi Flash tool" again.
Click to expand...
Click to collapse
I got stuck in a fastboot loop again have ran into a few different issues, first of which, is that I have a mismatching image or device, this doesn't always show at the start, sometimes it stops half way through and when I start it back up again I'm met with that. Other times it starts with that and once I remove that part of the script it does some stuff and stops on deleting boot. I'm pretty sure I've been using the right roms, or I should have at least once by now. Before it got into a fastboot loop I had the xiaomi eu rom and I flashed the vendor that I was told to flash with the rom, does either of those have anything to do with it?

Call the script from the terminal and post what the output is.
You can only execute the script directly if you have defined "fastboot" as a global PATH variable. You can verify this by checking that you can call "fastboot devices" from anywhere without getting an error message.

Niaz
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
thanks a lot brother

SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
It works thank you!!! :victory::victory:

Genius thanks!
SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thank yoou!!!!

SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thank you so much, you saved me of a lot of stress. It was literally the only thing that worked after searching all over the internet. You literally saved me of hundreds of dollars, money that in this current pandemic situation, I do not have.
Thank you very. very much.

Thank's
Thank you! Very much! After long hours of searching you're solution is the only one that worked.

SageDroid said:
I had the same problem. Forget the Mi Flash Tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the Mi flash tool and navigate to the subfolder "Source/Third Party/Google/Android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
Thanks a lot for this method!!! You saved me from losing all my data by flashing all except storage.

Thank you really
sagedroid said:
i had the same problem. Forget the mi flash tool. Just run the script "flash_all.bat" in the folder of the unzipped rom and wait until it finished.
If you haven't installed fastboot, do the following:
1. Go to the folder where you unzipped the mi flash tool and navigate to the subfolder "source/third party/google/android".
2. Copy the entire content (including fastboot.exe) and paste it into the folder where you unzipped the rom (and where the script is located).
3. Open a terminal window in the folder and execute the script "flash_all.bat".
4. Wait until the script has run.
Click to expand...
Click to collapse
you are god, i was really nervius!

This is bound to the latest MiFlash tool. You can skip it by getting into "Configuration" and then erasing that line at "Checkpoint". Hit "OK" and you're good to go.

Try copiying the rom zip (just folder that is 1 level back to images folder) to root of C drive and try installing the rom. It worked for me.. Flashtool doesnt like subfolders..
Sent from my Redmi K20 Pro using Tapatalk

abees said:
Try copiying the rom zip (just folder that is 1 level back to images folder) to root of C drive and try installing the rom. It worked for me.. Flashtool doesnt like subfolders..
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I am having a hard time using the cmd method with the error "flash_all.bat not recognized"
But i tried your method and it works . Thank you so much