Related
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
Good morning Guy,
i have a simple question that for me is not so simple because clearly i need some help. I have unlocked & rooted my tablet however now I get a notification for the Lollipop 5.0.1 OTA but when I try to install it and it reboots it then goes into the TRWP recovery mode and nothing else and if i choose to reboot from there the it reboots fine but without the upgrade. Any idea on how to fix this issue?
lucent6408d said:
Good morning Guy,
i have a simple question that for me is not so simple because clearly i need some help. I have unlocked & rooted my tablet however now I get a notification for the Lollipop 5.0.1 OTA but when I try to install it and it reboots it then goes into the TRWP recovery mode and nothing else and if i choose to reboot from there the it reboots fine but without the upgrade. Any idea on how to fix this issue?
Click to expand...
Click to collapse
Just flash the system.img with fastboot.
https://dl.google.com/dl/android/aosp/volantis-lrx22c-factory-8d83cd9b.tgz
They changed the way updating happens. If your rooted never plan on getting an OTA again
AlEsC said:
Just flash the system.img with fastboot.
https://dl.google.com/dl/android/aosp/volantis-lrx22c-factory-8d83cd9b.tgz
Click to expand...
Click to collapse
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
lucent6408d said:
Good morning Guy,
i have a simple question that for me is not so simple because clearly i need some help. I have unlocked & rooted my tablet however now I get a notification for the Lollipop 5.0.1 OTA but when I try to install it and it reboots it then goes into the TRWP recovery mode and nothing else and if i choose to reboot from there the it reboots fine but without the upgrade. Any idea on how to fix this issue?
Click to expand...
Click to collapse
Is possible that the problem is because you have a Custom Recovery (TRWP) installed.
Try to flash the Recovery Stock, and then maybe OTA can be installed. If not, try to flash whole Factory Image.
lucent6408d said:
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
Click to expand...
Click to collapse
You will have to extract several times to find the .img files
lucent6408d said:
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
Click to expand...
Click to collapse
Use winrar or 7-zip to extract it. Inside is a zip file, extract that too. There you will find the system.img
Sent from my Nexus 9 using XDA Free mobile app
lucent6408d said:
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
Click to expand...
Click to collapse
The you must extract .tar again. The you must use .bat or extract a .ZIP and then:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase cache
fastboot erase vendor
fastboot erase userdata
pause
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
But with this, all your data will be erased.
lept_2014 said:
The you must extract .tar again. The you must use .bat or extract a .ZIP and then:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase cache
fastboot erase vendor
fastboot erase userdata
pause
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
But with this, all your data will be erased.
Click to expand...
Click to collapse
You don't have to erase everything to update.
Code:
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
Will update your tablet without wiping everything.
Stock kernels with the "forceencrypt" flag changed to "encryptable".
These are "IMG" files that need to be flashed with fastboot.
(Oct) N6F27M-noencrypt-boot.img - https://mega.nz/#!e4AmQJTa!-b9VEDCUHMa2YedScgHpSpStmKfhVWQMFWQf93L0OCU
(Oct) NGI77B-noencrypt-boot.img - https://mega.nz/#!XsBR0QBb!nkNQibCAT-IMpGH3pPVKLmHsGzE90JQfBcDzkWWwHEM
(Sept) NGI55D-noencrypt-boot.img - https://mega.nz/#!6sYSUbTb!dT-pBFhY4iJuHcqGWnRZiFvnUHLxVlNxrDDfgl0L_9w
(Aug) N6F27I-noencrypt-boot.img - https://mega.nz/#!atxQSZYK!y4H4uFt8pNW0szhUyWrp_QinytKIE3WhszAQMNJ4rO0
(Aug) N8I11B-noencrypt-boot.img - https://mega.nz/#!voxiWQqY!DtV5VWhRRLH3cvpxL37QJDFGMUjZU9uubBP8NuADG0k
Hi, and which one is to use? Are these carrier specific versions?
day242 said:
Hi, and which one is to use? Are these carrier specific versions?
Click to expand...
Click to collapse
Sounds like the N8I11B build has some Verizon specific code. After reviewing, it appears they devs used the same kernel in both builds, so it should not matter which is flashed.
Lose data?
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
TheTomahawk said:
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
Click to expand...
Click to collapse
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release and maintain the exisiting data)
Re: lose data
jbaumert said:
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release any maintain the exisiting data)
Click to expand...
Click to collapse
Cool. Em, could you provide instructions, please?
Tnx
TheTomahawk said:
Cool. Em, could you provide instructions, please?
Tnx
Click to expand...
Click to collapse
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Much obliged.
im assuming one of these brings back ota? probably N6F27I
guessing one is official ota from 7.0 to 7.1.1
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
dudikaz said:
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
Click to expand...
Click to collapse
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
jbaumert said:
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
Click to expand...
Click to collapse
if i flash it after los it gets stuck on google logo and doesn't boot at all :/
---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------
ok so now i've went back to stock N8I11B which is force encrypted. could you tell me exactly what steps should i take to make it not encrypted please? also what about the franco kernel does it get rid of encryption as well maybe?
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
jbaumert said:
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
Click to expand...
Click to collapse
it's really confusing as this is what it says in the official los thread here on xda - "Current lineage 14.1 shamu nightlies are based on the N8I11B August 2017 update from google. So you should be using the radio and bootloader img from that update. " also how do i erase this userdata properly? "fastboot format userdata"? i think last time i did it my device didn't boot at all afterwards. going to try it again now.
Added September 2017 "no encrypt" boot.img to OP
Added October 2017 "no encrypt" boot.img to OP
thumbs up !!!
i was looking all over for the latest img. really grateful for your work. thanks a lot
Thank you very much
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Jeffro64 said:
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also, can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Click to expand...
Click to collapse
You can leave the name of the file (unless you just want to type in a short command with fastboot). As for the backup of "userdata", if you are updating the phone from one stock version to another and following the instructions you quoted, there is no need to backup. Coming from another ROM you would want to wipe and then yes, a backup is a good idea (needed).
Your bootloader must be unlocked.
You can't lock the bootloader, to do this you will need a signed firmware from Motorola (and no one found yet). Instead you can use Magisk to hide the unlocked bootloader, bypass SafetyNet and be able to use Google Pay, for example.
You will not get OTA updates from Motorola even if you somehow lock the bootloader because your phone is registered forever to the "retcn" software update channel, instead of "retail" or "retbr".
Recommended: set your Platform Tools (adb and fastboot) system wide using this guide
https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240
Tested for updating from Oreo stock without wipe.
Steps for clean flashing or update
- Place the suitable script attached on the extracted ROM folder and flash (these scripts are only for XT1710-08 variant to prevent lost modem signal)
- After all the commands succeeded, wait for a full reboot (because of encryption)
- Flash TWRP
- Flash Magisk normally through TWRP
- Be happy
Firmware (you can use this on other XT1710 variants)
Version: PPS29.133-30 (Android 9.0 Pie)
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Other versions:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
TWRP
https://forum.xda-developers.com/z2-play/development/-t3715660
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Motorola drivers https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
Google SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Commands for flashing and wipe
PS: the difference from the official `flashfile.xml` commands is that it doesn't contains `fastboot erase modemst1` and `fastboot erase modemst2`
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Commands for flashing without wipe (update)
PS: the only difference from the previous one is that it doesn't contains `fastboot erase userdata`
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Thanks to
@eqbirvin
@Junior Passos
@HTCDevil
Hello. If I use your script is unzipped the rom with update to August 2018 is the same? They are currently on custom rom Firehound! I would like to go back to the Motorola Blur retail. Do I have to give all the commands from fastboot?
cuciu70 said:
Hello. If I use your script is unzipped the rom with update to August 2018 is the same? They are currently on custom rom Firehound! I would like to go back to the Motorola Blur retail. Do I have to give all the commands from fastboot?
Click to expand...
Click to collapse
Yes! To go back to Motorola stock ROM you must follow this tutorial to make a clean flash, using the flash-wipe script.
my post was wrong, Moderators please delete my post.
Did'nt know i can't delete my own post.
felipecassiors said:
Yes! To go back to Motorola stock ROM you must follow this tutorial to make a clean flash, using the flash-wipe script.
Click to expand...
Click to collapse
the password does not work.
I tried to open the file with 7zip and zip extractor pro. I enter the password!
wrong password.
cuciu70 said:
the password does not work.
I tried to open the file with 7zip and zip extractor pro. I enter the password!
wrong password.
Click to expand...
Click to collapse
Firmware:
https://drive.google.com/open?id=1rcgUvLG5c7l9jH8AzuTg3WPJnORQ6VlY
The password is
Code:
MotorolaFirmwaresLB
I use WinRAR, but 7-Zip should work. Try again please, here is working.
Would it be easy to update the system with the latest patch? I have magisk installed with system from April patch. If so what how would be the procedure?
Followed all the steps and got it working. Thanks so much, the original software on this version of the phone is terrible!
One thing, like a few others, my fingerprint sensor isn't working. Is it as simple as a wipe after install?
pjcons said:
Followed all the steps and got it working. Thanks so much, the original software on this version of the phone is terrible!
One thing, like a few others, my fingerprint sensor isn't working. Is it as simple as a wipe after install?
Click to expand...
Click to collapse
Take a look at this post friend:
https://forum.xda-developers.com/z2...reo-retail-via-fastboot-t3786153/post76486376
Try to flash again but evading this 4 commands.
felipecassiors said:
Take a look at this post friend:
https://forum.xda-developers.com/z2...reo-retail-via-fastboot-t3786153/post76486376
Try to flash again but evading this 4 commands.
Click to expand...
Click to collapse
Yes I took those out when flashed and still no fp sensor. Thanks for sending on though. I read everything b4 flash but still no fp sensor.
But I didn't wipe 1st so might flash again and wipe 1st?
Everything else working 100% :good:
pjcons said:
Yes I took those out when flashed and still no fp sensor. Thanks for sending on though. I read everything b4 flash but still no fp sensor.
But I didn't wipe 1st so might flash again and wipe 1st?
Everything else working 100% :good:
Click to expand...
Click to collapse
If you can, please try wiping in first. If still doesn't work, the procedure to solve this is:
- Flash the original ROM (that ugly ZUI one) to get it working again
- Flash the ROM on this thread, wiping, evading that 4 commands
I can help you to find the ZUI ROM if you need.
felipecassiors said:
If you can, please try wiping in first. If still doesn't work, the procedure to solve this is:
- Flash the original ROM (that ugly ZUI one) to get it working again
- Flash the ROM on this thread, wiping, evading that 4 commands
I can help you to find the ZUI ROM if you need.
Click to expand...
Click to collapse
Cheers mate. If u can send me a link to the very ugly Zui rom just in case would be great.
pjcons said:
Cheers mate. If u can send me a link to the very ugly Zui rom just in case would be great.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1322778262903986742
Just make sure your device is XT1710-08
Tested on a XT1710-06 full wipe and it works great, because i wanted to do and update and i goot bootloop.
Just in case someone find this, im from México, I flashed this fastboot rom and installed Magisk to get root, used the Canary build to make it work with my fav games that are Fate go and Pokemon go (spoof) and it works like a charm, thanks.
felipecassiors said:
https://androidfilehost.com/?fid=1322778262903986742
Just make sure your device is XT1710-08
Click to expand...
Click to collapse
Yep, it's an XT1710-08 for sure! Thanks again...
pjcons said:
Yep, it's an XT1710-08 for sure! Thanks again...
Click to expand...
Click to collapse
Friend, use the tutorial of this thread, but instead of that script, use this attached to flash the ZUI stock ROM.
8bitcode said:
Tested on a XT1710-06 full wipe and it works great, because i wanted to do and update and i goot bootloop.
Just in case someone find this, im from México, I flashed this fastboot rom and installed Magisk to get root, used the Canary build to make it work with my fav games that are Fate go and Pokemon go (spoof) and it works like a charm, thanks.
Click to expand...
Click to collapse
Friend, for models other than XT1710-08 (outside China), you can use this script attached. It is more recommended.
Thank you for the feedback!
felipecassiors said:
Friend, for models other than XT1710-08 (outside China), you can use this script attached. It is more recommended.
Thank you for the feedback!
Click to expand...
Click to collapse
Hey I got back to ZUI - the Chinese ROM came up. Fingerprint working. So rebooted into BL and flashed the firmware as per OP. Again, no FP sensor.
I'm gonna try again and wipe after install ZUI, BEFORE flash and wipe Oreo.
[2nd try no better??]
It flashes ok but FP sensor just won't work. Everything else working. When you say "Flash the ROM on this thread, wiping, evading that 4 commands" I use the flash and wipe script and remove the 4 commands (the erase modem seem to have been removed already from the script). Any ideas, I'm so close! Have flashed back and forth a few times tonight. It's fun though! Cheers!
pjcons said:
Hey I got back to ZUI - the Chinese ROM came up. Fingerprint working. So rebooted into BL and flashed the firmware as per OP. Again, no FP sensor.
I'm gonna try again and wipe after install ZUI, BEFORE flash and wipe Oreo.
[2nd try no better??]
It flashes ok but FP sensor just won't work. Everything else working. When you say "Flash the ROM on this thread, wiping, evading that 4 commands" I use the flash and wipe script and remove the 4 commands (the erase modem seem to have been removed already from the script). Any ideas, I'm so close! Have flashed back and forth a few times tonight. It's fun though! Cheers!
Click to expand...
Click to collapse
Mine XT1710-08 fingerprint sensor works without removing the 4 commands, I just remove the 2 erase modem (already removed in the flash scripts). Anyway, try to install the ROM of this thread (https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153) and see if it work for you. Please post here if you have news about it.
Rooting
I did all the steps and completely reinstalled android 8.0 on my moto z2 play, I then got twrp and tried flashing magisk 17.1, I got stuck in a bootloop but managed to flash the whole thing again, which solved the problem. To make sure this doesn't happen again, could you please state the steps for rooting. I cant remember if it was because I did not input the code into the terminal. When I input the code am I supposed to get a response or message, because it just stays bank?
Thank you
So i rooted my Oneplus Nord 2 and got into a bootloop wiped the device using TWRP booted into rooted OS and wifi and bluetooth are not working. I dont have a backup of EFS partition.
Flash Boot image
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
pankspoo said:
Flash Boot image
Click to expand...
Click to collapse
Didnt work
krugm0f0 said:
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
Click to expand...
Click to collapse
Didnt work
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
fellu4485 said:
Didnt work
Click to expand...
Click to collapse
You need to flash stock Boot image not rooted
pankspoo said:
You need to flash stock Boot image not rooted
Click to expand...
Click to collapse
I did
krugm0f0 said:
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
Click to expand...
Click to collapse
I can't get WiFi and Bluetooth to work
This error is almost exclusively caused by having the wrong boot.img.
I know you already said you're certain you flashed the correct boot.img, but the fact your phone is showing these symptoms means you likely have the wrong boot.img, as is true in 99.999% of these cases.
The only other possible cause of these symptoms would be because you wiped or corrupted your persist partition.
The persist.img partition contains unique data calibrated to your own device which contains calibration specific to your phone's wifi and bluetooth module/antennas, if you wiped this partition by accident, you will need to find a backup of the persist.img taken from YOUR OWN DEVICE and reflash it, no one else on these forums will be able to provide these for you.
Again, I'll restate that the chances of the persist.img case being the cause here is almost unheard of unless you distinctly remember tampering with the persist image, which you would have had absolute ZERO reason to have done so.
I would highly recommend that you double, triple, and quadruple check you flashed the CORRECT boot.img before resorting to messing with your persist.img, it's likely your download source provided the wrong one, or you mixed up the files in your downloads folder which happens frequently.