Database Develop

[Q] Stuck in CWM bootloop

Hi,
So I finally got my first error. :crying:
I did a reboot from an app called quick reboot to recovery, and now I am stuck in CWM bootloop.
The sad thing is that I went into recovery to do a nandroid so doing a restore from that backup didn't help.
Any way to fix this without flashing the device back to stock?
Thanks!
Edit:
Sorry, forgot to mention I am running cocore 3.9 kernel with deodexed JB.

YMatrix said:
Hi,
So I finally got my first error. :crying:
I did a reboot from an app called quick reboot to recovery, and now I am stuck in CWM bootloop.
The sad thing is that I went into recovery to do a nandroid so doing a restore from that backup didn't help.
Any way to fix this without flashing the device back to stock?
Thanks!
Edit:
Sorry, forgot to mention I am running cocore 3.9 kernel with deodexed JB.
Click to expand...
Click to collapse
You know how to use ADB shell? You need to install any other kernel with dd command, or try to do "reboot" from ADB shell in recovery.

I have used the ADB shell on a sony xperia phone so I know more or less how to use it.
Do I need to install any additional files for my phone, or is the ADB ready for my phone (in the xperia I had to get the google usb driver and update it to be able to get into fastboot mode)?
How do I get the phone to be recognized by ADB if i'm stuck in recovery mode?
Which commands do I need to run to reboot the device?

Ok, this is weird. It is fixed by itself
I actually didn't do anything.
I removed the battery again to turn the device off.
I got the cable plugged to my PC (the device showed the charging logo) then turned the device on (to get ready to use ADB).
Surprise surpise the device booted up normally.
I had already tried the process of removing the battery, and did multiple reboot from the CWM option, with no success before.
Now to try to understand.
What just happened?
Why did it get stuck in the recovery bootloop in the first place (I have used this app on GB, so it should also work on JB)?
How did it fix itself? Connecting the cable before the device was on "freed it" somehow?
Most importantly what do you need to do if that happens in the future?
If you have any advice how to backtrack what happened, I would be glad also to share for other users who might come across this situation.

YMatrix said:
Ok, this is weird. It is fixed by itself
I actually didn't do anything.
I removed the battery again to turn the device off.
I got the cable plugged to my PC (the device showed the charging logo) then turned the device on (to get ready to use ADB).
Surprise surpise the device booted up normally.
I had already tried the process of removing the battery, and did multiple reboot from the CWM option, with no success before.
Now to try to understand.
What just happened?
Why did it get stuck in the recovery bootloop in the first place (I have used this app on GB, so it should also work on JB)?
How did it fix itself? Connecting the cable before the device was on "freed it" somehow?
Most importantly what do you need to do if that happens in the future?
If you have any advice how to backtrack what happened, I would be glad also to share for other users who might come across this situation.
Click to expand...
Click to collapse
What happend is the problem with J4FS driver in system (kernel). So do not use Reboot recovery untill it is fixed in kernel.
Probably removing battery reseted it, and you could go to system normaly.

