Related
All,
I'm really enjoying my cyanogen rooted NOOK. I use my kindle and nook app and I find it much more useful than the stock unit. Matter of fact I'm considering purchasing another one for family use, not sure if I will keep it stock or not - Content concerns for children and such, but the reason for my post is, well, I understood the rooting process overwrites the factory software but yesterday I had a little bit of trouble manually rebooting into CWM to flash a package and ended up interrupting the boot several times in a row. Suddenly, I'm looking at a factory ROM counting from 1 to 99% - boom, then I'm looking at the original NOOK OEM sign up screen.
My take away from this is that anyone can always flash back to stock anytime they want, just by interrupting the boot up process...what? 5 6 7 times? (actually it's 8 times, lesson to self, always read all posts before posting)
So, is it correct to say that, the factory image is always there in a rooted NOOK?
Anyway, thanks again for this forum and it's many experts on here that have made using my NOOK a more enjoyable endeavor.
:good:
50bux said:
All,
I'm really enjoying my cyanogen rooted NOOK. I use my kindle and nook app and I find it much more useful than the stock unit. Matter of fact I'm considering purchasing another one for family use, not sure if I will keep it stock or not - Content concerns for children and such, but the reason for my post is, well, I understood the rooting process overwrites the factory software but yesterday I had a little bit of trouble manually rebooting into CWM to flash a package and ended up interrupting the boot several times in a row. Suddenly, I'm looking at a factory ROM counting from 1 to 99% - boom, then I'm looking at the original NOOK OEM sign up screen.
My take away from this is that anyone can always flash back to stock anytime they want, just by interrupting the boot up process...what? 5 6 7 times? (actually it's 8 times, lesson to self, always read all posts before posting)
So, is it correct to say that, the factory image is always there in a rooted NOOK?
Anyway, thanks again for this forum and it's many experts on here that have made using my NOOK a more enjoyable endeavor.
:good:
Click to expand...
Click to collapse
You are correct, a copy of the factory ROM is stored in a separate partition and when the boot fails 8 times in a row, the system will reinstall it. But that only happens if you still have stock recovery installed. If you replaced stock recovery with CWM or TWRP, it fails when trying to put stock back.
Sent from my BN NookHD+ using XDA Premium HD app
Ah! Thank you! That'll teach me to blindly follow instructions rather than ACTUALLY READ the menus. It looks so obvious in retrospect! And I just tested it out and everything seems fine. So no need to be concerned about the other issues (no file_contexts, flickering screen - which didn't happen when I really backed it up to the SD card)?
Thanks again! For the help AND the speedy responses.
Ello,
This is my first post!
I've just bought a Asus TF701t and I want to install CROMi-X. I've already done a Nandbackup using CWM booted from fastboot so I still have the stock recovery. However I hear that this tablet allows for a much lower level of backup using APX. Before I do any further changes to this tablet I would like to backup the boot loader.
Is this possible? All the tutorials are for older Transformers.
I'm currently on 10.26.1.18 bootloader with Stock rom.
Thanks...
Read the FAQ
IcePee said:
Ello,
This is my first post!
I've just bought a Asus TF701t and I want to install CROMi-X. I've already done a Nandbackup using CWM booted from fastboot so I still have the stock recovery. However I hear that this tablet allows for a much lower level of backup using APX. Before I do any further changes to this tablet I would like to backup the boot loader.
Is this possible? All the tutorials are for older Transformers.
I'm currently on 10.26.1.18 bootloader with Stock rom.
Thanks...
Click to expand...
Click to collapse
Ooops, I just read: http://forum.xda-developers.com/showthread.php?t=2554744. Doh! Newbie mistake.
This leads to my next question Does anyone know if we will be getting this feature?
IcePee said:
Ooops, I just read: http://forum.xda-developers.com/showthread.php?t=2554744. Doh! Newbie mistake.
This leads to my next question Does anyone know if we will be getting this feature?
Click to expand...
Click to collapse
It took a very long time to get nvflash working on Android 4.2.1 on the TF201, TF300 and TF700. As we have fewer devs working on the TF701 I would say you have zero chance of seeing anything insode the next 6 months.
As long as you follow the guides it is hard to brick. If unsure ask first And NEVER wipe from the BOOTLOADER. EVER.
OK, going for it
sbdags said:
It took a very long time to get nvflash working on Android 4.2.1 on the TF201, TF300 and TF700. As we have fewer devs working on the TF701 I would say you have zero chance of seeing anything insode the next 6 months.
As long as you follow the guides it is hard to brick. If unsure ask first And NEVER wipe from the BOOTLOADER. EVER.
Click to expand...
Click to collapse
Thanks for getting back to me this quickly.
OK, I'm going for it! I've already done a wipe data/factory reset and wipe cache partition. Let's see where we get to...
Result!
Just to let you know I've successfully installed the CROMi-X firmware. It went very smoothly once I could get it going. I kept having problems installing from the keyboard dock's SDCard reader. It kept failing the initial checksum process. I switched to a higher capacity MicroSD in the internal reader and it went on without a hitch.
Hi everyone. I'm new to the forum; this is my first post.
I have an M7 on a stock HTC/AT&T ROM running Lollipop 5.0.2 with Sense 6.0.
I would like to root the device so that I can do things like eliminate ads, remove bloatware, run more advanced software, etc., but I do not want to loose things like Beats Audio/Boom Sound. So I'm thinking I just want to stick with the stock AT&T/HTC M7 ROM.
I have seen reference to the Sunshine App, but unless someone can tell me it does something absolutely magical for the one-use $25 payment they expect, I'm fine doing it the free way. I got the impression about Sunshine that it doesn't actually get you all the way to root. If it got me all the way and saved my data/apps, too, I'd be all over it.
Can someone please give me the full path of steps I need to go through to get this done? I'm not a dumb guy. Pretty computer savvy, actually, but there is a lot of jargon and intermediate steps that seem to be involved in all of this. Some of the videos I'm seeing are quite dated at this point, and I have to wonder if they are relevant to an AT&T M7 on Lollipop a this point. But I thrive on step-by-step tutorials, so if you guys point me to the right videos or written tutorials, I should be fine.
Any suggestion on the best way to backup my device would be appreciated, too. I understand I'm going to get all my data and programs wiped somewhere along the path.
Thank you!
djMot said:
Hi everyone. I'm new to the forum; this is my first post.
I have an M7 on a stock HTC/AT&T ROM running Lollipop 5.0.2 with Sense 6.0.
I would like to root the device so that I can do things like eliminate ads, remove bloatware, run more advanced software, etc., but I do not want to loose things like Beats Audio/Boom Sound. So I'm thinking I just want to stick with the stock AT&T/HTC M7 ROM.
I have seen reference to the Sunshine App, but unless someone can tell me it does something absolutely magical for the one-use $25 payment they expect, I'm fine doing it the free way. I got the impression about Sunshine that it doesn't actually get you all the way to root. If it got me all the way and saved my data/apps, too, I'd be all over it.
Can someone please give me the full path of steps I need to go through to get this done? I'm not a dumb guy. Pretty computer savvy, actually, but there is a lot of jargon and intermediate steps that seem to be involved in all of this. Some of the videos I'm seeing are quite dated at this point, and I have to wonder if they are relevant to an AT&T M7 on Lollipop a this point. But I thrive on step-by-step tutorials, so if you guys point me to the right videos or written tutorials, I should be fine.
Any suggestion on the best way to backup my device would be appreciated, too. I understand I'm going to get all my data and programs wiped somewhere along the path.
Thank you!
Click to expand...
Click to collapse
just posted this for someone else
Flash TWRP 2.8.5.0
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
/ enter recovery
Exit recovery choose yes to Root
when the phone boots up go to the SuperSU Icon in the app drawer
it will ask to update / choose TWRP
after it reboots your rooted
clsA said:
just posted this for someone else
Flash TWRP 2.8.5.0
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
/ enter recovery
Exit recovery choose yes to Root
when the phone boots up go to the SuperSU Icon in the app drawer
it will ask to update / choose TWRP
after it reboots your rooted
Click to expand...
Click to collapse
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
djMot said:
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
Click to expand...
Click to collapse
Yeah, that's not going to happen
Read the FAQ >> http://forum.xda-developers.com/showthread.php?t=2228274
and the So you came at XDA-Developers to find help
If your still stuck after that then ask questions.
Hint: I described all the steps in post 2 above
djMot said:
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
Click to expand...
Click to collapse
Hi,
I know its 2019, four years since you posted this request, but I just pulled my HTC One M7 AT&T after 3 years and had the exact same query and needed a way to ensure that steps mentioned in posts like these in 2015 are still relevant/applicable on our device running Android 5.0.2 with HTC Sense 6.
I was looking to have a device specific tutorial to finally make the plunge to install a custom ROM (someone ported Android 10 to this device!) , but remember there being some complexities back in the day to do this on our device. Were you able to get around this? Look forward to your response.
Thanks & regards,
Deepesh
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.
Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?
danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp
getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread
Hi guys, it's been awhile.
As stated in the headline, I've been around awhile, not new to rooting, unlocking, flashing, but it's been 5+yrs since I've touched anything and I'm coming back fresh on a Pixel device (Panther), so I'm now completely oblivious, nothing is the same lol.
I've been trying to wrap my head around what's changed and I'm still in confusion, hell, I still don't understand how to navigate XDA properly with this new "look", what happened to the option to revert to the old XDA layout!?
To my question, would anyone be able to write me up, or point me to some helpful guides that could walk me through what's changed from Nexus to Pixel, recovery to these new A/B partitions, how to unlock, root, safely and effectively (god I hate that sentence lol) pass Safety Check for Google Pay ECT....I need to be taught like I'm a fool (but I'm not so much, maybe slightly).
IDK if I want to go to a custom ROM or kernel just yet, but I'd like to know I can, and can come back to stock(unlocked and rooted, once there).
Seems gone are the days of TWRP, Philz and custom recoveries....hell....how do you even go about making a full backup (assuming through adb to my PC now) and getting it back onto the phone
Thanks in advance for an old guy who's in new territory.
dirtyjersey856 said:
Hi guys, it's been awhile.
As stated in the headline, I've been around awhile, not new to rooting, unlocking, flashing, but it's been 5+yrs since I've touched anything and I'm coming back fresh on a Pixel device (Panther), so I'm now completely oblivious, nothing is the same lol.
I've been trying to wrap my head around what's changed and I'm still in confusion, hell, I still don't understand how to navigate XDA properly with this new "look", what happened to the option to revert to the old XDA layout!?
To my question, would anyone be able to write me up, or point me to some helpful guides that could walk me through what's changed from Nexus to Pixel, recovery to these new A/B partitions, how to unlock, root, safely and effectively (god I hate that sentence lol) pass Safety Check for Google Pay ECT....I need to be taught like I'm a fool (but I'm not so much, maybe slightly).
IDK if I want to go to a custom ROM or kernel just yet, but I'd like to know I can, and can come back to stock(unlocked and rooted, once there).
Seems gone are the days of TWRP, Philz and custom recoveries....hell....how do you even go about making a full backup (assuming through adb to my PC now) and getting it back onto the phone
Thanks in advance for an old guy who's in new territory.
Click to expand...
Click to collapse
Here's a Pixel 7 Pro guide. The principles remain the same.
Rooting is a little different than old school nexus twrp days. You can't just flash a zip for root. On the p7 you have to extract the init_boot.img from the factory image, patch it using magisk, and fastboot flash it. (There may be other solutions, but this works for sure.)
Here is a guide... https://forum.xda-developers.com/t/rooted-my-pixel-7.4505525/
And this is a good kernel to try if you want to go that route - once you are rooted you can flash it through a kernel manager app and it will retain root... https://forum.xda-developers.com/t/...-2023-03-16-unified-pixel7-pixel7pro.4543551/
Have fun!
dirtyjersey856 said:
Hi guys, it's been awhile.
As stated in the headline, I've been around awhile, not new to rooting, unlocking, flashing, but it's been 5+yrs since I've touched anything and I'm coming back fresh on a Pixel device (Panther), so I'm now completely oblivious, nothing is the same lol.
I've been trying to wrap my head around what's changed and I'm still in confusion, hell, I still don't understand how to navigate XDA properly with this new "look", what happened to the option to revert to the old XDA layout!?
To my question, would anyone be able to write me up, or point me to some helpful guides that could walk me through what's changed from Nexus to Pixel, recovery to these new A/B partitions, how to unlock, root, safely and effectively (god I hate that sentence lol) pass Safety Check for Google Pay ECT....I need to be taught like I'm a fool (but I'm not so much, maybe slightly).
IDK if I want to go to a custom ROM or kernel just yet, but I'd like to know I can, and can come back to stock(unlocked and rooted, once there).
Seems gone are the days of TWRP, Philz and custom recoveries....hell....how do you even go about making a full backup (assuming through adb to my PC now) and getting it back onto the phone
Thanks in advance for an old guy who's in new territory.
Click to expand...
Click to collapse
The thread in the quoted post directly below this sentence is the premiere guide to all the major points of going off stock experience for the Pixel 7's. It will answer much, if not all, of your questions...
Lughnasadh said:
Here's a Pixel 7 Pro guide. The principles remain the same.
Click to expand...
Click to collapse
O.J. Simpson said:
And this is a good kernel to try if you want to go that route - once you are rooted you can flash it through a kernel manager app and it will retain root... https://forum.xda-developers.com/t/...-2023-03-16-unified-pixel7-pixel7pro.4543551/
Click to expand...
Click to collapse
One caveat you should know about flashing a custom kernel on the Pixel 7's is that you have to disable verity & verification -- which will require you to wipe your device, just for the first time -- but you will also have to put into the command to disable verity and verification every time you update through a Full Factory image.
You'll definitely be told this, so I'll be the first to tell you that using badabing2003's PixelFlasher is a GUI that will automate almost anything you'd wish to flash & do for your Pixel -- from unlocking, to firmware updating, to rooting, to custom kernals, to custom ROMs, to OTAs, and more. If you ever feel overwhelmed or want a simpler method with an interface, that is your best bet.
*Although he and I would suggest you going over roirraW "edor" ehT's guide to familiarize yourself with the methods and reasonings behind what he put a GUI to automate & do...
Happy hunting!