Hey there,
i have TWRP installed and used Lineage Custom Rom. Everything was stable and worked great for the last few weaks.
Today my phone was connected to the charger and when I came back it showed the LG Logo and the little text "Bootloader state: Booloader unlocked!".
If i restart the phone it again ends at that screen (excpet once it kept booting but crashed after about 30 seconds that i used it).
I am NOT able to get to recovery anymore. If I try to I select "Yes" on the first screen. Then I select "Yes on the second screen" but this freezes the phone again.
What can I do?
All the best and already thank you very much for your help!
Related
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
I'm unfortunately stuck in a very similar situation.
I was updating the firmware on my tablet to 4.4.2 downloaded off Sammy mobile, uploading using Odin. I've done this dozens of times since my S2 which was 12 handsets and 6 Android tablets ago. This time, about a third of the way through the process hung for a few minutes then the device restarted without warning and now its stuck in a loop where it starts normally
http://imgur.com/MTwiE5V [1]
Then says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery.
Then this
http://imgur.com/Ua1nmhi [2]
and stays on that screen for short periods before rebooting and starting the above again.
Thanks in advance for any tips or help you guys can provide!
SleepyDonald said:
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
Click to expand...
Click to collapse
Have tried factory reset/clear cache/clear dalvik?
shayind4 said:
Have tried factory reset/clear cache/clear dalvik?
Click to expand...
Click to collapse
Thanks, but it turns out the solution to my problem was simple. I took it to the place I got it from and the guy just pressed power, vol and menu button long enough until it rebooted. I'm quite a noob it seems.
I'm not sure if it will help you Nationalmaverick, because my problem was slightly different.
First, thank you to anyone willing to give me some advice.
Today while using my tablet it randomly restarted and was stuck at the "swirling balls of light" for a couple minutes. I held the power button to turn it off and then restarted it except not it was stuck at the black screen with the Google logo. I can get to the recovery console but any option I choose other than "power off'" just takes me back to the Google screen.
I tried the WugFresh toolkit using Flash Stock + Unroot with the soft-brick option and it finished in under 10 seconds with some failures due to the bootloader being locked. I tried the toolkit's recommendation and ran it again in "force flash" mode and this time it lock up at "erasing cache".
I should say I'm not rooted and I received the newest update about 2-3 weeks ago.
Any advice?
Hello everyone,
Yesterday when I was going to use my tablet I noticed it was off, but minutes before it was on, so I tried pressing the power button and nothing happened, plugged the charger in, nothing, no signs, it seemed bricked, so I tried to power through download mode and it worked, after that I pressed volume down to cancel it to start normally, the first samsung logo showed up (that one that says the model and stuff), but it was there for really long, i left it running and after 5 mins or so it changed to the pulsing blue samsung logo, left it there and about 30 mins later it was back to the 1st samsung logo again. I also tried a soft reset and booting to safe mode, didn't work either.
This tablet has no custom rom installed (I think it is on stock 4.4.2), the only thing different I installed is TWRP and root, years ago, but I cant boot to TWRP through the vol up+home+power, it doesnt work, tbh it never worked since back then, the only way I found to boot to twrp was thru "adb reboot recovery" using adb, which didnt work in download mode, I want to be able to backup some data before flashing it with Odin, so here are my questions:
1- Is there any other command I could try to force it to boot to recovery?
2- Is there any way to backup data via download mode on this device?
Thank you for your attention
Hi,
I have a Brazilian stock mMoto Z2 Force, XT1789-05, never unlocked the bootloader or root or whatever in this phone, just did the normal Motorola updates as they arrived.
2 months ago I had some battery issues, changed it and was working just fine until this morning. Today the phone restarted after I closed the alarm, and got stuck in boot loop.
I read some threads about this problem for people messing with Roms and baseband, but they don't really apply for me.
The phone reaches the Motorola logo and after a few seconds it restarts.
I can go into fastboot and select recovery mode, but then there's just a black screen with "No commands" written.
Tried Factory Mode with no success.
LMSAA don't recognize the phone, and don't let me select the correct one.
Is there anything else I could try? Maybe force LMSA to do it's magick? manually selecting my phone model for example?
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.