[Q] Stock Recovery, Encryption and OTA - G 2014 General

This seems silly, but I'm on 22.11.6.titan_retuaws.retuaws.en.US.retus and have encrypted my phone. When I copy the OTA to the sdcard and then boot into recovery to apply the OTA, it never prompts me to decrypt the phone. Does anyone else have this problem?

Related

Encrypting the phone resulted in a bootloop

Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
jodvova said:
Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
Click to expand...
Click to collapse
Chances are very low. I had the same issue and the only way I was able to fix it was to use the Google factory image and completely wipe the phone. Then boot it before flashing anything including TWRP. It encrypts in about a minute. Setup the phone, and then flash TWRP, modified root boot image if you want, and the corresponding SU zip.
Sent from my Nexus 6P using Tapatalk

Stuck in a bootloop, please help

So I had my phone with TWRP and rooted, but then I upgraded to the latest firmware using Smart Switch on my PC.
Without doing any research I then stupidly flashed TWRP to my phone thinking I would just re-root it using TWRP and flashing the latest SUPERSU file; however, now TWRP doesn't recognize my internal storage and it is stuck in a boot loop unless I can flash SUPERSU or DT Verity fix. The internal storage is not recognized by my computer either when I plug my phone on even if I enable MTP in TWRP, I think this is something to do with the last USB debugging options but I am not sure?
What is my best solution without wiping my data?
If I copy the files to an SD card will TWRP recognize them? I am guessing no?
Can I flash stock back over TWRP to save my data? If so I am on Wind Mobile Canada, what file should I be flashing?
Lastly, I believe there is someway to send the files over ADP but I can't find any straight forward instructions on how to do so.
Thanks,
superskid said:
So I had my phone with TWRP and rooted, but then I upgraded to the latest firmware using Smart Switch on my PC.
Without doing any research I then stupidly flashed TWRP to my phone thinking I would just re-root it using TWRP and flashing the latest SUPERSU file; however, now TWRP doesn't recognize my internal storage and it is stuck in a boot loop unless I can flash SUPERSU or DT Verity fix. The internal storage is not recognized by my computer either when I plug my phone on even if I enable MTP in TWRP, I think this is something to do with the last USB debugging options but I am not sure?
What is my best solution without wiping my data?
If I copy the files to an SD card will TWRP recognize them? I am guessing no?
Can I flash stock back over TWRP to save my data? If so I am on Wind Mobile Canada, what file should I be flashing?
Lastly, I believe there is someway to send the files over ADP but I can't find any straight forward instructions on how to do so.
Thanks,
Click to expand...
Click to collapse
I bet your internal storage is encrypted, so that TWRP won't be able to read from it because it's not supported yet.
If you copy the supersu zip to an external SD and install it from TWRP you won't loose any data and you will be ok.
The boot loop is caused when you swipe on the first screen in TWRP and don't install anything (installing either dm-verify of supersu will let you boot again).

rooted but running stock image... how to upgrade?

A while back i rooted my 4g plus and ran CyanogenMod for a while... it had a few small issues and people were raving how stable the stock image was so i downloaded and applied a stock image and have been running since.
Recently started getting the update notice but when i try to apply it the reboot just dumps me into TWRP, if i reboot from TWRP my phone boots back up and tells me the update has failed.
I have been googling around like crazy but am finding alot of different answers:
The download of the image is stored in cache and you just need to point TWRP to that temp image and it will upgrade
Where is the cached image stored on the phone?
Will this keep my phone rooted?
Download the latest release and apply it via TWRP like i did originally.
Will this update or wipe my phone like new?
Will the phone stay rooted?
Thanks!
I may have misinterpreted what you wrote - however, if you're referring to the stock (i.e. images from Motorola), you cannot update via OTA whilst you have TWRP recovery; the OTA updates only will flash via a stock recovery. Furthermore, the OTA update will fail if you're rooted or have other modifications to your system/recovery. Having an unlocked bootloader does not appear to matter.
In order to apply an OTA update, you'll have to un-root and flash a stock recovery onto your system, or flash a stock image (such as this Nougat fastboot image: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) which will remove root and TWRP on your system. Depending on what options you choose with the fastboot ROM, you can elect not to wipe your internal storage (but still a wipe of your cache and Dalvik at least is advised), check the linked topic for more information.
Then you should be able to update. Failing that, perhaps someone will be able to provide a TWRP backup of their system with the latest updates included, but from what I've seen, you may have to clear cache and data to boot.
If you wish to find the OTA update, it's not in your cache, it's actually hiding in '/data/data/com.motorola.ccc.ota/app_download'. You'll need root access to see the OTA file though.

