Related
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
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
bazanster said:
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
Click to expand...
Click to collapse
Flash a stock ROM, preferably LP and see if it works, this is done through fastboot, look around.
bazanster said:
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
Click to expand...
Click to collapse
I faced the same problem here is what i did
flash the twrp2.8.x again in fastboot mode
boot into recovery
restore your backup if you have backedup your previous rom
Rohit99 said:
I faced the same problem here is what is did
flash the twrp2.8.x again in fastboot mode
boot into recovery
restore your backup if you have backedup your previous rom
Click to expand...
Click to collapse
Thanks man, as simple as it was, it worked <3
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
wilsonhlacerda said:
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
Click to expand...
Click to collapse
Unfortunately, nope..
Jasiniok said:
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Click to expand...
Click to collapse
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Kglim said:
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Click to expand...
Click to collapse
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Jasiniok said:
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Click to expand...
Click to collapse
I think you could save ur data partitiin and sjust system wipe and dirty flash for carry yiur data.
Good luck to ya!!! :fingers-crossed:
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.