Database Users

Zenfone 5 boot loop NEED HELP

Dear value members i need some help with my Zenfone 5 AC501CG it stuck on boot
i tried many methods but all of it doesn't work
i can boot in fast boot with no problem but the bootloader is locked
1- i tried sideload via adb for kitkat nad lolipop it fail to complete as E: can't mount data ... recovery etc
2- i tried via xFSTK-Downloader tool and flashed dnx and other files it complete but doesn't accept ant rooms
3- i tried via ASUS Flash Tool and flash raw files a message say " oem partion command failed retval = -1
4- i tried to unlock bootloader to flash TWRP but all files excute some order and when sending dnx and iwfi fail of command and message say unlocked success but in fact the bootloader stil locked and i can't flash TWRP
here some photo
how can i pass this problem i had 4 days searching without any progress
{
"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"
}

have you checked the partition.tbl file? there's some editing as i have red a couple of days ago. it's a known error on some raw firmwares. but honestly i haven't even started using Zenfone yet coz I'm still stuck at boot 😂
and im guessing you're on fake Chinese firmware too is that right? those are firmware versions 2.99 with fake serial. reference was your screenshots uploaded. but correct me if I'm wrong

If u need to unlock bootloader
use auto unlock go to this thread http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263

gradd said:
have you checked the partition.tbl file? there's some editing as i have red a couple of days ago. it's a known error on some raw firmwares. but honestly i haven't even started using Zenfone yet coz I'm still stuck at boot 😂
and im guessing you're on fake Chinese firmware too is that right? those are firmware versions 2.99 with fake serial. reference was your screenshots uploaded. but correct me if I'm wrong
Click to expand...
Click to collapse
i don't think so
i update the phone many times via OTA and i checked imei via imei info and all correct and last room was kitkat 2.22.40 as i remember

alvinhaw said:
If u need to unlock bootloader
use auto unlock go to this thread http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
Click to expand...
Click to collapse
i face this error and unlocking by other ways other error see pictures

The main problem in flashing partion.tpl file
i got this error fron asus flash tool or if i used fastboot flash

somaare said:
i face this error and unlocking by other ways other error see pictures
Click to expand...
Click to collapse
study the thread
this is the easiest method
there is 2 build
i use build 3 successfuly unlocked
i use auto unlock cuz I'm not sure
what model it is...
u can manually fastboot flash it
using Advance User Download
follow the instruction
anyway I'm new to zenfone
never buy zenfone again!

alvinhaw said:
study the thread
this is the easiest method
there is 2 build
i use build 3 successfuly unlocked
i use auto unlock cuz I'm not sure
what model it is...
u can manually fastboot flash it
using Advance User Download
follow the instruction
anyway I'm new to zenfone
never buy zenfone again!
Click to expand...
Click to collapse
none of the 2 build success to unlock the boatloader
the same error when sending dnx and iwfi : command fail invalid angrument

i think u need to check DNX & ifwi
with ur stock rom, cuz u mention
ur device is A501CG
U try to get this 2 file from stock rom
n flash via fastboot see still error not...if not then Google search for related A501CG unlock bootloader

[Q] Bricked - after TWRP restore - unsuccessful

It is the same problem as written here : https://forum.xda-developers.com/p8...awei-p8-lite-2017-pra-lx1-brick-trwp-t3660664
I've followed every steps, but my phone is still bricked.
My build version is (I guess?) PRA-LX1C432B100
I tried several firmware builds to restore on, but when I try to install it (by pushing POWER / VOL - / VOL +) :
- PRA-LX1C530B130 : firmware versions mismatch
- PRA-LX1C33xxxx : can't install, I don't remember error message but surely the same as the above one.
- PRA-LX1C432B128 : "Installing update" at 5% then "Software install failed" with sub message "Get help from http://www.emui.com/emotiondownload?mod=restore"
I followed the rooting method from a french website that was for build PRA-LX1C432B100 but I can't find this firmware anywhere.
Can someone have the link ? Tried with Firmware Finder.. Now i'm downloading from needrom but still don't know if it's for the good build version...
When the phone boots, it displays :
- HW Logo
- Warning about the BL
- HW logo
- blank
- HW logo
- Warning about the BL
- erestore
When trying to download and reboot from erestore, it says "Getting package info failed" and thus, can't download.
----
TWRP
I also tried to flash PRA-LX1C530B130 update.zip, but I get the exact same thing as here : https://forum.xda-developers.com/attachment.php?attachmentid=4008385&d=1484772172
---
Any way to unbrick this d*mn thing ?
I need help, thank you.

