Related
Hi, I have a bootloop after install xposed on chuwi vi10, I've tried to flash a recovery image trough fastboot and also tried intelandroidfbrl, but I can't get to flash it.
These are the images.
http://es.tinypic.com/view.php?pic=103v311&s=8
http://es.tinypic.com/view.php?pic=bhx8yc&s=8
Please I need help.
fperez76 said:
Hi, I have a bootloop after install xposed on chuwi vi10, I've tried to flash a recovery image trough fastboot and also tried intelandroidfbrl, but I can't get to flash it.
These are the images.
http://es.tinypic.com/view.php?pic=103v311&s=8
http://es.tinypic.com/view.php?pic=bhx8yc&s=8
Please I need help.
Click to expand...
Click to collapse
What Android version are you running? Which files from which thread here on XDA did you install on your device? Your screenshots do not provide enough information.
orville87 said:
What Android version are you running? Which files from which thread here on XDA did you install on your device? Your screenshots do not provide enough information.
Click to expand...
Click to collapse
Hi, thank you for your answer, android kit kat, I've installed a xposed trough an app from the store( Xposed Gel Settings). I've tried the program from this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and install drivers but I can't show my device with command adb device, with fastboot device I can show my device but I get an error during the process to flash the recovery, you can watch it on the image. Thank you.
fperez76 said:
Hi, thank you for your answer, android kit kat, I've installed a xposed trough an app from the store( Xposed Gel Settings). I've tried the program from this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and install drivers but I can't show my device with command adb device, with fastboot device I can show my device but I get an error during the process to flash the recovery, you can watch it on the image. Thank you.
Click to expand...
Click to collapse
First of all, Xposed is a great danger for unexperienced users. Do not do some "cool things" to your phone without having a backup of your entire system available.
Hopefully you are able to boot into recovery again and restore your backup. If you do not have a backup, do a factory reset (you will lose all your data, but without a backup available...)
If you are on KitKat, install Xposed directly from here.
You can flash a custom recovery for your device by using an app called Flashify.
So my advice for you: try booting into recovery (if you do not know how: search for "your device name" + "recovery volume key". There should be a key combo available to boot into recovery. If this is not possible, make yourself familiar with flashing a kdz file...
orville87 said:
First of all, Xposed is a great danger for unexperienced users. Do not do some "cool things" to your phone without having a backup of your entire system available.
Hopefully you are able to boot into recovery again and restore your backup. If you do not have a backup, do a factory reset (you will lose all your data, but without a backup available...)
If you are on KitKat, install Xposed directly from here.
You can flash a custom recovery for your device by using an app called Flashify.
So my advice for you: try booting into recovery (if you do not know how: search for "your device name" + "recovery volume key". There should be a key combo available to boot into recovery. If this is not possible, make yourself familiar with flashing a kdz file...
Click to expand...
Click to collapse
Thank you, but my problem is into recovery, when I press and hold power button and +, my device shows me to enter a command with fastboot but when I try to enter in adb mode on windows with cmd my devices doesn't show, with command fastboot my device shows but i can't manage to flash a recovery image for my tablet (the second image), I'm trying to connect with my device trough adb or fastboot on windows, this is my problem. I can't enter to android, remember I've a bootloop and install flashify is not possible.
Finally I found the solution,
Solved. Bootloop on chuwi vi10 after install xposed. No adb or fastboot.
If you can't enter adb or fastboot (remote: unknown command)
You must boot Windows(hold power button and - volume) choose windows with volume buttons and later power button to select.
Boot windows and install ext2fsd http://sourceforge.net/projects/ext2.../Ext2fsd/0.62/
Start the program and you'll see all the partitions. Choose android partition 7gb more or less and ext4 type.
Assign a letter and select the option to mount on the next restart.
Restart windows, now you can enter into the partition on my computer.
Search files called xposed and delete them.
Icon change OS and accept. Boot android normally.
So how to install Xposed on chiwu vi10 without bootloop
rfiore said:
So how to install Xposed on chiwu vi10 without bootloop
Click to expand...
Click to collapse
I want to know this too.... ^.^
you can try this. Couldn't get it to work for me though, I get the same error as the other guy in the thread, but it seems to work for others.
http://techtablets.com/forum/topic/...-guide-on-stock-android-4-4-4-for-chuwi-vi10/
---------- Post added at 02:37 AM ---------- Previous post was at 02:18 AM ----------
lol, okay, spoke too soon. not sure what I did differntly, but I tried it a few more times and it worked. Maybe plug in tablet only after you install the apk? meh. working now, I have xposed.
Enter e fastboot mode through the normar recovery and use ADB to unlock the boot loader, it should work
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL (I forgot to mention that Im coming from CM13, that makes it need bootloader unlock n root probably?)
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU (credit to @Chainfire) (thanks to @Cr0ssL1nk for notify me about the updated SuperSU! )
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
It works on my ZE601KL!!!
Thank you very much xyexiaoyuer in your first post
I would assume this process is the same for any of the variants for which the bootloader is already unlocked and assuming you use the correct TWRP image.
If nothing else, it should work for any Z00T phone. I'll try it on my ZE551KL tonight.
xyexiaoyuer said:
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU ive tested SuperSU Root BETA v2.67.zip credit to them (help me credit them as i dont know who to tag)
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
Click to expand...
Click to collapse
On the "fastboot boot recovery.img", I first got it to successfully transfer over something, then the second line said that it failed.
I continually did this and got the same results and my phone continued to say "fastboot" in the corner, so I wasn't sure if anything had happened.
I finally "gave up" and pulled the battery but I booted into the Recovery (Vol down + Power) and found that TWRP actually was installed and from there I flashed over SuperSU and was rooted in minutes.
Great job, and thanks! I may be a bit rusty with all this since this is my first Android device in about 3 years.
Joxefo said:
It works on my ZE601KL!!!
Thank you very much xyexiaoyuer in your first post
Click to expand...
Click to collapse
wooot~ npnp bro..thank god it works for you too!!
rczrider said:
I would assume this process is the same for any of the variants for which the bootloader is already unlocked and assuming you use the correct TWRP image.
If nothing else, it should work for any Z00T phone. I'll try it on my ZE551KL tonight.
Click to expand...
Click to collapse
i forgot to mention the bootloader bro. sorry about that. already edited in my 1st post. So how was ur phone? does the method work on your ZE551KL?
ndh777 said:
On the "fastboot boot recovery.img", I first got it to successfully transfer over something, then the second line said that it failed.
I continually did this and got the same results and my phone continued to say "fastboot" in the corner, so I wasn't sure if anything had happened.
I finally "gave up" and pulled the battery but I booted into the Recovery (Vol down + Power) and found that TWRP actually was installed and from there I flashed over SuperSU and was rooted in minutes.
Great job, and thanks! I may be a bit rusty with all this since this is my first Android device in about 3 years.
Click to expand...
Click to collapse
good to hear that bro!! probably it failed because of bootloader? hv u unlock it before? im sorry didnt mention it on my first post. my bad my bad
Boot twrp, not flash it to root?
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
long2ski said:
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
Click to expand...
Click to collapse
hi broo..you can always flash stock recovery after u flash superSU using twrp =)
xyexiaoyuer said:
hi broo..you can always flash stock recovery after u flash superSU using twrp =)
Click to expand...
Click to collapse
Thanks, but I am pretty sure Flashing twrp writes over stock recovery and unless someone else has the stock image, you can't get it back. I don't know how to make a backup of stock recovery, that's why I wondered if only booting twrp will work.
long2ski said:
Thanks, but I am pretty sure Flashing twrp writes over stock recovery and unless someone else has the stock image, you can't get it back. I don't know how to make a backup of stock recovery, that's why I wondered if only booting twrp will work.
Click to expand...
Click to collapse
if ure using ze601kl, i think the stock recovery can be downloaded here .. download according to your version of firmware of course =) let me know if its work for you. the last time im coming from cm13 to Lollipop im using recovery from there to write off twrp. hope this helps =)
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
long2ski said:
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
Click to expand...
Click to collapse
i dont think so..better dont as i only tested this with ze601kl =( buttttt the stock recovery for your model probably can be downloaded here not sure it will work though..proceed at ur own risk.
sorry bro if its not being helpful
xyexiaoyuer said:
i forgot to mention the bootloader bro. sorry about that. already edited in my 1st post. So how was ur phone? does the method work on your ZE551KL?
Click to expand...
Click to collapse
Yep, worked fine on the ZE551KL.
long2ski said:
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
Click to expand...
Click to collapse
long2ski said:
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
Click to expand...
Click to collapse
You can boot into TWRP without overwriting your stock recovery using:
HTML:
fastboot boot twrp.img
That would allow you to install SuperSU without actually installing TWRP. If you want to replace stock recovery with TWRP, you would use:
HTML:
fastboot flash recovery twrp.img
xyexiaoyuer said:
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL (I forgot to mention that Im coming from CM13, that makes it need bootloader unlock n root probably?)
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU ive tested SuperSU Root BETA v2.67.zip credit to them (help me credit them as i dont know who to tag)
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
Click to expand...
Click to collapse
Are you sure your phone is truely rooted and that apps needing root really works ?
Because in the official SuperSU page on XDA: http://forum.xda-developers.com/showthread.php?t=1538053 , the developpers says your phone must already be rooted before flashing SuperSU.
Also, change the 2.76 Beta's link you gived for SuperSU in your tutorial to the 2.76 Stable version from my link to the official SuperSU XDA page.
Cr0ssL1nk said:
Are you sure your phone is truely rooted and that apps needing root really works ?
Because in the official SuperSU page on XDA: http://forum.xda-developers.com/showthread.php?t=1538053 , the developpers says your phone must already be rooted before flashing SuperSU.
Also, change the 2.76 Beta's link you gived for SuperSU in your tutorial to the 2.76 Stable version from my link to the official SuperSU XDA page.
Click to expand...
Click to collapse
Welp! now that i check back using "root check" apps it seems that the app hv some trouble to detect whether the phone is rooted. the last time everything was okay except for busybox. Perhaps because i rebooted the device? nvrtheless i will update the link and test the stable supersu given in the link
xyexiaoyuer said:
Welp! now that i check back using "root check" apps it seems that the app hv some trouble to detect whether the phone is rooted. the last time everything was okay except for busybox. Perhaps because i rebooted the device? nvrtheless i will update the link and test the stable supersu given in the link
Click to expand...
Click to collapse
I don't think rebooting caused this.
The thing that makes me worry is that Busybox was not okay the first time you rooted your phone, because it must be one of the first thing that must be ok when you root a phone.
Have you got any updates on your side about making root really working ?
Cr0ssL1nk said:
I don't think rebooting caused this.
The thing that makes me worry is that Busybox was not okay the first time you rooted your phone, because it must be one of the first thing that must be ok when you root a phone.
Have you got any updates on your side about making root really working ?
Click to expand...
Click to collapse
Hi Brooooo, im happy to report that the SuperSU is still intact even if the device has been rebooted several times. thx a lot broooo and busybox is installed correctly toooo. already put thumbnails attachment at the 1st post for proof
xyexiaoyuer said:
Hi Brooooo, im happy to report that the SuperSU is still intact even if the device has been rebooted several times. thx a lot broooo and busybox is installed correctly toooo. already put thumbnails attachment at the 1st post for proof
Click to expand...
Click to collapse
No problem, proofs are just great ! :highfive:
Also, check this post: http://forum.xda-developers.com/showpost.php?p=67978015&postcount=8
Because you also must allow SuperSU in ASUS' Autostart Manager, that may be the problem you also got.
But please remember: Do not post something that seems to work but is not, a Beta or something not stable to other people without a lot of checking first
rczrider said:
Yep, worked fine on the ZE551KL.
You can boot into TWRP without overwriting your stock recovery using:
HTML:
fastboot boot twrp.img
That would allow you to install SuperSU without actually installing TWRP. [/HTML]
Click to expand...
Click to collapse
Thanks to everyone's help and ideas and especially to @rczrider. On my ze551kl, I successfully booted the twrp.img in fastboot, did a backup through twrp, then installed supersu zip, and successfully rooted. No overwrite of stock recovery with all the root privileges. Perfect.
hello everyone
Buy a Chinese mi8, unlock it waiting for the days that xiaomi tells you.
I installed the global version, and everything works correctly, but I want to change the rom.
I've tried to install TWRP with adb and it's impossible, it tells me the ADB template that OKEY, but never restarts in recovery mode with TWRP, so I can not install magisk, or any rom that is not official.
Is there any way to install a ROM (.zip) without TWRP?, how do I do Root without magisk? Has it happened to anyone?
thanks!
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
trahzebuck said:
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
Click to expand...
Click to collapse
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
You are trying to be smart? Well...
Why didn't you post your exact steps with fastboot in the first post?
Now it's clear what you did wrong. I already expected it. And you did NOT read what I wrote:
You are rebooting your device with fastboot reboot. In this case your twrp is wiped out by the XIAOMI recovery. Use: fastboot boot yourimagename.
btw, why are you using such an old TWRP? You won't be able to flash actual roms.
So I'd like to come back to my advice in the first answer....
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Vuska said:
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
cheteuk said:
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
Click to expand...
Click to collapse
Use the all in one tool, to remove encryption and flash a compatible TWRP.
tsongming said:
Use the all in one tool, to remove encryption and flash a compatible TWRP.
Click to expand...
Click to collapse
What is the all in one tool?
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Goalach said:
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Click to expand...
Click to collapse
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
cheteuk said:
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
Click to expand...
Click to collapse
You can't flash a ROM without TWRP and Magisk is the only way you can root your phone that I know of. If you don't even know these simple things/haven't done simple research you might risk to softbrick or even hardbrick your new and shiny phone. There are many guides on how to flash TWRP but you can PM me if you want more help.
Also you don't install TWRP with adb, you need to use fastboot...
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
The number 1 result
http://bfy.tw/Nvtb
You can try this
Make sure you have activated the usb debugging in developer options.
1. Download the tools from here: bit.ly/FlashToolMi8
2. Install the minimal_adb_fastboot_v1.3.1_setup
3. Copy the twrp-3.2.3-0-dipper.img to Minimal ADB and Fastboot Folder
4. Turn off your phone completely. then press power button + volume down to boot in fastboot mode.
5. Run CMD as Administrator then cd to the installed Minimal ADB and Fastboot folder. (Ex: cd C:\Program Files (x86)\Minimal ADB and Fastboot)
6. Use this command on your cmd: fastboot flash recovery twrp-3.2.3-0-dipper.img
7. Then: fastboot boot twrp-3.2.3-0-dipper
8. And: fastboot reboot recovery
9. You're now in twrp recovery mode
10. Copy Disable_Dm-Verity_FEC_v1.1 and Magisk-v18.1 to your phone
11. Install Disable_Dm-Verity_FEC_v1.1 from twrp
12. Then install Magisk-v18.1
13. Reboot, Your phone now rooted
Hi everyone ,
First of all sorry if my english is bad it's not my first language .
Let me explain my problem :
- I root magisk using twrp to root my phone but every time i do that my phone can't boot to system but only twrp (boot loop) and i have to factory reset to get back to the system . Also when i try to install unimod when i installed magisk it says that magisk is not installed .
- So i tried super su , it installed correctly and can boot properly but root checker says that he's not rooted ...
Can someone help me ? Thanks
Astrusky said:
Hi everyone ,
First of all sorry if my english is bad it's not my first language .
Let me explain my problem :
- I root magisk using twrp to root my phone but every time i do that my phone can't boot to system but only twrp (boot loop) and i have to factory reset to get back to the system . Also when i try to install unimod when i installed magisk it says that magisk is not installed .
- So i tried super su , it installed correctly and can boot properly but root checker says that he's not rooted ...
Can someone help me ? Thanks
Click to expand...
Click to collapse
Extract "boot.img" from your stock rom and flash it.
Reboot again to TWRP, then flash magisk. Reboot
gringo80 said:
Extract "boot.img" from your stock rom and flash it.
Reboot again to TWRP, then flash magisk. Reboot
Click to expand...
Click to collapse
Can you tell me how i can extract it ? I'm a beginner xD
gringo80 said:
Extract "boot.img" from your stock rom and flash it.
Reboot again to TWRP, then flash magisk. Reboot
Click to expand...
Click to collapse
Or maybe a tutorial ?
Astrusky said:
Or maybe a tutorial ?
Click to expand...
Click to collapse
With software like winrar or 7zip click right click on recovery rom and extract, then turn off your phone, press volume down and connect usb, you will see fastboot logo on your phone. Put previously extracted boot into same folder with minimal adb fastboot, flash with command fastboot flash boot boot.img
Stefke93 said:
With software like winrar or 7zip click right click on recovery rom and extract, then turn off your phone, press volume down and connect usb, you will see fastboot logo on your phone. Put previously extracted boot into same folder with minimal adb fastboot, flash with command fastboot flash boot boot.img
Click to expand...
Click to collapse
When i do that twrp is not working anymore i get back to the regular recovery ...
Astrusky said:
When i do that twrp is not working anymore i get back to the regular recovery ...
Click to expand...
Click to collapse
Edit when i install magisk via a pre patched boot image it works until the app asks me to install additional things to make it work and then stuck in twrp
Stefke93 said:
With software like winrar or 7zip click right click on recovery rom and extract, then turn off your phone, press volume down and connect usb, you will see fastboot logo on your phone. Put previously extracted boot into same folder with minimal adb fastboot, flash with command fastboot flash boot boot.img
Click to expand...
Click to collapse
And in the app they say everything is installed except additional zip but when i try to install uninstall mod they say magisk is not installed
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.