Database Develop

Unbrick ASUS ZENFONE GO (ZB452KG)

Hi!
First i want to apologize for my english and if i made a mistake posting a new thread.
I own an ASUS Zenfone GO (ZB452KG) and i tried to root it, now it's bricked it.
The phone it opens and get stuck on the bootloader. The device is seen by fastboot, but i can't flash anything, it get stuck on writting...
The original firmware for device don't contain recovery.img, only boot.img, any suggestion to flash a recovery to use adb sideload to unbrick my phone?
{
"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"
}

anyone?

up

Hello , see here for your Problem ;
https://boycracked.com/tag/unbrick-asus-zenfone-go-zc500tg/?_e_pi_=7,PAGE_ID10,9943662066
If you still wanna root then , see here
http://forum.xda-developers.com/android/help/asus-zenfone-zc500tg-root-request-t3282861

try this
arahmatharh.blogspot. /2016/09/unbrick-asus-zenfone-go-x014d-bootloop.html
completly this space .com

thank you for your help, but my model is an MSM device, not a processor powerd by intel

Search guides by chipset here https://boycracked.com/flashing/
Sent from my Redmi Note 2 using Tapatalk

Asus ZB452KG on Qualcomm HS-USB QDLoader 9008
Does anyone know if this phone can be revived through QPST Software, is powered by a MSM8212 Snapdragon 200, i searched the raw firmware for this phone, but no success.

asus zenfone go x014d can't enter to recovery mode
hello, anyone who can help me,
i use asus zenfone go x014d, i try to flash twrp recovery via rashr aplication from playstore, and then my phone can't enter to twrp or stock recovery again, only asus logo that shown,
but my phon still can booting to OS normaly
i have try to flash my recovery with adb tool and put command "adb devices" it show my device,
boot i can't flash my phone with adb because i never get to enter recovery, fastboot, or bootloader mode, because it always only asus logo that shown
please help me

Sorry for the thread bumping, but I was wondering if it would be possible to root this device (ZB452KG) at the moment. I found ASUS official firmware in case of brick, but I don't know if it would be useful: https://www.asus.com/support/Download/39/2/0/13/QE1YCzvNxiwct6Y7/32/
I have not found any ROM for the devide, but it would be possible to adapt some of the Zenfone 2 to this one?
Thanks in advance!

I have the same problem and still not ok until now.

Friend I'm with the same problem and with the same android device, somehow managed to solve the problem ..? If by chance you can help me..?

Marcos Andrebrbrbr said:
Friend I'm with the same problem and with the same android device, somehow managed to solve the problem ..? If by chance you can help me..?
Click to expand...
Click to collapse
here fixed problem
https://arahmatharh.blogspot.co.id/2016/09/unbrick-asus-zenfone-go-x014d-bootloop.html?m=1
or pm me

Failed
arahmath2010 said:
arahmatharh.blogspot. /2016/09/unbrick-asus-zenfone-go-x014d-bootloop.html
completly this space .com
Click to expand...
Click to collapse
i try to follow steps on that site, but my phone getting worse, before i try those steps i still can see the battery meter while charging, but after follow those steps my phone really dead.

Just download it's latest firmware from ASUS official web, put that zip file to sd card and install it from recovery mode. It's works well without pc.

Need urgent help! Didn't OEM unlock in Dev and now stuck!!

Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"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"
}

try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.

To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.

infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running

bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha

Stuck in the "ALL-FAILED" screen, when re-booting

Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"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 mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:

Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!

Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!

[GUIDE] Hardest Brick Huawei P9 lite!! VNS-L21 - No Recovery, No Fastboot, No SD

