There are threads here and there but I couldn't find anything who has gotten encryption working on a custom ROM, except on a thread that someone did it with Jedi X Rom. Anyways, I have tried the following ROMs + TWRP to encrypt with no luck:
jfltevzw_JellyBeans_B7
S4_Echoev29.1_S5PORT_VZW_090814
S4_Echoev29_VZW_100814
Danvdh-CM11-09-18-2014-M9-stable
Danvdh-GPE-5-12242014
EclipseTW-S4-v4.0.2-KitKatNC5
HyperdriveRLS20KKS4Final
All of the above ROMS, after I enable encryption, green Android comes up, reboot and then back to Android like nothing happened. I tried disabling superuser, safe mode... Closest to success was JellyBeans where it encrypted successfully but then asked password for Storage which the password did not work.
Anyone has gotten encryption working on their custom ROM? If you did, what recovery/ROM/build combination? Anything special you had to do to get it working?
I disabled SU, ran the encryption then re-rooted. I was running stock NC5 so not really "custom," but it worked.
ammjr71 said:
I disabled SU, ran the encryption then re-rooted. I was running stock NC5 so not really "custom," but it worked.
Click to expand...
Click to collapse
Oh so many questions...
Which stock NC5 you were running - Can you point me to the file?
How did you install to your S4? Odin/recovery?
Which recovery do you have TWRP/CWM?
Why didn't you just enable SU after encryption instead of re-rooting?
Lastly, was using a PIN enabled available for encryption for this ROM or did you have to use a password instead?
Sorry for all the questions, but I see light at the end of the tunnel. I was going to go back to stock so that I can enable encryption. (My company policy requires 'Google Apps Device Policy')
Thanks!
ammjr71 - which stock NC5 ROM did you use?
Anyone else out there to successfully encrypt a rooted ROM?
OK, I think I see the light at the end of the tunnel for encryption on a custom ROM.
This method seems to work for most of the custom ROMs:
In SuperSU, uncheck 'enable superuser' and then in application manager, Turn off SuperSU. Make sure SuperSU is in turned off page. After that, reboot and encrypt should work... Also, I noticed for encryption to work, security software version under about phone should not be blank. It should be something like MDF v1.0 Release 3.. Lastly, try a password with 6 characters and one number; not a simple 4 digit PIN.
Related
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
To do that, you must uninstall the Towelroot app (shouldn't be too hard) then, to finish it off, try running these commands in an adb shell:
Code:
su
mount -o rw,remount /system
rm /system/bin/su
rm /system/xbin/su
mount -o ro,remount /system
exit
You are now unrooted!
Sent from my Nexus 7 using Tapatalk
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
blade22 said:
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
Click to expand...
Click to collapse
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i have done the same steps and factory reset..faced no Issues.
and may be people facing issues might not have uninstalled xposed module and xposed framework
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
Thanks for all the great feedback. I should have provided more detail to start. I have a follow up question/clarification. This is what did:
1. Run Towel root - success
2. Followed directions to block ota updates and install supersu. - success
3. With root confirmed, Installed exposed frame work and module from here: http://forum.xda-developers.com/showthread.php?t=2618158 (to get play store and other google apps). - success
4. Activate exposed module and update. - success
5. Installed hdxposed.Apk, enabled it, Rebooted, and play store worked. - success
6. In any order, installed the files from the link. - success
Install play services
Install framework
Install Google account manager
7. Overall, all worked well.
Question:
What is the best way to undo everything I did?
Enable OTA updates?
Update to the latest firmware (basically to get prime music and fix wifi issues I'm having)?
Re-root?
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
brooklynstar220 said:
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
Click to expand...
Click to collapse
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Davey126 said:
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Click to expand...
Click to collapse
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
brooklynstar220 said:
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
Click to expand...
Click to collapse
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
I was able to get that version of Safestrap installed and was able to flash roms again but ADB is still not connecting when attached to the computer. Do you think a nanroid restore from my original setup could help fix this?
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
Thank you for your help with this. What is crazy but was probably a driver issue the whole time, I udated my laptop to Windows 10 and somehing told me to try it again and it worked immediately with the Toolkit and re-enabled the OTA updates. Thanks again.
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.
DO NOT USE ON FOF6 FIRMWARE. WILL "BREAK" YOUR CAMERA. CHECK YOUR FIRMWARE VERSION.
Root method for FOG6 / 5.1.1 for the G900t THIS WILL TRIP KNOX. If you don't want to trip knox don't use this. If you do use it and whine you tripped knox because you didn't read ,we will all point and laugh at you.
Named it TrapKernel because well its not my normal HispAsian Kernel and I listened to a crap ton of Trap Music while doing it.
Thanks to @g.lewarne and his root method with his Unibase and Unikernel for the s6 , we finally have root after I ported it over to us. So be sure to thank him for his work.
What's included:
Auto installation of root and busy box
SuperSu.apk
A stock build prop with secure storage set to false so wifi passwords and etc aren't forgotten after reboots.
Kernel set to permissive
Otherwise stock
So here's the deal. Stupid simple.
1. Download the kernel
2. Flash in recovery (if twrp asks if you want to install su say NO)
3. Reboot and profit.
If you need more detailed help go HERE
Download
TrapKernel G6 [TWRP ZIP]
TrapKernel G6 [ODIN TAR]
Do NOT mirror this link. That means you "Android Geeks".
Special thanks to:
@g.lewarne for the obvious reason of being awesome and his root method for the s6. I suggest donating to him here [emoji14]
@ashraf sharif for testing
@Chainfire for SuperSU
also mine
This is wonderful. Thank you, sir.
EDIT: Works perfectly.
i just flashed it and somehow it broke the fingerprint scanner. nvm after a reboot, it is working now.
Awesome... thanks man!
Thanks! Working good. This. Is the 5.1.1 we should have gotten.
So when I come BAck I have everything.... is this new update faster the older one. was so buggy like 4-5 random restarts and freezes
I tripped Knox thanks bro ahaha!!!!
edited. My questions seemed too dumb
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
dpluigi said:
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
Click to expand...
Click to collapse
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Just did mine. All seems good. Camera working.
Question. Lately, anytime I flash anything, when clicking on twrp reboot, it gets stuck on tmobile screen on reboot, and sometimes I long press power button and it's finishes boot and my homescreen loads. Other times, I gotta pull battery, and then boots fine and all further reboots are fine, no hang ups. What you think this is? Something in my twrp? I leave everything checkmarked in twrp restore, cache and everything. Wonder if that is causing it somehow. Should I wipe cache and dalvik in twrp reboot?
Thanks for the new trapkernel! I missed my root access those past two days and not having my adaway to block ads.
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Thanks, that was quick and easy. TWRP was updated to 2.8.7.0, and with TrapKernel both Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not letting TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. So under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks,
Donat
dpluigi said:
Thanks, that was quick and easy. Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not let TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. Under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks
Click to expand...
Click to collapse
Because hispasian kernel doesn't contain the auto root.
You should be able to update it. I've havent been prompted yet
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
CptCrackers said:
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
Click to expand...
Click to collapse
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
What dhould the wake and sleep be set at and what do they do ?
Thanks
Sent from my SM-G900T using XDA Free mobile app
ShinySide said:
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
Click to expand...
Click to collapse
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
CptCrackers said:
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
Click to expand...
Click to collapse
Yeah you can
what will happen if I try to do this with SM-G900V ?
I really did not know what to title this, here goes:
I have a Verizon SGS 4 (SCH-I545), running stock 4.4.2, no custom recovery (am currently running the stock recovery B.S.), bootloader I545VRUFNK4, build ID KOT49H.I545VRUFNK4, release date 4/26/13 & have been rooted with KingRoot V. 4.8.0135 and is unlocked (haven't really any idea what that means, upon boot-up it shows an unlocked lock icon and says CUSTOM, the dealer I bought it from, just a shop where they buy & sell new/used phones, said that it is unlocked for use on any carrier I want.)
Now I don't know how important, if at all, all of that is but I want to update to the most up-to-date OS, reroot & maybe start flashing new custom roms.
The problem is I don't have access to a computer without install restrictions, meaning I can download things but I can't install them without admin name & password trying it directly from the settings (Settings/More/Software update) it keeps saying service unavailable...
I'm lost, is there any way to update via stock recovery or install a custom recovery (TWRP/CWM) via stock recovery or a root app?
I would suggest you to upgrade your phone with a custom rom, elseway if you do it with any official update your bootloader will be upgraded and there are a lot of cons with that.
We cannot have TWRP, CWM or other recovery (thanks to the bootloader), so the best you can do it's getting SafeStrap and then flash any of these custom roms:
stang5litre Ediition 5.0
Albe95 S6 FULL PORT 4.7
Albe95 ASTRA v2 Note 5 PORT
(I listed those because you want to update your phone). You can find SafeStrap and the roms in Verizon Samsung Galaxy S 4 Android Development sub-forum
SafeStrap must not be compatible with my phone cause I tried to use it multiple times but it is not installing any recovery, I'm still stuck on stock recovery.
AlphaTekk said:
SafeStrap must not be compatible with my phone cause I tried to use it multiple times but it is not installing any recovery, I'm still stuck on stock recovery.
Click to expand...
Click to collapse
I'm in the same bootloader so you should be able to install it, you just need SuperSU as your superuser app and busybox
Busybox, ya, I have it and ran it but KingRoot installed it's own supersu thing and it won't let me switch, if there'sa way to switch to supersu from the Play store, how?
The recovery is being overwritten by a script in the system. The title of the file is..
Install.recovery.sh
Rename this file with adding ".bak" then reinstall safestrap
Sent from my SCH-I545 using Tapatalk
I searched Root Explorer but have no idea where this is found, maybe you could point me in the right direction.
Ok, my phone's settings say I545VRUFNK1 for baseband but the build number says KOT49H.I545VRUFNK4 and Samsung Smart Switch comes up with FNK4 (VZW)! It is a Verizon SCH-I545 but how can I update it without Smart Switch cause it keeps saying its up to date?
Can I use Odin and what recovery would I use with Odin?
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
drickles said:
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
Click to expand...
Click to collapse
Personally I would not do the OTA as it may not update properly (if even at all). Every phone I have rooted before this was one of the cautions usually posted... I would double check in what ever tutorial, thread, utility faq you used to make sure.
I would suggest you wait for an update to be made that is flashable with your custom recovery. If your custom recovery has the feature (like TWRP) make a backup of what you have installed, flash the update and if things don't work you can restore your backup.
I miss having that kind of backup/restore ability via custom recovery on my phone.. sure comes in handy when things go sideways
Nothing happens. According to my experience and contents in the OTA zip, twrp will simply just spit it out. No dm-verity re-lock or bricking too.
You can always download one of the custom systems which are regularly updated.
Example would be Soldier ROM.
I recommend find your new firmware and flash it. You will lose all of your file and root-recovery you can have them all back