Related
I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting
Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.
Hi everyone,
I am giving this phone to my mom since I don't need it anymore (bought Samsung S6 few months ago)! Phone is currently on Android 4.4.4 kangkat 5.1 and is customised pretty nicely( no Ads, working fast , no FC ,pretty snappy).
Should I update to Marshmallow before I give it to her or should I just leave it the way it is? She is just the regular user and will not use anything more that dialer, sms, browser, weather, calendar, calculator, camera, etc.. So just basic apps and I will strip this phone to bare minimum but was just wondering should I get her Android 6 on this (at least battery live maybe inproved?)
Any thoughts or ideas will be appreciated.
If you have the knowledge to do it, then yes, it's probably worth installing MM as stock and leaving it like that - no custom recovery, no root. That way she can get the regular security updates with the minimum of fuss. The uninterested user doesn't need the hassle of a rooted device. And easier for you in not having to strip the phone - a new installation will do that for you anyway, and will allow her to sign in as herself and properly own the phone.
dahawthorne said:
If you have the knowledge to do it, then yes, it's probably worth installing MM as stock and leaving it like that - no custom recovery, no root. That way she can get the regular security updates with the minimum of fuss. The uninterested user doesn't need the hassle of a rooted device. And easier for you in not having to strip the phone - a new installation will do that for you anyway, and will allow her to sign in as herself and properly own the phone.
Click to expand...
Click to collapse
I do have knowledge (well maybe I might remind myself a little using Google). I am running Xposed on this build and like I've said phone is super stable with this build but also pretty simple to use for basic /regular user. Future updates are just going to confuse her.. The only thing I would like for her is maybe improved battery live and that's why I would go to MM. I was also thinking to maybe get new battery on this one(don't know how hard is to change it?). Anyway thanks for responding ,
Flash latest 6.0.1 MM on it and lock bootloader... give it to her barebones and let her enjoy it...
just did that with my oldest brother who lost his phone to a muggin.... and its the easiest way for them to stay up to date on latest security patches, etc
"maybe get new battery on this one(don't know how hard is to change it?)"
It's actually pretty simple: https://www.youtube.com/watch?v=VSGNUrpwIno
Though there's another thread that I read just today that shows there's a certain risk: http://forum.xda-developers.com/google-nexus-5/help/nexus-doesnt-boot-fastboot-t3282033
chaco81 said:
Flash latest 6.0.1 MM on it and lock bootloader... give it to her barebones and let her enjoy it...
just did that with my oldest brother who lost his phone to a muggin.... and its the easiest way for them to stay up to date on latest security patches, etc
Click to expand...
Click to collapse
I actually never gone back to stock so I don't know how hard is it and how time consuming is it? I am on TW recovery v2.7.0.0. should I just flash nandroid or do I have to flash factory image first and than lock bootloader?
dahawthorne said:
"maybe get new battery on this one(don't know how hard is to change it?)"
It's actually pretty simple: https://www.youtube.com/watch?v=VSGNUrpwIno
Though there's another thread that I read just today that shows there's a certain risk: http://forum.xda-developers.com/google-nexus-5/help/nexus-doesnt-boot-fastboot-t3282033
Click to expand...
Click to collapse
You are right , I am not going to mess with battery replacement. The old one should be OK for some time ...
I would also not bother relocking the bootloader. How many threads in these forums contain wails from people who have cacked their devices and there is no way to recover because the bootloader is locked?
This thread actually refers to the Nexus 6, but since Nexus devices are so similar in many ways it's probably still relevant, and should put you off taking this unnecessary step: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Stock is extremely simple. Download the factory image (Google "factory image"), unzip and run flash-all - obviously after you've got all your drivers set up to communicate with the device. If you haven't yet, I'll bore you again with recommending Wugfresh's Nexus Root Toolkit, which has a really helpful button to walk you through the driver setup. If the flash-all script doesn't work (it doesn't for some people), you can unzip all the components, put them in your ADB/fastboot directory and flash each component separately.
dahawthorne said:
I would also not bother relocking the bootloader. How many threads in these forums contain wails from people who have cacked their devices and there is no way to recover because the bootloader is locked?
This thread actually refers to the Nexus 6, but since Nexus devices are so similar in many ways it's probably still relevant, and should put you off taking this unnecessary step: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Stock is extremely simple. Download the factory image (Google "factory image"), unzip and run flash-all - obviously after you've got all your drivers set up to communicate with the device. If you haven't yet, I'll bore you again with recommending Wugfresh's Nexus Root Toolkit, which has a really helpful button to walk you through the driver setup. If the flash-all script doesn't work (it doesn't for some people), you can unzip all the components, put them in your ADB/fastboot directory and flash each component separately.
Click to expand...
Click to collapse
I just updated Wugfresh Nexus Root Toolkit since I had old version on my laptop. Should I use RESTORE/UPGRADE/DOWNGRADE option and than FLASH STOCK + UNROOT?
P.S. DONE.. Running MM now on it.
Thank you all
roundel.... easy to do
make sure u have latest ADB installed on your PC.... so open SDKManager and run it so it updates...
download the latest Factory Image
extract the image, place it on the platform tools folder of your SDK and double click the flash.all.bat file... let the magic happen
google returning back to stock, there are tons of tutorials out there showing how to do this.
chaco81 said:
roundel.... easy to do
make sure u have latest ADB installed on your PC.... so open SDKManager and run it so it updates...
download the latest Factory Image
extract the image, place it on the platform tools folder of your SDK and double click the flash.all.bat file... let the magic happen
google returning back to stock, there are tons of tutorials out there showing how to do this.
Click to expand...
Click to collapse
I did it and phone is running MM now. I am amazed with battery life now, it is crazy good comparing to KK!
So I am now back to stock unrooted but I left bootloader unlocked. Will she (my mom) get any updates if this Nexus get OTA updates?
A stock unrooted rom with stock recovery is all that is needed for ota updates. The bootloader can remain unlocked for ota updates.
Update it now and give her. I was doing the same stuff with my mom and she denied which then later made me try this phone out. Overall it's good but battery sucks.
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
Hi all,
I tried to find basic informations about Magisk without success.
Is anyone here could explain what is Magisk, as if I was 5 years old ?
Thanks in advance for your replies.
dont know if you saw this , but here is the thread for magisk. maybe will help. :what:
http://forum.xda-developers.com/showthread.php?t=3473445
mrrocketdog said:
dont know if you saw this , but here is the thread for magisk. maybe will help. :what:
http://forum.xda-developers.com/showthread.php?t=3473445
Click to expand...
Click to collapse
Thanks for your reply.
The thread for Magisk is too technical for me. In a first approach, I want only to understand with simple words, what Magisk can do.
root your device.
iwanttoknow said:
Thanks for your reply.
The thread for Magisk is too technical for me. In a first approach, I want only to understand with simple words, what Magisk can do.
Click to expand...
Click to collapse
I'm with you - that main thread completely lost me - I installed the manager and it errored from twrp and I guess it leads on to something about finding a boot.img to patch - but i'm lost
Lothaen said:
I'm with you - that main thread completely lost me - I installed the manager and it errored from twrp and I guess it leads on to something about finding a boot.img to patch - but i'm lost
Click to expand...
Click to collapse
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
IronRoo said:
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
Click to expand...
Click to collapse
yeah - i've been through both of those, but mine error during the flash with issue with the boot image, so then I get stuck and have no idea how to fix it or where to go - I tried asking on the Magisk thread but its so chatty I think it got lost very quickly.
IronRoo said:
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
Click to expand...
Click to collapse
Thanks a lot IronRoo for your reply !
After reading I have understood that Magisk implies to install a recovery tool like TRWP.
So I have only to unlock the device's bootloader to install a recovery tool and after Magisk. Magisk doesn’t modify system files.
Ok but I don't understand how it's possible the device obtains root access. It's certainly magical
Most of the time I don't look for the sort of 'tell me like I'm a 5 y/o' info - but Magisk IS an exception for that, for me.
There is very little that I can find which is written in plain, simple words such that I can even figure out -IF- it is usable as I'd like it to be.
My example:
I have an unlocked Moto E6 - can I even get TWRP installed & working in that phone ??
No clue.
Prior to Android V5.x gaining root access was loads easier to accomplish & I've happily done so for my several older LG devices & our previously daily use Kyocera phones.
BUT:
For my couple of devices with versions of Android newer than V5 - I am only able to de-bloat those somewhat via ADB shell - but they are locked to AT&T which would mean I'd have to fulfill their unlocking requirements to get 'em unlocked - or am I mistaken about that ??
The closest I've found to a VERY simplified guide to using Magisk is here:
Root Android Phone with ADB Command, Magisk & TWRP
Here are 2 different methods to root your Android phone or tablet using ADB and Fastboot commands, Magisk and install TWRP Recovery.
technastic.com
But method 1 is not possible for my devices AFAIK & method 2 requires me to have a stock firmware IMG to patch...but I've zero idea where I might get those for a Moto or a 'modern' LG phone - is there any particularly good way to accomplish that ??
So - as the OP said - please tell me like I'm a 5 year old ?!?
Thanks.
Long time rooter who has more or less given up in recent years.
Rooted:
HTC hero
HTC desire
Samsung Galaxy s1
Nexus 4
Nexus 5
Nexus 5x
Not rooted:
Pixel 2
Pixel 4xl
Just got a pixel 4 but would be tempted to root the pixel 2 while it's still got some life in it.
Got a few quick questions as to what has changed recently. Would be using magisk to achieve root after installing twrp. (Unless this is old hat and something else is the method of choice). Probably will have to unlock bootloader can't remember if I ever did it on the pixel 2
What's the procedure for monthly updates can they be done via ota or do I need to bring adb into it?
Best guides floating about at the moment? Any other pertinent advice? Muchthx
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
IMO the rooting party is pretty much over. I also returned to xda after many flashes years ago. For the Nexus, the great Beanstown dev provided monthly flashes for your custom recovery, but it looks so much more complicated today, to the point it's not worth the effort anymore. I'm sticking with stock till the '2 dies. The risk of unlocking the bootloader and getting root is simply not worth the headache as evident in the Q&A posts. So for now, for my much wanted rootness, I resort to debian linux on the desktop, a command line, and the luxury of typing sudo!!
sudoxd said:
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
Click to expand...
Click to collapse
Very impressive signature of the number of many devices you have. Maybe a new wall plaque perhaps?