shut_down said:
What happend is the problem with J4FS driver in system. So do not use Reboot recovery untill it is fixed in kernel.
Probably removing battery reseted it, and you could go to system normaly.
Click to expand...
Click to collapse
But I just now succeeded going into recovery the normal way (turn off device -> vol up+home+power) 3 times (also did another nandroid :good and back to system with no problems. So I am guessing there is a bug when trying to reboot to recovery with the app?
If removing the battery did the trick why didn't it work the first time I did it?

YMatrix said:
But I just now succeeded going into recovery the normal way (turn off device -> vol up+home+power) 3 times (also did another nandroid :good and back to system with no problems. So I am guessing there is a bug when trying to reboot to recovery with the app?
If removing the battery did the trick why didn't it work the first time I did it?
Click to expand...
Click to collapse
Problem is with doing command "reboot recovery" while you are booted in system. That does not consider going there by using hardware buttons. For ability to use reboot recovery from some app you need fixed J4FS driver in kernel. I got bootloop to recovery too with some version of CoCore. Now you can't do anything untill it is fixed. Look at kernels thread for updates, and report your problem.
About that solution, I do not know. I solved it with flashing other kernel from recovery with ADB shell and DD command. Didn't try anything else.

Thank you!
I will notify cocafe of the bug.

[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

bootloop (starting, charging mode and also, with pc) z3c how to solve?

Hi guys, first of all sorry for my bad english
anyway, when I tryed to restart my phone, it was going to infinite bootloop... so, I tryed to lauch twrp and swipe all data also reinstalling the rom with adb/pc.. but in this moment happened the inaspected.. it go, to bootloop even if it was off, (changer screenshot, bootloop)
How Can I lauch adb, if my pc doesnt finds my z3c , because it goes to bootloop even if is off?

Xalein said:
Hi guys, first of all sorry for my bad english
anyway, when I tryed to restart my phone, it was going to infinite bootloop... so, I tryed to lauch twrp and swipe all data also reinstalling the rom with adb/pc.. but in this moment happened the inaspected.. it go, to bootloop even if it was off, (changer screenshot, bootloop)
How Can I lauch adb, if my pc doesnt finds my z3c , because it goes to bootloop even if is off?
Click to expand...
Click to collapse
So it won't stay off, even if you press power and volume up together for a few seconds? Which rom were you using, what did you do before it bootlooped, bootloader unlocked, etc...?

levone1 said:
So it won't stay off, even if you press power and volume up together for a few seconds? Which rom were you using, what did you do before it bootlooped, bootloader unlocked, etc...?
Click to expand...
Click to collapse
even it wont stay off, always bootloop;
If I remember well, first I unlock the phone with the code from sony; after launch the twrp with adp on pc (for a strange motive it (the phone) doesnt load the twrp without pc) , clean cache and co, like 2/3 times, after installing the new rom
it seems to me the omni rom 7.1.2

Xalein said:
even it wont stay off, always bootloop;
If I remember well, first I unlock the phone with the code from sony; after launch the twrp with adp on pc (for a strange motive it (the phone) doesnt load the twrp without pc) , clean cache and co, like 2/3 times, after installing the new rom
it seems to me the omni rom 7.1.2
Click to expand...
Click to collapse
Sorry to repeat, but just to be clear - when you press and hold power and volume up, what happens? Are you saying it turns off, and then automatically turns back on, and bootloops?

levone1 said:
Sorry to repeat, but just to be clear - when you press and hold power and volume up, what happens? Are you saying it turns off, and then automatically turns back on, and bootloops?
Click to expand...
Click to collapse
strangely this time go, it go on twrp..
but since I have encrypted, twrp request me the pass.. but, inserting the right pass, it always failed.. there is a way, to bipass this process (even with formatting the phone) to acess to twrp?

Xalein said:
strangely this time go, it go on twrp..
but since I have encrypted, twrp request me the pass.. but, inserting the right pass, it always failed.. there is a way, to bipass this process (even with formatting the phone) to acess to twrp?
Click to expand...
Click to collapse
Try fastboot flash, (different kernel or different recovery...), or flash stock rom with FT.

levone1 said:
Try fastboot flash, (different kernel or different recovery...), or flash stock rom with FT.
Click to expand...
Click to collapse
I solved with format data.. thanks
I have to re-installed the rom.. but I just to have wait to understand if it is still a bootloop or the classic installation phase..

Xalein said:
I solved with format data.. thanks
I have to re-installed the rom.. but I just to have wait to understand if it is still a bootloop or the classic installation phase..
Click to expand...
Click to collapse
10+ minutes is not unusual for first boot for stock rom.

levone1 said:
10+ minutes is not unusual for first boot for stock rom.
Click to expand...
Click to collapse
solved
but futhermore, another problem (hardware problem, I don't want to open another post):
today I open my cell phone because the screen had stuck, discovering that the connector had disconnected.. ok solved.. but the cellphone seems electrically charged, I mean more than 5 (I think) time I got the shock
any solution?/possible causes? (isnt the first time that I open the phone)

Stuck in a bootloop, any hopes?

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.

Question Xiaomi Note 11 stuck to rebooting into recovery mode 5.0 after unlocking the screen

Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.

I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...

Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001

asabaraba said:
Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001
Click to expand...
Click to collapse
It's really weird that it happens to other people too!

AdonysGames said:
I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...
Click to expand...
Click to collapse
That might be it since it happens not only to me.

Same problem happening for me too from today. Anyone know a fix for it ?

hrishi654 said:
Same problem happening for me too from today. Anyone know a fix for it ?
Click to expand...
Click to collapse
Did a second data wipe and it worked this time, the phone's been running all night without any issue. I disabled xiaomi updates for the time being

Same issue here, please any solution, I've not been able to do anything since 48 hours

Is there a way to go through this without losing my data and files?

same problem i will try to wipe data again and see if it works

ReaperCat65 said:
Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.
Click to expand...
Click to collapse
I didn't put mine to charge and this happened

mateuszzsa said:
same problem i will try to wipe data again and see if it works
Click to expand...
Click to collapse
Can you give us an update if it works? I also post the problem on Reddit and some people there were also able to fix it by wiping the data.

Will wiping the data fix the issue, if it does, please do let us know

Dr_toluwani said:
Will wiping the data fix the issue, if it does, please do let us know
Click to expand...
Click to collapse
47 minutes since i wiped the data by the second time and my phone its working, I don't know until when.

Does anyone know of way to save the data? Surely it must be accessibl.

ishouldbeworking said:
Does anyone know of way to save the data? Surely it must be accessibl.
Click to expand...
Click to collapse
I found a way to do so. The problem is that once the phone is unlocked you have a few minutes before it gets booted into recovery mode. So:
Step 1) Have the phone connected to a computer before booting it up, with file explorer in the "this pc" category (where the phone storage will appear)
Step 2) boot the phone and input the password (if any)
Step 3) QUICKLY pull down the notification bar and press the usb options notification
Step 4) QUICKLY press the second option for file transferring
Step 5) QUICKLY open phone storage from pc once it pops up (at this point the phone screen will probably be black with a white loading circle but the phone storage is still accessible!!! You now have a few minutes to transfer any data you want)
Step 6) QUICKLY search through phone storage for any important data and copy/paste it to your computer
Sooner or later the phone will be booted to recovery mode and the mi logo will appear and the phone storage will disappear from the computer so repeat above steps until all your data is backed up.
If a file transfer gets stopped while running, copy/paste the data again on the next "run" and choose to ignore files that are already copied. With this method I managed to backup all my photos and files before wiping the phone.

This problem might be due to a problematic firmware update. My phone was running MIUI version 13.0.12(RGKEUXM) (europe version). I wiped the data and updated my phone to version 13.0.13(RGKEUXM) after setting it up just in case. I will update this thread if the problem reappears.

I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.

akallabeth said:
I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.
Click to expand...
Click to collapse
did you try to perform 2 wipes? apparently my device is working properly after that.

mateuszzsa said:
did you try to perform 2 wipes? apparently my device is working properly after that.
Click to expand...
Click to collapse
Which wipe method did you do? Just a factory reset or a reflash?