Your phone is locked. Try the unlocking by huawei unlockcode.

Thank you for this fast answer,
though, where do I enter the code(s) ?
I went to https://tools.texby.com/unlock-codes/huawei/ to obtain my code, is that correct ?
I entered fastboot, no devices found with "huawei code writer"
Same with recovery mode and eRecovery :
{
"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"
}

Do this command in fastbootmode by adb:
fastboot oem unlock 1234567...... (your unlock code from Huawei.

Oh okay, but i'm already unlocked.
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Click to expand...
Click to collapse

Ok., then flash the stock recovery again and make a factoryreset.

I can't find the stock recovery on internet nor on Firmware Finder. Do you know where I can find PRA-LX1C432B100 ?
I flashed many times on differents build versions those files :
recovery.img
boot.img
system.img
cust.img
Do I need to only flash the stock recovery (if I can find it..) to make everything else work ?
if I have no stock system nor stock boot, will it boot ?
And by "stock" I mean "stock for my device" because I've tried many stock images that end up in erecovery, even after a factory reset in the stock recovery.
-- EDIT --
With the mobile app, it says that the PRA-LX1C432B100 has been removed from the server.

Flash TWRP and see if it starts there.

ChinHon said:
Flash TWRP and see if it starts there.
Click to expand...
Click to collapse
Flashed TWRP.
Can still not boot on system (it's going on eRecovery) but sure I can boot in TWRP.

You have removed the usb cable during the reboot?

I have bricked my phone, can't install rom from erecovery becouse doesn't retrive update from server. What can I do?
I'm disperate can you help me?

ChinHon said:
You have removed the usb cable during the reboot?
Click to expand...
Click to collapse
Yes I did

Sw0ut said:
Yes I did
Click to expand...
Click to collapse
Ah, but I did it again and it worked.
Go TWRP and I can boot. I can indeed see my build version which is PRA-LX1C432B164.
I can boot, so i'm gonna follow the tutorial again.
Thanks.

Sw0ut said:
Ah, but I did it again and it worked.
Go TWRP and I can boot. I can indeed see my build version which is PRA-LX1C432B164.
I can boot, so i'm gonna follow the tutorial again.
Thanks.
Click to expand...
Click to collapse
:good:

Lenovo P2 Root Tool

Lenovo P2 Root Tool
{
"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"
}
Download
Instructions
Bootloader Unlock
1. Open settings in your phone
2. Scroll down to the last open about phone
3. Find the option build number, tap on it continuously until you see a toast message "You are now a developer"
4. Now go back and open the developer options, Find the option usb debugging & enable it
5. Now enable OEM-Unlock , you need to accept one licence agreement by lenovo, In next page you need to login/signup with
lenovo id
6. After submitting request , you need to wait 14 days for unlocking OEM (Bootloader)
Warranty
After subbmitting oem-unlock request also your device will have warranty officially
After Clicking on OEM-Unlock Button in my tool, Your device will losse warranty officially
But in Lenovo website it shows your device still in warranty for 365 days from date of purchasing this mobile
Tool Setup
1. Download my Root Tool into your pc
2. No need to install this software, Just double click on it like opening a file in pc
3. Now click on drivers to install lenovo usb drivers in your pc
OEM unlock after 14 days
1. Copy all data in your mobile to pc or to any other mobile, because now all the data on phone gonna erase including apps ,
photos
2. Connect your Mobile to pc, And click on oem unlock
3. Now your phone will automatically boots into fastboot mode
4. Your device OEM will gonna unlock now (No need to do anything , sit back and relax !)
5. After unlocking oem successfully
6. you will get a message that oem unlocked successfully in PC
7. Your device will reboot from fastboot mode to normal mode
8. Login with your google account which signed into device previously doing these process
TWRP & Magisk Install
1. As we know mobile reseted (erased) after reset, so again enable developer options and usb debugging
2. Connect mobile to PC, Launch P2 Root Tool
3. Click on TWRP install button to install twrp in your phone
4. Now your phone will again boot into fastboot mode to install twrp, after installing twrp, now phone boots to twrp recovery
5. Now click on root in pc and choose root provider (supersu or magisk) just click on magisk
6. Now magisk.zip will sends to phone, click on install in twrp menu, and choose magisk.zip and swipe to confirm install
7. It may take a minute to install magisk in your phone, after installation click on reboot system
Features
Reboot Manager - You can reboot device to different modes (Normal, Recovery, Bootloader)
OEM-Unlock - Unlock P2's bootloader with one click (Need to wait 14 days from date of requesting oem unlock)
Root Manager - Can root device either SuperSu , Magisk
Drivers - You can install Lenovo USB drivers
Stock Images - You can install stock Boot or Recovery images to pc
TWRP Install - You can install twrp in your phone with one click
Screenshots
Still Have doubts ??
You can reach me via telegram chat
Watch a tutorial video on Rooting P2 with this tool in my youtube channel
Like my work offer me a coffee, no matter it may be a small cup or large cup
PayTm Donation Link
PayPal Donation Link
XDA:DevDB Information
Lenovo P2 Root Tool, Tool/Utility for the Lenovo P2
Contributors
Varun Sai
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2018-07-07
Created 2018-06-07
Last Updated 2018-12-25

Reserved

Reserved

good job bro ?

Excellent work bro

tank you

perfect tool !

Another grateful user :good:

OEM-Unlock will delete my files on the phone?

haqy said:
OEM-Unlock will delete my files on the phone?
Click to expand...
Click to collapse
no it won't do that
but when you flash the TWRP recovery you should definitely have the files backed up.

[/COLOR]
haqy said:
OEM-Unlock will delete my files on the phone?
Click to expand...
Click to collapse
Yes
Varun Sai said:
OEM unlock after 14 days
1. Copy all data in your mobile to pc or to any other mobile, because now all the data on phone gonna erase including apps ,
photos
Click to expand...
Click to collapse

Tab A7 (SM-T500) - Cannot boot custom kernel

Hi everyone, as the title already says, I am having issues booting a custom kernel on my SM-T500. I have been able to flash agreenbhm's TWRP and boot that just fine, but that is using the prebuilt kernel. When I try to boot a custom kernel, OEM locking gets enabled out of nowhere and I have to reflash the stock ROM in order to be able to use the tab. I initially tried booting a WIP close-to-mainline kernel, so I assumed it's just an issue of the bootloader not liking the mainline kernel, but then I tried to flash a custom compiled downstream kernel and I got the same issue. Has anyone else ever had such an issue, even if it's on another device? Were you able to work around it? If yes, how? Thanks in advance for any answers.

LegoLivesMatter said:
Hi everyone, as the title already says, I am having issues booting a custom kernel on my SM-T500. I have been able to flash agreenbhm's TWRP and boot that just fine, but that is using the prebuilt kernel. When I try to boot a custom kernel, OEM locking gets enabled out of nowhere and I have to reflash the stock ROM in order to be able to use the tab. I initially tried booting a WIP close-to-mainline kernel, so I assumed it's just an issue of the bootloader not liking the mainline kernel, but then I tried to flash a custom compiled downstream kernel and I got the same issue. Has anyone else ever had such an issue, even if it's on another device? Were you able to work around it? If yes, how? Thanks in advance for any answers.
Click to expand...
Click to collapse
What do you mean by "OEM locking"? Do you mean the FRP lock that you disable by enabling OEM mode in Developer options? That only requires you to enter the google account login and password to finish booting.

lewmur said:
What do you mean by "OEM locking"? Do you mean the FRP lock that you disable by enabling OEM mode in Developer options? That only requires you to enter the google account login and password to finish booting.
Click to expand...
Click to collapse
OEM locking is indeed what I mean. Google Account is not a problem because I never log into it in the first place, and when I open up developer options OEM unlocking is enabled and grayed out with a "Bootloader is already unlocked" message.

LegoLivesMatter said:
OEM locking is indeed what I mean. Google Account is not a problem because I never log into it in the first place, and when I open up developer options OEM unlocking is enabled and grayed out with a "Bootloader is already unlocked" message.
Click to expand...
Click to collapse
If you don't have a google account setup on the tablet, the FRP is irrelevant. So what's the problem? BTW, the FRP lock and the bootloader lock are two entirely different things. One has nothing to do with the other. The FRP lock has been around long before Samsung started locking the bootloader on non-carrier tablets.

The problem is that, even when the bootloader is unlocked, the tablet simply won't accept a custom kernel. If you want to know why I believe OEM lock is at fault here, first take a look at the download mode screen **before** flashing a custom kernel:
{
"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"
}
Then, after flashing a custom kernel:
(sorry for the below average picture quality, especially on the last one)
After flashing the custom kernel, "Current Binary" goes from "Samsung Official" to "Custom", and **OEM lock** goes from Off to **On**, and every time I restart the tablet it will go straight to download mode until I reflash the stock firmware.

LegoLivesMatter said:
The problem is that, even when the bootloader is unlocked, the tablet simply won't accept a custom kernel. If you want to know why I believe OEM lock is at fault here, first take a look at the download mode screen **before** flashing a custom kernel:
View attachment 5371623
Then, after flashing a custom kernel:
View attachment 5371625
(sorry for the below average picture quality, especially on the last one)
After flashing the custom kernel, "Current Binary" goes from "Samsung Official" to "Custom", and **OEM lock** goes from Off to **On**, and every time I restart the tablet it will go straight to download mode until I reflash the stock firmware.
Click to expand...
Click to collapse
If you ever get the tablet to boot, and look in Develper options, you find the setting for OEM is enabled and greyed out so you can't change it. IOW, OEM lock is ON and your custom ROM has no Factory Reset Protection. If someone steels the tablet, they can get past the lock screen simply by doing a factory reset. There is some other reason you are boot looping.

The 'qualcomm_secureboot' enabled might be the actual problem.

I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM. I copied the following from the thread on installing LOS 18.1.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.

lewmur said:
I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM. I copied the following from the thread on installing LOS 18.1.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Click to expand...
Click to collapse
did u ever solve this

xAriana said:
did u ever solve this
Click to expand...
Click to collapse
I'm not the one who had the problem. I've had LOS 18.1 installed for a long time.

lewmur said:
I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM. I copied the following from the thread on installing LOS 18.1.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Click to expand...
Click to collapse
I don't know if that file is something you want to use... I recently flashed it and have been having a similar issue ever since... I can root the device and everything but after some time it will fail to boot out of nowhere and give me the "only official binaries may be flashed" error with the vbmeta file shown as the issue. And even after reflashing the stock firmware. It always shows that the device is custom in the settings/device status menu and won't do updates. No matter what I do I cannot get it to show device normal anymore... and once it shows that error the ONLY fix is to flash stock firmware. I can't reflash the disabled vbmeta or even a stock vbmeta on its own to the device. It has to be the full firmware. Period... I think that disabled vbmeta file has some sort of issue with it and it needs to be checked into. I know pretty much everything there is with samsung devices and I've never seen any device act this way until the day I flashed that vbmeta file...

I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM.
Click to expand...
Click to collapse
Thanks for mentioning that, judging by what's going on this very well could be the cause.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Click to expand...
Click to collapse
Can this be created manually with
Code:
avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
or do I have to download it from the LineageOS post?
did u ever solve this
Click to expand...
Click to collapse
Not yet.

Lenono TB-X606F to TB-X606FA

Hello, Having a Lenovo TB-X606F tablet, I purchased a Lenovo Smart Dock, but cannot get it to work with this tablet. Is it possible to flash the tablet in TB-X606FA so that the dock are finally recognized? I installed the Amazon Alexa apk - Show mode and Lenovo Smart Dock Firmware Updater but nothing recognized
Thank you

thekiller91 said:
Hello, Having a Lenovo TB-X606F tablet, I purchased a Lenovo Smart Dock, but cannot get it to work with this tablet. Is it possible to flash the tablet in TB-X606FA so that the dock are finally recognized? I installed the Amazon Alexa apk - Show mode and Lenovo Smart Dock Firmware Updater but nothing recognized
Thank you
Sébastien
Click to expand...
Click to collapse
There are probably missing kernel drivers ?
You could try loading the X606FA ROM using LMSA. Use the off-line rescue option.
No guarantees it will work. It's an experiment, so it might brick your device. If it fails, LMSA might be able to restore the X606F ROM.

Hello, with LMSA I could flash with firmware TB-X606FA_S300269_210602_BMP for example? the 2 tablets are identical in terms of hardware I do not see why this would brick I can not find how to do it in LMSA it suggests that the firmware TB-X606F_S300320_210716_BMP Thank you

{
"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"
}
Hello, I tried via LSMA now my tablet is running in a loop, I just manage to go to fastboot mode, what to do?
Thank

following that I tried to send the original boot.img by adb and here is what I have
following that I tried to send the original boot.img by adb and here is what I have

thekiller91 said:
Hello, I tried via LSMA now my tablet is running in a loop, I just manage to go to fastboot mode, what to do?
Code:
Your device has failed verification and may not work properly.
Please download boot image with correct signature or disable verified boot.
...
following that I tried to send the original boot.img by adb and here is what I have
Code:
fastboot flash boot boot.img
FAILED (remote: 'not allowed in locked state')
fastboot: eroor: Command failed
Click to expand...
Click to collapse
Have you unlocked your bootloader? To flash in fastboot, you have to unlock your bootloader first. If you didn't allow that in Settings before you started, then you'll need to reload your old ROM to do it.
The simplest thing to do is to rescue your tablet using LMSA. Make sure you are using the "manual selection" mode. Select you original tablet designation (TB-X606F). When Android boots:
enable developer settings
allow OEM unlock and USB debugging
unlock the bootloader
make sure you can load twrp (which tests that fastboot is working)
make sure adb is working in twrp (adb shell)
do a backup
Then you can start your experiment again.

Yahoo Mike said:
Have you unlocked your bootloader? To flash in fastboot, you have to unlock your bootloader first. If you didn't allow that in Settings before you started, then you'll need to reload your old ROM to do it.
The simplest thing to do is to rescue your tablet using LMSA. Make sure you are using the "manual selection" mode. Select you original tablet designation (TB-X606F). When Android boots:
enable developer settings
allow OEM unlock and USB debugging
unlock the bootloader
make sure you can load twrp (which tests that fastboot is working)
make sure adb is working in twrp (adb shell)
do a backup
Then you can start your experiment again.
Click to expand...
Click to collapse
I managed to recover the tablet with the stock rom and with LSMA, it detected the fastboot and restored the rom. On the other hand my smart dock remains incompatible with my tablet just because of a software, really bad on the part of lenovo! I try with LSMA in manual the FA model to see, I hope that it will not crash!

thekiller91 said:
I managed to recover the tablet with the stock rom and with LSMA, it detected the fastboot and restored the rom. On the other hand my smart dock remains incompatible with my tablet just because of a software, really bad on the part of lenovo! I try with LSMA in manual the FA model to see, I hope that it will not crash!
Click to expand...
Click to collapse
Hey, any success?