Related
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?
it is said this Dirty COW vulnerability is affected almost all Android devices, so is it possible to use this Dirty COW to get a temp root for Xperia XZ ?
Believe me, you are not the only one, who hopes that
Read on here: http://forum.xda-developers.com/general/security/dirty-cow-t3484879
Sorry if this is a derail, but what exactly is the point of a temp root? Would you be able to temporarily root the phone, then run something like Adaway, restart ->unroot, but still have all the adblocking capability? Without affecting bootloader and android pay etc?
maidguitar said:
Sorry if this is a derail, but what exactly is the point of a temp root? Would you be able to temporarily root the phone, then run something like Adaway, restart ->unroot, but still have all the adblocking capability? Without affecting bootloader and android pay etc?
Click to expand...
Click to collapse
temp root is for backup TA/drm partition before unlock bootloader, that means you will not lose warranty even unlocked bootloader 'cuz you can restore TA partition any time you want
BloodEdge said:
temp root is for backup TA/drm partition before unlock bootloader, that means you will not lose warranty even unlocked bootloader 'cuz you can restore TA partition any time you want
Click to expand...
Click to collapse
Aaah, that makes sense. In this case though, would my example of running a one-time root app like Adaway work?
maidguitar said:
Aaah, that makes sense. In this case though, would my example of running a one-time root app like Adaway work?
Click to expand...
Click to collapse
no idea honestly, but though you have already backup TA so why not just unlock bootloader and let it root permanently:silly:
BloodEdge said:
no idea honestly, but though you have already backup TA so why not just unlock bootloader and let it root permanently:silly:
Click to expand...
Click to collapse
I want to keep android pay functionality, and it looks like the latest updates to pay check for unlocked bootloader, etc.
So I was thinking to do whatever root things I need, like Adaway hosts file patch, TiBu backup/restores, and then reboot to get rid of root.
maidguitar said:
I want to keep android pay functionality, and it looks like the latest updates to pay check for unlocked bootloader, etc.
So I was thinking to do whatever root things I need, like Adaway hosts file patch, TiBu backup/restores, and then reboot to get rid of root.
Click to expand...
Click to collapse
hmmmm, maybe you should check about Magisk
maidguitar said:
I want to keep android pay functionality, and it looks like the latest updates to pay check for unlocked bootloader, etc.
So I was thinking to do whatever root things I need, like Adaway hosts file patch, TiBu backup/restores, and then reboot to get rid of root.
Click to expand...
Click to collapse
I like the concept. Intrigued. But doubtful perhaps
Was speaking to someone about this recently.
WIll post if anything comes from it.
BloodEdge said:
it is said this Dirty COW vulnerability is affected almost all Android devices, so is it possible to use this Dirty COW to get a temp root for Xperia XZ ?
Click to expand...
Click to collapse
I don't see it happening anytime soon on any xperia x devices temp root or full locked bootloader root+recovery no one seems to care all I ever get is use the DRM-fix been waiting 4mths for a way to back up the ta keys/get lb root
Sent from my Xperia XA using XDA Labs
This is just sad... Im faced with a decision I dont want to make.. which is NOT get a Sony phone...... What is wrong with these companies? They think we want to pay 700$ and not beable to use it the way WE WANT? come on ! this is just ridiculous.... Ill just have to buy a older phone, newer models mostly all of them, the ones i really want, are not dev friendly...
Old discussions... Just realize there is a very small amount of people needing root. Also on this point you have to discuss the question of security - rooting.
Good morning guys. The vulnerability is still out there.. could be possible to achieve temp root to backup TA partition?
Hi,
Unfortunaltelly my magisk cant hide gpay (safetynet true). Im wondering about unroot my pixel3.
Please tell me, which way is the best to unroot/lock bootloader? If I flash blueline-image with - w in flash-all.bat, can i lock bootloader with any problems (bricks)? Sorry for my english.
Thx for advice.
Wysłane z mojego Pixel 3 przy użyciu Tapatalka
If you successfully flashed the factory image (no errors) without removing the -w flag you should be able to relock the bootloader, yes. I believe locking the bootloader will induce another wipe so be sure you have things backed up if you have used the phone since flashing the factory image.
I have not rooted my devices since Pixel 1 and things have changed since then so someone else can chime in to confirm, but flashing the full factory image should be a reliable way to return to pure stock.
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
83097markcynt said:
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
Click to expand...
Click to collapse
That's good to know. I don't use gpay so didn't know that.
Unlocking Verizon Bootloader
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
I'm not sure what you're asking? Is what possible?
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
jd1639 said:
I'm not sure what you're asking? Is what possible?
Click to expand...
Click to collapse
You cannot unlock the bootloader on a Verizon device. It's software locked based on IMEI. The ones sold at Best Buy are Verizon versions and are fully locked.
Gpay works fine with magisk. If it's not working for you, I'd dig into why before unrooting and relocking.
If you don't want to do that, just flash the magisk uninstaller to get rid of root and then flash a custom kernel. Pretty much all custom kernels will hide an unlocked bootloader and allow you to pass safety net.
New here to this community.
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
NightWingJbr said:
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
Click to expand...
Click to collapse
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
jd1639 said:
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
Click to expand...
Click to collapse
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
NightWingJbr said:
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
Click to expand...
Click to collapse
See the "Factory reset via fastboot" section at https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
This will not remove the warning at boot, but is a necessary step. To lock the bootloader, read all the posts (especially the ones that detail the consequences of relocking) at https://forum.xda-developers.com/pixel-3-xl/help/how-to-lock-bootloader-t3866074 and pick a method.
I strongly recommend against relocking the boot loader, though. It is easy to brick your phone during the relock process. Also, a locked bootloader severely limits your ability to recover a bricked phone. Just ignore the warning at boot message. Removing it may come at a high cost.
Thank you so much. I will ignore then..
what is -w..
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
comic_nightwing said:
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
Click to expand...
Click to collapse
In the flash-all batch file in the factory image the -w (part of a line in the batch file) controls whether it wipes clean or does a dirty install leaving apps and data (user).
Title says it all. I never trusted Lenovo with updates. They always manage to **** something up! Anyway to get it back? Will downgrading to Android 10 fix it?
George Malas said:
Title says it all. I never trusted Lenovo with updates. They always manage to **** something up! Anyway to get it back? Will downgrading to Android 10 fix it?
Click to expand...
Click to collapse
I mean mine is fine so not sure why yours dropped honestly, fully rooted with magisk the uses zygisk and using kdragons safety net fix
Try jsut reflashing the stock firmware, thats the best I can say to a possible fix, you can't downgrade due to downgrade protections that I believe are found within the gpt file unless thats changed
ninjakira said:
Try jsut reflashing the stock firmware, thats the best I can say to a possible fix, you can't downgrade due to downgrade protections that I believe are found within the gpt file unless thats changed
Click to expand...
Click to collapse
Mine shows this in DRM info.
Can I reflash stock without factory reset?
George Malas said:
View attachment 5665339
Mine shows this in DRM info.
Can I reflash stock without factory reset?
Click to expand...
Click to collapse
George Malas said:
View attachment 5665339
Mine shows this in DRM info.
Can I reflash stock without factory reset?
Click to expand...
Click to collapse
Unfortunately no, what you could do before doing the reflash is just doing a backup, you can use the backup option the phone/Google provides in settings if you want, personally that's what I do but I don't use twrp either so I'm not sure if you have twrp and if twrp affects that. I will say though I also have the Motorola edge 2021 and when I unlocked the bootloader while it was still on Android 11 my widevine got dropped down to L3 but then I did the ota to Android 12 since I didn't use magisk at that time yet and I'm not sure what I did or anything like that but my widevine went back to L1 and it's stayed that way since and I got 2021 in may, could be a similar thing happening with you just with the 2020 model. I can also say since I still own the Moto edge 2020 and got it on day of release I never had an issue with my widevine being dropped to L3 as shown in my screenshot it's on L1 using dev check, and I did just download DRM info to double-check that on the Moto edge 2020 and it is still showing L1 so I can't say if doing a reflash of the Android 11 firmware will work but it might. I've had to reflash The 2020 edge hella including using a blank flash to get it out of hard brick and it still hasn't dropped to L3 once
ninjakira said:
when I unlocked the bootloader while it was still on Android 11 my wide Vine got dropped down to L3
Click to expand...
Click to collapse
Thing is I've never unlocked the bootloader on this phone nor rooted it. Only thing I did is have it perform multiple OTAs one after the other when I decided to upgrade to Android 11. Maybe something got corrupted during that?
Anyway, thanks for the help. I may just leave it as is since I'm worried I'll screw up reflashing it lol.
George Malas said:
Thing is I've never unlocked the bootloader on this phone nor rooted it. Only thing I did is have it perform multiple OTAs one after the other when I decided to upgrade to Android 11. Maybe something got corrupted during that?
Anyway, thanks for the help. I may just leave it as is since I'm worried I'll screw up reflashing it lol.
Click to expand...
Click to collapse
Oh if your bootloader is locked and everything and you just been doing the OTAs that's 100% just some random BS lmao that's actually a situation if you know the phone still in warranty you can probably call Motorola about that and get a replacement fr lol, and I'll be the one to say/ask it since other people will probably see this and be like yo what the hek, how is it you're a senior member but you're worried you'll screw up reflashing it lol jsut use the moto flash utility provided here (not being a butt I swear, text makes me sound bad lmao) really unless you're trying to watch Hulu and Netflix exclusively on your phone widevine honestly is not that important to deal with either I don't think Spotify is affected by it so your music quality "should" be the same still at least but again idk for sure since I haven't had widevine issues with mine, jsut the 2021 model, but that fixed itself otaing to 12 lol
Hi,
I've done a quick search but can't find anything definitive so a quick response on here would be greatly appreciated.
Are there any reasons not to root on a P7P? Like tripping Knox on Samsung devices? Basically, irreversible side effects of unlocking the BL or installing Magisk? I'm rooted on a Doogee S98 Pro, a Xiaomi MiPad 4 and a Samsung Tab S6 at the moment and I don't think I could go back to having no root. It's pretty much my main reason for not buying an S22 Ultra.
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
s3axel said:
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
Click to expand...
Click to collapse
Perfect answer, thanks!
Pretty hard to brick a Pixel.
Just make sure you don't relock your bootloader unless you're fully stock. I've seen a bunch of people doing that throughout these forums here for some reason.
Yup, if you want to unroot once you're rooted, it's absolutely imperative you flash full stock before toggling OEM Unlock and issuing any ADB commands to re-lock the bootloader. Do that without flashing back to factory stock and you end up with a phone that can't boot because the bootloader is locked with a non-stock build, you can't unlock the bootloader because the OEM is toggled, and you can't flash a stock build because the bootloader is locked. Brick time.
Other than that it's a fairly safe phone to play around with.
I strongly recommend Pixel Flasher, it makes the whole process easier, but make sure you read up on it before doing anything.
📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
GrapheneOS also supports relocking the bootloader, although I can't think of a reason why you'd want to.
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
jaseman said:
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
Click to expand...
Click to collapse
Call recording, full backup and restore, hosts based ad blockers.
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Guyinlaca said:
disable all Magisk mods, run updates, then re-root every month
Click to expand...
Click to collapse
You're adding steps and no indication of why. Just install the update with modified boot.img and call it good.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
without root I could not even get 5G working. Furthermore the AOSP Mods on the stock ROM... Systemless Hosts AdBlocking, Re-Vanced, .......
I unlocked and rooted the phone before even booted it the first time
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month.
Click to expand...
Click to collapse
Updated to November, didn't disable any Magisk mods, no issues.
It's only some mods which cause issues. Not got them installed, you can perform the update without touching Magisk.
Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Click to expand...
Click to collapse
You don't have to disable all your Magisk Mods
K1nsey6 said:
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
Click to expand...
Click to collapse
And wasn't it funny when you realized that root on Pixel is actually easier than everything else?
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
ZoM4cs said:
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
Click to expand...
Click to collapse
Here is a guide you can follow.
96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
Umm that's illegal bro.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Maybe where you are, but not here and not in most places. So keep your legal advice to yourself, BRO.
chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Actually in most jurisdictions it's what's called a one party consent requirement wherein one of the parties involved must be aware and consent. In this case the person doing the recording qualifies as the consenting party. In other places two party or more consent is required but not everywhere