Stuck in a bootloop, any hopes? - Xiaomi Redmi 4X Questions & Answers

Yesterday I was using my phone and it suddenly started rebooting itself. Since my bootloader was locked, my phone was stock rom, no root, no custom recovery and usb debugging off my hopes of doing something through ADB or Fastboot vanished. I think it is fixable but I would like to recover all my data first. I heard that you can try to get your phone into EDL mode in order to recover your data, so I tried to via test point method and my phone is now recognized as Qualcomm 9008. However, afaik this mode wont let me recover any data, and I need to get it to be 9006 instead of 9008. Any help?

Proceed at your risk.
The test point method http://en.miui.com/thread-693884-1-1.html it is using Mi flash tools to flash the ROM so you can opt out for save user data in order to keep internal storage.
in that thread it is mentioned to clean flash but there is one step given to save user data so i don't know what things will be saved and what not. most possibly itll wipe app and its data so messages,call logs,contact will get wiped if there are in internal storage if they haven't backed up to the cloud.
do read carefully and then proceed.

metelhammer said:
Proceed at your risk.
The test point method it is using Mi flash tools to flash the ROM so you can opt out for save user data in order to keep internal storage.
in that thread it is mentioned to clean flash but there is one step given to save user data so i don't know what things will be saved and what not. most possibly itll wipe app and its data so messages,call logs,contact will get wiped if there are in internal storage if they haven't backed up to the cloud.
do read carefully and then proceed.
Click to expand...
Click to collapse
I guess I´ll try that then, I already saw this ''Wipe everything but userdata'' option but was not sure, as it seems a bit strange. I'll give it a shot, thanks!

Lolo147 said:
I guess I´ll try that then, I already saw this ''Wipe everything but userdata'' option but was not sure, as it seems a bit strange. I'll give it a shot, thanks!
Click to expand...
Click to collapse
Your welcome, hope to see that work.

metelhammer said:
Your welcome, hope to see that work.
Click to expand...
Click to collapse
So I tried this and, after dealing with many versions of Mi Flash (newer ones crashed, older ones had many errors) I was finally able to flash a fastboot rom but unfortunately I'm still stuck in the bootloop. I guess wiping data is an unavoidable fate. Thanks again 4 everything

1.Install twrp.(if you dont have)
2.Turn off phone and click power volup+voldown and when phone turns on release power btn. Recovery will appear wipe data,cache,dalvik,system,vendor then install any rom (i recommend pixelexperience or miui stable). Then wait if there an bootloop i cant help bye.

Related

[Q] cant see phone storage via pc anymore

