Develop Bugs

Huge problem with moto z2 play trying to flash twrp

Hi. Today I decided to root my device (Moto Z2 Play, XT1710-06) and install a good custom ROM, but after unlocking bootloader I tried to flash the recovery with the command fastboot
PHP:
flash recovery twrp.img
and I got the message
PHP:
error: cannot open 'twrp.img'
. So I went with the newest version for albus (twrp-3.2.3-0-albus.img) and I got this:
PHP:
target reported max download size of 534773760 bytes
sending 'recovery' (15564 KB)...
OKAY [ 0.344s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.195s]
finished. total time: 0.539s
After partially flashed it I could only use it once. When rebooting to system (stock) it would overwrite the stock recovery, so TWRP would dissapear. Then I decided to root with the stock ROM in but it got bootlooped.
Finally, I flash recovery again so I could wipe (Including data and system) and install a custom ROM, but didn't work yet because the error messages I get in TWRP after trying to flash the ROMs zip is ERROR 255. I have tried with ToxicRom, LineageOS and Pixel Experience.
What's happening? Did I do wrong wiping the stock system? I'll appreciate any help.
Thanks for reading.

Caney said:
Hi. Today I decided to root my device (Moto Z2 Play, XT1710-06) and install a good custom ROM, but after unlocking bootloader I tried to flash the recovery with the command fastboot
PHP:
flash recovery twrp.img
and I got the message
PHP:
error: cannot open 'twrp.img'
. So I went with the newest version for albus (twrp-3.2.3-0-albus.img) and I got this:
PHP:
target reported max download size of 534773760 bytes
sending 'recovery' (15564 KB)...
OKAY [ 0.344s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.195s]
finished. total time: 0.539s
After partially flashed it I could only use it once. When rebooting to system (stock) it would overwrite the stock recovery, so TWRP would dissapear. Then I decided to root with the stock ROM in but it got bootlooped.
Finally, I flash recovery again so I could wipe (Including data and system) and install a custom ROM, but didn't work yet because the error messages I get in TWRP after trying to flash the ROMs zip is ERROR 255. I have tried with ToxicRom, LineageOS and Pixel Experience.
What's happening? Did I do wrong wiping the stock system? I'll appreciate any help.
Thanks for reading.
Click to expand...
Click to collapse
Flash Magisk, after TWRP.

I kinda solved it. Now I'm on Resurrection Remix Oreo but Magisk 18.0 can't be flashed, neither on LineageOs 15.1

I have the xt1710-06 that the operating system is 32 bit from Argentina
I do not know if it's the same cell phone I finally see that someone manages to install the twrp and a custom rom could do a tutorial please?
there is no tutorial for this model and I do not know if you can install a 64bit android in one that has a 32bit operating system
THANKS

Hi, how did you solve it?

Boot TWRP, then flash it from inside TWRP. Flashing from fastboot always throws some error, but just booting the same image has no problem. And of course TWRP can flash itself.
When flashing Magisk, make sure it keeps dm-verity and enforce encrypt. At least Magisk v19 doesn't give me any problem when setting them before. I think v18 was a version acting up here and there

Can't flash TWRP - rollback warning. Please advise

I have Chinese 6gb 128gb Mi Max 3 with latest China stable ROM. Finally i decided to get root but i can't flash TWRP over fastboot as in all instructions. My bootloader is unlocked. I get following warning
J:\Xiaomi Mi Max 3 - root>fastboot flash recovery twrpteamwin.img
target reported max download size of 536870912 bytes
sending 'recovery' (61164 KB)...
OKAY [ 1.333s]
writing 'recovery'...
(bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: Please check your package anti version!!!)
finished. total time: 1.353s
I tried 3 versions of TWRP. I also installed latest global stable ROM. Same error. What should i do? Please help...

Same for me. Tried
Code:
C:\platform-tools>fastboot flash recovery twrp-3.3.0-0-nitrogen.img
Sending 'recovery' (61164 KB) OKAY [ 1.325s]
Writing 'recovery' (bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: 'Please check your package anti version!!!')
fastboot: error: Command failed
Is it safe to do the oem ignore_anti thing and force it or would it brik my device?
Device should be official global 64gb 4 gb RAM bootloader unlocked official with 720h waiting periode. Currently MIUI Global 10.2.1.0 installed.