Hey Devs!
i did brick while downgrading from custom rom and lockedup bootloader..
Then.
Full dead Huawei p9 lite vns-l21! No Fastboot, No Recovery, No SD card dload mode!!!
Only Detected via testpoint on PC!!
Tried a lot of way not worked at last! found the right Board Firmware for VNS-L21!
Flashed VNS-L21 Board Firmware on testpoint mode via IDT! Then Got Alive
:laugh::fingers-crossed:Now Get Ready! >
1. Download These Files
**Firmware VNS-L21(P9 lite)(Freee!! :victory
**IDT Image Download Tool (for flashing)
*Huawei Testpoint 1 Driver
*P9 lite Update(for sdcard update )
Operation Process>
1. Get Your all file prepared.
2. Get Your phone to PC via testpoint 1 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"
}
3. start IDT with Run as administrator.:good:
set Image XML file (extract Board Fw, and find HL2VENUSMAA001027_Download) ..
4. Tap start download. :fingers-crossed: if your phone in testpoint 1 mode.
it will start Processing..(keep patient )
Code:
20200109-21:49:40 usb1:Start downloading with VCom!
20200109-21:49:40 usb1:Load DownLoadBoot Version 2.0.0.9
20200109-21:49:41 usb1:eek:pening COM5 Success
20200109-21:49:43 usb1:download mode enter:31
20200109-21:49:43 usb1:Downloading xloader begin.
20200109-21:49:43 usb1:Writing xloader...
20200109-21:49:43 usb1:Write delay = 3000 ms.
20200109-21:49:46 usb1:Download xloader end.
20200109-21:49:46 usb1:download mode enter:255
20200109-21:49:46 usb1:Downloading fastboot begin.
20200109-21:49:52 usb1:Writing fastboot...
20200109-21:49:52 usb1:Write delay = 3000 ms.
20200109-21:49:56 usb1:Download fastboot end.
20200109-21:49:56 usb1:VCom download successfully.
20200109-21:51:30 usb1:Continue downloading with Fastboot!
wait for the progressbar DONE to PASS. it would take 10 Minitues. and after Pass. your phone will boot with an old firmware..!(wait to startfor first time)! :laugh::fingers-crossed:
Here you go>>
*** Now Update new update from SDcard ***:fingers-crossed:
:laugh::laugh:

How to run testpoint mode?
I installed rollback on emui 5 and system,recovery,erecovery not work.
While running of phone i started fastboot&rescue mode, hisuite not work with vns-l21. I had ftr locked and i unlocked frp with dc-phoenix and I unlocked bootloader and I can not start now fastboot&rescue mode. And now my phone is bricked.
I found thia post and I think that this can help my. I can try.

Edit:
I installed rollback on emui 4
I sorry I didn't load the picture before
I shoule connect plate with place as red line on the picture? While runnig phone?

Hi, I've registered to say thanks, this saved my phone. BTW, after flashing board software using IDT phone is unlocked in some weird way, you can adb root and fastboot flash orginal images, i had even DD twrp on phone but it dosent work well, but twrp showed up , some devs could look at that, maybe there is a way to not pay for bootloader code

Question I locked the bootloader by misstake

Hello, what I did was the following:
1. signed on a new phone with account A, waited a week and unlocked the bootloader
2. signed on the same phone with account B
3. flashed fastboot rom on the device with mi flash tool, but forgot to uncheck the " lock the bootloader"
4. the phone is not starting - i can only get the recovery and the fastboot mode.
5. mi flash tool wont let me flash to locked device . Mi flash tool2 makes me go into Mi assistant mode, starts the instalation process but failes after a few mins ( on the pc i reach ~ 700% but on the phone the bar is on 4.99 or 52.78 % )
6. Xiaomi ADB/Fastboot Tools doesnt want to flash as the device is locked and if i try the OEM UNLOCK button i get "FAILED (status read failed (Too many links))"
7. If I try to unlock the bootloader again and I log account B i get message that i need to log on the phone and wait for a week
If i log accont A i get this :
{
"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"
}
Any Idea how to fix it
Thanks in advance, and sorry if this is the wrong place for this question

As far as I know, the only way is to ask after-sale for help.

ddspj said:
As far as I know, the only way is to ask after-sale for help.
Click to expand...
Click to collapse
They might have more underlying tools to unlock and flash your phone.

fastboot flashing unlock
for most of aosp rom this is the command. but i'm not sure that works on miui. i found a java tool that maybe can help you. https://miui.blog/any-devices/xiaomi-adb-fastboot-tools-one-utility/ i have used to debrand my phone without unlock it

I had to send it to a friend of mine who was able to install chaina rom, using EDL mode, but now, for some reason the IMEI's are gone. I can not add mi account, and for that reason I can't unlock the bootloader, right now I am battaling with the IMEI restoration ( i have the original imei's on the phone case) I am trying to use modem_meta_tool, but with no suxcess . I can't get my phone connected
Long story short, EDL mode was needed to get out of my original situation

seem you have lost imei cause you have installed china rom. or a rom incompatible with your region. try install global rom via edl. but if you lost imei, restore it is not simply... you can try to enter into engineering mode. i'm not sure but there's a function to change imei. but not working for all mtk processors