Rooting not successful, even though it says it is

I have a US996 with an unlocked bootloader. I installed TWRP (although I still can't get it to decrypt data). I installed the latest SuperSU - and there were no errors (although without the ability to decrypt, TWRP couldn't wipe Dalvik/cache).
But after rebooting, Root Checker still says I'm not rooted.
What am I doing wrong?
Figured it out. Unless I disable the default encryption to formatting Data, installing SuperSU fails. Once I format Data, the install works properly.
Haphim said:
Figured it out. Unless I disable the default encryption to formatting Data, installing SuperSU fails. Once I format Data, the install works properly.
Click to expand...
Click to collapse
How did you disable default encryption? I flashed twrp but in recovery it always says it had to decrypt in order to mount. I don't know the password twrp is asking for. Thanks
I followed the instructions and flashed TWRP. However it asks for a decrypt password when TWRP loads. How do I get past this? I formatted data twice and I am unable to flash SuperUser since I can't see any mount points. Its read only. Thank you to anyone that can help.
SOLVED:
Here is what I did wrong. After I ran all the dirtycow commands and got permissive root access I rebooted into TWRP. TWRP showed that the sdcard was encrypted. What I kept doing at this step was formatting the sd card which is correct, however I kept rebooting back into system. That was my mistake. I needed to immediately reboot back INTO TWRP RECOVERY instead. Once I rebooted directly back into TWRP recovery after the format I was able to view file system information move su.zip to sd card and install SuperUser.zip from TWRP.
When rooting my H990ds the guide said when TWRP asks for a password just press cancel. It should be the same for you too.
inurb said:
How did you disable default encryption? I flashed twrp but in recovery it always says it had to decrypt in order to mount. I don't know the password twrp is asking for. Thanks
Click to expand...
Click to collapse
Sorry, the text you quoted from me should have read that disabled default encryption *by* formatting Data. Formatting Data is what takes care of it.

Can't accsess /data in TWRP and Have no root

Something recently broke Twrp so now I cant touch my /data partition, ive read that I need to format my phone to fix this issue, the problem is that a recent update from Lineage OS is what broke it I believe, and I updated from within LOS (check for new updates download and install) which auto restarted, so when I went to go back into TWRP to reflash Magisk I started getting the issue
So now I have no root, and no twrp abilities that I know off, which means I cant use a decent backup program
can anyone help?
EDIT: I don't know if they has any relevance but ADB does have root permissions,
EDIT 2: I found out that I can reinstall magisk VIA ADB Sideload from within TWRP, as such I now have root again
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
AnonVendetta said:
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
Click to expand...
Click to collapse
Getting into twrp is no issue, the issue is that TWRP cannot read the internal storage, it can read external fine, but fails to read internal storage, which means i cant flash anything, an reflashing twrp does nothing
im fine with reformatting the phone, but i need to backup my stuff first, which i can not do since no root
@foxtrotdragon: Unfortunately for you, backing up the contents of your internal storage is no longer possible, unless you can think of some ingenius method to decrypt without formatting. Formatting /data is your only option. In the future, you should make backups *BEFORE* disaster strikes.

Categories

Resources