That's what I'm trying to figure out, if it's safe to override it. I don't want to brick my phone. Right now i had installed China beta ROM which has a root built in. But Android Auto refuses to work with this ROM. So i have to either go back to China stable without root, or flash TWRP somehow

So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.

bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
PLease let me know if you were able to flash ROM after that! I'm waiting for your reply and biting my nails

Try
fastboot boot twrp.img
And then flash twrp.img through booted recovery.

bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
So, did it work? Were you able to flash ROM after overriging ARB warning during TWRP install?

If anyone is interested in overcoming this error: I have done the following, here are my steps:
My phone: China Stable ROM, 6Gb/128Gb Mi Max 3
- Make sure oyu have unlocked bootloader
- I flashed Global Stable ROM first, with the chinese software tool: essentially just automated flashing via fastboot, but any method works. Custom ROMs would be flashed after TWRP.
- Copy TWRP image on a flash drive, make sure it's accessible from the phone
- Phone in fastboot mode, conenct to PC "fastboot boot twrp-tw3300.img" (renamed latest teamwin TWRP image for Mi Max 3)
- Phone boots in TWRP
- Select flash - image - and flash TWRP from inside TWRP (no wiping, nothing else, flash image to recovery partition)
- If root is desired, flash Magisk.
- Reboot to recovery, to see that it sticks
- Reboot to system
- Install Magisk apk, check root.

Sorry for late reply, was bussy getting RR GSI up and running. But sadly it was stuck in bootloop. So i flashed a room from mi-glob roombuilder. This worked so far succesfully, but the chines dialoges do not go well with me.
From my understanding, the warning from the Booloader ist just a warning. In this case may be triggered by ARB, wich means that fastboot or the BL can not guarantee that the room or recovery will work on that phone or may even brick it or is at least not from the vendor.
After you type in :
Code:
fastboot oem ignore_anti
basically this compatibillity check is disabled. After that you can flash any room or recovery you like. If you do flash an older firmware on an ARB activated device you will produce a nice paperwight. But that is another topic.
I do not know, which part (bootloader or fastboot) is responsible for the warning, as i am a total noob regarding flashing android devices.

restart loop with V10.3.5.0.ODEMIXM after factory reset

I have my MI MIX 2 with official global V10.3.5.0.ODEMIXM. I upgraded to this version via regular OTA update about 2 weeks ago.
After factory recovery I did last day I stuck in restart loop with error.
I picked up language, region, and after that on Just a sec screen I have error Find Device closed unexpectedly and going to restart loop.
Via Mi suite 3 beta I am able to flash same firmware, but this is causing same error and loop. Older firmwares are not possible to flash because of error. (flashing firmware older the nactual firmware on phone)
Via fastboot I am not able to flash anything as phone has locked bootloader and is not assigned to my Mi account so unlock tool is not able to unlock it.
So.. what can I do to fix it ?

hi , if you have access to fastboot look if arb is on , download this => https://androidfilehost.com/?fid=24686681827312411 and copy/paste that => fastboot getvar anti ,, if you get 4, arb is on ..... if you have under , you can flash older firmware
So if you have 4 , search '' Anti-rollback Protection and Fastboot Unlocker '' to download antirbpass dummy.img

So
fastboot getvar anti
anti: 1
fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.002s]
writing 'antirbpass'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.006s
Mi suite 3.0 still says:
Sorry, I can't support the rollback to a non-newer previous version.
Push Man Brush Pack Version: V10.3.5.0.ODEMIXM

hi you have anti 1 , you can flash older rom without brick , you have unlock bootloader
rom 10.2.2.0 =>http://bigota.d.miui.com/V10.2.2.0....XM_20190109.0000.00_8.0_global_ffb701bb41.tgz ,, you can flash ,, after that make upgrade firmware via update
ps: un flash.bat it will ask for 0 to flash ............. i did mistake ....... you can try flash beta rom , it's under pie , i flashed it to and it's stable
=> https://bigota.d.miui.com/9.5.30/ch...30_20190530.0000.00_9.0_global_6c535734e7.tgz
after flash search update normaly get 9.6.13