Hi, So I've follow through the steps from
http://forum.xda-developers.com/showthread.php?t=2265618
and i've reached the part "Flashing custom recovery" where i was doing the nandroid backup using CWM 2 from this link
http://forum.xda-developers.com/showthread.php?t=2172979
however backup is done i rebooted the device when trying to access files on the storage via my pc i can no longer see any files or folders.
I've rebooted a few times files do not appear any longer...
phone currently showing tempered and unlocked.
kenl said:
Hi, So I've follow through the steps from
http://forum.xda-developers.com/showthread.php?t=2265618
and i've reached the part "Flashing custom recovery" where i was doing the nandroid backup using CWM 2 from this link
http://forum.xda-developers.com/showthread.php?t=2172979
however backup is done i rebooted the device when trying to access files on the storage via my pc i can no longer see any files or folders.
I've rebooted a few times files do not appear any longer...
phone currently showing tempered and unlocked.
Click to expand...
Click to collapse
You need to flash the latest custom recovery .. http://forum.xda-developers.com/showthread.php?t=2173863.
It is normal for your device to show tampered as you have tampered with it lol and unlocked because you unlocked the bootloader. Just flash the latest CWM and try restore again. Personally I never restore. If you're having issues I'd do a clean install of whatever ROM you are using.
AllAboutTheCore said:
You need to flash the latest custom recovery .. http://forum.xda-developers.com/showthread.php?t=2173863.
It is normal for your device to show tampered as you have tampered with it lol and unlocked because you unlocked the bootloader. Just flash the latest CWM and try restore again. Personally I never restore. If you're having issues I'd do a clean install of whatever ROM you are using.
Click to expand...
Click to collapse
My problem is not the fact that it says tempered and unlocked... I know that much...
Problem is I cannot see the phone storage , the drive shows up but it's empty
kenl said:
My problem is not the fact that it says tempered and unlocked... I know that much...
Problem is I cannot see the phone storage , the drive shows up but it's empty
Click to expand...
Click to collapse
So just install the newest recovery and reflash whatever ROM using an OTG cable and flash drive. Have you even tried a factory reset or anything? You need to at least try and help yourself and do some troubleshooting. The first thing I'd do if I had a problem would be a clean install and see if the problem persists.
Installing the latest TWRP or CWM would be a start, followed by formatting the internal storage and see if it shows up.
AllAboutTheCore said:
So just install the newest recovery and reflash whatever ROM using an OTG cable and flash drive. Have you even tried a factory reset or anything? You need to at least try and help yourself and do some troubleshooting. The first thing I'd do if I had a problem would be a clean install and see if the problem persists.
Installing the latest TWRP or CWM would be a start, followed by formatting the internal storage and see if it shows up.
Click to expand...
Click to collapse
dude of course tried everything that i know of outside of any other tools i am not aware of with unlocking... I have i just havent had to changed to say it, i was asking to see if anyone else know of the issue or if it was just something that is happening to me.I know I am a n00b at using these tools at the moment, you don't have to point each time trying to help someone.
so of course i have reset to factory, of cause i have try to try something before asking. i was seeing if this is an known issue rather.
anyway it turned out to be something on my machine that somehow its not showing the phone storage.
ok to make this post helpful to other users.
if you were to have your phone plugin to your pc while it reboot out of cwm ensure that you have the usb unplug first before rebooting from cwm else you may see a empty internal storage, if so simply unplug the cable from your phone, reboot and plug back onto your pc.
hope this helps someone else.
Regards
K
Look in data/media/0

TWRP asking for password

Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...
kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.
ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.
Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .

[HELP] Moto X won't boot to OS after strange happenings...

Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?
THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app
So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.
I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app
Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk
I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!
I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app
As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app

My mi 8 is stuck in fastboot mode

