hey! a question to all the pros here: i just went to unlock and root the new pixel 6 pro of a buddy and missed that the phone was only updated to the 036 nov build (and not the 037 one). however, for the rooting process i went with the factory image of the latest nov build (the 037 one) and thus flashed vbmeta and a patched boot img from that build on the 036 one, that was installed. is this mismatch somewhat harmful to the device? thanks guys!
xflowy said:
hey! a question to all the pros here: i just went to unlock and root the new pixel 6 pro of a buddy and missed that the phone was only updated to the 036 nov build (and not the 037 one). however, for the rooting process i went with the factory image of the latest nov build (the 037 one) and thus flashed vbmeta and a patched boot img from that build on the 036 one, that was installed. is this mismatch somewhat harmful to the device? thanks guys!
Click to expand...
Click to collapse
nothing harmful but mismatch images will not boot your system so restore the system back to get it fixed.
Yeah, if in doubt just flash the entire .037 factory image to start completely clean, either with removing the -w to wipe, or not removing, your choice to try but probably fine not wiping, as long as verity and verification are both already disabled. Just make sure and add the verity and verification disable switches in place of the -w if you do flash the whole factory image.
roirraW edor ehT said:
Yeah, if in doubt just flash the entire .037 factory image to start completely clean, either with removing the -w to wipe, or not removing, your choice to try but probably fine not wiping, as long as verity and verification are both already disabled. Just make sure and add the verity and verification disable switches in place of the -w if you do flash the whole factory image.
Click to expand...
Click to collapse
thanks guys!
so if i flash the factory image again, i am good and there wont be damages done anyhow?
xflowy said:
thanks guys!
so if i flash the factory image again, i am good and there wont be damages done anyhow?
Click to expand...
Click to collapse
Yep, you're good. Same as @rc chanu said, there's not going to be any lasting damage no matter what - just at worst your phone won't work right until you flashback to proper stock. (just for emphasis) Just reminder to always put the disable verity and verification switches in, now and any other time in the future you flash the stock image, otherwise you'd have to wipe user data once you have any and start from complete scratch.
xflowy said:
thanks guys!
so if i flash the factory image again, i am good and there wont be damages done anyhow?
Click to expand...
Click to collapse
Yes
roirraW edor ehT said:
Yep, you're good. Same as @rc chanu said, there's not going to be any lasting damage no matter what - just at worst your phone won't work right until you flashback to proper stock. (just for emphasis) Just reminder to always put the disable verity and verification switches in, now and any other time in the future you flash the stock image, otherwise you'd have to wipe user data once you have any and start from complete scratch.
Click to expand...
Click to collapse
Do you know how to flash null vbmeta? If yes please help
rc chanu said:
Do you know how to flash null vbmeta? If yes please help
Click to expand...
Click to collapse
I don't know what null vbmeta is. I found some Google search results that could help you though (right here on XDA).
roirraW edor ehT said:
I don't know what null vbmeta is. I found some Google search results that could help you though (right here on XDA).
Click to expand...
Click to collapse
Thanks btw.
rc chanu said:
Thanks btw.
Click to expand...
Click to collapse
You're welcome!
Related
This is confusing the heck out of me. So I realize there's 2 partitions and why they're there. So the B partition is just a fresh blank copy of whatever image you're on? I see posts about flashing to a and b, but when I look in a stock image folder they aren't labeled a and b. My pixel is in the stock October ROM. I flashed TWRP alpha 2 as alpha 1 and rc1 just showed the TWRP splash screen and kept flickering. I backed up my stock os then wiped and flashed pure nexus. Wouldn't flash, some Android binary update error (I've heard my boot.img was the wrong version possibly?). Said okay, just restore my backup. Did that and looked like everything went fine, rebooted and it rebooted right back to TWRP, wouldn't boot to os. Eventually just flashed the stock October image. Am I missing something? Do I need to be on a newer Android version for the rc1 TWRP to work? Any help is appreciated, thank you.
To get out of the bootloop just dl latest factory Image from Google and flash bootimage to slot a and b.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
So my backup restore most likely went fine, I just missed this step?
danielson2047 said:
So my backup restore most likely went fine, I just missed this step?
Click to expand...
Click to collapse
did you first boot to twrp and then flashed twrp zip from twrp?
also, any particular reason for being still at October software?
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
Don't have Verizon edition, but pretty sure it wouldn't lock it.
danielson2047 said:
I wasnt sure my unlock would stick if I flashed new image (Verizon edition).
Click to expand...
Click to collapse
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention​ tje probable class action lawsuits.
So can i keep my stock rom as is and use twrp to flash to the "b' side? I suppose as soon as i'd update the stock side it would just override the b side huh.
TonikJDK said:
It won't.
I don't see it ever doing that. One, I am not sure it is even possible. And 2 it would trigger a full data wipe. Even VZ isn't crazy enough to wipe peoples data. The FCC fine would be massive not to mention​ tje probable class action lawsuits.
Click to expand...
Click to collapse
Good thought. I was thinking in terms of "poor me my phones locked". Never thought about it from the data side.
I keep getting a zram dump pop up that can never got before after flashing in twrp. Does anyone else have this issue? It turns into a boot loop when flashing arise sound mod and sometimes after flashing ROMs. It boot loops between the Google splash and the zram dump screen. Man this is annoying Any help would be highly appreciated!
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
What process did you use when doing the complete factory flash?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
And did you flash the 7.1.2 factory image or 7.1.1?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
If you bought your pixel from google and NOT from verizon, flash the 7.1.2 factory image, then boot twrp RC1 and flash RC2
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Thank you I appreciate it going to do this when I get home
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Guessphx said:
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Click to expand...
Click to collapse
I have the 128GB and never once had an issue. I know with the N6 it happened to it, but I'm not if that happens to our pixels .
I'm getting crashes on an app Im testing on a custom rom I'm using (Dirty Unicorns) so I want to temporarily go back to stock 8.1 and test if the errors occur there as well but I want to return to the custom ROM after testing and get back to the exact state I was in before going back to stock. So basically I want to:
Backup the custom rom with all data and settings
Return to stock 8.1 (without losing data on internal storage)
Return back to the state I was in when I backed up the custom rom with all data and settings
Any help would be greatly appreciated.
ranasrule said:
I'm getting crashes on an app Im testing on a custom rom I'm using (Dirty Unicorns) so I want to temporarily go back to stock 8.1 and test if the errors occur there as well but I want to return to the custom ROM after testing and get back to the exact state I was in before going back to stock. So basically I want to:
Backup the custom rom with all data and settings
Return to stock 8.1 (without losing data on internal storage)
Return back to the state I was in when I backed up the custom rom with all data and settings
Any help would be greatly appreciated.
Click to expand...
Click to collapse
In twrp....backup boot, system, data of DU.
Fastboot the 8.1 factory image you want to return to by removing the -w from the flash-all.bat file. That will return you to stock 8.1 without wiping your data.
Then do your app testing. When done, go back to twrp and do a twrp factory reset with the swipe bar, then restore your DU backup. I would remove your screen lock security, and any substratum themes before you make your backup as well. And there ya go :good:
Keep in mind that this is the P2XL, which can be bipolar at any given time. So, don't hold me personally responsible if anything goes awry!
Badger50 said:
In twrp....backup boot, system, data of DU.
Fastboot the 8.1 factory image you want to return to by removing the -w from the flash-all.bat file. That will return you to stock 8.1 without wiping your data.
Then do your app testing. When done, go back to twrp and do a twrp factory reset with the swipe bar, then restore your DU backup. I would remove your screen lock security, and any substratum themes before you make your backup as well. And there ya go :good:
Keep in mind that this is the P2XL, which can be bipolar at any given time. So, don't hold me personally responsible if anything goes awry!
Click to expand...
Click to collapse
Thank you my friend for the clear instructions. much appreciated.
Badger50 said:
In twrp....backup boot, system, data of DU.
Fastboot the 8.1 factory image you want to return to by removing the -w from the flash-all.bat file. That will return you to stock 8.1 without wiping your data.
Then do your app testing. When done, go back to twrp and do a twrp factory reset with the swipe bar, then restore your DU backup. I would remove your screen lock security, and any substratum themes before you make your backup as well. And there ya go :good:
Keep in mind that this is the P2XL, which can be bipolar at any given time. So, don't hold me personally responsible if anything goes awry!
Click to expand...
Click to collapse
just a quick question. In file I should change fastboot -w update image-taimen-opm2.171026.006.h1.zip to fastboot update image-taimen-opm2.171026.006.h1.zip to prevent wiping of data ?
ranasrule said:
just a quick question. In file I should change fastboot -w update image-taimen-opm2.171026.006.h1.zip to fastboot update image-taimen-opm2.171026.006.h1.zip to prevent wiping of data ?
Click to expand...
Click to collapse
Yes :good:
Badger50 said:
In twrp....backup boot, system, data of DU.
Fastboot the 8.1 factory image you want to return to by removing the -w from the flash-all.bat file. That will return you to stock 8.1 without wiping your data.
Then do your app testing. When done, go back to twrp and do a twrp factory reset with the swipe bar, then restore your DU backup. I would remove your screen lock security, and any substratum themes before you make your backup as well. And there ya go :good:
Keep in mind that this is the P2XL, which can be bipolar at any given time. So, don't hold me personally responsible if anything goes awry!
Click to expand...
Click to collapse
flashed stock (tried multiple times)_....stuck in bootloop
ranasrule said:
flashed stock (tried multiple times)_....stuck in bootloop
Click to expand...
Click to collapse
Try flashing it to the other slot then.
Badger50 said:
Try flashing it to the other slot then.
Click to expand...
Click to collapse
doesnt flash-all.bat flash to both slots ?
ranasrule said:
doesnt flash-all.bat flash to both slots ?
Click to expand...
Click to collapse
Not with the -w removed. To know what slot your on, probably A, run...fastboot getvar all....
To change to the other slot run....fastboot --set-active=a(b)
Badger50 said:
Not with the -w removed. To know what slot your on, probably A, run...fastboot getvar all....
To change to the other slot run....fastboot --set-active=a(b)
Click to expand...
Click to collapse
Aright so I was able to boot into stock and now Im back to DU. Thanks a million for your help sir.
ranasrule said:
Aright so I was able to boot into stock and now Im back to DU. Thanks a million for your help sir.
Click to expand...
Click to collapse
No problem my friend. Just glad to hear that your P2XL didn't go bipolar on you! :laugh:
Badger50 said:
No problem my friend. Just glad to hear that your P2XL didn't go bipolar on you! :laugh:
Click to expand...
Click to collapse
You proved to be a good psychiatrist :laugh:
This is ONLY for the H932. There are no ASSERT checks, so you better pay attention. If you flash this on any other model, you will brick your phone.
Also, I was in a hurry so there is no progress indicator. Just let it flash, you will know when it is done -- it doesn't take THAT long.
Flash this zip: link in TWRP.
Code:
SHA256: [B]6e69250ed78166865501491501e49419cd90e745f422c9744a79ef4736193a7f[/B]
You can dirty flash it over 10d or 20k.
It is 100% stock. The only change I made was removing recovery-from-boot.p, but it appears that isn't enough to keep recovery from getting wiped if you don't flash Magisk.
After flashing this, you MUST flash Magisk again or you will lose TWRP and root -- and your data will be encrypted, and have to use lafsploit all over again.
So boot to TWRP.
Flash this zip
Flash Magisk
-- Brian
Awesome. So just for my ease of mind, this is just like any other ROM I would flash, right? I'm on Lineage and if, for whatever reason, I want to go back to using stock LG, I just boot into TWRP, wipe everything, flash the ROM and Magisk and I'm good to go? I'm pretty sure that's how it goes but again, just to ease my mind for future reference. I may just keep this zip on my device for safe keeping. Thanks
jsgraphicart said:
Awesome. So just for my ease of mind, this is just like any other ROM I would flash, right? I'm on Lineage and if, for whatever reason, I want to go back to using stock LG, I just boot into TWRP, wipe everything, flash the ROM and Magisk and I'm good to go? I'm pretty sure that's how it goes but again, just to ease my mind for future reference. I may just keep this zip on my device for safe keeping. Thanks
Click to expand...
Click to collapse
You got it.
-- Brian
Hate to be "that guy". Getting an error 6 and the sha256 checks out good on my computer. Is it possible the transfer from computer to sd card corrupts the file?
EDIT Checksum is good after the transfer to sd card.
Same here error 6 re downloaded tried again same error 6
Error 6 for me too. Not sure about everyone else but I had to download it through the Google drive app as I couldn't access the file at all with 4 different internet browsers I tried. Didn't get an error but it just kept showing me a blank screen when trying the link.
Probably just a drive issue
redacted
Error 6 also. Downloaded to pc and copied to sd card.
Error 6. Damn,
The first line in the updater script is missing a quotation mark at the end. Not sure if that would cause an issue.
runningnak3d said:
snip
-- Brian
Click to expand...
Click to collapse
Sent from my LG-H932 using XDA Labs
Xblackberryuser said:
The first line in the updater script is missing a quotation mark at the end. Not sure if that would cause an issue.
Click to expand...
Click to collapse
Yep .. typo. I will fix it when I get to work.
Sorry about that.
-- Brian
OK -- fixed version has been uploaded.
-- Brian
runningnak3d said:
OK -- fixed version has been uploaded.
-- Brian
Click to expand...
Click to collapse
Thanks Running!
Sent from my LG-H932 using XDA Labs
runningnak3d said:
OK -- fixed version has been uploaded.
-- Brian
Click to expand...
Click to collapse
Same link at the beginning of this thread? I redownloaded it, and I'll still getting the verification error in TWRP.
Total lack of caffeine......
Should be fixed, but I have no way to test -- so try again.
-- Brian
runningnak3d said:
Total lack of caffeine......
Should be fixed, but I have no way to test -- so try again.
-- Brian
Click to expand...
Click to collapse
I just re-downloaded and I didn't get an error this time. I was trying a dirty flash and It said it flashed successfully but it was done as soon as it started so I think something is still messed up. I wiped cache and dalvik and it still said 20K when it booted back up.
It worked for me
yah it worked but anyway you can make it so it doesn't autoreboot to system after installation.. yes its my fault.. I let it run, wasn't sure how long it was going to take.. walked to get coffee, walked back, and was already rebooting to android. I hard powered it off and did hardware key combo, was hoping TWRP was still there but nope. Factory reset device. Good thing I did twrp backup so no real lose for me.. But do I have to do all of the root steps again. to get twrp back. or can I do something quicker? maybe just run linux part only?
[Cruzer said:
;78082606]yah it worked but anyway you can make it so it doesn't autoreboot to system after installation.. yes its my fault.. I let it run, wasn't sure how long it was going to take.. walked to get coffee, walked back, and was already rebooting to android. I hard powered it off and did hardware key combo, was hoping TWRP was still there but nope. Factory reset device. Good thing I did twrp backup so no real lose for me.. But do I have to do all of the root steps again. to get twrp back. or can I do something quicker? maybe just run linux part only?
Click to expand...
Click to collapse
I've never had TWRP auto reboot on me. always had 2 options after successfully flashing a zip file: wipe dalvik and cache and reboot to system.
I have a simple question if I follow the very first way to root my op9 pro, will it wipe my data or my phone will just get rooted with everything intact
If your bootloader is not already unlocked then your phone will be wiped.
The bootloader always must be unlocked before rooting. Unlocking bootloader will wipe everything. Rooting shouldn't reset everything, depends on what you are doing. I never had a one plus so I don't know how it's there, so I'm going from common knowledge. If you are flashing a SU binary zip file from TWRP it shouldn't wipe, but if you are flashing a PATCHED BOOT.IMG may get wiped.
LAST_krypton said:
The bootloader always must be unlocked before rooting. Unlocking bootloader will wipe everything. Rooting shouldn't reset everything, depends on what you are doing. I never had a one plus so I don't know how it's there, so I'm going from common knowledge. If you are flashing a SU binary zip file from TWRP it shouldn't wipe everything, but if you are flashing a PATCHED BOOT.IMG stuff is going to get wiped.
Click to expand...
Click to collapse
Flashing a magisk patched boot.img on this device does not wipe anything since boot is a separate partition. (Other devices may be different.)
As previously mentioned, unlocking the bootloader WILL wipe everything (the "fastboot oem unlock" step triggers the wipe). However, if your bootloader is already unlocked you're fine, just follow the pinned guide.
One last question, not going to open another thread for this simple thing but can someone help me with a program that will backup ALL my data (gallery photos included) and will restore it when the whole rooting process is done.
Example, iphone has itunes.
So something similar, user friendly
if pixel 6 will not have overheating problems during normal operation then i will definitely replace my op9pro
bugac said:
if pixel 6 will not have overheating problems during normal operation then i will definitely replace my op9pro
Click to expand...
Click to collapse
Good for you, bud. What does that have to do with this thread?
RumRunner19 said:
Good for you, bud. What does that have to do with this thread?
Click to expand...
Click to collapse
sorry, wrong thread. This post should go to "google pixel" thread