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.
Related
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
jayreed1 said:
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
Click to expand...
Click to collapse
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
tabp0le said:
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
Click to expand...
Click to collapse
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
jayreed1 said:
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
Click to expand...
Click to collapse
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
andybones said:
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
Click to expand...
Click to collapse
I read the entire post as you recommended, and I believe I now know how to proceed.
Unfortunately, I've ran myself clear out of free time.
I'll give this a go and report back as soon as I get a few free hours again--probably Friday or so.
Thanks a million!
You guys are very welcome.
Please proceed at your own risk (as with any flashing).
I've tried to make the guide I used as clear as possible and will certainly help if anything is unclear, but keep in mind nougat wasn't out at the time it was created. I don't foresee any issues as really the main thing that is making it boot was anyone that had flashed the us unlocked firmware at any point in time, and I believe people are still converting, The guide is really flashing the us unlocked firmware then back to your (Sprint) RUU.
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
jayreed1 said:
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
Click to expand...
Click to collapse
Nice! Great to finally see some feedback from a sprint user. Wanted to try this myself before I upgrade to nougat firmware. Only thing I'm confused about is you having to erase modem 1&2. What does that mean?
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
jayreed1 said:
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
Click to expand...
Click to collapse
Awesome thanks! Sprint released Nougat OTA yesterday and OMJ extracted firmware that we can flash. Sprint Nougat RUU isn't out yet though waiting for it on HTC's site. Check it out on Sprint HTC 10 XDA dev page. If you flash the firmware and everything still works fine please let me know. Should be trying this if I have time tonight. Have a lot of homework :silly:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
andybones said:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
Click to expand...
Click to collapse
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
Click to expand...
Click to collapse
Very welcome, least I can do.
Nice work on finding the difference. Will certainly save alot of trouble for many!
guys right now what i have to do?
* i updated my htc 10 sprint till the last MM ota, i didn´t make nougat update
* i unlocked my bootloader and install unoficial twrp that i found here
* i have last viper rom
what should i do so i can install other custom roms because right now i can´t pass the boot logo
i´m s off
---------- Post added at 05:27 AM ---------- Previous post was at 05:19 AM ----------
i just need to flash this?
Attached Files
File Type: zip rfg_3.imgs.zip - [Click for QR Code] (1.91 MB, 12 views)
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Click to expand...
Click to collapse
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
beastlymonkey said:
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
Click to expand...
Click to collapse
Are you flashing it while in Download mode or bootloader?
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Are you flashing it while in Download mode or bootloader?
Click to expand...
Click to collapse
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
beastlymonkey said:
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
Click to expand...
Click to collapse
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Click to expand...
Click to collapse
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
beastlymonkey said:
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
Click to expand...
Click to collapse
Yeah I know TWRP is flashed from Download mode, but some stuff apparently still use the bootloader.
Sent from my Sprint HTC 10 using Tapatalk
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.
So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Somebodyz said:
So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Click to expand...
Click to collapse
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
KrisM22 said:
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
Click to expand...
Click to collapse
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Somebodyz said:
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Click to expand...
Click to collapse
What version of RSD do you have - it's on the top bar when you stat RSD.
KrisM22 said:
What version of RSD do you have - it's on the top bar when you stat RSD.
Click to expand...
Click to collapse
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Somebodyz said:
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Click to expand...
Click to collapse
yes, now try a number of different cables. Make sure your phone is in fastboot mode.
That work?
KrisM22 said:
That work?
Click to expand...
Click to collapse
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Somebodyz said:
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Click to expand...
Click to collapse
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
KrisM22 said:
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
Click to expand...
Click to collapse
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Try to reflash the latest TWRP
mijing said:
Try to reflash the latest TWRP
Click to expand...
Click to collapse
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Somebodyz said:
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Click to expand...
Click to collapse
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it ?
mijing said:
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it
Click to expand...
Click to collapse
as i said i did try to reflash it and it gave me that message. and yea i did unlock the bootloader first.
Somebodyz said:
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Click to expand...
Click to collapse
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
KrisM22 said:
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
Click to expand...
Click to collapse
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Somebodyz said:
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Click to expand...
Click to collapse
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
KrisM22 said:
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
Click to expand...
Click to collapse
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Somebodyz said:
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Click to expand...
Click to collapse
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
KrisM22 said:
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
Click to expand...
Click to collapse
So adb devices doesnt let me see my device. but adb sideload works. only problem is, is: This package supports bootloaders: 0xc105, 0xC106, 0xC107, 0xC112, 0xC113 and this device has bootloader 0xc014. do i need an older version then or what should i do?
i just found this https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91, is that a good thing for me to do?
I got a Huawei mate se and didn't realize that allowing it to update to Android o would block the bootloader unlock tool. Is there anyway to downgrade my firmware so I can unlock my bootloader?
voldomart13 said:
I got a Huawei mate se and didn't realize that allowing it to update to Android o would block the bootloader unlock tool. Is there anyway to downgrade my firmware so I can unlock my bootloader?
Click to expand...
Click to collapse
There is a roll-back ROM on firmware finder. As long as it shows your IMEI as approoved, it should install.
That's the nice clean way.
There is a dirty ( possibly dangerous way ) by using the nougat service ROM. That ROM is for bnd-L21, so not sure how an unlocked bootloader will handle it. It has worked on unlocked before.
mrmazak said:
There is a roll-back ROM on firmware finder. As long as it shows your IMEI as approoved, it should install.
That's the nice clean way.
There is a dirty ( possibly dangerous way ) by using the nougat service ROM. That ROM is for bnd-L21, so not sure how an unlocked bootloader will handle it. It has worked on unlocked before.
Click to expand...
Click to collapse
I have been attempting to use firmware finder but I can't wrap my head around actually pushing the update. I heard you need an outdated version of hisuite but no one specifies what version. Any help is appreciated =)
voldomart13 said:
I have been attempting to use firmware finder but I can't wrap my head around actually pushing the update. I heard you need an outdated version of hisuite but no one specifies what version. Any help is appreciated =)
Click to expand...
Click to collapse
Insttall firmware finder from playstore.
In the app select the "hamburger" menu, from top left corner. Select instructions. Either watch videos, or read the text guides
mrmazak said:
Insttall firmware finder from playstore.
In the app select the "hamburger" menu, from top left corner. Select instructions. Either watch videos, or read the text guides
Click to expand...
Click to collapse
The mobile app as far as I can tell doesn't work on newer versions of android. They even have a disclaimer mentioning that the app only works for older devices now.
voldomart13 said:
The mobile app as far as I can tell doesn't work on newer versions of android. They even have a disclaimer mentioning that the app only works for older devices now.
Click to expand...
Click to collapse
You are not on 8.1, the app can work.
But I was only referencing the app for the guides linked inside.
You should be able to use it to flash b330. Which should work in DC
mrmazak said:
You are not on 8.1, the app can work.
But I was only referencing the app for the guides linked inside.
You should be able to use it to flash b330. Which should work in DC
Click to expand...
Click to collapse
My bad I am on 8.0 to be specific bnd-l34 8.0.0.341(c567) and as much as I've tried I can not get it to work on the phone following along on the videos. They are using the app on emui 5.0 not 8.0. It doesn't work anymore on 8.0
All there videos revolve around emui 5.0 or lower. It stopped working with 8.0
voldomart13 said:
My bad I am on 8.0 to be specific bnd-l34 8.0.0.341(c567) and as much as I've tried I can not get it to work on the phone following along on the videos. They are using the app on emui 5.0 not 8.0. It doesn't work anymore on 8.0
Click to expand...
Click to collapse
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
mrmazak said:
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
Click to expand...
Click to collapse
Which mate thread?
voldomart13 said:
Which mate thread?
Click to expand...
Click to collapse
I'm searching. I know i have recommended this process many times, and got many success responses. But I am striking out in finding threads with confirmed responses.
This search only shows 4 found matches for the search info. One does fit real good, but the author has made it sound , not real credible.
https://forum.xda-developers.com/search/forum/7100?query=unlock mate service-rom#posts
mrmazak said:
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
Click to expand...
Click to collapse
What about this method? https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/
mrmazak said:
I'm searching. I know i have recommended this process many times, and got many success responses. But I am striking out in finding threads with confirmed responses.
This search only shows 4 found matches for the search info. One does fit real good, but the author has made it sound , not real credible.
https://forum.xda-developers.com/search/forum/7100?query=unlock mate service-rom#posts
Click to expand...
Click to collapse
This post you made here sounds doable.
This service rom so far has been only thing we found that will load with three button method (dload)
But it is not a full rom to keep on device. It needs you to follow up with flashing fullOTA of your correct version after.
https://www.androidfilehost.com/?fid...83647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Enlighten me what is huru or hwota? If I were to flash this does it boot up into android or is it non functional?
voldomart13 said:
This post you made here sounds doable.
This service rom so far has been only thing we found that will load with three button method (dload)
But it is not a full rom to keep on device. It needs you to follow up with flashing fullOTA of your correct version after.
https://www.androidfilehost.com/?fid...83647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Enlighten me what is huru or hwota? If I were to flash this does it boot up into android or is it non functional?
Click to expand...
Click to collapse
Yes, this should leave you able to boot. And with build level that should allow DC unlocked to give you the code.
Remember like I said before this is kind of a dirty way around and 'could' have issues unknown. Like what if DC does not give you a code, you would then be stuck . (Though you are stuck now)
Huru and hwota are very similar. They both use TWRP to give custom flashing control.
Hwota uses modified stock recovery to flash full ota files.
Huru repacks full ota files so that TWRP can flash them.
Since doth start with TWRP , bootloader unlock is needed.
mrmazak said:
Yes, this should leave you able to boot. And with build level that should allow DC unlocked to give you the code.
Remember like I said before this is kind of a dirty way around and 'could' have issues unknown. Like what if DC does not give you a code, you would then be stuck . (Though you are stuck now)
Huru and hwota are very similar. They both use TWRP to give custom flashing control.
Hwota uses modified stock recovery to flash full ota files.
Huru repacks full ota files so that TWRP can flash them.
Since doth start with TWRP , bootloader unlock is needed.
Click to expand...
Click to collapse
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
voldomart13 said:
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
Click to expand...
Click to collapse
Just spent most of the morning going back and forth with someone else with mate see, and they just did restored his device with the service ROM.
I do not now what he was restoring from, but he ended up with "unknown model" and default build number of 8.0.0.46
This is because of (probably) some data corrupt issue making the flash go bad. But he was able to run the ROM and unlock boooader.
Difference is he already had his unlock code.
https://forum.xda-developers.com/honor-7x/help/dload-method-stuck-5-t3821898
voldomart13 said:
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
Click to expand...
Click to collapse
Have you seen this guide?
It is for "official" hisuite roll-back
I have not rolled back so do not know it it works though.(I checked with my device, it shows no downgrade available)
I know the roll-back firmwarm listed on firmware finder was listed as "bond" and not "bnd". So this means not available "officially"
https://usermanual.wiki/Huawei/EMUI...roid70OperationInstructionpdf.1621060771/help
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
In theory, it is possible to update.
My device is RETAR channel. And I updated using this file from the RETAIL channel.
Sorry if my English is not good: D
I also have a xt1706 from att mx, i used the method in this post https://forum.xda-developers.com/z2-play/how-to/download-z2-play-pie-ota-t3977367 but i had to install first the stock rom for retail moddel, exactly the ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, after that i copied the ota file from the post above to internal storage, searched on my system apps for motorola update services, give it storage permissions, reboot phone and when it booted the OTA appeared, so i just installed the OTA and rebooted, everything is working fine, a lot better than oreo stock or other pie based roms. the only issue i had was with Netflix, i can't install from play store due the phone showing on search for updates that system integrity is at risk.
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
I have the XT1710-06 AMXMX Channel (not the ATTMX) with bootloader unlocked and rooted with Magisk. I upgraded to Pie using the retail version firmware from the page you mention.
1.- First I was on this stock Oreo version for my phone: XT1710-06_ALBUS_AMXMX_8.0.0_OPSS27.76-12-25-15-2-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.- Then I installed the retail Oreo ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip to check if everything was working fine
3.- And finally I installed Pie with this firmware: ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Maybe I could skiped the step 2, I'm not sure.
I had an issue with my SD Card because system said it was damaged and I had to format it like 2 or 3 times. This happened randomly when I restarted the phone. Now all is working fine.
irvingagm said:
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Click to expand...
Click to collapse
The thing with Netflix will be solved once you rooted your phone with Magisk.
̶Y̶e̶s̶ ̶y̶o̶u̶ ̶c̶a̶n̶,̶ ̶b̶u̶t̶ ̶a̶t̶ ̶l̶e̶a̶s̶t̶ ̶m̶y̶ ̶X̶T̶1̶7̶1̶0̶-̶0̶6̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶r̶e̶c̶o̶g̶n̶i̶z̶i̶n̶g̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶o̶n̶ ̶P̶C̶.̶ ̶I̶ ̶h̶a̶v̶e̶ ̶t̶e̶s̶t̶e̶d̶ ̶m̶a̶n̶y̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶'̶s̶,̶ ̶A̶O̶S̶P̶,̶ ̶A̶E̶X̶,̶ ̶L̶i̶n̶e̶a̶g̶e̶ ̶O̶S̶ ̶f̶o̶r̶ ̶8̶.̶1̶,̶ ̶9̶ ̶a̶n̶d̶ ̶1̶0̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶e̶m̶ ̶g̶e̶t̶s̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶p̶r̶o̶p̶e̶r̶l̶y̶,̶ ̶h̶o̶w̶e̶v̶e̶r̶,̶ ̶a̶l̶s̶o̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶o̶s̶e̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶s̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶S̶p̶e̶a̶k̶e̶r̶s̶,̶ ̶s̶p̶e̶c̶i̶a̶l̶l̶y̶ ̶w̶h̶e̶n̶ ̶t̶h̶e̶r̶e̶ ̶i̶s̶ ̶a̶n̶ ̶o̶n̶g̶o̶i̶n̶g̶ ̶c̶a̶l̶l̶ ̶i̶t̶ ̶d̶i̶s̶t̶o̶r̶t̶s̶ ̶t̶h̶e̶ ̶a̶u̶d̶i̶o̶ ̶s̶o̶ ̶m̶u̶c̶h̶ ̶i̶t̶ ̶i̶s̶ ̶i̶m̶p̶o̶s̶s̶i̶b̶l̶e̶ ̶t̶o̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶d̶a̶i̶l̶y̶ ̶f̶o̶r̶ ̶c̶a̶l̶l̶s̶,̶ ̶w̶h̶i̶c̶h̶ ̶i̶n̶t̶e̶r̶e̶s̶t̶i̶n̶g̶l̶y̶ ̶t̶h̶i̶s̶ ̶i̶s̶s̶u̶e̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶ ̶h̶a̶p̶p̶e̶n̶ ̶o̶n̶ ̶S̶t̶o̶c̶k̶ ̶R̶O̶M̶.̶ ̶H̶a̶s̶ ̶a̶n̶y̶o̶n̶e̶ ̶h̶a̶d̶ ̶t̶h̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶?̶
EDIT: Actually the USB connection issue is caused by a bad guide that lacks some commands. This guide gets everything right without any issues.
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
EDIT2: The audio issue only affects users who have upgraded to Stock Pie. This ROM's modem file causes distortion on audio during calls and must be avoided during the upgrading process. To fix the audio issue simply flash the modem file from Stock Android Oreo.
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Yes, you can.
AndroidManager said:
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Click to expand...
Click to collapse
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
leodexe said:
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Click to expand...
Click to collapse
yes
AndroidManager said:
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
Click to expand...
Click to collapse
Do you speak spanish by any chance? I also have that model and that one comes from Spanish Providers for Latin America. I had some issues earlier because of some inaccuracies and other stuff I wasn't aware like the modem thing from Stock Android 9 distorting audio during calls. Now I got everything working properly and flashed Custom ROM AEX (you need Treble TWRP to flash custom ROMs) with working audio without problems.
I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...
I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...
Are you using fastboot or mfastboot? And you are using up to date adb?
Didn't work. Invalid signature again. :/
Screw this. I'm gonna unlock bootloader, then root the phone, then flash Pie ROM through RSDlite. If even that fails, then screw Pie. I'll stay on Oreo.
AndroidManager said:
I tried the internal storage method, but nothing happened.
Click to expand...
Click to collapse
Sometimes this method works, sometimes may not work.
AndroidManager said:
Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
Click to expand...
Click to collapse
You need bootloader unlocked for this process.
felipecassiors said:
Your bootloader must be unlocked.
Click to expand...
Click to collapse
JulioCeesarC said:
I recomend bootloader unlocked for this process
Click to expand...
Click to collapse
HTCDevil said:
Bootloader unlocked but without root
Click to expand...
Click to collapse
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
AndroidManager said:
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Click to expand...
Click to collapse
RSD Lite isn't recommended as it can screw up your basebands getting a phone with no signal whatsoever. The standard ADB fastboot is recommended over everything else.
AndroidManager said:
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
Click to expand...
Click to collapse
In 1:30 of the video, the following commands are missing:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Without these commands, the USB and MTP Mode of the phone will never work. This is true for the XT-1710-06, and probably true for all other variants. Besides, it will do a heavier installation, meaning it will install all the OEM stuff that will eat space, resources and you will not probably use anyways.
AndroidManager said:
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
Click to expand...
Click to collapse
Yes, it is, in fact, it is the exact same method as the standard ADB fastboot flash, because you need to extract the zip file anyways. But this video is mostly based on @JulioCeesarC's guide, which specifically lacks these three commands which are needed for a proper correct installation.
A better guide for flashing/updating Z2P to Pie 9.0 is this one: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
The first statement in this guide is that YOUR BOOTLOADER must be unlocked for this process. This will become useful later if something goes wrong. As a locked bootloader can render the phone completely bricked if something goes wrong during the process. You were so LUCKY because your locked bootloader refused to flash the update. Otherwise you could end with a dead unrecoverable phone.
However, all of these guides in XDA forgets another important REQUIRED step:
If you upgrade to Stock Pie, and you decide to flash a Custom ROM later, you will have audio issues during calls. This is caused by the Stock Pie's faulty modem file (NON-HLOS.bin), the good thing is that the Stock Oreo's modem file works flawlessly and must be skipped during the upgrading/flashing process.
If you wanted a Spanish guide, then all you had to do is just ask for one. There might be more spanish users that don't quite understand english very well and might mess up with this trivial process. I will make a Spanish guide to help them and avoid more conflicts and unwanted bricks. I know all this through proper testing with trial and error.
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
BTW, Now i am running Pie & have an unlocked bootloader. Please tell me the proper way to root the phone. I tried rooting before with TWRP & Magisk, but the phone went to bootloop. I then had to reflash the Pie ROM with ADB method to get it working again. I think the problem has to do with DM-Integrity & Encryption, but I've already wasted hours getting Pie to run on it, and don't want to waste more hours trying to root it. So a quick and easy working guide would be useful.
Also, i don't intend to install any custom ROMs on it. I just have to root it so i can enable Camera2 API (disabled on my variant), and enable wifi display (disabled by default on most AOSP based ROMs, including mine).
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Well, i followed this thread: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
And was able to root my phone without bootlooping. All is well for now. Now i will enable Wifi Display & Camera2 API. Once those are done. I'll have peace at last.
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Just successfully enabled wireless display (persist.debug.wfd.enable=1) & camera2 API (persist.camera.HAL3.enabled=1) within build.prop
Both are working as intended. I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
AndroidManager said:
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
Click to expand...
Click to collapse
Oh, mine is XT1710-06 and it had issues with the USB mode, I figured out it was because of the missing OEM commands, I tested several times flashing without these and the USB connection would never work, after a simple flash with all the commands it started to work again, so if yours worked without these then maybe it's a thing of luck. But keep in mind that without the OEM commands there will be more installed stuff, I prefer to include the OEM commands to remove all the bloatware, so the user can decide which thing to install later.
AndroidManager said:
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Click to expand...
Click to collapse
I am doing a spanish guide anyways, so spanish users can properly do the upgrade process without messing everything.
AndroidManager said:
I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
Click to expand...
Click to collapse
Same feeling bro, it took me a few nights and lots of headaches to get things working after upgrading.
AndroidManager said:
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
Click to expand...
Click to collapse
Hey, thanks, no problem, the first time I arrived at this forum I had no clue how to do most things, so I'm here to help anyone whenever I can. Keep up the good work!