Database Develop

Please Guide How to Flash a New ROM (Stock) on ASUS ZENFONE 4 T00I

Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
Bootloader : Could never unlock. Tried the app but never success.
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
Final Status: No System on / No firmware on device at all. Can use Droidboot thats all.
Now please help me to give life to the device...
Thank you in advance.
C:\Zenfone>fastboot flash boot boot.img
sending 'boot' (8661 KB)...
OKAY [ 1.375s]
writing 'boot'...
OKAY [ 1.859s]
finished. total time: 3.234s
C:\Zenfone>fastboot flash fastboot droidboot.img
sending 'fastboot' (11253 KB)...
OKAY [ 1.578s]
writing 'fastboot'...
OKAY [ 2.156s]
finished. total time: 3.734s
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-9.9.9.0-user.zip
sending 'update' (825100 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
==================================================
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-7.4.4.0-user.zip
sending 'update' (837024 KB)...
OKAY [ 37.469s]
writing 'update'...
FAILED (remote: problem with creating ota update file!)
finished. total time: 37.578s
==================================================
AFT not detecting device and showing this error everytime I connect or disconnect device (in droidboot mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Maybe you can search this files on google :
1. 6.5.35 system.img.gz file
2. 6.5.35 boot.img file
3. 6.5.35 fastboot img file
Should be the same version, then flash it..

Ok, I will try that.
Although I wanted to know whats d fault and where did I go wrong on procedures? I could not unlock bootloader so will fastboot allow me to flash the mentioned firmware images?
Why AFT dint worked for me and. Lot of questions around.. I AINT NOOB FOR ANDROID but. Dis device does not hv anything similar to axnormal android.
Sorry for behaving noob.
Thnkyou for help

Help me please
the AFT i installed on my pc doesnt detect the raw file i have
i've spend two weeks to solve this still no luck
please give me some advice how do i fixed my zenfone 4 its stuck on ASUS LOGO
Fix it already but got a new problem
Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))

u guys can use this method
http://forum.xda-developers.com/zenfone-4/general/guide-how-to-flash-stock-rom-relock-t3302917

Device is LOCKED. Status Code: 2 and failed to validate system image

Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)

Have you fix it yet? I have the same problem....

b4toons said:
Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)
Click to expand...
Click to collapse
select option 4 ,format device and reflash rom

Hay !!
After you lock your bootloader then flash the Entire ROM and make sure after flashing use those two command
$ fastboot erase userdata
$ fastboot erase cache
then reboot
$ fastboot reboot

Hi, sorry for necroposting. Did you fix it?

Help with finding stock recovery

Hi,
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Code:
fastboot.exe oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot.exe oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.069s
fastboot.exe getvar vendorcountry
vendorcountry: optus/au
Finished. Total time: 0.007s
fastboot.exe oem get-build-number
(bootloader) :
OKAY [ 0.004s]
Finished. Total time: 0.007s
fastboot.exe oem oeminforead-System_Version
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed

greyjoy said:
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Click to expand...
Click to collapse
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery

zgfg said:
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery
Click to expand...
Click to collapse
No other errors that I can see when I run the oem commands at least, see screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

