Database Info

[Q] Rooting My Samsung Tab 2

I've read instruction's from the web on rooting my Samsung Galaxy Tap 2.
First, the instructions mention to allow USB debugging but I find no setting for this in my apps menu.
I was also instructed to put the device in download mode but the device got stuck at Downloading.... for around 15 minutes until I restarted by holding the volume up and power.
Any ideas what I'm doing wrong?
James

Usb debugging is in developer option- toggle the switch on.Scroll down. You will see usb debugging.
And how you try to root the phone? Using odin? Hit a thanks if I helped you!
Sent from my GT-I9100 using xda app-developers app

I failed to install the Samsung drivers.
The device is rooted now.
Now what?
Where do I find tools for the rooted device?
Where do I get custom roms?

You getting usb device not recognized error?You using desktop or laptop? And please mention the os. Try reconnecting the usb to other ports.windows 7 installs drivers automatically. I am not sure about mac. If its desktop try connecting to back usb ports. Try changing usb cables. There are lots of issues with usb cables and smartphones.no one knows what it is..
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------
If you want cm11. You can download it from www.get.cm from your phone and follow the imstructions..
Its the easiest way for rooting and installing custom roms. It automatically detects device, roots, install recovery and roms.. Most of them are stable too..
Sent from my GT-I9100 using xda app-developers app

I wasn't getting an error.
In Odin I clicked PDM and selected the auto root file.
When I would click Start nothing happened.
Finally, after installing the correct drivers for my device it worked fine.
I'm using Windows 8.1. on a desktop.
The device isn't a phone, it's a tablet.
Just not sure what tools will be helpful.
Also need to know haw to flash a combatable rom.

Ok.Cyanogen mod supports p3100. Hope yours is the same. Go to www.get.cm from your tablet. And download the apk file or switch into usb debugging. After that go to www.get.cm from your computer. Download the cm installer for pc. Open it. It will take a few minutes to setup upgrading and other process. When it asks to connect your tab or phone. Make sure you have a back up of all.Connect it in usb debugging mode. It will detect your device and download latest recovery, rom and system apps. After downloading everything.it asks for install. It automatically loads downloding mode. You don't even have to press volume, power and all stuffs. Actually just connect your tab and relax.:beer::beer: That's all....
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 05:15 AM ---------- Previous post was at 05:08 AM ----------
Or you could manually choose a rom. Check this http://forum.xda-developers.com/galaxy-tab-2/7-inch-development and choose one you want. Before that. You need to flash recovery if you are doing it manually. To flash recovery download rom manager from play store. It gets you the latest recovery. You can also make a backup of your current rom using that tool.
Sent from my GT-I9100 using xda app-developers app

Bricked and no internal_sd or fastboot -hlp plz..

Hello peoples
On my htc one s (s4) I did something pretty stupid, as it turned out. I did a factory reset from bootloader. Now its pretty screwed.
Im on Hbot 1.15 and s-on, unlocked with htc's tool. Using TWRP 2,7
My pc wont recognize the handset, it comes up with error, and cant install drivers. The htc standard drivers wont work, nor does htc drivers from "here and there".
adb/fastboot cant find the device in bootloader/fastboot bevause of the drivers issue
In TWRP i cant find "internal_sd" nor "sdcard", and cant mount it to PC either.
So my handset is effectively without ROM, and without any mean to communicate with my pc for adb/fastboot (win8)
If anyone has any suggestions for getting communication between my handset and my PC, and/or get the "internal_sd" to mount, please share.

daABBA said:
Hello peoples
On my htc one s (s4) I did something pretty stupid, as it turned out. I did a factory reset from bootloader. Now its pretty screwed.
Im on Hbot 1.15 and s-on, unlocked with htc's tool. Using TWRP 2,7
My pc wont recognize the handset, it comes up with error, and cant install drivers. The htc standard drivers wont work, nor does htc drivers from "here and there".
adb/fastboot cant find the device in bootloader/fastboot bevause of the drivers issue
In TWRP i cant find "internal_sd" nor "sdcard", and cant mount it to PC either.
So my handset is effectively without ROM, and without any mean to communicate with my pc for adb/fastboot (win8)
If anyone has any suggestions for getting communication between my handset and my PC, and/or get the "internal_sd" to mount, please share.
Click to expand...
Click to collapse
Uninstall all usb drivers / HTC sync.
Then install this drivers --> LINK