I've installed lineage OS and didn't like it, then I downloaded the pixel experience ROM to try it out.
So i went into TWRP, wiped everything, internal storage, cache, dalvik, system, etc. and then flashed the pixel experience ROM, and now it is stuck in the fastboot mode..
It will not boot into the normal OS! And now i've wiped everything again, and then powered off the phone
What should I do? I'm feel panicked now..please help
guyzz6370 said:
I've installed lineage OS and didn't like it, then I downloaded the pixel experience ROM to try it out.
So i went into TWRP, wiped everything, internal storage, cache, dalvik, system, etc. and then flashed the pixel experience ROM, and now it is stuck in the fastboot mode..
It will not boot into the normal OS! And now i've wiped everything again, and then powered off the phone
What should I do? I'm feel panicked now..please help
Click to expand...
Click to collapse
Download AIT Here : https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807
Use it to reinstall TWRP and unencrypted userdata ( only if needed) Then reinstall whatever Rom, Gapps ( if needed) and Root.
You likely missed a step or flashed something such as gapps on the Pixel Rom, and that caused this issue. FYI, as long as you have fastboot there is never a need to worry. Once this is sorted out I would highly recommend that you make a TWRP backup and save it to your PC, to resolve any deeper issues such as sensor problems.
tsongming said:
Download AIT Here : https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807
Use it to reinstall TWRP and unencrypted userdata ( only if needed) Then reinstall whatever Rom, Gapps ( if needed) and Root.
You likely missed a step or flashed something such as gapps on the Pixel Rom, and that caused this issue. FYI, as long as you have fastboot there is never a need to worry. Once this is sorted out I would highly recommend that you make a TWRP backup and save it to your PC, to resolve any deeper issues such as sensor problems.
Click to expand...
Click to collapse
Ok, it happens like this. First I had MIUI, then I installed LOS (which is working) but I didn't like it, so I went and downloaded the PE ROM, and then I just went into TWRP, deleted everything, wipe everything, etc and then I transferred the PE zip file to my phone's internal storage via usb and then I flash it using TWRP. I then went to reboot system, and now it is stuck in the fastboot.
flashed something such as gapps on the Pixel Rom, and that caused this issue
Click to expand...
Click to collapse
I really didn't flash gapps on the PE ROM, because I read that PE had gapps pre-installed, this is something I'm sure I didn't do.
FYI, as long as you have fastboot there is never a need to worry
Click to expand...
Click to collapse
Really thanks for telling me this, I feel relieved already! :laugh:
deeper issues such as sensor problems.
Click to expand...
Click to collapse
really? sensor problems? omg
Use it to reinstall TWRP and unencrypted userdata ( only if needed) Then reinstall whatever Rom, Gapps ( if needed) and Root.
Click to expand...
Click to collapse
okok, how do I use it? which options to click on?
FIXED! Ok, I fixed by downloading the MIUI fastboot ROM located here >> http://en.miui.com/a-234.html
When you download the ROM, you need to extract it, because it comes downloaded as a .tgz, when you extract it becomes a .tar, then you need to extract AGAIN to have the final normal folder, inside this folder you will find all the needed .bat files.
Then you need the Mi flash tool >> api.en.miui.com/url/MiFlashTool
After you download the Mi flash tool, you need to connect your phone via usb and go into fastboot (volume up + power button), then inside the Mi flash tool you need to click on refresh to detect your device.
Once you see your device, you need to go to your final extracted folder and then copy the path of the folder (the location of the folder), by right-clicking the path and click on copy.
You now paste the path onto the mi flash tool, and then click on flash!
When it finishes flashing, it will reboot, but this time into the system! :laugh::laugh::laugh::laugh::laugh:
omg, I'm so happy this is fixed, i thought my mi 8 was gone forever!
Hopefully someone will find this useful in the future!
guyzz6370 said:
FIXED! Ok, I fixed by downloading the MIUI fastboot ROM located here >> http://en.miui.com/a-234.html
When you download the ROM, you need to extract it, because it comes downloaded as a .tgz, when you extract it becomes a .tar, then you need to extract AGAIN to have the final normal folder, inside this folder you will find all the needed .bat files.
Then you need the Mi flash tool >> api.en.miui.com/url/MiFlashTool
After you download the Mi flash tool, you need to connect your phone via usb and go into fastboot (volume up + power button), then inside the Mi flash tool you need to click on refresh to detect your device.
Once you see your device, you need to go to your final extracted folder and then copy the path of the folder (the location of the folder), by right-clicking the path and click on copy.
You now paste the path onto the mi flash tool, and then click on flash!
When it finishes flashing, it will reboot, but this time into the system! :laugh::laugh::laugh::laugh::laugh:
omg, I'm so happy this is fixed, i thought my mi 8 was gone forever!
Hopefully someone will find this useful in the future!
Click to expand...
Click to collapse
Glad you fixed it but you didn't really need to use the flashbat method for this issue. although yes it works.
I have written these exact instructions in the questions and answers section numerous times. You should still download and install AIT, in case you ever need it in the future. Plus, it has other great features such as keeping fastboot tools up to date, systemwide ADB use, as well as the many, many other features.
To help you understand what happened
Somehow, your data became encrypted, badly enough that you could not access your data, system or recovery. This issue has happened to alot of people including myself...many times.
So when I was talking about using AIT to remove encryption, what that basically means is the AIT tool formats the userdata/user storage. After that is resolved, you can, reinstall TWRP, and be back to being able to use custom roms again.
Now that you are restored,
Boot to TWRP and make a complete backup up of your installation, checking everybox.
Next connect to your PC and copy the backup from storage/Twrp/Backups, over to your PC.
Never delete this backup. If you have an issue in the future, such as Wifi, BT, or cellular not connecting, or if you have a Wifi mac address of 02:00:00:00:00 you can use the Recovery to restore your partitions, notably the persist partition.
Restoring your backup will fully resolve those kinds of issues, even when flashbat will not.
Enjoy
This issue has happened to alot of people including myself...many times.
Click to expand...
Click to collapse
I'm interested to read about this too, can you link me to some threads of other people having the same issue?
Now that you are restored,
Boot to TWRP and make a complete backup up of your installation, checking everybox.
Next connect to your PC and copy the backup from storage/Twrp/Backups, over to your PC.
Never delete this backup. If you have an issue in the future, such as Wifi, BT, or cellular not connecting, or if you have a Wifi mac address of 02:00:00:00:00 you can use the Recovery to restore your partitions, notably the persist partition.
Click to expand...
Click to collapse
Yeah, time to make a backup! A working one!
guyzz6370 said:
I'm interested to read about this too, can you link me to some threads of other people having the same issue?
Yeah, time to make a backup! A working one!
Click to expand...
Click to collapse
Sure this post has an issue that I also ended up having myself :
https://forum.xda-developers.com/mi-8/help/xiaomi-mi-8-wifi-issue-help-t3941288
Read through the post, everything that I recommended usually works ...most of the time. However, I recently had the exact issue where nothing worked including using Fastboot FlashAll.bat , and I tried several versions of stock and kept having persist issues, which caused my Wifi and mobile to not work. Note, the solution here is using your backup ( Using someone else's, apparently does not always work)
What finally resolved my issue was restoring my own recovery backups which fortunately I had previously made one with the Xiaomi EU version of the backup and it finally solved the issue.
For the record, booting the phone into EDL mode and using the QPST program to restore the factory rom should also work. Plus, QPST has a built in tool that is specific to repairing the Radio, IMEI, Mac Address Etc. Needless to say, restoring your TWRP backup is much much easier and much less stressful than doing trial and error with QPST.
See the screenshots ( attached) One backup made with official TWRP makes a highly compressed version of the backup. I would also suggest making a backup of with the linked version of TWRP from the Xiaomi.EU website, this version decompresses some of the driver images allow you to restore individual files such as individual persist images
TWRP-3.3.1-0607-XIAOMI8-CN-wzsx150 .zip ( Two Languages, Chinese and English)
https://mega.nz/#!QstBnAaD!V6riZpEjctWhzWhoFcDDEv0wRlFESfcEsxAHpdaerxE
tsongming said:
Sure this post has an issue that I also ended up having myself :
https://forum.xda-developers.com/mi-8/help/xiaomi-mi-8-wifi-issue-help-t3941288
Read through the post, everything that I recommended usually works ...most of the time. However, I recently had the exact issue where nothing worked including using Fastboot FlashAll.bat , and I tried several versions of stock and kept having persist issues, which caused my Wifi and mobile to not work. Note, the solution here is using your backup ( Using someone else's, apparently does not always work)
What finally resolved my issue was restoring my own recovery backups which fortunately I had previously made one with the Xiaomi EU version of the backup and it finally solved the issue.
For the record, booting the phone into EDL mode and using the QPST program to restore the factory rom should also work. Plus, QPST has a built in tool that is specific to repairing the Radio, IMEI, Mac Address Etc. Needless to say, restoring your TWRP backup is much much easier and much less stressful than doing trial and error with QPST.
See the screenshots ( attached) One backup made with official TWRP makes a highly compressed version of the backup. I would also suggest making a backup of with the linked version of TWRP from the Xiaomi.EU website, this version decompresses some of the driver images allow you to restore individual files such as individual persist images
TWRP-3.3.1-0607-XIAOMI8-CN-wzsx150 .zip ( Two Languages, Chinese and English)
https://mega.nz/#!QstBnAaD!V6riZpEjctWhzWhoFcDDEv0wRlFESfcEsxAHpdaerxE
Click to expand...
Click to collapse
Well well, it seems that there are some scary stuff that can happen to your device that thank God I personally don't have to deal with :laugh:
I was already scared sh**less when I started this post, and luckily for me my device is fine now running the PE ROM (so smooth and beautiful) and never encountered any radio/sensor issues..
So from what I can gather...always make a TWRP back up of your device so if anything stupid happens in the future (I think it's unlikely, but just to be safe...) you can easily restore and your device is safe again..so yeah thank God I don't have to deal with more complex issues :fingers-crossed:
And thanks for answering, it very comforting to know that there are people like you who answer on these forums whenever urgent help is needed...so thanks for that!:good::good:
guyzz6370 said:
Well well, it seems that there are some scary stuff that can happen to your device that thank God I personally don't have to deal with :laugh:
I was already scared sh**less when I started this post, and luckily for me my device is fine now running the PE ROM (so smooth and beautiful) and never encountered any radio/sensor issues..
So from what I can gather...always make a TWRP back up of your device so if anything stupid happens in the future (I think it's unlikely, but just to be safe...) you can easily restore and your device is safe again..so yeah thank God I don't have to deal with more complex issues :fingers-crossed:
And thanks for answering, it very comforting to know that there are people like you who answer on these forums whenever urgent help is needed...so thanks for that!:good::good:
Click to expand...
Click to collapse
Yes, exactly and although its somewhat rare it happened to me for no real reason, suddenly the phone froze and would not boot again. To be fair I was trying out an untested version of TWRP. However I was not experiencing any issues for weeks, until I installed Swift themer, similar to Substratum. Though I am not sure that it was related to the issue.
Bottom line, make the TWRP backup ASAP, it will literally take you no more than 15 minutes to make it and back it up to your PC. This way you never ever have to worry about unpredictable issues., pass it on to any friends or relatives to do the same.
Enjoy your awesome phone, Cheers.
tsongming said:
Yes, exactly and although its somewhat rare it happened to me for no real reason, suddenly the phone froze and would not boot again. To be fair I was trying out an untested version of TWRP. However I was not experiencing any issues for weeks, until I installed Swift themer, similar to Substratum. Though I am not sure that it was related to the issue.
Bottom line, make the TWRP backup ASAP, it will literally take you no more than 15 minutes to make it and back it up to your PC. This way you never ever have to worry about unpredictable issues., pass it on to any friends or relatives to do the same.
Enjoy your awesome phone, Cheers.
Click to expand...
Click to collapse
So I tried restoring from the backup and...wasn't what I expected..I expected it to be 100% exact. I thought it will be as if I restarted my phone and when I turn on the phone again, it will be like nothing ever happened..
but the restore feature isn't perfect
Firstly, when I checked all the partitions to restore, it gave me the 255 error..so what ended up working for me was to uncheck the recovery,cache, and data partitions..this restored the device and the device booted (it wasn't booting before this, it will show the mi logo and shut off).
After booting up, I still needed to set up my phone..
But other than that...it does seem to save some of phone's settings
certain settings, wallpapers, status bar icons, home screen icons..these things seem to have been saved..but everything else is still starting from fresh..
What gives? I thought it was supposed to behave as if I restarted my phone and nothing happened...
guyzz6370 said:
So I tried restoring from the backup and...wasn't what I expected..I expected it to be 100% exact. I thought it will be as if I restarted my phone and when I turn on the phone again, it will be like nothing ever happened..
but the restore feature isn't perfect
Firstly, when I checked all the partitions to restore, it gave me the 255 error..so what ended up working for me was to uncheck the recovery,cache, and data partitions..this restored the device and the device booted (it wasn't booting before this, it will show the mi logo and shut off).
After booting up, I still needed to set up my phone..
But other than that...it does seem to save some of phone's settings
certain settings, wallpapers, status bar icons, home screen icons..these things seem to have been saved..but everything else is still starting from fresh..
What gives? I thought it was supposed to behave as if I restarted my phone and nothing happened...
Click to expand...
Click to collapse
What? It seems that you missed the point of what I was suggesting.
Why would you assume that the restore would restore everything and it would be like nothing happened, where did I say that? Restoring the back would definitely be like nothing happened to your missing partitions.
I never said anything about fully restoring your phone although that is indeed completely possible if done right, and you restore the system base and files in storage that were present when you made the backup.
The only thing that I was talking about is when/ if you eventually experience a unsolvable persist issue. If you flash a lot of different roms, frequently it is a problem that you may eventually experience for yourself. Google Xiaomi persist issue. A lot of people had that issue about a month ago.
So again, the point is to have a quick fix on hand, that you can restore, drivers and crucial partitions without having to use EDL mode.
The full backup does not include your files, or settings and that message appears within TWRP when you make the back up.
Some devices including Xiaomi have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. However, it's usually a good idea to make a single backup of these partitions and hang on to them just in case.
tsongming said:
What? It seems that you missed the point of what I was suggesting.
Why would you assume that the restore would restore everything and it would be like nothing happened, where did I say that? Restoring the back would definitely be like nothing happened to your missing partitions.
I never said anything about fully restoring your phone although that is indeed completely possible if done right, and you restore the system base and files in storage that were present when you made the backup.
The only thing that I was talking about is when/ if you eventually experience a unsolvable persist issue. If you flash a lot of different roms, frequently it is a problem that you may eventually experience for yourself. Google Xiaomi persist issue. A lot of people had that issue about a month ago.
So again, the point is to have a quick fix on hand, that you can restore, drivers and crucial partitions without having to use EDL mode.
The full backup does not include your files, or settings and that message appears within TWRP when you make the back up.
Some devices including Xiaomi have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. However, it's usually a good idea to make a single backup of these partitions and hang on to them just in case.
Click to expand...
Click to collapse
oh.. because i thought it would be perfect like nothing happened ? that's the whole point of backing up right?
I expected to be like a normal hard disk on your computer..on a hard disk i can just make a clone of the disk and clone it to a new hard disk, and the computer starts like nothing happened...
so i assumed it was the same for a phone too, but apparently not ?
guyzz6370 said:
oh.. because i thought it would be perfect like nothing happened ? that's the whole point of backing up right?
I expected to be like a normal hard disk on your computer..on a hard disk i can just make a clone of the disk and clone it to a new hard disk, and the computer starts like nothing happened...
so i assumed it was the same for a phone too, but apparently not ?
Click to expand...
Click to collapse
Miui local backup works something like that. Titanium backup used to be awesome for that kind of restore, but on pie roms it's kind of buggy
If using an Aosp rom, there is a program called migrate that can restore apps but the user data part hasn't always worked for me.
TWRP full restore, along with manually restoring storage media from the desktop will be close to using a restore point from a PC or restoring a time machine backup on a mac but still not the same.
Now you have the backup so your phone is safe from weird future issues. If that ever happen message me and I will help you .
Sent from my Xiaomi MI 8 using XDA Labs

Question My Realme x7 max 5G stuck in recovery loop after uninstalling bloatare like glance, finshell pay, hot apps

like the title says I uninstalled the mentioned apps using adb and all of a sudden my camera stopped working so I decided for a simple restart and the device stuck in the loop ever since.
it restarts several times and open realme UI recovery and when I choose language it says " KINDLY REMINDER : system error, after select language, please select Online update(keep data) to recovery system, thanks! " .
So I did what the message said and I connect the wifi but instead of updating it says no updates found.
I also tried to wipe data but I got asked whether to retain contacts/media or format data.
I obviously tried the first one because I need the data but as expected it didn't work.
I am skeptical to clean format because I feel that I can still fix it with retaining the data.
I tried all the key combinations but only the realme UI recovery comes up . Please help me!
thank you
I don't think you'll be able to fix this without a full reflashing of the ROM using SP Tools and a format of the data partition from Recovery. You probably don't have access to full ADB now, if at all, and Fastboot won't help you recover anything. However, you should be able to rescue important files before you do this, as long as you have unlocked your bootloader.
Follow the steps here to install TWRP custom recovery. Once done, you can boot into it from fastboot by running `fastboot reboot recovery`. Once you're in TWRP, you can mount partitions so you can access them over USB from your PC.
Once you've got your important files transferred to your PC, take a full backup to be safe, then flash the stock ROM. This thread can help you do both of those things. Note that flashing the stock ROM using SP Tools will also restore the stock recovery. Once the process is done, boot right into fastboot and use it to reboot back into the stock recovery before letting it actually boot the ROM. Format your data partition (yes the whole thing). Now you can restart, and it should go through first time setup just fine.
I was going to uninstall these apps, but was too lazy. Guess lazyness is not too bad after all.
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
e_v_i_l_x_ said:
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
Click to expand...
Click to collapse
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance !
Ricodey said:
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance
Click to expand...
Click to collapse
for me the issue was like i just downgraded my device to the a.15 firmware after setting up i uninstalled the bloatware apps and some google apps which were not needed obviously and restarted my device and it got a bootloop, the issue of bootloop wasn't new to me i previoulsy had the same issue when i have downgraded to a.19 firmware. there is a simple fix, if you want to get rid of the bloatware apps now also you can use the disable command like.
(pm uninstall-user --user 0 ----package name---) this will not give any bootloop and can enjoy a part of RAM....
THIS WILL HELP
get in touch if need anything else

Categories

Resources