Related
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie
berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...
I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.
I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.
My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.
Can't figure out how to disable it asking for the PIN at initial boot.. I'm returning to Tmobile(JUMP).. I'm assuming they'll have a problem with this. I miss good 'ol odin , just flash stock. Any info or help to get it back to stock would be appreciated, it's been well over a year since I've rooted/unlocked and I'm going to start restoring tonight.
Odin?!?! With Nexus devices you can use fastboot which is much more powerful than Odin.
Here are factory images for Nexus devices and on the page are included instructions on how to return to stock.
its a google security feature. even if you factory reset 10 times, itll still ask for your pin. just enter it, then you can change it. or did you steal the phone? btw, thats why its there, so no one can steal your phone, factory reset it, then use it.
Thanks for the input.. didn't know it was a google feature, was thinking it was something with the rom I installed since it started around that time(cataclysm). Anyway.. I got it figured out.. downloaded stock image and ran the flashalll.bat .. sheesh that was easy.
tri0xinn said:
Thanks for the input.. didn't know it was a google feature, was thinking it was something with the rom I installed since it started around that time(cataclysm). Anyway.. I got it figured out.. downloaded stock image and ran the flashalll.bat .. sheesh that was easy.
Click to expand...
Click to collapse
the only issue others could have is flash-all not working. to get around that, you just flash each part separately.
So I messed up...Was trying to root and got stuck in a bootloop after flashing MAGISK, so I tried to just reflash the stock image...
I flashed successfully and got out of the bootloop but my wifi stopped working, so I rebooted and tried to reflash with the Pie image instead of oreo. For some reason I was getting errors so I got this bright idea to run the commands one by one in the Flash-All.bat.
But I still kept getting errors so I thought id reboot the bootloader and try again...thats where everything went south..Screen went black cant get to fastboot mode cant get to recovey..Pc recogizes the phone as "Qualcomm HS-USB QDLoader 9008" Bashing my head finding old LG threads that cant work for the razer, I dont know what to do...Any suggestions? Or am i just completely screwed.
Bad news I'm afraid but that's a hard brick you've got there there's nothing you can do to fix that afaik.
Mate, try this link? I googled around for you and this came up. Worth a shot -- best case it fixes it, worst case you're back to square one.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
w00tnezz said:
Mate, try this link? I googled around for you and this came up. Worth a shot -- best case it fixes it, worst case you're back to square one.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Click to expand...
Click to collapse
I saw that link on my hunt but I can't use it because the files provided are specific to LG L70 devices, the Razer doesn't use TOT files for firmware they use I'm going file's and the software he provided (which I tried) can only flash tot files.
Thank you though!
Rox598 said:
Bad news I'm afraid but that's a hard brick you've got there there's nothing you can do to fix that afaik.
Click to expand...
Click to collapse
Yeah that's what I was afraid of. Well luckily I am able to get it replaced... maybe not the most honest way but I only had it for a day so I went to where I bought it and told them it stopped working and they are sending me a replacement. Since it doesn't actually turn on they can't see that I unlocked the bootloader.... however...I'm still gonna try to root it I'll be more careful but I need root! I've been rooted since way back in Evo4g and Galaxy S1 days I use allot of root features I just can't give up..it's why I dropped Samsungs and went to Razer since Samsung started locking bootloader's... anyway hope it goes better the second time around lol
majicmazo said:
Yeah that's what I was afraid of. Well luckily I am able to get it replaced... maybe not the most honest way but I only had it for a day so I went to where I bought it and told them it stopped working and they are sending me a replacement. Since it doesn't actually turn on they can't see that I unlocked the bootloader.... however...I'm still gonna try to root it I'll be more careful but I need root! I've been rooted since way back in Evo4g and Galaxy S1 days I use allot of root features I just can't give up..it's why I dropped Samsungs and went to Razer since Samsung started locking bootloader's... anyway hope it goes better the second time around lol
Click to expand...
Click to collapse
I'm glad you're getting it replaced! May I ask what factory image did you try to flash onto the device? Pie MR0 or MR1?
Rox598 said:
I'm glad you're getting it replaced! May I ask what factory image did you try to flash onto the device? Pie MR0 or MR1?
Click to expand...
Click to collapse
It was MR1 from March 2019 the 9.0 one.
Just an update got my replacement and rooted it! I didnt bother with the TWRP method I just patched my boot image with Magisk and BAM! anyway now im happy time to transfer over my old phone stuff and im good!
majicmazo said:
I use allot of root features I just can't give up
Click to expand...
Click to collapse
With the lack of Custom ROMs what root features are you looking for exactly?
I just ordered mine today and like you I've rooted all my past phones except my current LG G6 (which can't be hence my upgrade)
The only thing I usually really need root access for is the free tethering without AT&T knowing and I was able to do that to the G6 without root.
Not trying to be mean or anything I'm just curious.
Nitrous729 said:
With the lack of Custom ROMs what root features are you looking for exactly?
I just ordered mine today and like you I've rooted all my past phones except my current LG G6 (which can't be hence my upgrade)
The only thing I usually really need root access for is the free tethering without AT&T knowing and I was able to do that to the G6 without root.
Not trying to be mean or anything I'm just curious.
Click to expand...
Click to collapse
Block ads.
Overclock for speed
underclock for battery.
Remove bloatware
Change boot animations
Thats just some of many more...
A whole world of possibilities woth root beyond tetheting and roms.
Sorry for the months later answer i just saw this.
Btw i got this thing replaced and rooted the second time around just fine im very happy now
If you ever had loaded into recovery in temporary TWRP you'll note that even after formating /data/ and doing an advance wipe (selecting everything), then enter the file manager there is still a bunch of folders and some files throughout your device.
Is there a way to wipe out everything and start completely 100% fresh?
DO NOT DO THIS --- OR --- DO but do not cry about it
I have an answer to my question and it is as I suspected. The short and more official answer is, no. The longer answer is, yes, technically. -- But you should not try it unless you are 100% sure you can live without your phone (forever).
As it turns out no one had a full 100% flash for the whole device and its complete file system structure (except for Motorola). But as it turns out without a manufacturing cable it would be useless anyway. This is because part of your phone is protected and cannot be wiped clean and flashed so blindly... ie... Unlike your desktop computer. But if you're like me you have noticed some orphan files (a few logs).
Is it worth taking the risk just to clear some orphan files? Probably not. But since you do not have a manufacturing cable and technically, your phone can recover, what you can do is the following.
Do NOT use the TWRP installed on your phone. Rather use it in memory
Code:
sudo fastboot boot twrp-3.3.1-0-payton.img
Load TWRP and format DATA
Reboot, go to advance wipe, wipe everything.
Reboot to TWRP (again)
In TWRP via the terminal type in
HTML:
rm -r -f *
You will see a lot of things that cannot be deleted. This is because you do not have permission to do so. What little is removed will likely be restored after reboot from the master rom hidden somewhere on your phone which cannot be played with unless you have a manufacturing cable (so I am told). ---- If you have such a cable --- DO NOT DO THIS. --- If you suspect you have such a cable --- Do NOT do this. -- I did this with just my normal charging cable.
After you have run the command which will take forever. Tell TWRP to reboot to bootloader. You will now have a BLACK screen. This is where I panicked. I waited a while and long pressed down the power button (presumably turning off my device). Then I pressed down the power button and the lower volume button. -- Keep holding the buttons. -- It will take longer than you like but your phone will boot up. And low and behold everything that was in the master rom (chip?) has been restored and you will now see the bootloader screen (finally). Load TWRP and install your ROM of choice.
How many times have I done this successfully? 2x
Does this mean this is dependable? Unlikely
Do I recommend this? No.
Should you depend on this? No.
Are you taking a large gable? YES
Can this brick your device? YES, more than likely.
Should you do this if you have any doubts? NO.
Will you get any help if this goes wrong? NO.
So why did I do it? As I look to possibly upgrade my phone in the future I feel a little more daring and can afford to do so. lol
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
KrisM22 said:
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
Click to expand...
Click to collapse
After performing this I installed only the official firmware. No additional ROM or GSI. The firmware itself includes the stock software.
A word of caution. --- I did this on 3 phones now. 2 work just fine. But 1 does not. The one that does not reports my IMEI as 0. This means it boots, it loads, it will play games and apps and update via Google Play Store, but it will never make a single phone call ever again. --- Food for thought.
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
MotoX4 said:
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
Click to expand...
Click to collapse
Thanks! Yeah, in the past I have been a lot on Ubuntu and stuff like this is not forgiving for wine.
It's a darn shame that we can't just send these phones to Moto with $25 and get it fixed. Oh well!
KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
Moto smart assistant can`t recognize the phone in rescue mode..
St.Noigel said:
Moto smart assistant can`t recognize the phone in rescue mode..
Click to expand...
Click to collapse
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
KrisM22 said:
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
Click to expand...
Click to collapse
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
MotoX4 said:
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
Click to expand...
Click to collapse
6.2.4 won't recognize a Moto X4 after it is upgraded to Pie.
I used RSDLite since the times of the P2K and MAGX (Linux)... but since it's easier to use fastboot commands...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
joel_sinbad said:
...snip...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
Click to expand...
Click to collapse
In all probability, NO.
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
joel_sinbad said:
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
Click to expand...
Click to collapse
If you read a lot on this forum, that's the message I see.
I agree, NO going back. You can, I have... flash any factory Pie rom . All will flash fine and no IMEI, wifi. Radios are gone. I use Google Fi and cell data services go wierd on custom roms, if you want carrier switching.
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
joel_sinbad said:
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
Click to expand...
Click to collapse
I don't recall thinking that the Moto Atrix 4g was at all dangerous when I had one - a rather nice phone imho, though that was a very long time ago. I don't think of the Moto X4 as "dangerous" - it is simply that there is not a correct understanding of the Pie file structure by the custom ROM devs such that their ROMs would not so change the file structure of the phone as to prevent it from being flashed back to stock.
Users need to recognize that, with this phone, you can't get back to stock if you flash any custom ROM.
afaik.
This change happened with the file structure and boot structure changes of the Pie update. Prior to that, folks could get away with all manner of mods. Devs for this phone need to approach modifications with the idea of assuring that any mod can be flashed back to stock, BEFORE it is released. That has not happened. And likely won't. User beware!
KrisM22..... Thank you for stating what I could not do as well.
kkjb said:
KrisM22..... Thank you for stating what I could not do as well.
Click to expand...
Click to collapse
we ALL do it, and CAN do it - all in hopes of saving some newbie from disaster!
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!