So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Recently I've been thinking about rooting the device for maybe some little extras. For example, I have GTA SA installed but I would like to play it with the Cleo mod to have a little bit more fun. Or maybe I'll install some kind of adblocker so I could enjoy my brand new phone without the annoying gold diggers. Or perhaps I want to hide some apps from my app drawer so it would look neat and organised. Or I would like to install an apk that isn't available for non-rooted devices. Or in case I want to see the battery percentage next to the time display or anything like that.
As you can see I would only want to root it for rather small reasons. I definitely don't want to overclock anything because it already meets my criteria for speed, nor do I want to install any custom ROMs because I really like the pure android experience. So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
root/unlockbootloader/install twrp&busybox no data loss
root/unlockbootloader/install twrp&busybox no data loss without P.C, okay here we go mod's remove if you think it's not helping. download towelroot by geohot,now the rest from playstore, es file exploer,super su,busybox,reboot app,nexus unlock bootloader,
make sure you have security unknowen sources ticked and verify apps unticked.
download towelroot from chrome with es file exploer open and install hit make it rain tab, next install busybox,next install super su app.unlockbootloader with in the app.,install twrp and auto install recovery for hammerhead from twrp, now you should have full root after reboot.super user and busybox unlocked bootloader and twrp installed, and you know what the reboot app is for . no data loss and without a P.C, or you could use fastboot install just look in Q&A, kind regard's joe hope this help's.
Spaceblow said:
Is my current data going to be wiped if I would want to root it?
Click to expand...
Click to collapse
Yep; when you unlock bootloader of your device (before root), all of data will be wiped.
Spaceblow said:
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
Click to expand...
Click to collapse
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
Spaceblow said:
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
Click to expand...
Click to collapse
We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
Spaceblow said:
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
Click to expand...
Click to collapse
In my case, to connect NTFS filesystem.
Spaceblow said:
And is it actually 100% safe...?
Click to expand...
Click to collapse
Maybe, but it's at your own risk.
Jongmin Kim said:
Yep; when you unlock your device (before root), all of data will be wiped.
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
No. We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
In my case, to connect NTFS filesystem.
Maybe, but it's at your own risk.
English is too difficult... I'm trying to understand right now.
Click to expand...
Click to collapse
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Spaceblow said:
So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Click to expand...
Click to collapse
First of all:
Lethargy said:
I think OP got his question reversed. Should be:
"Why buy a Nexus 5 if you're not going to root?"
:angel:
Click to expand...
Click to collapse
Spaceblow said:
So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
Click to expand...
Click to collapse
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Spaceblow said:
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
Click to expand...
Click to collapse
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Spaceblow said:
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore). The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
lol yeah i have to agree with you, but i find this help's when on the go,
joecool666 said:
lol yeah i have to agree with you, but i find this help's when on the go,
Click to expand...
Click to collapse
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Lethargy said:
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Click to expand...
Click to collapse
i do use my p.c and lg flashtool and fastboot.just incase lol.and it is the better way of doing it, p.s when OTG rooting don't forget to bring the XDA app.
joecool666 said:
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Click to expand...
Click to collapse
You mean Towelroot? I'm also considering this option because it would be nice to keep all my data.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Spaceblow said:
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Click to expand...
Click to collapse
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Lethargy said:
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Click to expand...
Click to collapse
Thanks for helping me but I used Towelroot and it works flawlessly!
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
back up
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
make sure you make a back up back up most important,regard's joe
To be clear, the *whole* phone including your sdcard partition will be wiped so make sure you back up before unlocking your bootloader. I would use an app like ES File Explorer and copy all your files to Dropbox or Google Drive if you dont have a computer but you'll need a computer anyway.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
To be clear, the *whole* phone including your sdcard partition will be wiped
Click to expand...
Click to collapse
If we want to be clear, we should also be accurate. The *whole* phone is not wiped. The /data partition is wiped, which includes /data/app (where user apps are stored) /data/data (where user settings and app data is stored) and /data/media (where /sdcard data is stored)
Lethargy said:
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
Click to expand...
Click to collapse
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
joecool666 said:
make sure you make a back up back up most important,regard's joe
Click to expand...
Click to collapse
By using Titanium Backup?
Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
Click to expand...
Click to collapse
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
By using Titanium Backup?
Click to expand...
Click to collapse
or helium back up
Owning a Nexus makes fastboot your best friend, especially if you have issues.
Read up on adb/fastboot and forget OTA's. Nothing like a clean fresh install of a new version. And there's many options to save /backup your data and important files.
Without learning fastboot and adb.... Simple fix issues can become major headaches.
Don't be intimidated. Read, learn, then do. ?
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
@rootSU has everything you need in his sticky roll up thread.
rootSU said:
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Click to expand...
Click to collapse
Well, you convinced me to take my N5 to a step further.
So I already Towelrooted my phone which gave me root access and an untouched bootloader and recovery. My next step would be to backup every app and all data to be sure in case something goes wrong, this would be done by using Titanium Backup. Then I should be unlocking the bootloader by simply using BootUnlocker for Nexus Devices so I wouldn't get my data wiped (I know I would be able to restore it with my backup but I rather do it a bit faster and less complex). When I did that, I have to head over to this thread and flash TWRP by following the instructions at "2. Installing a Custom Recovery".
So after all these steps my phone would have no limitations and it would be as unlocked as for example your Nexus 5, right?
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?
Someone's bound to hose up their phone. Wondering where factory images are?
Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk
me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.
There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.
https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932
Hey Guys,
So, I've got an A8 2018 (jackpotlte) and currently have it rooted and TWRP installed.
I'd like to update the firmware using Odin to the latest version, but I don't want to lose my app setups etc. The firmware I want to flash is from the same CSC (EVR) that I have currently.
I've got a full TWRP backup incase anything goes wrong, and all data such as photos is backed up separately as well.
My question is, what do I need to do to get this update installed without losing my settings etc?
Will I need to reflash TWRP to the recovery after the update? And if so, I'm assuming I'll have to re-apply the no-verity and opt-encrypt patches?
Thanks for your help!
Last paragraph is correct.
Will I need to reflash TWRP to the recovery after the update? And if so, I'm assuming I'll have to re-apply the no-verity and opt-encrypt patches?
Yes
You can try backing up apps and settings in Samsung Cloud.
Also, this app here may work for you. It keeps all your settings intact. Not sure how it'll work after an update, but I've used it while switching ROMS and if anything, it'll save you loads of time on your downloads after updating.
https://forum.xda-developers.com/an...ation-tool-t3862763/post78060823#post78060823
AntMUK said:
Hey Guys,
So, I've got an A8 2018 (jackpotlte) and currently have it rooted and TWRP installed.
I'd like to update the firmware using Odin to the latest version, but I don't want to lose my app setups etc. The firmware I want to flash is from the same CSC (EVR) that I have currently.
I've got a full TWRP backup incase anything goes wrong, and all data such as photos is backed up separately as well.
My question is, what do I need to do to get this update installed without losing my settings etc?
Will I need to reflash TWRP to the recovery after the update? And if so, I'm assuming I'll have to re-apply the no-verity and opt-encrypt patches?
Thanks for your help!
Click to expand...
Click to collapse
IF YOU FLASH STOCK FIRMWARE, YOU WILL LOSE ROOT. wITH THE NEWER FIRMWARE, YOU WILL HAVE TO USE THAT SPECIFIC VERSION OF THE FIRMWARES ROOT METHOD. yOU WILL HAVE TO FLASH THE csc TO DO WHAT YOURE WANTING TO DO, WHICH WILL FACTORY RESET.
Crap, all in caps. Im not gonna retype it, just know i wasnt yelling lol
there are app backup apps you can get like titanium backup that will restore most of your stuff including personalization.
youdoofus said:
IF YOU FLASH STOCK FIRMWARE, YOU WILL LOSE ROOT. wITH THE NEWER FIRMWARE, YOU WILL HAVE TO USE THAT SPECIFIC VERSION OF THE FIRMWARES ROOT METHOD. yOU WILL HAVE TO FLASH THE csc TO DO WHAT YOURE WANTING TO DO, WHICH WILL FACTORY RESET.
Crap, all in caps. Im not gonna retype it, just know i wasnt yelling lol
there are app backup apps you can get like titanium backup that will restore most of your stuff including personalization.
Click to expand...
Click to collapse
I seriously thought you were angry. I was waiting for the part that... never came.
I re-tried the migrate app (also in zee store).
It's better than i remembered.
BUT IF YOU READ THE PREVIOUS POST, IT IS ALSO CORRECT. THERE. THAT SHOULD GIVE YOU PLENTY OF OPTIONS. (Couldn't help it).
mindlery said:
i seriously thought you were angry. I was waiting for the part that... Never came.
I re-tried the migrate app (also in zee store).
It's better than i remembered.
But if you read the previous post, it is also correct. There. That should give you plenty of options. (couldn't help it).
Click to expand...
Click to collapse
well, just so ya know, i had something funny as a response here and it was in all caps. Well, xda un-capped the whole thing except for the beginning of sentences and so forth where it would have been correct to do so. I was just gonna go back and correct it, but i found this explanation to be even funnier than the original post, so here we are LOLOL!!!
I want to clarify, i already saw many threads mentioning how you can protect your data with an unlocked bootloader, so no need to go deep into that.
But it also seems to me, many people just avoid the other issues, like an attacker being able to sideload malware in your device.
How to mitigate those other risks?
cablop said:
I want to clarify, i already saw many threads mentioning how you can protect your data with an unlocked bootloader, so no need to go deep into that.
But it also seems to me, many people just avoid the other issues, like an attacker being able to sideload malware in your device.
How to mitigate those other risks?
Click to expand...
Click to collapse
Sideloading malware requires physically access to your device. You have to reboot into bootloader mode and flashing e.g. a patched system.img and then reboot into system again. To avoid this: Never leave your device unattended.
WoKoschekk said:
Sideloading malware requires physically access to your device. You have to reboot into bootloader mode and flashing e.g. a patched system.img and then reboot into system again. To avoid this: Never leave your device unattended.
Click to expand...
Click to collapse
I am fully aware of that. But there are time you leave it unattended, you can't carry a bag with all your belongings with you to every place you must be in, e.g., bathroom, beach, gym, etc.
So, if you leave it unattended and then you come back and you think it was compromised, what can you do, apart from a full reset? Can't you have a tool that tells you if something changed, somebody took it, it rebooted, etc.?
cablop said:
I am fully aware of that. But there are time you leave it unattended, you can't carry a bag with all your belongings with you to every place you must be in, e.g., bathroom, beach, gym, etc.
Click to expand...
Click to collapse
It seems a bit paranoid... When I'm not at home my phone is in my pocket or locked up (e.g. gym). That's it.
cablop said:
So, if you leave it unattended and then you come back and you think it was compromised, what can you do, apart from a full reset? Can't you have a tool that tells you if something changed, somebody took it, it rebooted, etc.?
Click to expand...
Click to collapse
A full reset would do nothing for you. In bootloader menu you have no access to /data. Even if fully booted up nobody can access /data due to my display pattern. So, a full wipe wouldn't help you since it only wipes /data.
As I already said you could only patch the system.img/vendor.img with malware. But if Android verified boot is enabled, it's impossible to change something on these partitions.
WoKoschekk said:
It seems a bit paranoid... When I'm not at home my phone is in my pocket or locked up (e.g. gym). That's it.
Click to expand...
Click to collapse
Not really paranoid. You only need to see the ads offering ways to people to know what their partners do, don't they? Keyloggers predate Android phones, so how can i think they are not a real risk?
WoKoschekk said:
A full reset would do nothing for you. In bootloader menu you have no access to /data. Even if fully booted up nobody can access /data due to my display pattern. So, a full wipe wouldn't help you since it only wipes /data.
As I already said you could only patch the system.img/vendor.img with malware. But if Android verified boot is enabled, it's impossible to change something on these partitions.
Click to expand...
Click to collapse
BTW. If it was impossible to write on those partitions, then it would be impossible to change the firmware of the phone, but we do when we unlock the bootloader, and then we patch stuff, like a new recovery partition and even root the phone. So it is not something the Android verified boot can do.
It seems to me that while Google and the vendors think it is important to keep the bootloader locked for security reasons, the community keeps looking in other direction to say it is not, and there's no risk, but there is.
cablop said:
BTW. If it was impossible to write on those partitions, then it would be impossible to change the firmware of the phone
Click to expand...
Click to collapse
You mixed up things. A new firmware is not the same as patching /system on a stock ROM. Even a custom recovery requires a patched vbmeta.img in most cases.
Malware is an executable file that can only be stored on a file system. You can't store it on a boot.img or recovery.img since they are only binaries. No, you need e.g. /system or /vendor. Only there you could store a malicious file like a patched APK that gets executed by system during the next boot sequence.
WoKoschekk said:
You mixed up things. A new firmware is not the same as patching /system on a stock ROM. Even a custom recovery requires a patched vbmeta.img in most cases.
Malware is an executable file that can only be stored on a file system. You can't store it on a boot.img or recovery.img since they are only binaries. No, you need e.g. /system or /vendor. Only there you could store a malicious file like a patched APK that gets executed by system during the next boot sequence.
Click to expand...
Click to collapse
ok, that is interesting, but comes with a doubt... then, how does Magisk work? afaik it is a patch outside the firmware or system or data... Can't we install a malware to the phone in a similar way Magisk gets installed?
cablop said:
ok, that is interesting, but comes with a doubt... then, how does Magisk work? afaik it is a patch outside the firmware or system or data... Can't we install a malware to the phone in a similar way Magisk gets installed?
Click to expand...
Click to collapse
Even Magisk needs an installation for the Manager APK when a patched boot.img gets booted. The APK isn't part of the patch and the installation must be granted by the user.
WoKoschekk said:
Even Magisk needs an installation for the Manager APK when a patched boot.img gets booted. The APK isn't part of the patch and the installation must be granted by the user.
Click to expand...
Click to collapse
Hmmm.
Ok, maybe i am confused by thinking the bootloader of Android can work in a similar fashion as the boot of Linux or even Windows.
So, just to be sure, what you are telling me is that there's no way to install with an unlocked bootloader a malware in the system, either as new software or replacing an existing one, but that the risk is they can read my data, something that i can solve with a proper device or userspace encryption, right?
Can't we flash some things from the TWRP or alike like the GMS directly into the system?