LS.xD said:
Uninstall all usb drivers / HTC sync.
Then install this drivers --> LINK
Click to expand...
Click to collapse
Thanks for your reply
Tried uninstalling/reinstalling drivers as you suggested (actually 7th time I tried this..) No luck
Fired up my old laptop with fresh win7 and installed drivers. No luck
In both instances the PC's reports either that its something wrong with the handset, or that they cant find the correct drivers for the handset. Sometimes it comes up with "ville" sometimes not.
Either way neither fastboot or adb can communicate with the handset, (nor can HTC sync).
Is there a way to use the terminal on TWPR to write som magic code to restore what seems to be the reason behind all this: some error code which makes the handset unable to mount the "internal_sd"?

daABBA said:
Thanks for your reply
Tried uninstalling/reinstalling drivers as you suggested (actually 7th time I tried this..) No luck
Fired up my old laptop with fresh win7 and installed drivers. No luck
In both instances the PC's reports either that its something wrong with the handset, or that they cant find the correct drivers for the handset. Sometimes it comes up with "ville" sometimes not.
Either way neither fastboot or adb can communicate with the handset, (nor can HTC sync).
Is there a way to use the terminal on TWPR to write som magic code to restore what seems to be the reason behind all this: some error code which makes the handset unable to mount the "internal_sd"?
Click to expand...
Click to collapse
When it shows up "ville" you have to manually install the drivers.
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
LS.xD said:
When it shows up "ville" you have to manually install the drivers.
Click to expand...
Click to collapse
The way to make your internal_sd usable again is to flash the stock recovery and perform " cöear storage" in bootloader mode. This will only work with stock recovery installed. Means you nead working fastboot to flash it.

LS.xD said:
When it shows up "ville" you have to manually install the drivers.
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
The way to make your internal_sd usable again is to flash the stock recovery and perform " cöear storage" in bootloader mode. This will only work with stock recovery installed. Means you nead working fastboot to flash it.
Click to expand...
Click to collapse
Somehow I got it to work again today. First fastboot suddernly was responding,and eventually adb. Did some more or less random commands and flashed a couple of recoveries back and forth and pushed some different boot.img, then all of a sudden, my phone and my PC started talking again and I could format my internal_sd from PC. From there it was just the usual track
Happy to move my sim from my son's galaxy y back to my fresh cm11 ROM.
(I cant really say what did the trick, maybe connecting an old desire made some magic to my drivers, I dont know.)
Thanks for your efforts to help

my phone doesnt recognized by pc if i start downloading mode

Hi guys .
i flashed "by mistake " the wrong cwm recovery by ( Rsher ) . after the device is restarted the screen just stopped on welcome screen .
now i have no access to recovery mode .
so i tried the other choice which was the download mode .
and here is my problem my pc doesnt recognize my android phone , when i connect the phone the pc displays these words
"usb is not recognized . the last device you connected to computer malfunctioned and windows does not recognized it "
also odin does not recognize it .
now i have no access neither to recovery mod nor to download mode and the device still freezing on welcome screen . so my device practically is DEAD!!
PLEASE IF YOU WANT TO HELP ME :
**KEEP IN MIND THE DEVICE " BEFORE THIS " WAS RECOGNIZED WHEN IT IS TURNED ON
** KEEP IN MIND OTHER PHONES LIKE GALAXY DOUS OR GALAXY BEAM IS WORKING ON THE SAME PC AND RECOGNIZED ON ODIN
** my phone is galaxy s II Plus working on android 4.2.2
**my pc is HP working on windows 10
**i have the latest Samsung kies and the latest drivers
** what i have tried
*update the driver on my pc
*uninstall and reinstall the driver
*using different usb cables
*uninstall the drivers and restarting pc
*updating other generic usb hub
*changing values in the registry
*I have tried all versions of odin
*pull the battery and entering download mode several times
PLEAAAAAAASE HELP :crying::crying::crying: ​

Try installing the google USB drivers.They are normally installed with the android SDK. Maybe they can help you detect the phone or you can try to manually update the driver.
Sent from my Moto E using Tapatalk

Cruzy12100 said:
Try installing the google USB drivers.They are normally installed with the android SDK. Maybe they can help you detect the phone or you can try to manually update the driver.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
thanks for replay but nothing happened still the same problem

abdanoo said:
thanks for replay but nothing happened still the same problem
Click to expand...
Click to collapse
Because in most cases this would have fixed the problem.Try some other forum maybe to get a different set of answers.
Sent from my Moto E using Tapatalk
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Cruzy12100 said:
Because in most cases this would have fixed the problem.Try some other forum maybe to get a different set of answers.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Or could also try to repeat the same steps in a different system.
Sent from my Moto E using Tapatalk

