Develop Bugs

How can I install BND AL-10 (India) new OTA update 8.0.0.340

I have received a OTA update today 8.0.0.340 (559 MB)(current version 8.0.0.320). But I am unable to install the update due to TWRP recovery and unlocked bootloader.
Is there a way to install update it without flashing stock firmware again?

Download FullOTA firmware for 8.0.0.320-C675-D4 (Make sure your version match correctly)
Extract that firmware with Huawei Update Extractor
You will find RECOVERY_RAMDIS.img in the folder. (not eRecovery)
Boot into fastboot mode:
Power Off > Connect USB cable to PC > Plug USB to phone and hold Volume down
Make sure device is connected by typing: fastboot devices
Flash Stock Recovery by typing: fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Reboot
You can now update using OTA.
(I always recommend Factory Reset for major updates , but it's optional. Also log out off Google Account before factory resetting)

Hi @antariksh , thx for the brief tutorial. After flash stock recovery, can I flash the 1.7GB Firmware file or do I need to upgrade via OTA?
Also, got this error while flashing recovery:
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.889s

Any idea on how to extract version.img from stock ROM?

techack said:
Hi @antariksh , thx for the brief tutorial. After flash stock recovery, can I flash the 1.7GB Firmware file or do I need to upgrade via OTA?
Also, got this error while flashing recovery:
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.889s
Click to expand...
Click to collapse
What's your current build number and what command are you using to flash stock recovery?
You should try the OTA first and factory resetting the device will get you back to a Fresh stock version. Unless you know exactly which version to flash for your device.
You can also use HWOTA or HuRUpdater if you are on TWRP. But go through the entire thread thoroughly.
I have bricked my device for silly reasons, although I got Honor to replace entire SoC for free.
Flashing on EMUI devices is still not as robust as Stock Android ROMs

Thanks for your prompt reply, will try during next weekends and let you know.
Also, some other way to contact u quickly like Telegram/Whatsapp? so that I don't mess things up

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.

[HELP NEEDED] Can't unlock Lenovo Z2 Plus bootloader

I'm trying to unlock lenovo z2 plus bootloader using adb and fastboot on fedora. I'm using platform tools version 29. I'm trying
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
but this command won't work. I get this error message
fastboot: invalid option -- 'i'.
Apparently fastboot --help also doesn't shows -i as an argument.
So how can I unlock the bootloader?

Ignore that i part,
Just use fastboot flash unlock unlcok_bootloader.img

According to my experience, under Qualcomm's EDL mode (9008), it can actually flash TWRP without unlocking the bootloader.
"fastboot oem reboot-edl" or "adb reboot edl" will reboot the phone into 9008 mode. You may try special EDL USB cable as well, especially under tricky situations.
You need to download (and install) qpst 2.7.474 and stock ROM (for prog_emmc_firehose_8996_ddr.elf). QFIL has a nice partition manager feature, which allows you to flash anything you want - of course, this will introduce risk of data loss/bricking etc, if improperly operated.

fun_jack said:
I'm trying to unlock lenovo z2 plus bootloader using adb and fastboot on fedora. I'm using platform tools version 29. I'm trying
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
but this command won't work. I get this error message
fastboot: invalid option -- 'i'.
Apparently fastboot --help also doesn't shows -i as an argument.
So how can I unlock the bootloader?
Click to expand...
Click to collapse
These are for older version adb commands so you are facing issues either use older adb files or use new commands

No longer receiving unlock files
I bought an Indian version of Z2 plus on @mazon.ae. after 2 weeks of trying and waiting for the bootloader .IMG file to unlock the phone from official zuk developer site and with different Email including [email protected] CN (aliyun) I gave up and got the device 100% refunded. The latest possible patch date is Nov 1st 2016... Anyone got better results recently (Oct Nov 2019)?

Ludo56510 said:
I bought an Indian version of Z2 plus on @mazon.ae. after 2 weeks of trying and waiting for the bootloader .IMG file to unlock the phone from official zuk developer site and with different Email including [email protected] CN (aliyun) I gave up and got the device 100% refunded. The latest possible patch date is Nov 1st 2016... Anyone got better results recently (Oct Nov 2019)?
Click to expand...
Click to collapse
Ohhh no that seems bad I just received my z2 yesterday for sake of custom rom and rooting.If this does not work out, I have to refund it ASAP.
Please follow this thread and reply if anyone got the unlock file

Finally this thread https://forum.xda-developers.com/le...-receive-unlock-bootloader-img-t3731061/page4 Post Number 40 helped me unlock my bootloader as of 16th November 2019 and now I am on custom ROM

didn't need the file at all
Phone: ZUK Z2 Plus (Z2131)
After having tried many times following this tutorial and never receiving any E-Mail, I found a rather simple solution that worked:
I didn't really expect it to work, so this is from memory, wordings may differ a bit.
First: make backup of your data!
Make sure you have updated ZUI to the latest available version.
Enable developer options ( From your device go to " About -> ZUI version" , scroll down and click " build number " continuously until you see "You are now a developer")
Go to developer Options and look for the toggle "Allow OEM Unlock" (or similar) and set it to enable. Confirm.
Reboot.
The phone automatically performs a factory reset (All Data lost!).
Now you can continue with flashing custom recovery (TWRP) and ROM.
For example use Lineage OS. Instructions: (Sorry, can't post the link) go to lineageos.org and look for the decive and go to install instructions.
Finally I can enjoy the phone with custom ROM and up-to-date Android 10.
You may have to be on ZUI 3.5 (Chinese Version) - It may not work with the Indian Version.
Follow this hints to deep flash ZUI Chinese Stock firmware: https://forum.xda-developers.com/showpost.php?p=83808887&postcount=2
Also read this:
https://forum.xda-developers.com/showpost.php?p=80890653&postcount=40
Quote:
From ZUI 3.5.xxx on you don't need unlock_bootloader.img anymore.
You need to allow OEM unlock in developer options first, then just unlock by "fastboot -i 0x2b4c oem unlock-go" .
If you did not allow OEM unlock option in developer setting then you get error message.
Click to expand...
Click to collapse

can you help me ASAP
E:\Minimal ADB and Fastboot>fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (5 KB)...
OKAY [ 0.032s]
writing 'unlock'...
FAILED (remote: Invalid data)
finished. total time: 0.072s
always like that , i've tried to get new img but still like that.

Redmi note 8 pro, bricked for ever?

Hello guys:
One month ago i bought a Redmi note 8 pro, when it comes after a long time (almost 3 weeks) it comes with bootloader opened so i couldn use for example NFC pay. I looked for information to lock the bootloader i followed steps and bootloader was closed but phone was bricked too, so only can put smarthphone in fastboot or in recovery mode. I tried flash some roms by Fastboot using CMD in pc but appears this message
C:\adb>fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.004s
that was expected because bootloader is closed, but now i dont know if its posible to unlock bootloader and flash a new rom or beeing bootloader closed, flash a new rom for unbrick the phone.
To solve this problem I heard something abou autoriced xiaomi accounts and something about waiting seven days for unlock but i dont know nothing about it.
Thank you guys.

Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk

Sythel4 said:
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I have tried to flash with fastboot and with miflash pro, and it always fails, I imagine that the flash tool will do the same as miflash pro and it will also fail, I will try anyway.
Thank you.

Try and give me a feedback
Sent from my SM-A705FN using Tapatalk

Sythel4 said:
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I'm sorry for answering late, but I'm very busy with the current health situation.
What I have done is focus on unlocking the bootloader, and later will flash a new rom.
To unlock the device i have download "mi flash unlock tool"
Software recognice my phone
Click on "unlock">"unlock anyway">"unlock anyway"
Verifying device-ok
Unlocking-Fail
Couldn´t unlock
Please add your account in MIUI´s Settings > Developers option > Mi Unlock status
This way doesnt work.
I try by fastboot and cmd commands
Fastboot devices
Ok is connected and recognized
fastboot oem device-info
...
time 0.002s
Failed (remote: Unknown command)
fastboot oem unlock
...
time 18.455s
FAILED (Remote: GetVar Variable Not Found)
(Smartphone disconect and rebboy on recovery mode)
And well...I dont know what to do now.

It won't unlock because your device is already unlocked. You need to flash stock rom from custom recovery. Install custom recovery via adb. when you go back to stock rom device will be oem locked again. Also original account that was used to oem unlock device may be required that is why it might be failing.
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919 (useful software here)
After flashing stock rom In fastboot try
Linux: adb fastboot-linux oem lock
OSX: adb fastboot-mac oem lock
Windows: adb fastboot-windows.exe oem lock

Help with root for Alldocube M5X Pro

I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.

After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.