Please help me to unbrick my oneplus x-onyx HELPPPPPPPPPP!! - OnePlus X Q&A, Help & Troubleshooting

I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!

saagr_2800 said:
I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
Click to expand...
Click to collapse
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.

oneplus x fastboot images of rom
seacowx said:
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
Click to expand...
Click to collapse
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?

saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Thats disaster. Have you tried any steps i suggested earlier?
Re-check unlocked bootloader? and try flashing compatible TWRP within fastboot? hows the results?
• Download full ROM 3.1.4 zip and place in your computer (ADB folder)
• Directly boot to TWRP and use "ADB sideload" of full ROM zip (using ADB command)
Use search button (or just google it) how to use ADB sideload.
→Worst case scenario, follow the mega unbrick guide that should help you. OK. goodluck.
Note: Easiest way, contact oneplus support team for remote session. They will help you

adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that

can't flash factory oneplus rom from recovery
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)

saagr_2800 said:
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
Click to expand...
Click to collapse
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me

saagr_2800 said:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
Click to expand...
Click to collapse
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.

seacowx said:
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
Click to expand...
Click to collapse
I tried from mm recovery as well it says installation failed

saagr_2800 said:
I tried from mm recovery as well it says installation failed
Click to expand...
Click to collapse
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.

dchrono said:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
Click to expand...
Click to collapse
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way

Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.

seacowx said:
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
Click to expand...
Click to collapse
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks

Part.0 said:
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Click to expand...
Click to collapse
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin

seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
lol, nice thanks a lot man! im not intend to messing up with my modem either lol

Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
To repair EFS issues when fastboot only available. There are other ways as well however OP mentioned fastboot available only.
Edit: @Part.0 if you would have read OP correctly, you would have noticed he mentioned that he flashed the wrong modem files and my solution along with a fastboot reboot which I didn't mention would have solved his problem. fastboot erase modemst1/2 although you only know it for solving modem/GPS issues are also partitions. Remember our job here is not to convince @Part.0 of our solutions, next time a thank you would do well for teaching you something.

seacowx said:
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
Click to expand...
Click to collapse
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)

saagr_2800 said:
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
Click to expand...
Click to collapse
Ok since i can't reproduce your issue on this one, so i can't find the right solutions for your case.
• Unlocked bootloader + Working Recovery + Fastboot + Full ROM zip file
Those should enough fixing your issue.
Perhaps i missed something, like corrupted partitions (firmware). Maybe another user experienced with the issue can help you out.
Best luck for you.
Note: Maybe our friend here can help you out @dchrono or willing to help you. Thank you.
Ps: Try mountng of "Firmware" in mount section before flashing full ROM. So it will mounted (Firmware, System, data, cache) But wait, ask out before you do. Finger crossed

Download these files
https://www.androidfilehost.com/?fid=24269982087019810
http://www.mediafire.com/file/8g9v5fsslnbf1r6/Qualcomm+Driver+Setup.zip
1 switch off Oneplus x forced
2 install Qulacomm usb driver
3 press volume up button n connect with PC
4 extract Oneplus x unbrick tool
5 run msm downloder and click on start
6 if complete flashing flash stock ROM via memory card
Contact me on. WhatsApp if not success
+917756968834

seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
can it be done with TWRP recovery?

Related

How to flash new 5.0.1 System Image if Rooted

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.

[KERNEL] [STOCK] - N6F27M / NGI77B - "no encrypt"

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).

[STOCK] Flash or update guide for XT1710-08 [PPS29.133-30 (Android 9.0 Pie)]

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

TWRP 3.2.1

CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Reserved
is there a reason why this phone won't flash TWRP or ROMS directly from TWRP?
buschris said:
is there a reason why this phone won't flash TWRP or ROMS directly from TWRP?
Click to expand...
Click to collapse
It actually does that
Question on which partitions to backup in twrp. I'm on stock pie Moto g6 xt1925-6 and want to be able to flash back to it with no problems. Normally I would backup boot, data, system. If I want to try out a gsi however it's is a system image and that's not normally backed up in twrp. I guess I'm asking which partitions should I backup that allows moving between gsi images, stock rom and custom roms.? Thanks
Skippy12359 said:
Question on which partitions to backup in twrp. I'm on stock pie Moto g6 xt1925-6 and want to be able to flash back to it with no problems.lNormally I would backup boot, data, system. If I want to try out a gsi however it's is a system image and that's not normally backed up in twrp. I guess I'm asking which partitions should I backup that allows moving between gsi images, stock rom and custom roms.? Thanks
Click to expand...
Click to collapse
System.img is just the format the ROM (GSI) comes in. A regular system backup will restore just fine. The only difference is you can flash and backup system as an image if you want with TWRP now (boot and recovery too).
Data backups only work if you unencrypted your data. So restoring stock without root isn't possible (because of DM verity and forced encryption).
But restoring system and boot should work either way between GSI's. But unencrypted GSI backups of system and data should restore either way. You can make the backups as images if you want.
madbat99 said:
System.img is just the format the ROM (GSI) comes in. A regular system backup will restore just fine. The only difference is you can flash and backup system as an image if you want with TWRP now (boot and recovery too).
Data backups only work if you unencrypted your data. So restoring stock without root isn't possible (because of DM verity and forced encryption).
But restoring system and boot should work either way between GSI's. But unencrypted GSI backups of system and data should restore either way. You can make the backups as images if you want.
Click to expand...
Click to collapse
Really great feedback madbat99 and very much appreciated. Cheers
Nice to see, especially since Best Buy is running a sale on the G6 Unlocked (all of $150USD) - their cheapest Universal Unlocked handset during the current sale; at this price, even cheapskates like my Mom and her fiance could bite. (Further, at this price, we could even buy three - and I could run Lineage OS again - since Tracfone does not care if I don't run stock.)
the roms never start on my moto g6 . except the descendant.
tiagoneo said:
the roms never start on my moto g6 . except the descendant.
Click to expand...
Click to collapse
What other roms did you try?
tiagoneo said:
the roms never start on my moto g6 . except the descendant.
Click to expand...
Click to collapse
am having this issue with stock pie.
I run the flashing commands, some gives few errors as Key siganuteres or something. and finally doesnt boot.
I use same commands but with Oreo Stock Rom and phone starts working.
here is code I used
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase
fastboot oem fb_mode_clear
fastboot reboot
I ask to myself If I will take same luck with the custom roms.
maybe am a bit offtopic...
yurais said:
am having this issue with stock pie.
I run the flashing commands, some gives few errors as Key siganuteres or something. and finally doesnt boot.
I use same commands but with Oreo Stock Rom and phone starts working.
here is code I used
I ask to myself If I will take same luck with the custom roms.
maybe am a bit offtopic...
Click to expand...
Click to collapse
You can't use the exact same commands. Open the XML file in the zip and see what the flash commands are
Thanks, didnt know the important stuff was inside the XML, will check...
Enviado desde mi SM-G930F mediante Tapatalk
---------- Post added at 10:02 AM ---------- Previous post was at 09:33 AM ----------
madbat99 said:
You can't use the exact same commands. Open the XML file in the zip and see what the flash commands are
Click to expand...
Click to collapse
Ok. I checked the xml, compared with bat file and there were significant changes.
Vendor partition was not beeing flashed
There was no erase ddr command
And the order of commands is slightly different.
I CORRECTED, flashed, again saw the strange warning or error while flashing recovery and boot which read: Image signed with key bad key
But system booted this time... even though digitizer still doesnt work, my main purpose of uograding, as it stopped working when I flashed the previous running oreo version...another story, offtopic here
Thanks
Enviado desde mi SM-G930F mediante Tapatalk
I had tested the RR, AEX, HAVOC OS, LINEAGE. now it only starts if I install the stock from scratch, and put the gsi system image. but does not pick up with gapps
dmilz said:
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Click to expand...
Click to collapse
dmilz said:
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Click to expand...
Click to collapse
qual é a chave de decodificação?
UPHtx said:
qual é a chave de decodificação?
Click to expand...
Click to collapse
[TWRP][UNOFFICIAL] TWRP [64 Bit][3.7.0]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com

Need Help Installing LineageOS 17.1 on Umidigi A7 Pro (amd64 A-Only) with TWRP

Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205

Categories

Resources