Cruzy12100 said:
Because in most cases this would have fixed the problem.Try some other forum maybe to get a different set of answers.
Sent from my Moto E using Tapatalk
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Or could also try to repeat the same steps in a different system.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
as i mentioned above sir , the phone is recognized when it is ON but the problem occurs when i go to download mode . i think it is not concerned with the drivers

Have a look at this soft-brick help guide. If your phone is not even able to enter the Recovery Mode, you may have a case of NAND rw corruption and recovery may not even be possible (you may have to look at hard unbrick scenarios).
Having said that, these are a few things I might have still tried if I were you:
1. If you have access to a Linux PC or a bootable Ubuntu drive, start it and see whether it recognizes your phone using the lsusb command. It will help you to rule out any driver issues.
2. Try to drain the battery (by keeping a long time in that welcome screen) and then do a fresh recharge and then try again.

prahladyeri said:
Have a look at this soft-brick help guide. If your phone is not even able to enter the Recovery Mode, you may have a case of NAND rw corruption and recovery may not even be possible (you may have to look at hard unbrick scenarios).
Having said that, these are a few things I might have still tried if I were you:
1. If you have access to a Linux PC or a bootable Ubuntu drive, start it and see whether it recognizes your phone using the lsusb command. It will help you to rule out any driver issues.
2. Try to drain the battery (by keeping a long time in that welcome screen) and then do a fresh recharge and then try again.
Click to expand...
Click to collapse
Well. , I have to say this is new solution . thank you brother I'll try and give you feedback ??

LG L90 (d405n) wont turn on (black screen). Help please.

Hi,
I tried to unlock bootloader. Rooted phone using King Root successfully. Opened bootloader using inside terminal and installing proper aboot. Then without restart i also flashed proper TWRP usning Twrp manager and after clicking reboot bang... black screen and nothing happens. Phone wont act on power button , keys combinations etc. When i connect it using usb i see partition with 2 folders (version and images). I tried some methods like using LG Flash Tool 2014 but it stucks on 4% and wont go ahead no matter what i do (recconecting ,removing battery etc). I would be VERY thankful if someone can provide me step by step solution or just do it via Teamviewer. If someone would like to help using TV method please contact me via skype (siuted.max - ID) and i ll provide TV ID.
Regards
Mat.

I really need that help guys I am even willing to pay for someone who is able to fix it.

Lg toolkit and pc easy fix but if you cant see recovery too or fastboot.using key combo do hou have the lg toolkit?fastboot,adb?sounds like you need too reload 15 second adb fastboot installer.when flash tool gets to adb or fastboot and get stuck.go to update driver device manager,and see if theres a triangle or ? There,then update that driver.let me know?
Sent from my SM-J320P using Tapatalk

skully35 said:
Lg toolkit and pc easy fix but if you cant see recovery too or fastboot.using key combo do hou have the lg toolkit?fastboot,adb?sounds like you need too reload 15 second adb fastboot installer.when flash tool gets to adb or fastboot and get stuck.go to update driver device manager,and see if theres a triangle or ? There,then update that driver.let me know?
Sent from my SM-J320P using Tapatalk
Click to expand...
Click to collapse
Thank You for reply ! Would You like to make it step by step and exactly what to do or links ?
1. I have LG Toolkit 2014
2. Fastboot and adb i have on my pc but "device not found" no matter what i do.
3. How to reload 15 second adb fastboot installer ?

OK I know its tuff when its not being s hown like. A video ?,I researched your model a little,do you see you costom recovery when using the hold home and volume up keys?or is that also blacked out? And can you see fastboot using phone keys?does your phone make a sound when plugged too your PC?a lot of questions but its important? then I can easily direct you better!
Sent from my Sero 7 pro using Tapatalk
---------- Post added at 11:46 AM ---------- Previous post was at 11:38 AM ----------
If you phone makes a noise plugged in I can guide you,k?I brought 4 phones back from the dead this week!I'm on a roll!lol,,when I stayed reload 15 min.installer I meant you may have to turn on terminal to PC and hit adb devices then check driver updater and reinstall your drivers.very easy I just need to know where we stand.
Sent from my Sero 7 pro using Tapatalk

I see nothing on the screen. No matter what i push (any combination) nothing appears. After connecting phone there is no sound. PC recognizes it as Android device. Thats all. No fastboot as well.

