I'd hate to be a pain as I know newcomers don't seem to be welcome here. But it wouldn't let me post in the thread for the rom that I have a question for. It wouldn't even let me post in the relevant sub-forum. So sorry.
Anyway I have an XT890. It has an unlocked bootloader. I have a custom recovery installed. It is an EU device.
I tried to install the "Moto JB 4.1.2" rom. As we know, it doesn't work with EU devices.
My question- is it the EU OTA rom that it's incompatible with or the device itself? If I sbf a non-EU OTA rom to my phone, will that rom work?
I remembered to format /data and /system just like the installation instructions said to do, just to make sure it does indeed not work. I even formatted /cache and all the other ones. It went into a bootloop just like the description said would happen so I restored the backup that I made.
It's a shame since that looks like an awesome rom.
Veraster said:
I'd hate to be a pain as I know newcomers don't seem to be welcome here. But it wouldn't let me post in the thread for the rom that I have a question for. It wouldn't even let me post in the relevant sub-forum. So sorry.
Anyway I have an XT890. It has an unlocked bootloader. I have a custom recovery installed. It is an EU device.
I tried to install the "Moto JB 4.1.2" rom. As we know, it doesn't work with EU devices.
My question- is it the EU OTA rom that it's incompatible with or the device itself? If I sbf a non-EU OTA rom to my phone, will that rom work?
I remembered to format /data and /system just like the installation instructions said to do, just to make sure it does indeed not work. I even formatted /cache and all the other ones. It went into a bootloop just like the description said would happen so I restored the backup that I made.
It's a shame since that looks like an awesome rom.
Click to expand...
Click to collapse
Can you please upload a screenshot of your system information? Just to know how can i help you
Enviado desde mi XT890 usando Tapatalk 2
Is this what you need?
I see it says EN instead of EU. Maybe it turns out I don't know what I'm doing.
If it is showing the animation of the motorola logo but bootlooping there is a build that apparently allows you to first boot on those cases where the user comes from a weird ROM (it is still unexplained why it works, but you can try it).
OLD FILES FIle: "RazRi_JB_EU_Optimized-2013-Mar-25.bootloop_mysterious_fix.zip"
See if that boots, if that boots fine, once your done first setting it up you could go, format system only, and update to the latest, you could give it a try.
But the cleanest and safest would be to SBF the EU file, and then get the custom recovery installed and finally flash the ROM...
It was showing the Motorola boot animation when I was getting the bootloop on that rom. I tried the "mysterious_bootloop_fix" file in the link. It still made it bootloop. Note that I remembered to format /system and /data. I also formatted /cache.
Next, I will try sbf-ing to official 4.1.2, reinstalling the custom recovery and flashing the latest version of the rom.
Where can I download the 4.1.2 EU sbf file? I haven't been able to find it.
http://sbf.droid-developers.org/smi/CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip
Gesendet von meinem XT890
EDIT: I figured out how to get the sbf to flash. I was using rsd lite version 5.6 which is an old version. I downloaded 6.1.4 and was able to sbf to 4.1.2. I am currently trying to install the custom rom.
Edit: Alright. I tried flashing the latest version. It caused a bootloop. I then tried flashing the "mysterious bootloop fix" one. It made a bootloop too. I used the sbf that HSD-Pilot gave me the link to.
I attached a screenshot of my system info.
Any ideas? I'm REALLY close to getting it...
............\/ Disregard all that \/
OK so now I have a noob question. In the the sbf tutorial thread, it says:
- download fastboot file you need from here or here
- extract it in a folder, you have a XML file here
- run RSD lite
- browse XML file to the empty box
- connect the phone to the pc via usb cable in AP Fastboot mode
- click start button on RSD & be patient to flash the files
Click to expand...
Click to collapse
Is it saying to extract the content of the file "CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip" that I downloaded? When I do this, I get a folder called "CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml". This is not an actual xml file like it said. If I try to select the folder in RSD Lite, it opens the folder. There are several files in that folder as well as a file called "CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml". This file is a selectable xml file and not a folder but it's like 2kb.
Do I open the ~550MB zip file that I downloaded or the 2kb xml file with RSD Lite? Or does this just not work correctly with WinZip?
Edit: While I'm asking noob questions, should I format /system and /data before sbf-ing or does it not matter?
Another edit: I tried flashing the xml file in the extracted folder. It didn't work and under that status on RDS Lite it said "Failed flashing process. Failed flashing process. Unknown fastboot command. (oem); Phone connected"
Selecting the zipped file will result in the same thing after it gets extracted. I also didn't have to restore a backup after the failed flashing. It just boots back up like nothing happened.
Here's what it says in the "File Properties" box:
Filename: CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml
Creation Date: 01/18/2013 03:30:06
File size: 1462
Sofware Version: XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B
For Phone Model: Scorpion Mini I EMARA
Click to expand...
Click to collapse
Yet another edit: Will I get bricked if I just flash an OTA update via cwm? It doesn't work on the stock recovery.
Hi,
i have a European Razr I with locked bootloader on JB OTA update, stuck on boot loop. The bootloader can not be unlocked due to the JB update. That means I cant flash anything over 100mb.
I have tried to flash with RSD some ROMs that are under 100mb and recommended for Razr I on JB.
They are (81.5.31002-81.5.39001.XT890.Retail.en.GB, 81.5.32002-81.5.40002.XT890.Retail.en.EU), both Zip files.They decompress in RSD but error out with following msg
"Please check input file. Either XML format is wrong or image files associcated is missing".
I cant find any ROMs 100mb or less with an XML file in it. The bigger ROMs do but they error in the flashing process at step 8 of due to the file size bigger than 100mb.
I also tried to install the 100mb rom in fastboot mode from external sd card but got the error msg below.
Can it be flashed this way or only through RSD?
I am hoping there is a custom ROM for a phone in my situation that can be flashed?.
You cannot flash Roms with RSDlite, only original firmware - for Roms you would also need an unlocked bootloader.
Flash Blur_Version.91.2.26001.XT890.Retail.en.EU via RSDlite 6.1.5, don't try to flash the ICS versions of the EU Retail, they will probably brick your phone.
Thanks but this will not work as one of the files is over 100mb.
I read some where there was a way to edit the xml file to over ride this,is that true?
RSDlite 6.1.5 can flash in 100mb steps, its working 100%. Just download the zip, decompress and flash.
It worked!! . Thanks so much. I was using an older version of RSD.
I tried all versions of RSD Lite but still getting 'Please check input file. Either XML format is wrong or image files associcated is missing' with 81.5.39002-91.2.26001.O2.en.DE 4.0.4-4.1.2 found here: http://forum.xda-developers.com/showthread.php?t=2028814.
I went through lot of threads and there was something about a specific xml file, but I didn't find out where can I get it. Also every secon URL is not available any more so it is hard to try something...
Can someone help me?
I've tried so many things to fix this and it wont work. i tried flashing stock rom/recovery with mi flash tool and it got up to 20 mins and i just quit it. i was trying to install a rom so it has no os and boots straight to fastboot mode.
HeliosV said:
I've tried so many things to fix this and it wont work. i tried flashing stock rom/recovery with mi flash tool and it got up to 20 mins and i just quit it. i was trying to install a rom so it has no os and boots straight to fastboot mode.
Click to expand...
Click to collapse
I also cant get into recovery, i hold the buttons down but it brings me back to fastboot
HeliosV said:
I've tried so many things to fix this and it wont work. i tried flashing stock rom/recovery with mi flash tool and it got up to 20 mins and i just quit it. i was trying to install a rom so it has no os and boots straight to fastboot mode.
Click to expand...
Click to collapse
Use bat file present in extracted tgz rom instead of miflash. First install drivers
Remember one important thing among those TWRP in Mi9 : Never wipe system partition before rebooting your phone !! That means : You must flash ROM if you wipe system partition before rebooting your phone.
Before chosing rom in mi flash extract it on desktop then chose it in mi flash
HeliosV said:
I also cant get into recovery, i hold the buttons down but it brings me back to fastboot
Click to expand...
Click to collapse
After you've extracted the tgz file twice to reveal a folder that contains the images folder, put that main folder in root of C: drive on PC and point mi flash to it. Let us know how you get on...
Thanks guys! I eventually fixed it, i must of downloaded the wrong rom file
HeliosV said:
Thanks guys! I eventually fixed it, i must of downloaded the wrong rom file
Click to expand...
Click to collapse
Hello! I'm very new at those things, it s actually the first time I tried something like this and maybe it s my fault ahahaha... but i was about to root my xiaomi and then the phone get stuck in fastboot mode.. nothing works, like press the bottons etc, and with a terminal i can t reboot fastboot, it says no valid command. I m so so new in this that i have no idea what i can do. I think my error was with the wipe thing . Do you know something i can try ?
As stated above, I am trying to unbrick my Axon M with the firehose provided by Unjustified Dev. and firmware from deadman96385. When I tried using QFIL, even placing everything in its own directory on the root of the PC with no spaces in file names, it would get stuck when flashing. And whenever I tried to use MiFlash, I would get the error:"couldn't find flash script" when I selected the firmware folder. Any help is much appreciated.
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
ehsan96696 said:
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
Click to expand...
Click to collapse
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
boot
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
ff7cloudsnobody said:
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
Click to expand...
Click to collapse
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Drakosha said:
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
Click to expand...
Click to collapse
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
ehsan96696 said:
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Click to expand...
Click to collapse
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
Click to expand...
Click to collapse
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
Click to expand...
Click to collapse
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
ehsan96696 said:
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
Click to expand...
Click to collapse
Weird but awesome that it worked
Drakosha said:
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
Click to expand...
Click to collapse
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Root
ff7cloudsnobody said:
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Click to expand...
Click to collapse
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Drakosha said:
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Click to expand...
Click to collapse
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
ff7cloudsnobody said:
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
Click to expand...
Click to collapse
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Drakosha said:
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Click to expand...
Click to collapse
Doing the unpatched boot with security removed works, so this must be something that is in a subsection of boot.img other than build.prop. I'll have to look at what magisk changes, see what other locks ZTE has inside the image, and go from there.
edit: at this point, this conversation is not related to the post. If I make a breakthrough then I will make a new thread.
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Hi all
I need Loader please for this AT&T Z999 model
the one I found in this publication did not work for me : https : // forum.xda-developers.com/axon-m/how-to/rom-zte-axon-m-stock-firmware-firehose-t3909847
I just wish this method would work to update the AT&T Axon M from B30 to B37.
tj65 said:
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Click to expand...
Click to collapse
Are you able to provide the firehose that you used?
I tried the B37 and the firehost from this link https://forum.xda-developers.com/t/rom-zte-axon-m-stock-firmware-firehose.3909847/
along with the miflash from this link https://forum.xda-developers.com/t/edl-a2017-a2017u-emergency-dl-mode-twrp-unlock-upgrade.3553514/
But it always fails.
It will simply give an error of "Cannot receive hello packet"
then it will eventually go to the error of
"Object reference not set to an instance of an object."
I am using an AT&T Z999 that is on B30, and I am trying to get it updated to B37 (currently not looking to root or anything else, just want to update without having to have active AT&T service.
Edit: I think I found the right one. https://forum.xda-developers.com/t/...-unofficial-twrp-recovery-for-axon-m.3959314/
So far, copying that firehose file into the B37 folder seems to be allowing it to flash.
GUYS Please help I'm Scared as hell, my K20 is stuck in fastboot mode and I don't know what to do! So here is what I did, I heard about the K20 Pro 81hz refresh rate Mod and the android 10, I couldn't find twrp for k20 so i decided to flash k20 pro's twrp (which probably was a big mistake!), I don't exactly remember what exact files i was flashing! I remember after flashing few files or just the twrp of k20 pro (i dont remember exactly) my phone was stuck in fastboot and is still now if i restart or go to recovery or anything it just leads me back to fastboot screen. I flashed android 10 recovery rom via fastboot,which i was not supposed to do, i didn't know the difference b/w the fastboot and recovery rom at that moment, but when i did i downloaded another rom but a stock rom for k20 fastboot variant I don't remember where I downloaded all the files but I downloaded the recovery rom from : https://www.xda-developers.com/download-miui-11-beta-now-for-13-xiaomi-devices-changelog/ and I downloaded the stock rom from : https://rootmygalaxy.net/redmi-k20-and-k20-pro-stock-firmware/ and I downloaded twrp recoveries from other sites, well I guess this is not important where i downloaded these. But after I try to flash the K20 Stock Rom by Mi Flash Tool (keep in mind i tried to flash the android 10 rom with mi flash tool also and that too by any all settings like clean all , keep data, clean all lock, i was just trying everything to get my phone to work! ) So then it gave me error of mismatching device so i searched on youtube to fix this error and tried it but still it wasn't flashing, then I thought maybe when I was trying to flash the android 10 rom many times I might have locked the boot loader, so i used the mi unlocker tool to see, i clicked on unlock it said it started the process, 3 step process of verifying device ,unlocking ,and done but it showed an error on the verifying device it said "can't get info, connect again ". This scares me have I locked the bootloader and now is there no way to unlock it or what??? I need your guys help please tell me what Rom I have to flash or what steps I have to take to get my phone working again! Please
I have a K20 Indian Variant, oh and yeah my bootloader was unlocked before I started to do all of this. I know what I have written might be confusing But PLEASE HELP ME!
Edit: and I also tried to flash the boot by getting boot image from android 10 rom, basically i just flashed randomly...
I also saw a few videos about the edl mode, i tried to get into edl mode and I got into edl mode so If there is a way to flash rom using edl mode do tell me
Edit: And I also think maybe the rom isn't flashing because I might have got the global rom or something can anyone send link to Indian K20 Stock Rom?
Edit: I just downloaded the k20 indian rom the correct one but when i flash through mi flash it says success in 1 second time that means my bootloader is locked but now ALL i need from YOU GUYS is to tell me How to Unlock it, I can't unlock it via Mi Unlock Tool, is there another method?
itzabhi said:
GUYS Please help I'm Scared as hell, my K20 is stuck in fastboot mode and I don't know what to do! So here is what I did, I heard about the K20 Pro 81hz refresh rate Mod and the android 10, I couldn't find twrp for k20 so i decided to flash k20 pro's twrp (which probably was a big mistake!), I don't exactly remember what exact files i was flashing! I remember after flashing few files or just the twrp of k20 pro (i dont remember exactly) my phone was stuck in fastboot and is still now if i restart or go to recovery or anything it just leads me back to fastboot screen. I flashed android 10 recovery rom via fastboot,which i was not supposed to do, i didn't know the difference b/w the fastboot and recovery rom at that moment, but when i did i downloaded another rom but a stock rom for k20 fastboot variant I don't remember where I downloaded all the files but I downloaded the recovery rom from : https://www.xda-developers.com/download-miui-11-beta-now-for-13-xiaomi-devices-changelog/ and I downloaded the stock rom from : https://rootmygalaxy.net/redmi-k20-and-k20-pro-stock-firmware/ and I downloaded twrp recoveries from other sites, well I guess this is not important where i downloaded these. But after I try to flash the K20 Stock Rom by Mi Flash Tool (keep in mind i tried to flash the android 10 rom with mi flash tool also and that too by any all settings like clean all , keep data, clean all lock, i was just trying everything to get my phone to work! ) So then it gave me error of mismatching device so i searched on youtube to fix this error and tried it but still it wasn't flashing, then I thought maybe when I was trying to flash the android 10 rom many times I might have locked the boot loader, so i used the mi unlocker tool to see, i clicked on unlock it said it started the process, 3 step process of verifying device ,unlocking ,and done but it showed an error on the verifying device it said "can't get info, connect again ". This scares me have I locked the bootloader and now is there no way to unlock it or what??? I need your guys help please tell me what Rom I have to flash or what steps I have to take to get my phone working again! Please
I have a K20 Indian Variant, oh and yeah my bootloader was unlocked before I started to do all of this. I know what I have written might be confusing But PLEASE HELP ME!
Edit: and I also tried to flash the boot by getting boot image from android 10 rom, basically i just flashed randomly...
I also saw a few videos about the edl mode, i tried to get into edl mode and I got into edl mode so If there is a way to flash rom using edl mode do tell me
Edit: And I also think maybe the rom isn't flashing because I might have got the global rom or something can anyone send link to Indian K20 Stock Rom?
Edit: I just downloaded the k20 indian rom the correct one but when i flash through mi flash it says success in 1 second time that means my bootloader is locked but now ALL i need from YOU GUYS is to tell me How to Unlock it, I can't unlock it via Mi Unlock Tool, is there another method?
Click to expand...
Click to collapse
I found the solution all i had to do is change the rom folder to C:// and it worked!
Its not working for me plz help me
itzabhi said:
I found the solution all i had to do is change the rom folder to C:// and it worked!
Click to expand...
Click to collapse
i dont know what is wrong but falsh is getting completed in 1 second.
roushancool said:
i dont know what is wrong but falsh is getting completed in 1 second.
Click to expand...
Click to collapse
Bro first of all u need to edit the flashall commands with the notepad and then u should put the rom folder on the desktop and put the mi flash tool on a separate folder also on the desktop if u want me to tell u what to edit just message me and i will tell u how ?
itzabhi said:
I found the solution all i had to do is change the rom folder to C:// and it worked!
Click to expand...
Click to collapse
Bro first of all put the rom in a folder on the desktop (one folder and the files in it ) (not folder inside a folder)
Next copy the flashtool folder to the desktop also
Next edit the flash_all.bat and remove the commands up and keep only commands that starts with (fastboot)
And save.
Then choose the folder and then flash and make sure u choose only (clean all) and not (clean all and lock) from below goodluck bro hope the picture will make you understand