Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Solved: Always unlock_critical when unlocking your bootloader! Some say it's optional but it can/will lead to problems!
rank78 said:
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Click to expand...
Click to collapse
Did you extract the factory image? And then place all those files in the platform-tools folder?
Badger50 said:
Did you extract the factory image? And then place all those files in the platform-tools folder?
Click to expand...
Click to collapse
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
Shouldn't all those files be in the platform tools folder?
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
I agree as well. Isn't those files suppose to be in the root folder of platforms tools folder
Put those files in that folder and do the commands again. Should work
Badger50 said:
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
Click to expand...
Click to collapse
Dirty. I'll try doing that in the morning.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
Yes but kept them in a folder so you guys can see.
TonikJDK said:
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
Click to expand...
Click to collapse
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Nevermind, wrong thread. Sorry
rank78 said:
Dirty. I'll try doing that in the morning.
It won't matter, if you haven't done the command...fastboot flashing unlock_critical
Your not going to be upgrading everything with the factory image unless you try to flash them individually. Which probably still won't work without the updated bootloader.
Yes but kept them in a folder so you guys can see.
Yep, they'll need to go in the platform-tools folder.
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Click to expand...
Click to collapse
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Badger50 said:
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Click to expand...
Click to collapse
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
Amen to that bro! ????
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
This. When I first unlocked my bootloader I didn't see to unlock critical, and when I saw afterward it was said to be unnecessary. I'll start from scratch and report back. Sigh.
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
rank78 said:
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
Click to expand...
Click to collapse
I still use TiBu to restore the data on all my user apps. Google just doesn't quite do all of that just yet
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
dd66 said:
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
Click to expand...
Click to collapse
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Badger50 said:
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Click to expand...
Click to collapse
Solved. (ran fastboot oem-info)
Thanks anyway
Related
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
I'm going to be exchanging my pixel and getting another one. Just curious so I know for the future.. if I flash the full factory image via fastboot does that relock the bootloader? I'm gonna guess that it doesn't but just wanna make sure.
New to adb and fastboot so I've been reading around like crazy trying to learn. Is the only way to lock again to use the actual lock command in fastboot?
Edit: I'm referring to using the flash-all.bat script
Yes, you will have to re-lock the bootloader. Do it with fastboot in the bootloader.
Although, you don't have to re-lock the bootloader before sending your phone back... Especially since it will have the stock image flashed to it.
aholeinthewor1d said:
if I flash the full factory image via fastboot does that relock the bootloader?
Click to expand...
Click to collapse
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
cam30era said:
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
Click to expand...
Click to collapse
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
canemaxx said:
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
Click to expand...
Click to collapse
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
cam30era said:
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
Click to expand...
Click to collapse
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
canemaxx said:
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
Click to expand...
Click to collapse
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
cam30era said:
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Click to expand...
Click to collapse
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
canemaxx said:
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
Click to expand...
Click to collapse
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
cam30era said:
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
Click to expand...
Click to collapse
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
canemaxx said:
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
Click to expand...
Click to collapse
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
cam30era said:
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
Click to expand...
Click to collapse
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
In fact, on Windows I think you can just double click the flash-all.bat file (I'm on Linux, so I'm not 100% positive). Yes to your other questions. As long as nothing goes wrong.
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
Been here for about 4 minutes, is that normal?
canemaxx said:
Been here for about 4 minutes, is that normal?
Click to expand...
Click to collapse
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
cam30era said:
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
Click to expand...
Click to collapse
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
canemaxx said:
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
Click to expand...
Click to collapse
Very good.
You sure like living on the edge...
cam30era said:
Very good.
You sure like living on the edge...
Click to expand...
Click to collapse
Haha thanks again for all your help!! 7.1.1 installed and root is back!! This may be the last time I get to update my phone for a while lol
So, here's the error I get (per the phone screen): "E:\Update package is older than the current build, expected a build newer than timestamp 15107775026, but package has a timestamp 1510540413 and downgrade not allowed."
I think their QC department is a local elementary school. How can the timestamp on a file released today be older than a timestamp on a file released a month ago?
dafuq? I'm getting exactly the same error. idiots!
flash the whole image
At the moment you cannot sideload if you are on the Developer Preview 2, only way is to flash which will wipe everything.
IINexusII said:
At the moment you cannot sideload if you are on the Developer Preview 2, only way is to flash which will wipe everything.
Click to expand...
Click to collapse
anyone has the OTA for those on DP2?
I'm not on DP2 and mine won't sideload either.
c:\android-sdk\platform-tools>adb sideload taimen-ota-opm1.171019.011.zip
serving: 'taimen-ota-opm1.171019.011.zip' (~0%) adb: failed to read command: No error
Click to expand...
Click to collapse
IINexusII said:
At the moment you cannot sideload if you are on the Developer Preview 2, only way is to flash which will wipe everything.
Click to expand...
Click to collapse
if you edit the flash-all script it will not wipe anything
The issue is that the build that they used is older. Look at the numbers. .11 is the final and .12 is the beta. My guess is there was an issue in the beta build so they rolled it back .
Sent from my Pixel 2 XL using Tapatalk
Mikulec said:
if you edit the flash-all script it will not wipe anything
Click to expand...
Click to collapse
This is a stupid question, but I've never edited the flash-all file before. Do you just edit out the -w in notepad and save it? Or do I need something else to edit it?
Thanks!
EMcTx said:
This is a stupid question, but I've never edited the flash-all file before. Do you just edit out the -w in notepad and save it? Or do I need something else to edit it?
Thanks!
Click to expand...
Click to collapse
thats all you need to do.
just make sure the flash-all you run is the version you edited.
Flash all.bat is the easiest way
Mikulec said:
if you edit the flash-all script it will not wipe anything
Click to expand...
Click to collapse
True, but if you have to unlock the bootloader to flash then it will wipe regardless.
If bootloader is already unlocked then this will work.
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
you can do it now if you want to, flash the factory images.
else, wait for the OTA to come from Google.
Ops sorry I wrote unlocked but meant LOCKED!!!!
Can I flash factory images with locked bootloader without wiping data?
thegios said:
Ops sorry I wrote unlocked but meant LOCKED!!!!
Can I flash factory images with locked bootloader without wiping data?
Click to expand...
Click to collapse
No.
uicnren said:
No.
Click to expand...
Click to collapse
So I need to wait a specific ota from Google for those on DP2?
thegios said:
So I need to wait a specific ota from Google for those on DP2?
Click to expand...
Click to collapse
yes.
Thanks.
I thought that those on DP2 would get ota before the others...
thegios said:
Thanks.
I thought that those on DP2 would get ota before the others...
Click to expand...
Click to collapse
That's what I thought myself.
Anywho, what's the difference between DP2 and Final? Want to know if it's worth the time and effort.
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
nickdagriff said:
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
Click to expand...
Click to collapse
cant root dp2
will cause cash dump everytime
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
Do you know why
encoded
FizzyAps said:
encoded
Click to expand...
Click to collapse
Do you think I should just throw myself off a building?
i mean its beta what did you except lol
I was just hoping to be able to test it and root it like every other open beta.
What about twrp
You cant flash anything at this time
It will cash dump
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Burt Squirtz said:
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Click to expand...
Click to collapse
Yes I tried rooting both and they both end In cash dump
FizzyAps said:
Yes I tried rooting both and they both end In cash dump
Click to expand...
Click to collapse
How did you try though? Install to inactive slot, AND adb? Or just one of the other?
flashed patched img on both slots
FizzyAps said:
flashed patched img on both slots
Click to expand...
Click to collapse
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
ENCODED, NO METHODS WORK....
I rooted successfully with a Chinese tool
It works on both OOS12 and ColorOS12
Burt Squirtz said:
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I used this method to root last night and can confirm it works on OB 1 A12. I did the vbmeta part before flashing boot.img and didn't do the vendor_boot part at all.
https://www.droidwin.com/root-android-12-via-magisk-patched-boot-img-without-twrp/ this is the guide I followed.
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
ecera said:
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
Click to expand...
Click to collapse
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
terlynn4 said:
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
Click to expand...
Click to collapse
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
ecera said:
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
Click to expand...
Click to collapse
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
terlynn4 said:
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
Click to expand...
Click to collapse
It probably does boot a bit faster. Like you said that message is an extra few seconds. To me its not really noticeable, maybe to someone else it might be.