Related
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
bokjezd said:
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
Click to expand...
Click to collapse
You have to enable OEM unlock in Developer Options to prevent the secure boot error, then flash the recovery using Flashify and reboot.
adefesio said:
You have to enable OEM unlock in Developer Options to prevent the secure boot error
Click to expand...
Click to collapse
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
bokjezd said:
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
Click to expand...
Click to collapse
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
adefesio said:
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
Click to expand...
Click to collapse
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
bokjezd said:
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
Click to expand...
Click to collapse
I am sending a private message with the link. Let me know if it works.
adefesio said:
I am sending a private message with the link. Let me know if it works.
Click to expand...
Click to collapse
Thanks, it seems to work now, but it refuses to update because it detects root. Is there a way to hide it or do I have to do a full unroot? I already tried the "Hide my Root" app.
Edit: Never mind, I will just do the unroot and then update.
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
bokjezd said:
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
Click to expand...
Click to collapse
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
adefesio said:
Reset to factory settings, do the update, root, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
Wait, I need to do a backup of all my data, right?
bokjezd said:
Wait, I need to do a backup of all my data, right?
Click to expand...
Click to collapse
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
adefesio said:
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
I've reset my phone to factory settings, but it still refuses to update with error code 0x1125000 and after rebooting to home screen it says it detected root. I think I'm gonna update with LG Mobile Support Tool.
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
bokjezd said:
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
Click to expand...
Click to collapse
Too many complications. Just reflash the entire ROM with the most recent kdz. Root with Kingroot and don't replace it with SU. You know the rest.
Still nothing. Now it says it's the newest software available, but I cannot find that oem unlock. Are you sure it's available on Leon? I've read some manufacturers remove it...
I take no credit for any of this. Monkey saw, monkey did. MAKE SURE YOU FULLY READ THE ORIGINAL POSTS AS THE MONKEY MAY HAVE OMITTED SOMETHING. If you are clueless, not good at following instructions, or apprehensive you might want to pass. If you managed to already get unlocked and TWRPed, I imagine you are good to go. Still, if you break your phone, it's on you.
1. Do a TWRP backup.
2. Flash one of the choices here (READ THE ENTIRE THREAD) :
https://forum.xda-developers.com/moto-x-style/development/rom-marshmallow-6-0-september-2016-t3536120
REBOOT.
I went with the Deodexed one. Check out the Mods too. I added Viper.
3. Get Systemless Root back using using the flash-able Script in Post #8 here (READ ALL 1st):
https://forum.xda-developers.com/moto-x-style/general/systemless-root-info-t3373864
3a. Direct Link here:
https://forum.xda-developers.com/attachment.php?attachmentid=3809946&d=1468261256
REBOOT
I was still stock but Rooted with Xposed and I successfully Dirty Flashed. OP still recommends a CLEAN Install. After running the script, the phone came back looking the same. I did lose my custom Boot Animation and Viper so I re-flashed them. I also flashed the latest SU just to be sure i had the latest. Probably makes no difference.
Build now says MPHS24.49-18-8 and security Patch 09/01/2016.
Be sure and thank the OP's for the flash-able Update and the Systemless script.
THANK YOU OP'S,
Monkey
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
acejavelin said:
...Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
G_Man18 said:
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
Click to expand...
Click to collapse
No... That's fine. I mean you can't flash the full system image via fastboot.
acejavelin said:
No... That's fine. I mean you can't flash the full system image via fastboot.
Click to expand...
Click to collapse
Thanks for the quick response. I am surprised how many people get in trouble when TWRP backups are easy to do and can get you going when you screw up--which does happen to all of us. I post little but do read quite a bit in these forums; most of my questions have already been answered. You say you will nudge people in the right direction, but from what I have seen, no one on here answers as many questions so meticulously as you. Thanks!
acejavelin said:
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
robn30 said:
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
Click to expand...
Click to collapse
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
acejavelin said:
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
Click to expand...
Click to collapse
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
robn30 said:
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
Click to expand...
Click to collapse
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
acejavelin said:
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
Click to expand...
Click to collapse
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
robn30 said:
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
Click to expand...
Click to collapse
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
robn30 said:
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
schneid said:
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
Click to expand...
Click to collapse
Pretty sure there is a post in here somewhere that has a link to the 24.221.4 recovery, but I just used the one in this full firmware download. Just extracted the recovery.img file only and flash it using fastboot. Here is the link.
https://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
tl;dr: fastboot boot to stock boot.img, log in to snapchat, reboot.
Hello All,
I was trying to log in to Snapchat and I discovered that it won't let you log in if you're rooted. I searched the forums and I found a lot of different solutions, but they required me to install Xposed or fully unroot, which seemed like a hassle. So, I decided to make a guide for the best way to do this on a stock rooted ROM.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
You should now be logged in to Snapchat! Since you only booted to the stock unrooted image, you should still be rooted after you reboot in step 7.
Doesn't work babe
I just use magisk yes it's limited but it does what it need it for
avenator14 said:
tl;dr: fastboot boot to stock boot.img, log in to snapchat, reboot.
Hello All,
I was trying to log in to Snapchat and I discovered that it won't let you log in if you're rooted. I searched the forums and I found a lot of different solutions, but they required me to install Xposed or fully unroot, which seemed like a hassle. So, I decided to make a guide for the best way to do this on a stock rooted ROM.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
You should now be logged in to Snapchat! Since you only booted to the stock unrooted image, you should still be rooted after you reboot in step 7.
Click to expand...
Click to collapse
This method wont work with the stock kernel. You would need to use a kernel that includes the safetynet patch since Snapchat checks against this. Magisk does work though. Just select Snapchat from the Magisk Hide settings menu once you get it installed properly.
uodii said:
This method wont work with the stock kernel. You would need to use a kernel that includes the safetynet patch since Snapchat checks against this. Magisk does work though. Just select Snapchat from the Magisk Hide settings menu once you get it installed properly.
Click to expand...
Click to collapse
I got this to work on my own stock rooted Pixel with the stock kernel. You are booting into an unrooted image using my method, so the SU binary will not be present. This was sufficient to allow me to log in to Snapchat, even though my bootloader was still unlocked. This works because the Pixel uses a systemless root.
real_stacky said:
Doesn't work babe
Click to expand...
Click to collapse
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
avenator14 said:
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
Click to expand...
Click to collapse
SafetyNet checks for an unlocked bootloader. That's why I said a patched kernel is required...Unless they changed something again, but this was definitely required a few months back.
uodii said:
SafetyNet checks for an unlocked bootloader. That's why I said a patched kernel is required...Unless they changed something again, but this was definitely required a few months back.
Click to expand...
Click to collapse
Hm yeah I can't really speak to the inner workings of SafetyNet, however I did have an unlocked bootloader at the time of performing this, so from my own anecdotal experience I can say that this method allows Snapchat to log in with an unlocked bootloader (I haven't tried it with other apps) on build NHG47K.
avenator14 said:
Hm yeah I can't really speak to the inner workings of SafetyNet, however I did have an unlocked bootloader at the time of performing this, so from my own anecdotal experience I can say that this method allows Snapchat to log in with an unlocked bootloader (I haven't tried it with other apps) on build NHG47K.
Click to expand...
Click to collapse
If that's the case, then it's good info. Maybe it only does a SU check instead of SafetyNet. Good info.
avenator14 said:
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
Click to expand...
Click to collapse
Nvm i found an app on the play store that does the trick called Hide Rooting Lite. (Can't link it soz)
thanx this actually worked flawlessly. latest build twrp rc1 and rooted. I follow your instruction and it worked. now TB backup. thanx and rep for u.
Edit: after doing this I actually did a TB backup. deleted snapchat app and restore app+data using TB. having root and it still works.
Failed to boot boot.img ..... "dtb not found"....?
+1 mate
Titanium backup is also good for me cause I use the app kik and when you sign out you lose all your messages so I make backups and when restoring all my messages are back!!
Going be using that app more often now!!
https://www.youtube.com/watch?v=a-PtwtQFBWg
I made a video on how to increase your snap score. Hope you enjoy it!
cgrimm9 said:
I just use magisk yes it's limited but it does what it need it for
Click to expand...
Click to collapse
What do you mean it's limited? More features than SuperSU
---------- Post added at 11:29 AM ---------- Previous post was at 11:14 AM ----------
eduardmc said:
thanx this actually worked flawlessly. latest build twrp rc1 and rooted. I follow your instruction and it worked. now TB backup. thanx and rep for u.
Edit: after doing this I actually did a TB backup. deleted snapchat app and restore app+data using TB. having root and it still works.
Click to expand...
Click to collapse
Just use Magisk m8
What is the easiest way to completely reset my rooted android?
jdugery said:
What is the easiest way to completely reset my rooted android?
Click to expand...
Click to collapse
By reset do you mean restore it to "out of box" state? Then you need to restore your pre-root backup or flash stock via fastboot. But at this time locking the bootloader is not possible since we do not have the latest firmware, unless your device has older firmware installed (only the output of "fastboot getvar all" would tell us for sure)
acejavelin said:
By reset do you mean restore it to "out of box" state? Then you need to restore your pre-root backup or flash stock via fastboot. But at this time locking the bootloader is not possible since we do not have the latest firmware, unless your device has older firmware installed (only the output of "fastboot getvar all" would tell us for sure)
Click to expand...
Click to collapse
I just mean remove root and reset the phone so it is practically brand new. I don't care about locking the bootloader.
jdugery said:
I just mean remove root and reset the phone so it is practically brand new. I don't care about locking the bootloader.
Click to expand...
Click to collapse
What model xt15?? and version android do you have?
Twrp ver.?
Rooted with supersu or magisk?
Have you backup before rooting?
jdugery said:
I just mean remove root and reset the phone so it is practically brand new. I don't care about locking the bootloader.
Click to expand...
Click to collapse
Then you can chose the option that fit's best...
1) Unroot in the SuperSU app's Setting's menu with Full Unroot option. This will remove root but not restore the original recovery, most likely leaving TWRP in place, then boot into the bootloader, start recovery (TWRP most likely) and perform an advanced wipe including caches, user data, and internal storage
2) Boot into TWRP and restore your pre-root backup, then perform a factory reset. This may or may not remove TWRP depending on how you did the backup. If you booted TWRP and performed the backup, it should be essentially back to factory state including stock recovery, if you flashed TWRP first then backed up then TWRP will remain.
3) Restore to stock via fastboot with the latest factory image.
Your choice of which is most appropriate for your circumstances.
acejavelin said:
Then you can chose the option that fit's best...
1) Unroot in the SuperSU app's Setting's menu with Full Unroot option. This will remove root but not restore the original recovery, most likely leaving TWRP in place, then boot into the bootloader, start recovery (TWRP most likely) and perform an advanced wipe including caches, user data, and internal storage
2) Boot into TWRP and restore your pre-root backup, then perform a factory reset. This may or may not remove TWRP depending on how you did the backup. If you booted TWRP and performed the backup, it should be essentially back to factory state including stock recovery, if you flashed TWRP first then backed up then TWRP will remain.
3) Restore to stock via fastboot with the latest factory image.
Your choice of which is most appropriate for your circumstances.
Click to expand...
Click to collapse
I unrooted in SuperSU and wiped in TWRP but Snapchat still won't let me login. Root checker confirms I'm not rooted.
jdugery said:
I unrooted in SuperSU and wiped in TWRP but Snapchat still won't let me login. Root checker confirms I'm not rooted.
Click to expand...
Click to collapse
After you have unrooted, clear data on Snapchat and then log in again (or uninstall and reinstall Snapchat).
I don't use Snapchat or Whatsapp, but my understanding is that you have to login before you root... if you have tried to login, it remembers you were rooted until you clear data.
acejavelin said:
After you have unrooted, clear data on Snapchat and then log in again (or uninstall and reinstall Snapchat).
I don't use Snapchat or Whatsapp, but my understanding is that you have to login before you root... if you have tried to login, it remembers you were rooted until you clear data.
Click to expand...
Click to collapse
I did this still no luck. Apparently if you even have an unlocked bootloader you can't log into Snapchat. So I'm gonna have to lock my bootloader. Any ideas on the easiest method of doing that?
jdugery said:
I did this still no luck. Apparently if you even have an unlocked bootloader you can't log into Snapchat. So I'm gonna have to lock my bootloader. Any ideas on the easiest method of doing that?
Click to expand...
Click to collapse
Well, that shouldn't be it... but locking the bootloader is difficult depending on what version you are on now. The problem is you must flash a complete factory image to lock and we don't have the latest images.
jdugery said:
I did this still no luck. Apparently if you even have an unlocked bootloader you can't log into Snapchat. So I'm gonna have to lock my bootloader. Any ideas on the easiest method of doing that?
Click to expand...
Click to collapse
No I'm almost 99% positive that that's wrong you don't need a locked bootloader to log into snapchat? Where did you read this??
@acejavelin is extremely knowledgeable and will be able to help you with any problem you come across, but you should not need to lock bootloader...anything I find says snap blocks root...and safety net is tripped by an unlocked bootloader. The two don't go hand in hand though. Snapchat doesn't use safety net.
Edit: if you're able to make a backup of a snapchat that is logged in using Titanium backup, and then install that backup onto your phone. Don't know if you have an extra device around though. But really confused as to why reinstalling didn't even work? Is there a chance that the unroot option in superSU did not remove root fully??
acejavelin said:
Well, that shouldn't be it... but locking the bootloader is difficult depending on what version you are on now. The problem is you must flash a complete factory image to lock and we don't have the latest images.
Click to expand...
Click to collapse
Are you sure you don't need a locked bootloader to log into snapchat?
jdugery said:
Are you sure you don't need a locked bootloader to log into snapchat?
Click to expand...
Click to collapse
About 95% sure... Like I said, I don't use SnapChat, but to my knowledge the SafetyNet API doesn't check the bootloader status on Marshmallow devices, only on devices that shipped with Nougat (not that were upgraded).
There has to be some left-overs from root that are causing it to fail.
acejavelin said:
About 95% sure... Like I said, I don't use SnapChat, but to my knowledge the SafetyNet API doesn't check the bootloader status on Marshmallow devices, only on devices that shipped with Nougat (not that were upgraded).
There has to be some left-overs from root that are causing it to fail.
Click to expand...
Click to collapse
But I completely reset my device. Should I wipe everything in TWRP?
jdugery said:
But I completely reset my device. Should I wipe everything in TWRP?
Click to expand...
Click to collapse
I doubt it will help, but you can backup and try it... Most likely something is still in /system, you need to restore your pre-root backup for system and boot and wipe caches. If you don't have that backup then reflash the stock image.
acejavelin said:
I doubt it will help, but you can backup and try it... Most likely something is still in /system, you need to restore your pre-root backup for system and boot and wipe caches. If you don't have that backup then reflash the stock image.
Click to expand...
Click to collapse
Where can I find the stock image. And can I flash it using TWRP?
jdugery said:
Where can I find the stock image. And can I flash it using TWRP?
Click to expand...
Click to collapse
Hmm... maybe one of the links in my sig would help.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
Hmm... maybe one of the links in my sig would help.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Couldn't see your signature because I'm on mobile lol
But just wondering can I flash these using TWRP
jdugery said:
Couldn't see your signature because I'm on mobile lol
But just wondering can I flash these using TWRP
Click to expand...
Click to collapse
You can see a users signature and stats by tapping their icon.
No, they cannot be flashed in TWRP, must be done with fastboot.
acejavelin said:
You can see a users signature and stats by tapping their icon.
No, they cannot be flashed in TWRP, must be done with fastboot.
Click to expand...
Click to collapse
Finally that's how you do it!! Now I can see what the legend listens to for music?
Spencervb256 said:
Is there a chance that the unroot option in superSU did not remove root fully??
Click to expand...
Click to collapse
Yes it is.
Sometimes you need to flash stock/custom kernel. @jdugery
What is your version of system. Full numbers. Info about phone. 24...?
Hello, I recently got an exynos S8 and ai already installed TWRP and magisk. Is there a way to update to Oreo without losing my data and root? I barely finished setting everything up and it would be annoying to start over with a wipe
So, if We flash twrp straight after updating to oreo all data will be lost?
Use Titanium backup to get all your data back
I often change of custom ROM and I always keep all my data thanks to it
For the root, you will certainly lose it. But it takes 2min to flash the necessary file and get your root back
BigBen60 said:
Use Titanium backup to get all your data back
I often change of custom ROM and I always keep all my data thanks to it
For the root, you will certainly lose it. But it takes 2min to flash the necessary file and get your root back
Click to expand...
Click to collapse
Sounds good.Wll I have to reinstall TWRP too?
aleessio said:
Sounds good.Wll I have to reinstall TWRP too?
Click to expand...
Click to collapse
Not if you flash the ROM from TWRP.
But you will probably have to reinstall TWRP if you flash your ROM from Odin
BigBen60 said:
Not if you flash the ROM from TWRP.
But you will probably have to reinstall TWRP if you flash your ROM from Odin
Click to expand...
Click to collapse
Can you point me to an official Oreo build I can flash trough TWRP? All guides I found use odin.
aleessio said:
Can you point me to an official Oreo build I can flash trough TWRP? All guides I found use odin.
Click to expand...
Click to collapse
I'm afraid it's not possible.
Once you flash TWRP, you change the official recovery to a custom one. Once it's done, you can't get OTA anymore for example. So no more official stuffs.
If you want to get the lastest official build, you should use Odin. But it will also flash the official recovery and it will replace TWRP. So if you still want TWRP you'll have to flash it again (through Odin too and after you flashed the official firmware). But at this moment you'll lose official OTA
BigBen60 said:
I'm afraid it's not possible.
Once you flash TWRP, you change the official recovery to a custom one. Once it's done, you can't get OTA anymore for example. So no more official stuffs.
If you want to get the lastest official build, you should use Odin. But it will also flash the official recovery and it will replace TWRP. So if you still want TWRP you'll have to flash it again (through Odin too and after you flashed the official firmware). But at this moment you'll lose official OTA
Click to expand...
Click to collapse
I feared that from my experience with previous devices. I'm not so scared to reinstall TWRP and root as much as to lose my data, as I have a lot of apps that are annoying to reinstall (such as two factors authenticators or banking apps). I was thinking to try what they suggest in this post. But then, to install TWRP and root I would still need to wipe data, so it doesn't really solve my problem.
When you backup apps using titanium backup, do apps keep their data and configurations? For example, do you need to set again google authenticator or do you lose all access to your account?
aleessio said:
I feared that from my experience with previous devices. I'm not so scared to reinstall TWRP and root as much as to lose my data, as I have a lot of apps that are annoying to reinstall (such as two factors authenticators or banking apps). I was thinking to try what they suggest in this post. But then, to install TWRP and root I would still need to wipe data, so it doesn't really solve my problem.
When you backup apps using titanium backup, do apps keep their data and configurations? For example, do you need to set again google authenticator or do you lose all access to your account?
Click to expand...
Click to collapse
You keep everything as long as you restore app + data