skully35 said:
OK I know its tuff when its not being s hown like. A video ,I researched your model a little,do you see you costom recovery when using the hold home and volume up keys?or is that also blacked out? And can you see fastboot using phone keys?does your phone make a sound when plugged too your PC?a lot of questions but its important then I can easily direct you better!
Sent from my Sero 7 pro using Tapatalk
---------- Post added at 11:46 AM ---------- Previous post was at 11:38 AM ----------
If you phone makes a noise plugged in I can guide you,k?I brought 4 phones back from the dead this week!I'm on a roll!lol,,when I stayed reload 15 min.installer I meant you may have to turn on terminal to PC and hit adb devices then check driver updater and reinstall your drivers.very easy I just need to know where we stand.
Sent from my Sero 7 pro using Tapatalk
Click to expand...
Click to collapse
Hey. Sorry to say but phone is not giving any vibration or noise... Only windows gives a sound typical to connecting USB device and thats all. Phone looks like dead and only thing is recognizing it by windows.

Hey,
Anybody knows a solution ? I read some threads here but i failed when trying. I would really appreciate for step by step walkthrough.
Thank You!

Guide to unbrick lg l90
fazics1 said:
Hi,
I tried to unlock bootloader. Rooted phone using King Root successfully. Opened bootloader using inside terminal and installing proper aboot. Then without restart i also flashed proper TWRP usning Twrp manager and after clicking reboot bang...
Click to expand...
Click to collapse
Use this guide from one of the XDAmembers. Hope you get your phone get fixed soon.
https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

my zu680kl hard brick!!! hlp pls

i install twrp after unlock bootloader , i flashed stock rom but i forgot to wipe system , data before flashed
My device's No Fastboot, No recovery, No Display, hard bricked
i's only vibrate when i press power button
red blink when connect usb cable
anyone has same problem? help me pls..

Same here. But i have yet to find anyone to get it past the black screen.
.

when you try to boot into recovery.. try to. hold the vol up button for a sec after it it should have loaded.. that whats mine was doing.. black screening

Any news? My device also bricked.

Me to, I got stuck in updating firmware process or corrupted firmware file. I'm also stuck with black screen no recovery, Fastboot mode, computer won't recognize device, phone just blinks red notification light when cable plugged in, power button vibration, also looking for fix. The phones only week old, had to buy another one. I'm now stuck with the new device can't get into twrp just presented a black screen when booting into twrp, only way to get into twrp is with adb, fastboot/boot/twrp.Img which sucks really like the device

Same problem, I can't acces to bootloader, fastboot, recovery
it's only vibrate when i press power button and the red led blink when I connect the usb cable
Someone found a solution ?

Roxy34 said:
Same problem, I can't acces to bootloader, fastboot, recovery
it's only vibrate when i press power button and the red led blink when I connect the usb cable
Someone found a solution ?
Click to expand...
Click to collapse
I've been working on a similiar issue on a ZU680KL for a friend of mine for a few months now. I ended up buying a USB-C type of an EDL cable. I am able to get some software's to better recognize the phone now including Xiaomi's MiFlash, and have found variations of the files that QPST wants when trying it as a solution, but the raw flash programmer file's I have found, though for right chipset, or probably intended for other devices are the partition tables for example would all be different. This whole project to me as I just recently described it, feels like trying to glue a shattered light bulb back together using liquid glue like the kind they use to have us use in Elementary school on paper projects, and to make it more fun, every time you look away, someone's throwing away more and more of the puzzle pieces on us. lol. Frustrating as all hell. It's as if Asus never wanted or intended for us to restore these phones from an EDL or low level NVRAM status. Wish I had the exact answer. Plan to waste a few hours of today on it again though, being how I found this thread researching it some more. Good luck to all.

solved? I have easy way to fix
regards

grean said:
solved? I have easy way to fix
regards
Click to expand...
Click to collapse
what's easy way to fix? thanks^_^

If you watch YouTube videos, you find virtually nothing. There is one Portugese video, but they never show the phone in a completely dead state of black screen with a couple vibrations & an occasional blinking light. This state is truly bricked. There are a couple fake videos also, wanting you to just look at stuff, but it's just a stupid ad. We have one working Zenfone 3 ultra, & one seriously did one. I've offered 100's of $$ to anyone to bring it back to life, & have received ZERO takers. Anybody who's not insane can understand what that means. In other words, so far, forget it. No one has been able to unbrick this model. Only the other Asus models. This Asus model has relatively few purchasers - & has even fewer people willing to mess with it. What a shame.
.

Hello, if someone has a working zu680kl device we could extract the necessary image and fix it using this tutorial:
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I think it looks very promising.
I also have a bricked zu680kl device and I don't think about to give it up !!!!

We have a working one, but my better ½ is not about to give it up for an experiment.
.

