Related
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Morthawt said:
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Click to expand...
Click to collapse
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
LS.xD said:
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
Click to expand...
Click to collapse
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Morthawt said:
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Click to expand...
Click to collapse
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
LS.xD said:
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
Click to expand...
Click to collapse
Well I did get encryption working one time on a custom rom but I have no idea how I did it. What should I do to improve my chances of getting encryption working? I thought when I rooted the original rom it removed knoxx?
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
I have Cyanogenmod recovery so that updates auto install. I downloaded the 20151005 update, and hit install. Things went fine until the part where apps optimize. It would finish, then show the Cyanogenmod boot logo for a few minutes and restart optimizing, over and over. I tried downloading the update on my computer and putting it on my SD card to see if it was just the download was messed up, and it did the same thing. I downloaded a previous update the same way, because my phone can't boot into android, and it did the same thing again. So now I want to get TWRP to see if the recovery is the problem, but I don't know how. That's where your help comes in. (hopefully!) Or, if there is a way to fix this without that, that would be preferable. And yes, I already wiped the media partition, cache partition, and did a data/factory reset, which are the only things I can wipe in Cyanogenmod recovery.
Hi
Thank you for using XDA Assist.
Here you go
http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
TWRP is better recovery. I do recommend it
Yes, I agree. But if you read my post, or at least understood it fully, you would know that I was asking how to install TWRP from the Cyanogenmod Recovery. It only lets you flash Cyanogenmod update zips, and it replaces the stock bootloader as well, so I don't know if the regular ADB method of flashing TWRP will work. I can't break this phone, you see.
MatreyuC said:
Yes, I agree. But if you read my post, or at least understood it fully, you would know that I was asking how to install TWRP from the Cyanogenmod Recovery. It only lets you flash Cyanogenmod update zips, and it replaces the stock bootloader as well, so I don't know if the regular ADB method of flashing TWRP will work. I can't break this phone, you see.
Click to expand...
Click to collapse
I guess you can since CM Recovery is almost a stock recovery.
Since you have 10 posts now, you can directly have a confirmation by posting in the above thread.
unlocked note 3 n900 t mobile version, has twrp on it but my son either wiped or factory reset it, no operating system on it, d/l one (zip file) clicked install selected the zip, but it just seems to sit on the samsung galaxy note 3 screen, how long should this take? While I can do some stuff on computers, phones are a different fish.
kevin24018 said:
unlocked note 3 n900 t mobile version, has twrp on it but my son either wiped or factory reset it, no operating system on it, d/l one (zip file) clicked install selected the zip, but it just seems to sit on the samsung galaxy note 3 screen, how long should this take? While I can do some stuff on computers, phones are a different fish.
Click to expand...
Click to collapse
You booted to recovery, selected install zip, then after flashing, did you factory reset, wipe cache and wipe dalvik cache? If you didn't do the factory reset and wipe the 2 cache partitions, that would explain the bootloop(stuck at note 3 screen). If this is what you did, try booting to TWRP then factory reset and wipe the 2 cache partitions then reboot, it might take up 20 mins to an hour to restart and load the OS, just give it time to be sure.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You booted to recovery, selected install zip, then after flashing, did you factory reset, wipe cache and wipe dalvik cache? If you didn't do the factory reset and wipe the 2 cache partitions, that would explain the bootloop(stuck at note 3 screen). If this is what you did, try booting to TWRP then factory reset and wipe the 2 cache partitions then reboot, it might take up 20 mins to an hour to restart and load the OS, just give it time to be sure.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I did not do those things, thank you for taking the time to reply. What I did instead was download Odin, found a stock rom and loaded that, it worked the phone is functional. It's kind of fun actually, since I don't actually need this phone. My next step is to find out how to remove the rom and use a different one. I'm guess once it's unlocked it's unlocked and I don't have to contact the company again, right? thanks for your time.
kevin24018 said:
I did not do those things, thank you for taking the time to reply. What I did instead was download Odin, found a stock rom and loaded that, it worked the phone is functional. It's kind of fun actually, since I don't actually need this phone. My next step is to find out how to remove the rom and use a different one. I'm guess once it's unlocked it's unlocked and I don't have to contact the company again, right? thanks for your time.
Click to expand...
Click to collapse
If the stock firmware that you flashed has a locked bootloader, you won't be able to use TWRP or flash custom ROMs. If the bootloader is unlocked, then you can use TWRP and custom ROMs.
If there are any custom ROMs for your specific model number, you can do what you did previously, just do things in the right order this time.
Flash TWRP via Odin, boot into TWRP, select install, then select your custom ROM zip, then select "add more zips", then select the Gapps file to be flashed with your ROM(the correct gapps should be linked in the ROM thread where you find your ROM), swipe the slider to flash. After the ROM and Gapps are flashed, make sure you factory reset, wipe cache and wipe dalvik cache(do not do any other wipes), then reboot and wait for the OS to load and then sign in to the phone. You "should" be good to go after that, then you can install whatever apps you want and set everything up the way you want.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If the stock firmware that you flashed has a locked bootloader, you won't be able to use TWRP or flash custom ROMs. If the bootloader is unlocked, then you can use TWRP and custom ROMs.
If there are any custom ROMs for your specific model number, you can do what you did previously, just do things in the right order this time.
Flash TWRP via Odin, boot into TWRP, select install, then select your custom ROM zip, then select "add more zips", then select the Gapps file to be flashed with your ROM(the correct gapps should be linked in the ROM thread where you find your ROM), swipe the slider to flash. After the ROM and Gapps are flashed, make sure you factory reset, wipe cache and wipe dalvik cache(do not do any other wipes), then reboot and wait for the OS to load and then sign in to the phone. You "should" be good to go after that, then you can install whatever apps you want and set everything up the way you want.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
yeah I think I may have relocked it I'll mess with it later, but I think I tried to load it back into twrp with the power,home and up vol button but it didn't load into twrp, would I have to call tmobile to have it unlocked again? thanks for the help btw, much appreciated.
kevin24018 said:
yeah I think I may have relocked it I'll mess with it later, but I think I tried to load it back into twrp with the power,home and up vol button but it didn't load into twrp, would I have to call tmobile to have it unlocked again? thanks for the help btw, much appreciated.
Click to expand...
Click to collapse
TWRP was removed and replaced with stock recovery when you flashed the firmware via Odin.
Most Samsung devices with locked bootloader these days, can't be unlocked. You might get lucky though, T-mobile might unlock it for you or allow you to unlock it. If you get it unlocked, you can flash it with custom software, but if they won't allow it to be unlocked, you'll be out of luck and stuck with stock.
Sent from my LGL84VL using Tapatalk
Droidriven said:
TWRP was removed and replaced with stock recovery when you flashed the firmware via Odin.
Most Samsung devices with locked bootloader these days, can't be unlocked. You might get lucky though, T-mobile might unlock it for you or allow you to unlock it. If you get it unlocked, you can flash it with custom software, but if they won't allow it to be unlocked, you'll be out of luck and stuck with stock.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
bummer, well I'll give it a try, I couldn't get anything to load with twrp so i used Odin, still learning this stuff, thanks again.