Related
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Flash latest TWRP first. What happened during repartition?
You can allways acces the eeprom writer through short circuiting the sim card, there are a lot of tutorials, the only way to brick this phone is breaking its hardware
nsakhare said:
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Click to expand...
Click to collapse
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
aniketkuber said:
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
The Dork Knight Rises said:
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
Click to expand...
Click to collapse
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Inonotting said:
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Click to expand...
Click to collapse
Repartitioning will wipe both your system partitions [EDIT: Seems I was wrong?]. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
The Dork Knight Rises said:
Repartitioning will wipe both your system partitions. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
Click to expand...
Click to collapse
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Inonotting said:
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Click to expand...
Click to collapse
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
I think I'm back online
The Dork Knight Rises said:
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
Click to expand...
Click to collapse
OK,
I followed your links and flashed :
First : Repartition to Stock Layout
Then : Repartition to 1.2GB Single System
Strange, after this, I did a normal reboot, it rebooted into my old ROM.
Shouldn't that have been erased after partitioning ?
Anyway,
Then I flashed ; update-XenonHD-08-08-15-signed-.zip
WAIT WAIT .....
as I'm typing, I'm flashing update-XenonHD-09-05-15-signed-cancro.zip,
first ROM in a few weeks that seems to be installing.
Let me check is it really installed .... YEP .... progress
Flashing : pa_gapps-modular-pico-5.1-20150418-signed
Everything seems to be going smooth
OK, for the time being .... all good.
Thanks a lot :good:
If your device cannot boot, flash it thru fastboot mode. See the full detailed tutorial on en.miui.com
Well you can directly flash with miflash even with the extended partition. Just edit the fastboot script (.bat extension with windows) and search for line
fastboot flash system+system1
And then delete system1
Fastboot flash system
And use those script for flashing via miflash
Hi all,
I am new to the BLU R1 HD scene. Just got my phone this week. It's a amazon prime variant with firmware v7.4.2 (or v7.2.4?).
I got twrp installed and wiped everything through TWRP, including the internal storage - which removed my only NANDroid backup image.
My phone would freeze at the startup BLU logo now. But I could still enter recovery mode (TWRP). And I could still see the TWRP folder from my Ubuntu (which shows as a internal storage drive)
What should I do? Is there a way to flash it back to stock ROM? Where can I download a stock rom?
I am in panic mode now. Any help would be greatly appreciated!!
jimmythefung said:
Hi all,
I am new to the BLU R1 HD scene. Just got my phone this week. It's a amazon prime variant with firmware v7.4.2 (or v7.2.4?).
I got twrp installed and wiped everything through TWRP, including the internal storage - which removed my only NANDroid backup image.
My phone would freeze at the startup BLU logo now. But I could still enter recovery mode (TWRP). And I could still see the TWRP folder from my Ubuntu (which shows as a internal storage drive)
What should I do? Is there a way to flash it back to stock ROM? Where can I download a stock rom?
I am in panic mode now. Any help would be greatly appreciated!!
Click to expand...
Click to collapse
take it easy . sounds like you wiped /system too. but that is ok since you still have access to twrp
take a rom from here
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
copy it to the phone (internal storage) as seen from your ubuntu.
boot to twrp and select install, browse to the zip file copied to internal
mrmazak said:
take it easy . sounds like you wiped /system too. but that is ok since you still have access to twrp
take a rom from here
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
copy it to the phone (internal storage) as seen from your ubuntu.
boot to twrp and select install, browse to the zip file copied to internal
Click to expand...
Click to collapse
Oh my god that's good to hear! (especially from someone who knows his stuff!)
I was just looking at that other thread you posted.
Okay I give that a try. Thanks much!
It fixed my phone just as you said! The v8.4 rom is even better with higher level security update. Thanks!
Once you have twrp installed, you can recover from most things that go wrong.
One exception is when people do a "wipe all" and erase the phone's MEID unique identification. When that happens, the phone can boot and work but can no longer be connected to a phone service provider's network.
And the more common problem with this phone is people who accept an over-the-air update that disables SP Flash Tool and then want to get root or flash their phones. They are out of luck at that point.
Have my Mi 8 about a week, loving it BUT as the bootloader is unlocked I couldn't use Google Pay so I decided to install TWRP and get the Xiaomi.eu ROM.
I just installed TWRP and tried backing up the phone, but I got an error saying it Can not create the folder. I reinstalled TWRP, thinking maybe there was an issue with the first install but now it's stuck in a recovery boot loop. It loads to the MI screen with the unlocked icon but doesn't get to the powered by android, it goes straight into recovery.
The Rom is not on the device and I thought maybe could install it through the recovery but if I have the phone plugged into the laptop (Windows 10) and go into recovery, the touch screen on the phone doesn't work and the phone keeps rebooting itself.
I can also get into Fastboot and the device is detected by miFlash.
What should I do next, I don't trust my instincts. Any advice would be much appreciated. I'm currently downloading the Global Rom off Xiaomi (going to take a while on my 3mb broadband) and hoping I can flash that with miFlash tool, good or bad idea??
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
gm007 said:
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
Click to expand...
Click to collapse
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
cherbe.3 said:
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
Click to expand...
Click to collapse
Sure there must be a fastboot method but didn't tried it yet, i had this phone 3 days ago
Not sure if after formatting data and reboot to twrp you can copy the rom from pc to phone.
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
gm007 said:
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
Click to expand...
Click to collapse
Oh yes, thank you for the reminder, that slipped my mind with this whole mess.
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Click to expand...
Click to collapse
Cheers for the advice, I'll make sure to format before installing. Only issue now is that I can't get the rom onto the phone to install it. Do you reckon if I format the data through TWRP it will then allow me to copy over the rom onto the device? Currently, unless in fastboot, the laptop doesn't recognise the device - constantly reboots the phone causing it to connect and disconnect.
SPOCK_VULKAN said:
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
Click to expand...
Click to collapse
I like the sound of this solution but I have a few questions/need clarification as this mess has made me doubt myself (no issue flashing my previous phone mi5)
I downloaded the Global rom from here: http://en.miui.com/download-346.html#523 (just want clarification this is the official rom) I have the latest version of the miFlash. Am I right in thinking, put phone into fastboot, launch tool, locate unzipped rom folder, select 'Clean all' (and not save user data / clean all and lock (presume this means bootloader)) and click Flash??
And then do I start again, flash TWRP and hope it works?
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
If I do this (wipe data and format) will the laptop detect the device to allow me to move the rom onto the phone, currently it doesn't (well it loops between connecting and disconnecting when in TWRP, no issue detecting in fastboot)
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
deepblue2000 said:
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
Click to expand...
Click to collapse
I've tried several USB ports and different cables, no luck getting it to connect.
No the TWRP installed is 3.2.1-0611-XIAOMI8, yours uses the code name and seems to be a newer version and more legit, I'm going to flash that onto the phone. I presume do it the way I did it before - fastboot, shift right click to get to cmd line...etc.
I did indeed enable usb debugging when I installed it originally.
By the way, thanks so much for your help, I'm lost without my phone - it was love at first sight
Fastboot Flashing Code
Code:
Fastboot boot Twrp.img
Flash the recovery img again inside twrp and reboot to recovery again and it will stay.
If u are new to twrp, format data in twrp and reboot to recovery again and flash this file https://androidfilehost.com/?fid=3700668719832238534 after that u can flash the rom.
If u have already twrp installed, just flash the img in twrp
Click to expand...
Click to collapse
Actually I'm confused now, is this probably where I went wrong in the first place.
Boot the TWRP img and then flash it through TWRP, I've never done it this way before (have I been doing this worng all along?)
and whats the other file about? Disable_Dm-Verity_FEC_v1.1.zip
Sorry about all the questions
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
deepblue2000 said:
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
Click to expand...
Click to collapse
Right, so I got TWRP 3.2.3 installed and seems to be working (not disconnecting and reconnecting) BUT the phone is still not recognsed - It says unspecified in the devices . I ran through the ADB set up, all installed including drivers but still no phone showing up. I hate windows 10 and drivers, can't get them to play nice (or it's me)
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
deepblue2000 said:
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
Click to expand...
Click to collapse
AND WE'RE IN!!! THANK YOU, THANK YOU!! If you were here I'd hug you and get you a drink.
Forget my above nonsense and babble, PC wasn't happy with whatever was going on, once I got brave enough and actually followed your instructions in all fell into place!!
So conclusion -
I had the wrong TWRP (3.2.3 is needed)
PC didn't like whatever was happening without the OS
Wiped and formatted through TWRP - Phone was recognised
Dragged Xiaomi.eu rom over - copied perfectly
Flashed rom - successful and the wiped cache again to be safe
Rebooted and my smile came back the moment I saw the 'powered by android' icon
Went through set up and I'm back in.
Mi 8 - bootloop and locked device, no system, help?
Hi guys,
I did a pretty much bad thing on my phone, I've just bought it 2 weeks ago and I was loving the phone, my phone is unlocked but today I was rooting to install google camera with night sight and I don't know why my twpr was really weird, when pressing install all the folder that was showing was very different from youtube videos about mi 8 root and even compared to my old devices, it was showing folders like licence and others, but the weirdest was inside the sdcard folder that was showing a lot of unnamed folders(like this: 54u3hu6ijj4!ji5), the thing got worse when I've flashed magisk and the phone got stuck on bootloop, after that tried to flash a stock global rom from official Mi website on fastboot mode using Mi Flash Toll, what I did wrong is that I didn't see that the Lock option was ticked and than I pressed to flash, everything was going good when my device showed a message saying that the Miui wasn't compatible with my phone. After that I've tried to install TWPR again but my phone was locked by the Mi flash toll and know my device is without system and unlocked. I've also tried to unlock but is saying that my account is not bound to my device, so I have no idea what to do, I'm gonna never root any phone ever, worse thing I did.
Can Anybody know what I can do to unlock the phone?
Sorry about my English, that's not my native language.
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32
Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.
KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?
UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).
KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.
Hi everyone, I really need some help. Took my phone to I.T shop to have it unlocked and EU rom stable put on. I got my phone back with TWRP on it saying no rom. I know nothing about this kind of thing and now I am stuck. Is there someone who can fix this remotely for me?? Thanks in advance
In twrp Click install and Check in the download folder in case it's not in the root folder, if there is no ROM there you could fix it yourself by flashing the last fastboot ROM from a bat file or cmd line
i think it was 12.5.5 or something like that and then you can update to EU 12.5.12 stable via twrp
AND NEVER USE THAT SHOP AGAIN LOL
speedtripler said:
In twrp Click install and Check in the download folder in case it's not in the root folder, if there is no ROM there you could fix it yourself by flashing the last fastboot ROM from a bat file or cmd line
i think it was 12.5.5 or something like that and then you can update to EU 12.5.12 stable via twrp
AND NEVER USE THAT SHOP AGAIN LOL
Click to expand...
Click to collapse
Thanks for your reply. Could this be done remotely. I really have no idea how to do any of this stuff which is why i first went to a shop. Im happy to pay for a good outcome
Anyone who flashes ROMs could do it in a few minutes via team viewer or something.... But it maybe beneficial to learn for yourself
It's really simple, you've already done the hardest part if you've unlocked the bootloader and installed twrp
Just put the phone in fastboot mode and then plug into PC and click on the bat file
Download: MIUI 12 stable update rolling out to several Xiaomi, Redmi and POCO devices
MIUI 12 stable builds have begun rolling out to several Xiaomi, Redmi, and POCO devices. Head on over for Recovery ROM and Fastboot ROM download links!
www.xda-developers.com
Select your phone and download the MIUI stock ROM. (Do NOT extract it.)
Boot into Twrp and wipe and factory reset.
Move the miui stock rom to the phone.
Select flash and select the zip file.
Swipe to flash
Then download and flash(move to phone, flash) the 'ARM64 Android 11' Gapps(Google apps) https://opengapps.org/
Then reboot.
All data will be lost. If you want to keep your photos and videos, before doing everything, go to twrp , connect the phone to a pc, and move the 'Dcim' folder to the computer side.
If you have a working TWRP, just use it to flash latest EU version, format data, reboot system. Done.
Then if you want to go back to a stock ROM, flash it via fastboot or twrp depending on the ROM format you download.
Sathelp said:
If you have a working TWRP, just use it to flash latest EU version, format data, reboot system. Done.
Then if you want to go back to a stock ROM, flash it via fastboot or twrp depending on the ROM format you download.
Click to expand...
Click to collapse
If he's stuck in twrp how can he download a ROM to flash? I don't think you can transfer files to a phone that doesn't have a ROM to flash via twrp
Fastboot first from a PC cmd maybe the only way to get started
He is asking someone else to do the process he doesn't know anything about these things (and I don't understand why buying a phone to make things like this if not capable). Anyway go on YouTube and check people doing the process, I don't think is difficult watching a guy and copy what he is doing
I am replying to close this thread. He contacted me over telegram. I took a look at his phone and the phone is not being detected in fastboot mode on his pc. Maybe hard bricked or in edl mode. Also his twrp is not accessible. So i suggested him to contact the edl guy and he fixed the phone.
So ask mods to close this thread?
speedtripler said:
If he's stuck in twrp how can he download a ROM to flash? I don't think you can transfer files to a phone that doesn't have a ROM to flash via twrp
Fastboot first from a PC cmd maybe the only way to get started
Click to expand...
Click to collapse
I know it's closed as such but in twrp, I can copy files from pc to phone. He could have done the same. BTW, I'm using the very first twrp that many wouldn't install but my phone is recognised in Windows while in recovery. This might help someone else