Hi all,
I'm running CM11 on a Moto G. Due to work requirements I encrypted my phone via the security settings. It all went as expected, until I got to the screen where I have to enter my password to decrypt storage...
Once I enter the correct password, it loads a screen with an android on (I think it was similar to the one from the encryption screen) very briefly, then goes blank. I presume it turns off as it doesn't do anything else for quite a while. If I reboot and try enter an incorrect code, it prompts for the right code, so I'm definitely entering the correct pin.
My questions is - is there any way around this (without wiping the phone)? Any idea what's gone wrong?
I can still access recovery, but obviously it's rather limited as it's all encrypted. Is there any way I can connect via PC to get my files and decrypt them as I know the password?
Unfortunately my OnePlus is no longer able to function and would like some assistance/suggestion from the community.
OnePlus has TWRP installed
- installed Paranoid Android rom = no issues
- enabled encryption
Now here is where the issue occurs.
When I start the phone I am able to see the PA bootup screen, it prompts me to enter the password. Once the password is entered "bugdroid" appears on the screen for a quick flash and then disappears. The screen continue to stay blank/black with no further progress, I have left the phone in this state for at least 20mins but it still doesn't proceed further. It should also be noted the the soft keys STAYS lit once the password has been entered for decryption.
I am still able to boot into recovery, enter my password to decrypt and use the standard TWRP functions. It should be noted that unfortunately I haven't done a backup on the phone at all {something that I totally regret right now), plus there is no rom left on the phone for me to attempt a install.
Any help is appreciated
note: the phone as able to complete its bootup process when I initially activated encryption but has failed ever since the first reboot
There are multiple threads discussing this in the very section you posted this thread in. Have a look, you'll find what you need.
Transmitted via Bacon
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
hardballer83 said:
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
Click to expand...
Click to collapse
I guess you've tried this, but power on by holding power+down vol. Should get you to bootloader. Keep holding it until bootloader screen appears. Holding power for 10-20 seconds should power down tablet.
Sent from my HTC One M8 using XDA Free mobile app
Hi
Thanks for your answer.
Yup I tried it, I tried all the ways I found on the internet (there's a post somewhere in this forum where 7 or 8 different methods are explained) none of it worked.
So, did you have TWRP loaded on the regular flash partition vs. the Recovery partition?
Is it possible you were running TWRP as the Operating System, and when you wiped the partition, you destroyed the OS?
TF300T bricked?
Hi,
hardballer83 said:
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
Click to expand...
Click to collapse
Hi, Had the same thing happen to mine. Hold own power to force shutdown then hold volume down and recovery screen should come up. Worked for me.!
@hardballer83
Unfortunately a bad situation caused by yourself!
If you don't have any fastboot or ADB-access to your tablet now, only a new MB can bring your device back to life again.
I've had a problem with my phone since flashing Lineage and Gapps in TWRP, something went wrong, it's acting like I have a corrupted version of Lineage with only the basic functions, Gapps is not installed and I've lost root.
The phone is an Xperia Z5, prior to flashing Lineage zip I had successfully rooted the phone, i flashed Lineage and then Gapps, an error appeared saying Gapps had not installed (possibly because it was the wrong version). After that the phone went into a bootloop (Sony logo, battery icon, then restart with red light in the corner). I was able to turn the phone on by holding down the power button for 5 seconds and lineage started up as normal with just the basic apps, I have been using the phone for the last month like this unable to find an answer on the forum. If I was able to connect the phone to PC i could use flashtool to flash the stock rom and start from scratch, but it only charges even though i have usb set to MTP in developer options, it's not detected by PC no matter how many cables I try. Also, it will not install apps from the Play website, it downloads and says app is installed but app isn't shown in list of apps. Can't get into TWRP because it says device is not rooted. When I switch phone off it restarts again and goes into bootloop, have to hold down power button to start it up. I wondered if anyone was familiar with these strange symptoms and knew if there was any way out? My phones stuck in limbo until I can find a way of doing a hard reset but without being able to get into TWRP or connect phone to PC I'm stuck.
Hi!
I hope (VERY MUCH) that I must not through away my new bought XA2 ultra, after trying to install lineageOS just following the tutorial on the official page!
I activated the USB-debuging
opened the bootloader
seted the phone to the fastboot mode
booted the TWRP
formated, wiped everything
installed the LineageOS 16 (first time in sideload way, second time directly install on the sd card)
then i recognized, that there is no possibility for wlan (it could not be turned on, MAC-Adress was just something like 02:00:00 ...)
tried then the official SU-app (so installed it over TWRP on the sd card)
after that device hanged while booting (showing the circle, going on the line)
i formated everything, wiped in TWRP
installed just the lineageOS 16
now i have another problem:
the battery live is at the last red bar
if i let the device powering on the USB it starts after a while on itself and boot to the system
then its crashes to blackscreen (with red dot on)
after a while it starts again... and so on.
so i enter the system and then it crashes after some time.
i don't really understand, if the device is charging, while its in the system
the same issue was, as i was in the TWRP, it crashes while installing if i'm not quick enough.
if i let the device just lying on the table, it doesn't start by itself, but it also can not charge the battery.
Don't understand the problem and hope very much, that the new bought thing must not end up in the trash. :crying:
regards
layla
#Edit:
i read everywhere about wiping cache, but i saw and see not possiblity, because there is no option with "cache". I have davlik/art cache, system and data (by the way, it sais, that it can not find the data folder), but i have no folder option with "cache".
The problem seems to be in the missing possibility for the phone to charge.
It seem, that it was possible to charge it over the fastboot mode, but the charge notification sign shows just always 50%.
For now it doesn't crashes, i think until the battery is very low again.
So the actual problem seems to be the problem with charging (i tested the direct connection with the wall socket, with different cable AND laptop USB connection) and the problem with Wifi.
If I connect it just to the socket in the wall, it shows me no connection at all. If I connect it to PC, it shows me a connection, but it don't charge (just if I turn it off and put it to fastboot mode)
after flashing older firmware (oreo) 50.1.A.4.76_R1A and installing LOS 16 again, the issue with wifi and battery stays. So i can not charge the battery in the OS (just in fastboot mode) and i can not activate wifi.
The solution here: https://forum.xda-developers.com/android/general/fix-wifi-connecting-mac-address-t3891628 doesn't work for me, because i can not find any persist.img file in the firmware folder.
some ideas?
this firmware fixes the battery problem: H4213_Commercial and Journalists_1313-9995_50.1.A.5.59_R1A
but the wifi problem stays.
very easy solution for the wifi problem!
Just start the original Android (oreo) BEVORE installing the LineageOS, activate wifi there and THEN restart to TWRP, format, wipe and install the LOS. Then everything works well!