hillg001 said:
We have a working one, but my better ½ is not about to give it up for an experiment.
.
Click to expand...
Click to collapse
I think there is no risk to brick the device because there will be no installation of any kind of firmware at all. The only thing is to make a backup of all app data because a fresh clean device (factory reset) is necessary. If you like to have a look at the whole procedure search for
Guide, if you are NEW “Qualcomm HS-USB QDLoader 9008” MODE
on the mentioned page
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
If it would be possible to get the eMMC image I would try to go through the rest of the process. Maybe this brings back our dead devices to life.
Buy your better 1/2 some flowers before you ask

I managed to get it fixed tonight
I did the following steps:
1) Enable Qualcomm HS-USB QDLoader 9008 mode with help of an diy EDL cable.
2) Download the zu680kl raw firmware from here - was not easy to find : http://vietmobile.vn/threads/file-raw-asus-zu680kl-asus-zenfone-3-ultra-zu680kl.46825.html
3) Flash the raw firmware with QFIL
4) Reinstall the stock firmware with fastboot and adb sideload
5) Thank God for help !!!

luckychild said:
I managed to get it fixed tonight
I did the following steps:
1) Enable Qualcomm HS-USB QDLoader 9008 mode with help of an diy EDL cable.
2) Download the zu680kl raw firmware from here - was not easy to find : http://vietmobile.vn/threads/file-raw-asus-zu680kl-asus-zenfone-3-ultra-zu680kl.46825.html
3) Flash the raw firmware with QFIL
4) Reinstall the stock firmware with fastboot and adb sideload
5) Thank God for help !!!
Click to expand...
Click to collapse
Hey what files do you use with the qfil out that raw firmware package or do you just flash the whole raw zip

gubbilo144 said:
Hey what files do you use with the qfil out that raw firmware package or do you just flash the whole raw zip
Click to expand...
Click to collapse
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
deadmatrix said:
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
Click to expand...
Click to collapse
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.

deadmatrix said:
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
Click to expand...
Click to collapse
Good just got my edl cable in the mail, going try to fix my Asus zenfone 3 ultra that's been in my dresser for 6 months bricked.
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
deadmatrix said:
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
Click to expand...
Click to collapse
Were do run the ftm-flashall.cmd in qfil or adb

gubbilo144 said:
Good just got my edl cable in the mail, going try to fix my Asus zenfone 3 ultra that's been in my dresser for 6 months bricked.
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
Were do run the ftm-flashall.cmd in qfil or adb
Click to expand...
Click to collapse
Run it from a command prompt window. So like at a DOS Prompt. Nothing to do with ADB.
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
After running the command - it'll boot up to a custom Qualcomm rom - it will have no Gapps of any kind on it. That's why we still need to sideload the rom from Asus's website that you can download from them. I have trouble sideloading over here - not sure why. I have to put it onto a microSD card to flash it from the phone's recovery. Also - Don't forget to wipe data and factory reset it before booting up post of the sideloading. Otherwise it'll possibly get stuck trying to optimize apps - it froze on 'Android is Starting' for me and when I power cycled manually - it corrupted the UI. Had to go back and run the ftm-flashall.bat again.
Just realized the ftm-flashall.cmd that i listed earlier - is a typo - the propper file name should end in a .bat I believe. Sorry for the mistake. Not enough Coffee.

deadmatrix said:
Run it from a command prompt window. So like at a DOS Prompt. Nothing to do with ADB.
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
After running the command - it'll boot up to a custom Qualcomm rom - it will have no Gapps of any kind on it. That's why we still need to sideload the rom from Asus's website that you can download from them. I have trouble sideloading over here - not sure why. I have to put it onto a microSD card to flash it from the phone's recovery. Also - Don't forget to wipe data and factory reset it before booting up post of the sideloading. Otherwise it'll possibly get stuck trying to optimize apps - it froze on 'Android is Starting' for me and when I power cycled manually - it corrupted the UI. Had to go back and run the ftm-flashall.bat again.
Just realized the ftm-flashall.cmd that i listed earlier - is a typo - the propper file name should end in a .bat I believe. Sorry for the mistake. Not enough Coffee.
Click to expand...
Click to collapse
i got it thanks so much guys im updating in recovery now,my asus zenfone 3 ultra paperweight is back alive

gubbilo144 said:
i got it thanks so much guys im updating in recovery now,my asus zenfone 3 ultra paperweight is back alive
Click to expand...
Click to collapse
Glad to hear it! So we have a now reproducable cure after years of nothing in the pipe really. I am thinking of writing a start to finish post of how to deal with it for beginners that can be pinned by a mod. If someone else wants to beat me to this, feel free - especially since I don't actually even own this model of phone.. Might maybe pick it up though.