i have zenfone 4 A400CG(kitkat) always display error facebook, system ui, youtube etc. now i flash with same rom.
on adb folder i type in cmd : fastboot flash boot boot.img(success) but when i type fastboot flash fasboot fastboot.img
"Failed (remote : flash_cmds error !" can u help me ?
flash cmds error solve problem, now i flash error : "fail: no enought DATA space,please free 998 MB at least"
i try flash raw file in SD Download, after that stuck Asus logo. help me...
Seems like I somewhat bricked my brand new A2, trying to root it – see my post in another thread.
Being careless, I used a boot image from a different version ROM. While I got the device to boot again, WLAN doesn’t work anymore. Furthermore, system updates via Android’s settings fail.
Now, on miui.com, there is a page with the latest stable ROM for download. Also there is a flashing guide. However, it looks like the flashing guide is for turning the Mi 6X into an A2: It mentions MIUI update mechanisms that are not available on stock Android (naturally). How can I install the downloaded ROM on the A2? Can I simply flash all the included image files to the respective partitions manually?
I'm facing the "same problem" can't boot at all.
I think the easiest way is to restore in TWRP some working backup with Magisk fully functional.
Cagixxx said:
I'm facing the "same problem" can't boot at all.
Click to expand...
Click to collapse
How did that happen?
I think the easiest way is to restore in TWRP some working backup with Magisk fully functional.
Click to expand...
Click to collapse
AFAIK there is no TWRP for the A2/6X. Also, I do not want to install ROMs from unofficial sources.
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
I did run the script, see my post in the Magisk forum. To avoid error messages, the trick is to also do fastboot flashing unlock_critical.
Furthermore, as documented in that post, I managed to install the boot.img patched by Magisk. But: To boot into Android, the boot loader needs to remain unlocked. Otherwise I get an error message that the installation cannot be trusted. For security reasons, using a production device with an unlocked boot loader is a very bad idea!.
Update: Looks like I bricked the rooted device by disabling OEM unlock in the settings plus locking the boot loader. It’s documented in that other thread.
Any idea how to fix the A2 if the boot loader is locked and it doesn’t boot into Android?
When I try to enter Recovery by pressing power plus volume-up, I also just get the message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
I tried all kinds of button combinations, such as pressing only volume-up on reboot, or pressing volume-down plus volume-up, or pressing power plus both volume keys. Always I get the above message. I can enter Fastboot though, by pressing power plus volume-down on start.
feklee said:
I did run the script, see my post in the Magisk forum. To avoid error messages, the trick is to also do fastboot flashing unlock_critical.
Furthermore, as documented in that post, I managed to install the boot.img patched by Magisk. But: To boot into Android, the boot loader needs to remain unlocked. Otherwise I get an error message that the installation cannot be trusted. For security reasons, using a production device with an unlocked boot loader is a very bad idea!.
Update: Looks like I bricked the rooted device by disabling OEM unlock in the settings plus locking the boot loader. It’s documented in that other thread.
Any idea how to fix the A2 if the boot loader is locked and it doesn’t boot into Android?
When I try to enter Recovery by pressing power plus volume-up, I also just get the message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
I tried all kinds of button combinations, such as pressing only volume-up on reboot, or pressing volume-down plus volume-up, or pressing power plus both volume keys. Always I get the above message. I can enter Fastboot though, by pressing power plus volume-down on start.
Click to expand...
Click to collapse
Your tried copy in the ADB folder the images ROM downloaded, in CMD "fastboot flash boot_a boot.img" "fastboot flash boot_b boot.img" "fastboot flash system system.img" when flash end "fastboot reboot" in screen of phone follow screen indications for Factory Reset.
My english is very bad, sorry.
tzadkiel2 said:
"fastboot flash boot_a boot.img"
Click to expand...
Click to collapse
Thanks for the suggestion, but I can’t flash because my A2 is locked:
$ fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
Sending 'boot_a' (28632 KB)...
OKAY [ 1.264s]
Writing 'boot_a'...
FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.271s
And I can’t unlock the device because OEM unlocking is disabled in the Android developer settings:
$ fastboot oem unlock
FAILED (remote: Flashing Unlock is not allowed
)
Finished. Total time: 0.001s
And I can’t enable unlocking because Android doesn’t boot.
What is used, Linux???? I used Windows
Linux I do not use it for this, sudo/su??? $ # this is what should appear if I remember correctly
it has worked for me as indicated and I have had it in a very similar way to yours even though I had already unlocked bootloader
P.d. my english is very basic I have to help the translator I only speak expañol
tzadkiel2 said:
What is used, Linux?
Click to expand...
Click to collapse
Yes.
Linux I do not use it for this, sudo/su?
Click to expand...
Click to collapse
sudo/su are not needed if permissions are set up correctly.
even though I had already unlocked bootloader
Click to expand...
Click to collapse
Having an unlocked device is a huge difference. With an unlocked device, I know how to flash it successfully.
My device, however, is OEM locked. This is the problem!
The next thing that I tried is booting into EDL mode from fastboot: $ fastboot reboot emergency
But this does not work either. Briefly the screen flashes with a message, before it tries to boot Android which doesn’t work. I had to video record the reboot process to be able to read the message. It says: “Your device software can’tbe checked for corruption.Please lock the bootloader.” [SIC]
Sadly, this is a bogus error message. I wish it was true and the bootloader was not locked.
P.d. my english is very basic I have to help the translator I only speak expañol
Click to expand...
Click to collapse
De nada. Puedo entender. (but please don’t start speaking in Spanish – mine is super basic )
I do not even remember when it was the last time I used Debian; so I remember almost nothing about Linux; but you should have unlocked the bootloader first to try what you're saying, right?; I seem to remember that there are two rom to download here, use the one of MIUI or the last one, it will not be for an antirollback
-------------------------
Yo pude instalar TWRP pero ahí me quedé ya que ni recuperaba Backup con Restore (System no se podía montar Invalid Argument) al instalar Magisk no iniciaba el Sistema (No System OS) por OTG solo discos duros (HDD) y no había manera así que tuve que deshacer todo lo hecho, y me bastó con lo que te he indicado.
No recuerdo como se abren las carpetas en Linux, pero me parece recordar que al abrir el directorio queda en #
When I try to flash system.img it give an error: cannot load "system.img".
webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
Cagixxx said:
When I try to flash system.img it give an error: cannot load "system.img".
Click to expand...
Click to collapse
And did u try to start up the phone ?
webmasterone said:
And did u try to start up the phone ?
Click to expand...
Click to collapse
Phone boot to recovery (twrp).
I wipe system partition via TWRP. Now the only way is to flash a ROM in recovery or restore from a complete backup.
Success! I was able to flash a clean install on my A2 by using the test point method, which required opening the device. How I proceeded is documented in my thread: Which test points to short to flash locked device?
There is no other way to force test point or download mode without open the phone? xD
EDIT: I found cable to enter EDL mode. "Deep Flash Cable Repair Tool For Xiaomi"
webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
I'm experiencing same problem and i knew about what you wrote but for most of fastboot commands i get " remote: flashing is not allowed for Critical Partition " message
EDIT:
Solved
All tho phone show message bootloader is unlocked it wasn't so command " fastboot flashing unlock_critical " do the trick
HUGE thanks to you. I was stuck in a bootloop and I tried many things until this saved me. Again, thanks A LOT!!
webmasterone said:
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Click to expand...
Click to collapse
webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
thank you so much! you save me
---------- Post added at 06:43 AM ---------- Previous post was at 05:44 AM ----------
I have received some errors of: "remote: "flashing is not allowed for Critical Partition" but the system has gone up normal. its okaY?
i have the same problem...but what next ?
How i can return in stock ?
Thanks
webmasterone said:
i'de the same problem
i solved downloadind the official rom (A2 global) from http://en.miui.com/download-353.html (at the moment jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz)
than i rebooted into bootloadr
adb reboot bootloader
and then manually flashed all "images" foler files (copying from script flash all bat), this because some img flash file went in error and the script (if launched automatically) stop working at the first error
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr
fastboot reboot
Now i've bootloader unlocked but NOT rooted
i wait to find available e secure and easy to root way for my A2
Click to expand...
Click to collapse
Thank you for the guide there are .bat files I think it would be easier to than running each one but newbie here
Thankfully you saved my device tho
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase system
fastboot erase modem
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash dsp dspso.bin
fastboot flash parameter parameter.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img (if you failed, don't worry, try this step again and again.)
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
Download download necessary files https://drive.google.com/drive/folde...Ym?usp=sharing
good luck.
Click to expand...
Click to collapse
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
nabbed said:
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
Click to expand...
Click to collapse
modified link: https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
Hello I have this problem with my realme X2 Pro
I wanted to install TWRP on my phone using ADB and Fastboot after unlocking with success my bootloader The problem Is I first intalled with success TWRP BUT the touch was not working so I decieded to try a newer version but now this error apears
Sending 'recovery' (98304 KB) OKAY [ 2.354s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
I Tried to do adb push twrp-3.4.0-0-RMX1931-mauronofrio.img /dev/block/bootdevice/by-name/recovery but i did not work It got me this error
adb: error: failed to get feature set: no devices/emulators found
If anyone could help me it would very apreciated
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Uqbar said:
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Farchyk said:
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Click to expand...
Click to collapse
Are you really really sure the twrp image is the right size?
Mauronofrio's one is exactly 81920 KB, not 98304 KB.
Also the official TWRP has the same size, AFAIK.
I would re-download it and maybe checksum it.
Download and extract model specific firmware zip to the fastboot folder.
Enter fastboot by turning the device off and then turning it on using pwr+vol down for few seconds.
If it doesn't turnoff, then let the battery drain out on its own and then retry to enter fastboot.
Execute each of the below commands in the CMD window, one at a time. If you get any errors after executing any of these commands, then don’t leave the process mid-way. Rather continue executing the rest of the commands and then check the results.
Fastboot commandsfastboot erase boot_ab
fastboot flash xbl_ab xbl.elf
fastboot flash xbl_config_ab xbl_config.elf
fastboot flash abl_ab abl.elf
fastboot flash aop_ab aop.mbn
fastboot flash tz_ab tz.mbn
fastboot flash featenabler_ab featenabler.mbn
fastboot flash hyp_ab hypvm.mbn
fastboot flash modem_ab NON-HLOS.bin
fastboot flash bluetooth_ab BTFM.bin
fastboot flash dsp_ab dspso.bin
fastboot flash keymaster_ab km41.mbn
fastboot flash devcfg_ab devcfg.mbn
fastboot flash qupfw_ab qupv3fw.elf
fastboot flash uefisecapp_ab uefi_sec.mbn
fastboot erase imagefv_ab
fastboot flash imagefv_ab imagefv.elf
fastboot flash shrm_ab shrm.elf
fastboot flash multiimgoem_ab multi_image.mbn
fastboot flash cpucp_ab cpucp.elf
fastboot flash qweslicstore_ab qweslicstore.bin
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash rescue rescue.img
fastboot flash storsec storsec.mbn
fastboot flash spunvm spunvm.bin
fastboot flash rtice rtice.mbn
fastboot flash vendor_boot_ab vendor_boot.img
fastboot flash vm-bootsys_ab vm-bootsys.img
fastboot flash super super.img
fastboot flash cust cust.img
fastboot flash dtbo_ab dtbo.img
fastboot flash vbmeta_ab vbmeta.img
fastboot flash vbmeta_system_ab vbmeta_system.img
fastboot erase metadata
fastboot flash metadata metadata.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot flash boot_ab boot.img
fastboot flash logo logo.img
fastboot set_active a
fastboot reboot
If the device is still boot looping, fastboot -w (as the final option) and repeat all the above commands step-by-step.