I really appreciate your help, but I was not succesfull.
Bootloader is locked and unlocking via MI Unlock is not succesfull because no Mi account is bound to the device.
Flashing via Mi Suite 3 always ends like this:
V9.5.8 (pie) -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V9.6.13 -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V10.2.2.0.ODEMIXM - > ROM Package verification failed Unknown Error[2013]
V10.3.1.0.ODEMIXM -> Sorry, I can't support the rollback to a non-newer previous version.
V10.3.5.0.ODEMIXM -> Succesfull, but always get boot loop with error FIND DEVICE CLOSED UNEXPECTEDLY
I also tried to reboot to EDL with help of this srticle: https://www.xiaomigeek.com/edl-mode-xiaomi.html second option - 2. How to Boot into EDL From Fastboot Mode.
But it always restarts and goes to boot loop.
So is last try open the phone and test point method? http://en.miui.com/thread-1351514-1-1.html

Question about rooting with Magisk

I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?

Venomiz said:
I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?
Click to expand...
Click to collapse
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).

Az Biker said:
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).
Click to expand...
Click to collapse
Thanks for the reply. In the folder are the following files:
bootloader-taimen-tmz10n.img
flash-all.bat & .sh
flash-base.sh
radio-taimen-g8998-.....
And I overlooked the image-taimen-opd1.170816.010.zip
So, I patched with magisk the wrong file but it was successful (at least if I trust the onscreen text). I will now transfer the boot.img to the pixel, patch it, transfer it back, and flash. I will reply after doing so
PS: Android 8 is easier to use if you do something you should not in Pokemon Go... :silly:
And the

Why patch the boot image manually, flashing magisk via TWRP as it works fine. Ive never used the patch boot image method ever on any of the devices ive owned.
1) Flash ROM
2) Boot TWRP
3) Flash TWRP (optional)
4) Flash Magisk
5) Reboot

Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?

Venomiz said:
Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?
Click to expand...
Click to collapse
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?

Az Biker said:
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?
Click to expand...
Click to collapse
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.

Venomiz said:
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.
Click to expand...
Click to collapse
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.

Az Biker said:
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.
Click to expand...
Click to collapse
It worked perfectly, thank you!

Question xiaomi mi 11 lite 5g en (lisa) nv data is corrupted

xiaomi mi 11 lite 5g en (lisa) nv data is corrupted
modem file plase

gsmbakar said:
xiaomi mi 11 lite 5g en (lisa) nv data is corrupted
modem file plase
Click to expand...
Click to collapse
Install to another phone MIUI Downloader (from Playstore) - then you can easily download Global/EEA/CN/... fastboot/tgz stock ROMs.
Unpack tgz = tar, gzip, and you can find there all partitions

zgfg said:
Install to another phone MIUI Downloader (from Playstore) - then you can easily download Global/EEA/CN/... fastboot/tgz stock ROMs.
Unpack tgz = tar, gzip, and you can find there all partitions
Click to expand...
Click to collapse
need eng modem file
xiaomi mi 11 lite 5g en (lisa) eng modem file plase

gsmbakar said:
need eng modem file
xiaomi mi 11 lite 5g en (lisa) eng modem file plase
Click to expand...
Click to collapse
modem.img is 192 MB
Use PC, whatever, xiaomifirmwareupdater.com, find EXACT recovery/zip for your firmware (you should know were you on Global, Russia, whatever, were you on 12.5.7, 12.5.8, whatever)
Download the zip, unzip, find Payload_Dumper (Google is your friend) on XDA thread, install to PC, and dump img files from payload.bin
modem img 192 MB file cannot be attached here, and they can be different from firmware to firmware (although all for Lisa) - YOU MUST do yourself
Good luck

Any solution for nv data corrupted , mi 11 lite 5g lisa ,
i have unlock bl , already try flash diffrent firmware on fastboot mode , i have orignal qcn file , i have not modem backup
plz help experts

C:\Users\Aftab\Desktop\model checker\Check Model Xiaomi - Vivo>fastboot flash modem "C:\Users\Aftab\Desktop\model checker\Check Model Xiaomi - Vivo\NON-HLOS.bin"
target reported max download size of 805306368 bytes
sending 'modem' (191948 KB)...
OKAY [ 5.870s]
writing 'modem'...
OKAY [ 0.686s]
finished. total time: 6.572s
After write firmware modem , nvdata corrupted error solved , but usb , wifi sim not working , how i can restore orignal qcn
phone connect only fastboot mode and edl mode , not connecting on normal mode

My Mi 11 lite 4G has same problem anyone have solution??

Please help
How are you do fix nv data corrupted
Please solution or modem file share