After flashing the latest fastboot rom with MiFlash, my Redmi Note 9s (curanan EEA) ended up in a bootloop (reboot with vibration every few seconds). Flashing other fastboot roms did not help, flashing with TWRP (all 3 different) always ended up in an 'error 7' and was not successful.
Finally I was able to revert to the stock rom using XiaoMiTool V2 by Francesco Tescari. Ihad my Note 9 S connected via USB in the 'MiManager' mode of the original recovery. XiaoMiTool was able to detect it (in sideload mode), automatically downloaded and flashed the correct ROM. After that, it started without problems.
This might help some people in similar situations. Even returning to stock is much easier using this tool, since you don't have to look for the right ROM by yourself.
Thanks a lot. i got the same issue and copuld fix it this way.
Also many thanks from my side, had a bootloop and tried to install so many roms without succes. this tool rescued my phone !
Hi, I had used this tool before. But now its website is down. Is this tool still available?
Related
Hi y'all!
I'm really having trouble flashing an official stable rom on my device. The rom archive is miui_HM3_V7.3.2.0.LHPCNDD_6a5e1bc33c_5.1.zip.
I downloaded it and copied it to a folder (downloaded_rom) on the internal storage of my redmi 3. After selecting it in the updater app I get asked whether it's OK to delete all data, because the rom I'm updating to is older than the one installed. My phone's miui version is MIUI 77. Stable 77.1.1.0 (LHPCNCK). The doble 7s seem odd to me and may be part of my problem (I bought the phone like that). Then, the device is rebooting and I can see some kind of progression bar for a couple of seconds on the botton of the screen but then it just reboots into android and nothing changed
I also tried to flish it via Mi PC suite. Here, after connecting the device in fastboot mode, I got the message that my device isn't supported.
I also believe that the bootloader is locked and I already got the "permission" from xiaomi to unlock it but I had no luck with this either. The Mi unlock tool is telling me, that the "current account is different from the account info on the device" which wasn't the case after I double checked.
Am I missing something here?
kind regards
lunatikk
yes.
because you are currently in modified rom (rom supplier or seller, etc, etc) you cannot update or do anything about it
flash the official rom using miflash method
after that you can update using updater program
Ice Zodiac said:
yes.
because you are currently in modified rom (rom supplier or seller, etc, etc) you cannot update or do anything about it
flash the official rom using miflash method
after that you can update using updater program
Click to expand...
Click to collapse
I'll try that and report back. Thanks!
Okay, finally I managed to flash my phone with the newest miui.eu rom. What I did was:
- Flashing the official Xiaomi Rom (MiFlash package) via MiFlash (1st try in Win32 wasn't working. 2nd try on Win64 did the job)
- I had to update to the newest official stable OTA, because somehow, I wasn't able to unlock my bootloader with the older version.
- I unlocked the bootloader using the MiFlashUnlocker.
- Updated to the official MIUI 8 dev rom using updater app on my phone
- On dev rom I granted root acces to flashify and flashed the twrp recovery image on my device (which gets wiped from my device every time I reboot - anyone knows why??)
- Reboot into recovery and flash the MIUI.eu zip which is now running on my device.
Thanks for the help guys!
Hi.
I am having the same problem, with pre-installed rom: MIUI 77.1.1.0 Stable. The updater app obviously doesn't work (now i know why) and the MiFlash software doesn't seem to work either. It doesn't recognise the phone, browsing to the downloaded rom does nothing. Am i missing something?
Update, it now recognises the phone, but miflash is saying it can't find the file specified (0x80070002: Execute flash_all.bat)
Thanks for any assistance you can give.
Update 2. Just found out you need a different version of the Rom for fastboot. available from http://en.miui.com/a-234.html for anyone searching.
Okay so Miflash began the process when i had the Fastboot rom, but failed at about 2 percent as the device is locked.
Although i have permission the Mi unlock tool won't unlock my phone as it says the accounts don't match that on the phone, although i have quadruple checked them.
Research suggests it might be a problem with the custom rom on my phone, or that i need to be on the China Dev rom to unlock?
But i can't flash the China Dev Rom!!!
Is there any way to get my device to stock rom?
Sorted.
For the benefit of anyone searching, i followed the instructions here: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=242867&pid=4510751
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
x23are said:
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
Click to expand...
Click to collapse
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
GENiU5 said:
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
Click to expand...
Click to collapse
tnx for reply but my problem is i cant flash.
my bootloader is locked and i cant flash fastboot rom.
therefor i must use edl mode or updater app but both of them don't work as a said in first post.
You don't need an unlocked BL to flash official fast boot miui ROMs
GENiU5 said:
You don't need an unlocked BL to flash official fast boot miui ROMs
Click to expand...
Click to collapse
mi flash show me : bootloader unlock in flashing process
x23are said:
mi flash show me : bootloader unlock in flashing process
Click to expand...
Click to collapse
You may try the steps on this link http://en.miui.com/thread-235865-1-1.html
Skip the EDL thing and go directly to the part where they explain how to use the miflash tool to flash a fastboot ROM
I should have asked this first... what's the state of your phone right now? Does it boot, stuck on boot loop, or are you able to boot into some ROM.
maybe u have a vendors rom, flash the fastboot rom using edl
finally a downloaded adb 1.4.3 and installed it and i flashed dev rom in EDL mode.
but now i have some questions:
can i change kernel with locked bootloader?
if i change kernel does fingerprint work?
You just dont have proper drivers installed im 100% sure, else it would go via edl
Hehe was right������
And why dont you ask for official unlock approval? Its approved in less than a day, anyone saying otherwise have old news
Or you can always use a method in this forum...
This friday I got my tablet(lenovo tab 2 a7-10f). Yesterday I decided to install better rom on it. I rooted my device and installed twrp recovery. Unfortunally I didn't quite realize the importance of making back up and the fact that you can't flash this:
https://forum.xda-developers.com/android/software/rom-orionlp-v1-8-lenovo-tab-2-a7-10f-t3480918
on android 4.4. My device loops "lenovo powered by android" screen. I can boot it into TWRP recovery. I have been googling today for a whole day and I havent find any rom to flash it. I tried this:
https://forum.xda-developers.com/an...-stock-lollipop-5-0-roms-lenovo-tab2-t3418835
and I think thing like this for a KiKat (through twrp, probably that's why it doesnt work) .I couldn't quite boot it into fastboot and I can't use sp flash propely or it just simply doesn't work for me. Please help me to find any rom to flash it from twrp, since I am too stupid to do anything different way.
In short it loops, I can boot it to twrp, I just want to unbrick it. The ultimate goal is to propely install this *first link*
Thanks in advance!
maykapal said:
This friday I got my tablet(lenovo tab 2 a7-10f). Yesterday I decided to install better rom on it. I rooted my device and installed twrp recovery. Unfortunally I didn't quite realize the importance of making back up and the fact that you can't flash this:
https://forum.xda-developers.com/android/software/rom-orionlp-v1-8-lenovo-tab-2-a7-10f-t3480918
on android 4.4. My device loops "lenovo powered by android" screen. I can boot it into TWRP recovery. I have been googling today for a whole day and I havent find any rom to flash it. I tried this:
https://forum.xda-developers.com/an...-stock-lollipop-5-0-roms-lenovo-tab2-t3418835
and I think thing like this for a KiKat (through twrp, probably that's why it doesnt work) .I couldn't quite boot it into fastboot and I can't use sp flash propely or it just simply doesn't work for me. Please help me to find any rom to flash it from twrp, since I am too stupid to do anything different way.
In short it loops, I can boot it to twrp, I just want to unbrick it. The ultimate goal is to propely install this *first link*
Thanks in advance!
Click to expand...
Click to collapse
There is a way to flash a now rom with SP flash tool although you can't use sp flash tool propely.
You must open the lid of the tablet and unplugin the battery
(to unpluin the battery simply pull out this)
Then open your SP flash tool, load the scatter file of the rom, press download button, plugin the battery and your pc will start dowloading the rom normally.
Greetings everyone,
THIS IS FOR REDMI NOTE 3 SNAPDRAGON aka KENZO.
HOW IT STARTED: I was on latest stable NOS build 20170815. I mistakenly erased the persist partition, now that's serious, really. Getting to the point, everything was okay except that there was no VoLTE anymore.
WHAT I DID: I formatted the phone, tried restoring backups but unfortunately the EFS partition wasn't backed up earlier. Eventually and ultimately, I flashed the latest official stable MIUI 9, Android 6.0.1 Everything was back to normal, yay! Or not. The custom RECOVERY i.e. REDWOLF RECOVERY had been replaced by stock MIUI RECOVERY. I've tried Kingo, Queeno, ****ino no. of apps, but to no avail.
THE PROBLEM: I do not have a PC with me now and all these dickheads think a virus will creep in their systems if I send just one ****ing command, i.e. push a custom recovery using their cmd window, whenever I request them to allow me to use their laptops or desktops.
WHAT I'VE BEEN THINKING AND I'M IN REALLY NEED OF:
A SuperSU zip that can be flashed via official update app.
A way to send a command or push a recovery when I am booted into the RN3's bootloader, using another phone/tablet.
**THAT'S ALL. PLEASE COME FORWARD WITH ANY SUGGESTIONS YOU MIGHT HAVE.**
P.S. - Getting a computer or laptop is not an option, until now.
Thank you, everyone. Respect and regards.
Sent from my RN3.
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?