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.

Phonne won't get past boot logo after installing xposed module

i have successfully managed to install xposed framework and reboot my phone without any errors. But after i activate one module andm then reboot, my phone stucks on a boot logo forever until i wipe all data via recovery mode. What might be the cause of this, and how can i solve it?

phillipjack said:
i have successfully managed to install xposed framework and reboot my phone without any errors. But after i activate one module andm then reboot, my phone stucks on a boot logo forever until i wipe all data via recovery mode. What might be the cause of this, and how can i solve it?
Click to expand...
Click to collapse
We cannot help you at all.
We do not know what phone you have. We do not know what ROM your phone has. We do not know what version of Xposed you tried to install. We do not know what method you tried to install it with. We do not know what module you are trying to activate. We do not know what mistakes you made, what error messages were generated, or what was recorded in your log files.
We do not know why you didn't create a backup before installing Xposed, or why you don't restore that backup now.
Without all of this information, we cannot help you.

How to recover from Verification Failed, Bootloops, and Android/Carrier logo freeze.

In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!​
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!​
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10

Post any bricks below that you have encountered!
I'm interested in how many variations there are, and how common they are.

One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?

Hovo said:
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Click to expand...
Click to collapse
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?

TechNash said:
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
Click to expand...
Click to collapse
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.

It goes away when u log in to google with the last account that is associated with the phone

Hovo said:
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
Click to expand...
Click to collapse
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.

TechNash said:
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
Click to expand...
Click to collapse
It would make sense if it was an OTA update TY

Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?

Nightwinter said:
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Click to expand...
Click to collapse
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.

TechNash said:
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
Click to expand...
Click to collapse
Keep what in the SD card? the is no file in your quote.

Nightwinter said:
Keep what in the SD card? the is no file in your quote.
Click to expand...
Click to collapse
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs

graevon said:
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
Click to expand...
Click to collapse
Thanks for explaining that to him.

TechNash said:
Thanks for explaining that to him.
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data

Mujeeb64 said:
how to remove Verification Failed or root in the TWRP file manager without losing data
Click to expand...
Click to collapse
Flash ashyx-no-verity-no-encrypt.zip in twrp.
Reboot

TechNash said:
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!​
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!​
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Click to expand...
Click to collapse
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.

smirk24 said:
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
Click to expand...
Click to collapse
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.

TechNash said:
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
Click to expand...
Click to collapse
Id love to but i dont know how to get the marshmallow software and install it to the phone but id like to learn how.

How to recover from Verification Failed without losing data ?​Does installing TWRP via Oddin Works and does it able me to transfer my data after installing TWRP ? I dare not try doing it as i have never did it b4

Nokia 8 hangs on boot

Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys

t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp

MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...

t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky

t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...

shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.

Question Redmi Note 10 Pro Bootloop

Using crDroid 7.16 (Android 11) and TWRP 3.6.1_11 (twrp-3.6.1_11-0-sweet), unlocked of course, and rooted with Magisk v25.1, the phone suddenly entered a boot loop.
It will show the Redmi logo, then the CrDroid boot sequence, and then restart.
It is NOT possible to enter recovery, it will show the TWRP screen, and then just do nothing (not even reboot)
It is NOT possible to turn it off, it will just reboot no matter how long the power button is pressed
It IS possible to enter Fastboot
I have tried removing the SIM, no changes. Tried fastboot commands, to boot directly into TWRP (3.6.1, and 3.6.2) or flash a new TWRP - nothing works. Still bootloop, still can't turn it off, still not possible to go into TWRP.
Hoping for any ideas, I'm clueless.

J.PG said:
Using crDroid 7.16 (Android 11) and TWRP 3.6.1_11 (twrp-3.6.1_11-0-sweet), unlocked of course, and rooted with Magisk v25.1, the phone suddenly entered a boot loop.
It will show the Redmi logo, then the CrDroid boot sequence, and then restart.
It is NOT possible to enter recovery, it will show the TWRP screen, and then just do nothing (not even reboot)
It is NOT possible to turn it off, it will just reboot no matter how long the power button is pressed
It IS possible to enter Fastboot
I have tried removing the SIM, no changes. Tried fastboot commands, to boot directly into TWRP (3.6.1, and 3.6.2) or flash a new TWRP - nothing works. Still bootloop, still can't turn it off, still not possible to go into TWRP.
Hoping for any ideas, I'm clueless.
Click to expand...
Click to collapse
Try to flash newest orange fox recovery 12.1 or TWRP via PC again and reboot in it via hardware keys. Then format data with yes and reboot recovery. Flash ROM . Reboot system. Flash magisk after first Boot.

Laptapper said:
Try to flash newest orange fox recovery 12.1 or TWRP via PC again and reboot in it via hardware keys. Then format data with yes and reboot recovery. Flash ROM . Reboot system. Flash magisk after first Boot.
Click to expand...
Click to collapse
Thank you - tried it with Orangefox, directly booting and flashing, but the same issue as with TWRP - it shows the logo screen, and then just stops and does nothing for at least a few minutes.
I feel like the phone is having trouble decrypting or even accessing any of the data?
At this point I think there might not be a way to fix it without losing any data?
And even full wiping and flashing a stock ROM seems difficult, since I can't access recovery at all.

J.PG said:
Thank you - tried it with Orangefox, directly booting and flashing, but the same issue as with TWRP - it shows the logo screen, and then just stops and does nothing for at least a few minutes.
I feel like the phone is having trouble decrypting or even accessing any of the data?
At this point I think there might not be a way to fix it without losing any data?
And even full wiping and flashing a stock ROM seems difficult, since I can't access recovery at all.
Click to expand...
Click to collapse
I've told you to format data with yes. No other way.
Of course you loose every data

just encourage yourself until you execute
fastboot -w

Laptapper said:
I've told you to format data with yes. No other way.
Of course you loose every data
Click to expand...
Click to collapse
Alright. The problem is, that I can't get into the recovery, not with booting into it directly from fastboot, or flashing any other TWRP or Orangefox version and using hardware keys. It just won't load.
So seems like "fastboot -w" is the best option.