greyjoy said:
No other errors that I can see when I run the oem commands at least, see screenshot
Click to expand...
Click to collapse
This is all very strange. Even after custom ROM and/or brick it should know to answer on get-product-model or get-build-number.
Maybe only if some ... deleted all partitions by TWRP or so?!
Just one suggestion. Forget Platform tools and install to the PC very simple and small (only few MB) "Minimal ADB and Fastboot" package and execute from there (you don't need to type "fastboot.exe", just "fastboot" is enough)
Do you know at least, was it Android 6, 7 or 8. Almost certainly not 8, it would be CN, not AU. 6 only if stock was not updated from the beginning
From the TWRP version I would guess it was Nougat, i.e. EMUI 5.
In that case you can install generic/no-check version of Nougat stock recovery:
https://mega.nz/file/09k1wIST#IyMKcRwPq7llKEmnflOAQJSl2B4v8pmz6Myj_ZawxQs
You should also know was it L09 Single SIM or L19 Dual SIM
Searching for custs, Australia might be c636 or c183 but seems that c34 was Australia Optus
Find on FirmwareFinder or from:
https://pro-teammt.ru/firmware-database/?firmware_model=EVA-L09c34
"FullOTA-MF-PV" (only PV are suitable for DLOAD) firmware for e.g. EVA-L09c34, like EVA-L09c34b380 (pkg #93280 from 2017.08.15) and try simple DLOAD method
But if really all partitions were deleted, DLOAD would likely fail. You could try (with your c34, not c432 as in the guide) something like this:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7

General [VENDOR][EOL] Stock Vendor with No Oversharpening

So, you just got your new Redmi Note 10S and the software sucks. So you decided to flash a GSI, got it working and you still have one problem left, the video look oversharped and the colors might look weird. Well, this vendor will fix it.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what's new in this vendor?
A little bit debloated
And ofcourse, no oversharpening.
Anything else?
Nothing else, literally just that.
Download Link:
Google Drive
Requirements:
1. Unlocked bootloader.
2. A PC with fastboot tools.
3. Reading ability.
Flashing Process:
1. Reboot your phone into bootloader.
2. Check if fastboot detects your device.
3. Type fastboot reboot fastboot to reboot into fastbootd.
4. After that, type fastboot flash vendor path/to/vendor.img
5. That's it. Reboot and enjoy!
KEEP IN MIND
This vendor only has been tested on DotOS 5.1.3. If you possibly can, please try this on MIUI, and if it doesn't boot, report it to me. Thanks.
Now try watching video at 360p, and you might see a difference.

It failed:
target reported max download size of 134217728 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/8 (130795 KB)...
OKAY [ 2.928s]
writing 'vendor' 1/8...
FAILED (remote: This partition doesn't exist)
finished. total time: 2.933s
Any idea what happened?

It actually works with MIUI as well. However, color management seems to be disabled leaving the phone to oversaturate the colors at will.
EDIT 1: It's not just the color management that gets disabled. Changing the color temperature gets disabled, reading mode gets disabled as well. It seems like trying to solve one problem causes more.
EDIT 2: It could be solved by tweaking ro.vendor.mtk_pq_color mode. With this vendor, it's set to 1 which may be the reason why the phone is stuck in the "Saturated" mode.

EL66K said:
It failed:
target reported max download size of 134217728 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/8 (130795 KB)...
OKAY [ 2.928s]
writing 'vendor' 1/8...
FAILED (remote: This partition doesn't exist)
finished. total time: 2.933s
Any idea what happened?
Click to expand...
Click to collapse
you must flash it on fastbootd , using fastboot reboot fastboot or adb reboot fastboot. try to flast it again on every partition (a and b)

jacobpayag said:
It could be solved by tweaking ro.vendor.mtk_pq_color mode
Click to expand...
Click to collapse
How can i change this value? If i try edit build.prop on /vendor folder, this file erased and phone not boot again. Any try for restoring file from adb failed...

hey guys, this project is EOL. Please use my LiteE RN10S ROM instead, the ROM has no oversharpening while maintaining every display color related stuff.

J6idot said:
hey guys, this project is EOL. Please use my LiteE RN10S ROM instead, the ROM has no oversharpening while maintaining every display color related stuff.
Click to expand...
Click to collapse
Hey bro can you please provide device vendor (not .img)

General [TWRP] (Not works properly)[Camellia] [Camellian] [UNOFFICIAL] [BETA] TWRP 3.6.0_11 for Poco M3 Pro 5G & Redmi Note 10 5g

WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked.
Install ADB and Fastboot Drivers -->https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing FastBoot drivers:
if you encountered no file are copied then disable your anti virus and retry in Linux just type 'apt install fastboot' 'dnf install fastboot' 'pacman -S fastboot' based on your current linux distro
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN

Great! Is touch working on this?

great!!!!!

SalmanSH1 said:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked. Click here for a tutorial.
Install ADB and Fastboot Drivers from here (Select the latest) --> https://androidmtk.com/download-minimal-adb-and-fastboot-tool )
Install drivers for Camellian --> https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows (For Windows Only!)
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Click to expand...
Click to collapse
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com

up864 said:
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
Click to expand...
Click to collapse
i confirm, dont boot. i thik he didnt test before post

shi-no_tenshi said:
Great! Is touch working on this?
Click to expand...
Click to collapse
yes touch works
up864 said:
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
Click to expand...
Click to collapse
yes m3 Pro 5G
i'm not Developer

wetito said:
i confirm, dont boot. i thik he didnt test before post
Click to expand...
Click to collapse
do you tested ?
use xiaomi Fastboot tools ?

i edited 1st topic
i'll send Video of this Work

fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed

fastboot boot Twrp_-3.6.0_11_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
Not Booting Redmi Note 10 5G....
Please Fix

use xiaomi fastboot tools

SalmanSH1 said:
use xiaomi fastboot tools
Click to expand...
Click to collapse
Sir Twrp Not Booting On Redmi Note 10 5G

emhashmi said:
fastboot boot Twrp_-3.6.0_11_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
Not Booting Redmi Note 10 5G....
Please Fix
Click to expand...
Click to collapse
https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Use This ADB fastboot installer

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
< waiting for any device >
downloading 'boot.img'...
OKAY [ 0.957s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 9.357s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

emhashmi said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
< waiting for any device >
downloading 'boot.img'...
OKAY [ 0.957s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 9.357s
View attachment 5673465
Click to expand...
Click to collapse
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img

SalmanSH1 said:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked.
Install ADB and Fastboot Drivers -->https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing FastBoot drivers:
if you encountered no file are copied then disable your anti virus and retry in Linux just type 'apt install fastboot' 'dnf install fastboot' 'pacman -S fastboot' based on your current linux distro
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Click to expand...
Click to collapse
I got bootloop on MIUI 12.5.4 ID

This doesn't work
SalmanSH1 said:
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
Click to expand...
Click to collapse
I tried USB 3 and USB 2

SalmanSH1 said:
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
Click to expand...
Click to collapse
Already Change Usb And Change DATA Cable...But Doesn't work

SalmanSH1 said:
https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Use This ADB fastboot installer
Click to expand...
Click to collapse
i'm a linux user. my adb and fastboot driver are perfect

wetito said:
i'm a linux user. my adb and fastboot driver are perfect
Click to expand...
Click to collapse
I think he is trolling us. Or his phone is lucky one