I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
tvdang7 said:
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
Click to expand...
Click to collapse
I know Google implemented a new anti-role back feature to it's impossible to roll back if your bootloader is locked and your running stock recovery. If your running twrp you probably could do a system wipe and install 8.0, but I am not sure. I haven't tried haha. Hopefully someone can she'd more light on that.
Stock = No
TWRP = Maybe (Probably?)
Ericarthurc said:
I know Google implemented a new anti-role back feature to it's impossible to roll back if your bootloader is locked and your running stock recovery. If your running twrp you probably could do a system wipe and install 8.0, but I am not sure. I haven't tried haha. Hopefully someone can she'd more light on that.
Stock = No
TWRP = Maybe (Probably?)
Click to expand...
Click to collapse
damn thanks for the reply. I am on stock but bootloader is unlocked.
tvdang7 said:
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
Click to expand...
Click to collapse
From what ive read you can. But requires a full wipe of data.
This was possible for me to do before 8.1 was officially rolled out. I was on 8.1 developer preview, I wanted to go back to 8.0 to take advantage of the kernels which at the time we're only for 8.0, so I opted out of the developer preview with Google, they sent an ota to my device, it of course would not take as I was rooted, however the original factory image for 8.0 could be flashed through fastboot.
Yeah I did it to, but it takes a full wipe
jrbxx7 said:
From what ive read you can. But requires a full wipe of data.
Click to expand...
Click to collapse
mac796 said:
Yeah I did it to, but it takes a full wipe
Click to expand...
Click to collapse
Does this mean factory reset first then flash? or do i need to run some adb commands.
tvdang7 said:
Does this mean factory reset first then flash? or do i need to run some adb commands.
Click to expand...
Click to collapse
reboot to bootloader
Code:
fastboot -aa (sets slot a active)
flash-all (using Full Stock 8.0 Factory Image, not an OTA)
If you can catch it before it reboots, hold down the vol-dn to go back into bootloader after it's done flashing - otherwise power off and then power-on holding vol-dn to get back into bootloader.
Code:
fastboot -ab (sets slot b active)
flash-all
done.
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
That's it. Has worked twice for me on my 2XL, bought from Google)
No you cannot. Not even with twrp
You would need to flash the full image via fastboot, and ensure /data was wiped in the process. It would be much trickier due to the dual slots, and odds are you couldn't flash the bootloader with the other images, so it would be a mostly manual flashing process.
Sent from my Pixel 2 XL using Tapatalk
State.of.mind said:
No you cannot. Not even with twrp
Click to expand...
Click to collapse
I don't think this is correct. Apparently the Rollback Index is not updated for devices with unlocked bootloaders. Now I guess I'm not sure if it matters what Android version you were on before unlocking; for example I guess I'm not sure if you get a Pixel 2 XL, immediately update to 8.1, then decide to unlock you bootloader and then try to flash back to 8.0 if it will matter that your Rollback Index probably was updated because you had it locked when updating.
imnuts said:
You would need to flash the full image via fastboot, and ensure /data was wiped in the process. It would be much trickier due to the dual slots, and odds are you couldn't flash the bootloader with the other images, so it would be a mostly manual flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Isn't that what the instructions provided by @PhoenixPath (below) are meant to do?
PhoenixPath said:
reboot to bootloader
Code:
fastboot -aa (sets slot a active)
flash-all (using Full Stock 8.0 Factory Image, not an OTA)
If you can catch it before it reboots, hold down the vol-dn to go back into bootloader after it's done flashing - otherwise power off and then power-on holding vol-dn to get back into bootloader.
Code:
fastboot -ab (sets slot b active)
flash-all
done.
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
That's it. Has worked twice for me on my 2XL, bought from Google)
Click to expand...
Click to collapse
Out of curiosity, why are you saying not to use a USB C cable? I would've thought that would've sped things up a bit, if available on ones computer...
cognitivedissonance said:
Out of curiosity, why are you saying not to use a USB C cable? I would've thought that would've sped things up a bit, if available on ones computer...
Click to expand...
Click to collapse
re: USB-C: I have yet to see a PC USB-C port used reliably for this or any other flashing process. It either flat-out doesn't work, or it gets partway there and fails. If anyone has had success with it, I have not witnessed it or seen it reported, so I have to suggest sticking with Type-A ports on the PC-side of things for now.
You are, as always, free to give it a shot.
(If you do and it works for ya, let me know; I'd love to hear some success stories there.)
cognitivedissonance said:
I don't think this is correct. Apparently the Rollback Index is not updated for devices with unlocked bootloaders. Now I guess I'm not sure if it matters what Android version you were on before unlocking; for example I guess I'm not sure if you get a Pixel 2 XL, immediately update to 8.1, then decide to unlock you bootloader and then try to flash back to 8.0 if it will matter that your Rollback Index probably was updated because you had it locked when updating.
Click to expand...
Click to collapse
I didn't unlock the bootloader until after updating to 8.1 right after I got the phone. Since that time, I've flashed back to 8.0 no problem.
PhoenixPath said:
re: USB-C: I have yet to see a PC USB-C port used reliably for this or any other flashing process. It either flat-out doesn't work, or it gets partway there and fails. If anyone has had success with it, I have not witnessed it or seen it reported, so I have to suggest sticking with Type-A ports on the PC-side of things for now.
You are, as always, free to give it a shot.
(If you do and it works for ya, let me know; I'd love to hear some success stories there.)
Click to expand...
Click to collapse
Interesting, I would've assumed the new USB C standard would've worked much more reliably than the older methods. I wonder what causes the instability like that. Anyway, thanks for the heads up.
Oh just to clarify, my understanding is correct, right? Those instructions you posted will allow downgrading system versions for unlocked bootloader Pixel 2 XLs?
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
Str0ntium said:
I didn't unlock the bootloader until after updating to 8.1 right after I got the phone. Since that time, I've flashed back to 8.0 no problem.
Click to expand...
Click to collapse
This is very good to hear - thank you for confirming!! I assume you used the method Phoenix detailed?
cognitivedissonance said:
Oh just to clarify, my understanding is correct, right? Those instructions you posted will allow downgrading system versions for unlocked bootloader Pixel 2 XLs?
Click to expand...
Click to collapse
So long as it's not a Verizon device and the device has been given the "fastboot flashing unlock_critical" treatment, you should be good to go. I've done this on my Google-store bought 2 XL several times. Has worked for me going from 8.1 to 8.0 and from P to 8.0 (and 8.1).
The part that seems to trip up most users is the need to flash both slots.
PhoenixPath said:
So long as it's not a Verizon device and the device has been given the "fastboot flashing unlock_critical" treatment, you should be good to go. I've done this on my Google-store bought 2 XL several times. Has worked for me going from 8.1 to 8.0 and from P to 8.0 (and 8.1).
The part that seems to trip up most users is the need to flash both slots.
Click to expand...
Click to collapse
Yeah, the slots thing and the "unlock_critical" are both new to me, coming from a Nexus 6P. I'm going to do a bit of additional reading to just try and wrap my head around exactly what the changes are and what the additional commands do. Thanks again!
cognitivedissonance said:
This is very good to hear - thank you for confirming!! I assume you used the method Phoenix detailed?
Click to expand...
Click to collapse
Basically, yeah. I flashed the image to both slots without booting to OS. Then flashed twrp, magisk, etc...
PhoenixPath said:
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
Click to expand...
Click to collapse
For the record, and I know I am far in the minority on this, but flashing with a USB-C to USB-C cable works perfectly with my PixelBook and Pixel 2 XL.
Again, just to re-iterate, there are probably very few people who do this with USB-C to USB-C, and even fewer with a PixelBook, but it does work.
uicnren said:
For the record, and I know I am far in the minority on this, but flashing with a USB-C to USB-C cable works perfectly with my PixelBook and Pixel 2 XL.
Again, just to re-iterate, there are probably very few people who do this with USB-C to USB-C, and even fewer with a PixelBook, but it does work.
Click to expand...
Click to collapse
So...this is news to me. The PixelBook is a Chromebook, and I have one (A Chromebook, not the PixelBook). I have never even considered using it as my insta-boot phone flashing tool. Definitely going to have to read up on it if you're saying this is actually possible. Nice!
PhoenixPath said:
So...this is news to me. The PixelBook is a Chromebook, and I have one (A Chromebook, not the PixelBook). I have never even considered using it as my insta-boot phone flashing tool. Definitely going to have to read up on it if you're saying this is actually possible. Nice!
Click to expand...
Click to collapse
Well, its not an easy process, for sure, which is why I know I am in the very small minority.
Also, at the very least, your Chromebook will need to support (and you'll have to enable) developer mode.
Most do adb/fastboot through 'Crouton". Check that out.
On the PixelBook it can be done natively, but it is not an easy thing to do, as I said above. PixelBooks come with adb/fastboot already on them (once your in developer mode) however, they are out of date and will not work with newer Pixel phones, so, you need to go through a lot of hoops to update them to the latest.
Related
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
applezen said:
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
IDK much about computers much but I learn quick and understand well what I did was set the power-tools as path I didn't do fastboot but fastboot is in the power-tools folder so is this correct?
Sent from my Pixel 2 XL using Tapatalk
Install latest SDK and start the CMD from there
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Ace0spades808 said:
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Click to expand...
Click to collapse
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Click to expand...
Click to collapse
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh ???
Sounds like the same issue as here: https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187/page6 - that's post number 51.
The user resolved it by updating ADB/Fastboot.
Badger50 said:
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh [emoji108][emoji106][emoji41]
Click to expand...
Click to collapse
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Click to expand...
Click to collapse
Hell yeah!!! ???
non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Didn't mean to offend you or anything. I just wanted you to be aware that the developer preview isn't meant to be flashed because it is the "latest and greatest". If you want to try it out go for it but you could end up causing yourself more headache than it's worth (you could brick it or render your phone inoperable for days) since you yourself said you aren't sure what you are doing.
non_smoker0922 said:
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
uicnren said:
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
Click to expand...
Click to collapse
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
uicnren said:
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
Click to expand...
Click to collapse
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Click to expand...
Click to collapse
Did you run both bootloader unlocking commands?
Badger50 said:
Did you run both bootloader unlocking commands?
Click to expand...
Click to collapse
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
So the issue is that you can't get the phone unlocked? Do you still have the option to enable ""OEM Unlocking" in Developer Settings? If it is greyed out, you'll have to reset the phone. First backup and then perform "erase all data(factory reset) and then skip through all of the setup on the phone. Once you are in the phone, gain developer settings, enable "OEM Unlocking" and USB Debugging. You should then be able to unlock via fastboot.
non_smoker0922 said:
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Best I can suggest for you now, is to see HERE.
You can ignore the stuff about C:/D: drives.
Twice now you have used the term unlock_critical. Did you actually type in "fastboot flashing unlock_critical"?
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Please list your exact steps trying to flash back to Oreo.
Unless I am mistaken (it does happen) I was under the impression flashing the 8.1 factory image was all that's needed to return to stock Oreo.
List your steps/process (and files used) and let's see if someone can't help you out.
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Could be your Android PlatformTools are out of date?
abdane said:
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
Click to expand...
Click to collapse
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
abdane said:
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
Click to expand...
Click to collapse
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Az Biker said:
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Click to expand...
Click to collapse
I think I confused you guys, sorry, what i did is that I flashed the STOCK version of 8.1 Oreo, I wanted to downgrade from pie. I installed the official one from google and ran the "flash-all" command and failed at vendor_b
michaelbsheldon said:
Could be your Android PlatformTools are out of date?
Click to expand...
Click to collapse
I just uninstalled it, installed the latest version and still not working :/
I am trying to fastboot the files separately: bootloader, boot, radio, system and vendor images. They all pass except for the vendor image, it always fails there (Data write failure unknown error). Any help?
abdane said:
I just uninstalled it, installed the latest version and still not working :/
Click to expand...
Click to collapse
If you are for sure unlocked and critical unlocked, next step is to unzip everything in the Google factory image (about 25 files), then
use this with instructions listed: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
It's fixed things for me several times when I just could not get results with flash-all.bat.
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
abdane said:
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
Click to expand...
Click to collapse
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Az Biker said:
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
Click to expand...
Click to collapse
This exact info should be a sticky on every single thread!!
CyberpodS2 said:
This exact info should be a sticky on every single thread!!
Click to expand...
Click to collapse
I just created a "troubleshooting thread" for this situation in the 2 XL guides section
Link in my sig.
Should be much easier to point people to these steps before we spend two pages trying to help out just to find out it was a USB cable, or old SDK tools
Ble_Ale said:
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Click to expand...
Click to collapse
I've had this happened a couple of times no Rhyme or Reason the only way out of it is to flash The Flash all with the -w. I believe it has something to do with Googles security.
Edit. I take that back I've switched to the other slot before and restored a backup and gotten out of it if that other slot isn't corrupt
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
samteeee said:
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
Click to expand...
Click to collapse
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
uicnren said:
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
Click to expand...
Click to collapse
Got it. Thanks for the explanation.
Hey guys, I have a Pixel 3 XL that I am trying to repair because it's touchscreen doesn't work, however while doing the repair I found that it does not have the correct firmware and I cannot install the correct one. When in fastboot mode, it shows the product revision as "crosshatch MP1.0(ROW)" however when I go to recovery, at the top it says: "google/blueline/blueline" . I can only flash Pixel 3(blueline) firmware to it through adb sideload since the bootloader is locked. When I try to flash crosshatch firmware through adb sideload it makes it about 50% before failing due to inaccurate signature. Does anyone know how I can correctly return it's firmware to crosshatch. The touchscreen doesn't work due to I assume it having the wrong firmware. Any help is appreciated thanks .
Try unlocking bootloader first and clean up everything that is data and system and reboot back to bootloader and use flash-all script from the rim downloaded and let us know what happened.
lingarajug said:
Try unlocking bootloader first and clean up everything that is data and system and reboot back to bootloader and use flash-all script from the rim downloaded and let us know what happened.
Click to expand...
Click to collapse
Unfortunately I have no way to unlock the bootloader since the touchscreen doesn't work. I've been flashing through adb sideload as flash-all wasn't available to me due to the locked bootloader.
unifiedEthan said:
Unfortunately I have no way to unlock the bootloader since the touchscreen doesn't work. I've been flashing through adb sideload as flash-all wasn't available to me due to the locked bootloader.
Click to expand...
Click to collapse
Just a question why do you need a functioning digitizer to access or interact with the bootloader? Volume buttons are used to cycle through options and the power button confirms the highlighted option in both low level modes.
RagedElimanator said:
Just a question why do you need a functioning digitizer to access or interact with the bootloader? Volume buttons are used to cycle through options and the power button confirms the highlighted option in both low level modes.
Click to expand...
Click to collapse
Need to toggle it in dev options I think. I guess you could attach a pointer device?
wangdaning said:
Need to toggle it in dev options I think. I guess you could attach a pointer device?
Click to expand...
Click to collapse
Ah so you have access to the Android system locally, then if you could try attaching a mouse that should reverse the current situation you are in.
RagedElimanator said:
Ah so you have access to the Android system locally, then if you could try attaching a mouse that should reverse the current situation you are in.
Click to expand...
Click to collapse
I attached a mouse and was able to navigate around, however I am still not able to unlock the bootloader and the Pixel 3 OS crashes a lot on the Pixel 3 XL.
RagedElimanator said:
Ah so you have access to the Android system locally, then if you could try attaching a mouse that should reverse the current situation you are in.
Click to expand...
Click to collapse
I attached a mouse and was able to navigate around, however I am still not able to unlock the bootloader and the Pixel 3 OS crashes a lot on the Pixel 3 XL.
unifiedEthan said:
I attached a mouse and was able to navigate around, however I am still not able to unlock the bootloader and the Pixel 3 OS crashes a lot on the Pixel 3 XL.
Click to expand...
Click to collapse
Just out of curiosity where did you get this device?
RagedElimanator said:
Just out of curiosity where did you get this device?
Click to expand...
Click to collapse
I work at a tech repair site that buys phones and sells them online refurbished. I do software repair there and came across this phone while working there and it has me stumped. I think it might just be bad.
unifiedEthan said:
I work at a tech repair site that buys phones and sells them online refurbished. I do software repair there and came across this phone while working there and it has me stumped. I think it might just be bad.
Click to expand...
Click to collapse
Well if there is any chance you go flash the bootloader separately via fastboot try that. If that is successful then maybe the flash-all script could work
May be power off phone and hold volume down and connect to PC with cable and it should directly go to bootloader, make sure to download Google Android tools before hand and cmd to that folder and then u can unlock bootloader, let us know.
www.frpunlocked.com
Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.
Dang thank you for the guide, but rippers to people who still have their bootloader locked
CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse
bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?
bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?
bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Edit: Mod please remove.
CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.