Hello all, looking for some help please before I pull all my hair out. I am sorry in advance if I go on but I do like to be thorough... Here goes.
My Vega is stuck with the blank screen when I turn it on apart from the backlight and I cannot get into the recovery mode. I have tried numerous times like is advised but I have tried at least 100 times and I'm not joking with no luck. I have tried to follow a few guides advised on this forum but I must be doing something wrong so any guidance would be much appreciated. Here is what I have done so far....
Downloaded the Vega USB drivers and stock ROM from the myadventvega website.
When I connected the Vega to my laptop a generic USB driver installs but nothing else. The power cord is connected and charged to 100% this is where it ends for me. I cannot get into the recovery mode the screen either comes on and stays blank which is wrong or does not come on at all. I have checked this too thinking I may have been in recovery mode but am not as the laptop does not then ping to acknowledge and then proceed to let me install the recovery drivers
I also have Vega tools and used Audi to check and even install the correct drivers but no luck. All I get when I try to run the stock exe file is USB device not connected.
Thanks in advance for your help
Sent from my Nexus 7 using Tapatalk 2
You should hear the USB sound only then the screen stays blank untill you flash it . Is what I remember
I remember I got USB driver from origional updated Rom if that's any help
Sent from my HTC Desire S using xda app-developers app
Hello
I don't get anything as I can't get into the recovery mode I have lost count of the times I have tried. Never thought it would be this awkward
Sent from my Nexus 7 using Tapatalk 2
Sg231179 said:
Hello
I don't get anything as I can't get into the recovery mode I have lost count of the times I have tried. Never thought it would be this awkward
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
this is how i did it
first got the usb driver installed got Tegra Tab 10 USB Driver from a folder in VegaComb HC3.2 9b Installer on windows 7 it said unknown driver install anyway which i did
once working shut down the vega put it in recovery as i said earlier
the VegaModdedStock_v1.10_v2 didnt work so i extracted(unzipped it) it to a folder then went to the folder and doubled clicked on the lvds windows batch file which flashed modded stock to the tab worked great then
extracted VegaBean-Beta6-NVFlash to another folder and flashed using the lvds method again worked for me hope this helped
---------- Post added at 06:44 PM ---------- Previous post was at 06:36 PM ----------
gazzy21uk said:
this is how i did it
first got the usb driver installed got Tegra Tab 10 USB Driver from a folder in VegaComb HC3.2 9b Installer on windows 7 it said unknown driver install anyway which i did
once working shut down the vega put it in recovery as i said earlier
the VegaModdedStock_v1.10_v2 didnt work so i extracted(unzipped it) it to a folder then went to the folder and doubled clicked on the lvds windows batch file which flashed modded stock to the tab worked great then
extracted VegaBean-Beta6-NVFlash to another folder and flashed using the lvds method again worked for me hope this helped
Click to expand...
Click to collapse
As a note i am using this rom still best i have found but i had a freeze problem when watching video so i downloaded no-frills cpu and set the minimal governor to the 400 mark which fixed the freeze problem
hope this works for you
Hi thanks for the reply maybe I'm not getting the drivers installed I did download the USB drivers which I unzipped to a folder on my laptop but not sure how to actually install these drivers any idea
Thanks
Sent from my Nexus 7 using Tapatalk 2
is this any help
ROM] JellyBean for Advent Vega / PoV Mobii Tegra and other P10AN01 clones
Press the back button and keep it pressed during all the time.
After 2 seconds press the power button (keep the back button pressed) until your screen backlight turns on and/or you hear on your PC that an USB device has been attached.
Release the power button (keep the back button pressed).
After 2 seconds release the back button.
---------- Post added at 07:18 PM ---------- Previous post was at 07:09 PM ----------
I just done this a few days ago refreshed the tab as i changed the sd card and it is difficult and the tab screen staying blank dosnt help you have to hear the usb attached sound to know your in recovery then it still looks blank when flashing you might notice top of tab while flashing some tiny writing 1 line of text very small for my old eyes
and remember to wait untill dos box says press key to exit or the like
---------- Post added at 07:22 PM ---------- Previous post was at 07:18 PM ----------
yes to install the drivers goto device manager in windows 7
with the tab plugged
youll see an exclamation mark on it
right click update driver then browse to the folder and enter you might have to try this a few times i did lol
Hello
I did as you said and my laptop made the noise like it detected the device and the screen stayed black so I thought great now I'm in recovery. I then went to flash the ROM and the does box appears then says USB device not found press enter to continue. Just checked device manager and no yellow exclamation marks anywhere.
Thanks
Sent from my Nexus 7 using Tapatalk 2
this rom is really good it plays flash in the browser but it dosnt multitask very well so i use system panel app with the app killer widget and no frills cpu and es file explorer i also disable stuff using app quarantine which is very usefull but don't quarantine any critical apps as you may need to flash from start
tvcatchup works great also at the moment still a very usefull tab
---------- Post added at 07:47 PM ---------- Previous post was at 07:41 PM ----------
did you try lvds method
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks like driver has installed though good good lol
Hello
The ROM I downloaded to use is the view comb one and the USB drivers were from the myadventvega website. There is no lvds windows batch file in this
Sent from my Nexus 7 using Tapatalk 2
Sg231179 said:
Hello
The ROM I downloaded to use is the view comb one and the USB drivers were from the myadventvega website. There is no lvds windows batch file in this
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
do you mean VegaComb HC3.2 9b Installer
I can't find view comb
No its view comb 3.2 build 7.2 it's not a ROM issue tried flashing the stock and same message. Like the first post though I cannot get to recovery mode at all
Is there any way of using command prompts to put it into recovery mode
Sent from my Nexus 7 using Tapatalk 2
Sg231179 said:
No its view comb 3.2 build 7.2 it's not a ROM issue tried flashing the stock and same message. Like the first post though I cannot get to recovery mode at all
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
bcause you said
did as you said and my laptop made the noise like it detected the device and the screen stayed black so I thought great now I'm in recovery. I then went to flash the ROM and the does box appears then says USB device not found press enter to continue. Just checked device manager and no yellow exclamation marks anywhere.
i would think it's in recovery mode but the path to adb is wrong to get round this which is what i did bcause i'm a noob myself was to use winrar to extract unzip it into a seperate folder which has the adb comand program in the unzipped folder as part of the rom package and use the batch file lvds instead to flash the rom it is possible to do it your way but you'll have to research more which i didnt because the way i used was explained somewhere else in another forum and jelly been was the the rom .
Help we need a boffin
I have followed the recovery mode instructions precisely but it will not go into recovery the backlight always comes on indicating I have gone too far and not in recovery mode. I'm starting to think is the back button not working as if so the tablet genuinely think I was turning it on only and would explain a lot. But it definitely did work before this problem occurred.
Scratching my head now
Sent from my Nexus 7 using Tapatalk 2
if you hear the usb connect your in recovery you do see a blank screen but the brightness is low
---------- Post added at 09:12 PM ---------- Previous post was at 09:01 PM ----------
advent vega's meant to be unbrickable
The USB did make a noise and have checked and the APX driver is installed the screen is completely black indicating I am in recovery but when I try to flash I get the message USB device not found.
I'm lost on what I can do now
Sent from my Nexus 7 using Tapatalk 2
Have a cuppa lol look round the forums you will find the answer have you installed the android sdk and java ? have you used the command adb devices in the dos box ? after you have the driver installed so you a bit closer have another read i hop i have help atleast a little
You have been more than helpful thanks. The USB APX drivers are installed I also have android SDK tools too. It just won't go into recovery. Once in recovery I can flash but it won't do it. If there are adb command prompts to get in recovery then I'd love to hear it
Sent from my Nexus 7 using Tapatalk 2
yes post here on what you do finally I would be interested thanks
Sg231179 said:
You have been more than helpful thanks. The USB APX drivers are installed I also have android SDK tools too. It just won't go into recovery. Once in recovery I can flash but it won't do it. If there are adb command prompts to get in recovery then I'd love to hear it
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, but there are no adb commands to get into recovery mode for this tablet.
You will have to do with correct Windows drivers + right button combo.
Thanks for the reply but like I say I have the drivers installed but it just will not go into recovery mode. I have tried the correct and every other button combo I can think of.
Think I may truly have a bricked Vega
Sent from my Nexus 7 using Tapatalk 2
Related
Please hep immediately!!!!!!!!!!!!!!!!!!!!!! I Recently got a Kindle Fire And immediately when i got home i rooted it with no problems with burritoroot. Then after that I found a way to get The android Market on there And i was so happy. Then After that i began to flash the custom recovery on it everything went perfectly fine until i got to The Yellow Triangle on the the Kindle file and it told me to push the power button and it was waiting for device on laptop. So when i pressed the power button nothing happened so i pressed and held it and it did nothing but turn off and come right back to that screen I was waiting at the screen for an hour till i gave up and exited the Kindle Utility program on cmd and tried it without it now im stuck with this stupid yellow triangle on my screen and wish to got to my kindle os Can someone help me please??????
PS: I have all drivers Installed and followed the Video very thoroughly
I Exited out of Program before completion
It doesn't seem like this is the issue, but you could try changing the boot mode in adb to regular, instead of fastboot, its all i can think of right now. Does the device show up in adb?
Yeah, it sounds like it might be in the wrong boot mode.
Try using this utility if you haven't already. It helps a lot.
I tried That But I cant do that because My device driver is showing up as uknown and it wont let me update it so i cant access it T_T its just sitting there with a yellow triangle
this is where i can't help you, i only know mac stuff, no pc drivers crap and stuff, hope you find help elsewhere.
im bout to sob can someone please help me i just got this with the remainder of my money
oshea1995 said:
im bout to sob can someone please help me i just got this with the remainder of my money
Click to expand...
Click to collapse
You are stuck in fast bootmode, it's not a big deal, there a ton of threads and post about how to get out of it. Search and you should find what you need, if not I can try to walk you through it but I'm no expert.
---------- Post added at 10:09 PM ---------- Previous post was at 10:05 PM ----------
I found this... http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222 it's how I got myself out of fastboot.
You also might try reinstalling the drivers from the device manager. Your situation sounds similar to one I encountered and I solved it by reinstalling the drivers.
Sent from my SAMSUNG-SGH-I727 using xda premium
Like everyone said, it's no big deal. You need to reinstall the drivers and change out of fastboot mode (4002) and into regular boot mode (4000). This thread has it all in the first post:
http://forum.xda-developers.com/showthread.php?t=1417234
don't sob, calm down, it will be alright. I assume you are young, so almost bricking a device may give you a heart attack, but there is almost always a way out of it. For right now, take a break from the device, get your mind off of it, and come back later, it WILL be alright.
Power the kindle all the way off.
Power it all the way back on.
Install drivers.
Vashypooh said:
Power the kindle all the way off.
Power it all the way back on.
Install drivers.
Click to expand...
Click to collapse
This will work!. When Vashypooh says to install the drivers he means to do it manually like this here is a quote from my thread on the complete video guide that would have answered these questions for you and fixed your problem immediately:
• I have also noticed that some people also get stuck at 3:55 in this video at the firefire triangle. The fix for this is fairly easy and is explained in the video if you need a walkthrough step by step for doing this (Updating the drivers)here you go:
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
and you should be okay!
Here is that thread on the complete video guide that I find have answered many others questions....
http://forum.xda-developers.com/showthread.php?t=1417234
Hi there,
I rooted my Kindle Fire (6.2.2) a few days ago. It was working perfectly for two days. When I turned it on the 3rd day, the following happened:
1. It went into the recovery screen without me pressing the on/off button to turn it orange.
2. A few seconds later, a big android logo came up and there was a message (I'm sorry, I don't remember what it says)
3. I didn't know what happened so I turned the device off hoping to get rid of this problem.
After that, whenever I turn it on, it only shows the yellow triangle with picture of fire in it. I tried to hold on to the on/off button for 30, 60 and 90 seconds, all it does is to turn the device off.
I really need some help, please. I don't understand why it suddenly stopped working after two days. Is it related to the new 6.3 update?
Go into kfu and ten go into the boot menu... (1) then choose normal boot.. hope this helps!
Is the battery low or almost dead. You could try plugging it in and see if it boots up. Mine does this exact thing when the battery is dead. Just charge it up and good as new
Sent from my ADR6400L using xda premium
fiddlefaddle said:
Go into kfu and ten go into the boot menu... (1) then choose normal boot.. hope this helps!
Click to expand...
Click to collapse
Hi fiddlefaddle,
Thanks for the idea, but my Mac doesn't recognize the device.
Should I use a Windows machine and download the kfu somewhere?
Jmjohnson1717 said:
Is the battery low or almost dead. You could try plugging it in and see if it boots up. Mine does this exact thing when the battery is dead. Just charge it up and good as new
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Hi jmjohnson,
Thanks for your help. I'll charge it for a day and see what happens.
william_leong said:
Hi fiddlefaddle,
Thanks for the idea, but my Mac doesn't recognize the device.
Should I use a Windows machine and download the kfu somewhere?
Click to expand...
Click to collapse
Yes you should use windows... sorry I forgot you were using Mac... you can download the kfu in the android development part of the kindle forums.
---------- Post added at 09:06 PM ---------- Previous post was at 09:02 PM ----------
fiddlefaddle said:
Yes you should use windows... sorry I forgot you were using Mac... you can download the kfu in the android development part of the kindle forums.
Click to expand...
Click to collapse
Here is link http://forum.xda-developers.com/showthread.php?t=1399889
when you choose 1 for normal boot it will say waiting for device... shut your kindle off by holding the power and then turn it on.. and it will connect as its turning on
fiddlefaddle said:
Yes you should use windows... sorry I forgot you were using Mac... you can download the kfu in the android development part of the kindle forums.
---------- Post added at 09:06 PM ---------- Previous post was at 09:02 PM ----------
Here is link http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
Thanks for your patience.
I downloaded and unzipped the file. After turning the Kindle Fire on and off and "waiting for device..." didn't do/show anything else --- stuck.
Then I try to run the "install_drivers" from the extracted files list, the following message popped up:
"The current language is not supported by the Device Driver Installation Wizard.
Contact the vendor that provided you this package."
Does it mean I need to get a computer that is running English Windows to do this?
Thanks for your patience again.
william_leong said:
Thanks for your patience.
I downloaded and unzipped the file. After turning the Kindle Fire on and off and "waiting for device..." didn't do/show anything else --- stuck.
Then I try to run the "install_drivers" from the extracted files list, the following message popped up:
"The current language is not supported by the Device Driver Installation Wizard.
Contact the vendor that provided you this package."
Does it mean I need to get a computer that is running English Windows to do this?
Thanks for your patience again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
DJLamontagneIII said:
when you choose 1 for normal boot it will say waiting for device... shut your kindle off by holding the power and then turn it on.. and it will connect as its turning on
Click to expand...
Click to collapse
Thank you so much.
b63 said:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Hi guys,
I don't know what else to say. IT WORKS!
I'm so grateful for all of you here helping a total stranger.
Thank you so much!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
william_leong said:
Hi guys,
I don't know what else to say. IT WORKS!
I'm so grateful for all of you here helping a total stranger.
Thank you so much!
Click to expand...
Click to collapse
No problem... This is why we are here to help! (We all have to start somewhere) It took me 4 hours to get my drivers installed and rooted... lolz
Hello All,
i am tired and done everything to fix my lg g2 download mode. i've done all adb and fastboot methods but when i write "fastboot erase recovery" it stucks and nothing happening. In my device manager Android ADB Interface driver installed but when type in cmd "adb devices" its not listed. im using windows 7 and im done everything.... if anywhere im doing something wrong plzzzzzzzzzzzzzzz tell me or guide how to fix my lg g2 d802 fastboot issue...
in fastboot it showing me
1400 - fastboot mode started
1530 - reset -
1540 - portchange -
1800 - fastboot: processing commands
i will be really thankfull for your guidance...
Thank u jessica but still stuck
Thank you miss jesica for response.
I tried that adb drivers that u mention in link but same issue facing device not listed when i type adb drivers.
There are no official lollipop kdz to install in Lg g2 D802, so is that necessary to download that drivers one u mention in link?
When 1st time i face this problem, device manager showing me only android (no qhusb_xxx or qualcome whatever name it is) only showing android in unknow device.
Then i install lge adb interface driver from lg universal drivers from their extracted folder then lg g2 start giving fastboot and process commands in smartphone but when i try erasing recovery and laf its stuck or nothings happening.
And how do I disabled driver enforcement?
Thank You
And also there no yellow mark or any unk device.
Jessooca said:
A few questions, in device manager what does it show with your device? any yellow question marks in device manager?
Did you install fastboot and adb? Did you make sure any other drivers were uninstalled first? Including your LG driver if you have the LG PC suit software installed, remove it.
-- Typically the fast way to fix this issue is to remove all the drivers and reboot your computer, definitely reboot the computer afterwards.
Keep your phone disconnected from your computer during the following:
Then install this: ADB&Fastboot installer
Again, make sure you right click and run as administrator and Select Y(es) for all.
It has the newest driver for Android 5.0+ After you install it, install the latest driver from lg here:
Restart your computer, plug in your device and let it install any drivers.
Make sure you've enabled USB debugging on your phone. Power off your phone, reboot into recovery and plug it into your computer, if any drivers install, allow them to do so.
Go ahead now with what you were going to do, IF you still have problems let me know.
-Have you disabled driver enforcement from Windows? You may want to do that so youll never have problems with that doing anything on any device.
--Jessica
Click to expand...
Click to collapse
My Download Mode Corrupt and my problem is im facing fastboot mode started...
so i read forums it telling us how to fix fastboot but when im doing what they are say nothing happening....
im attaching my device manager android drivers plz have a look.
Jessooca said:
First... STOP with what you're typing into adb! Why are you telling it to erase anything?! How about you tell me what you're actually wanting to accomplish before you end up bricking your phone by sending the wrong command to your phone.
What country/carrier/model of G2 D802 are we fixing?
--I can get whatever LG tot/kdz is needed to fully return you to stock which will give you the recovery back etc....
What are you trying to do exactly, return your device to stock? is it just stock recovery that's your issue?
How are you running the adb command exactly? right click run as administrator on "command prompt"?
Download this and extract it
]
As for the drivers and everything I said to install, always install the latest drivers etc, so I would install the ones I suggested and uninstall yours first. Mine is adb and the fastboot drivers, so install the one I suggested and be sure to restart your computer after and try the adb list command again
From device manager uninstall the device, it should give you the option (a checkmark box) to delete the driver as well, do this then refresh device manager. Now right click your phone in device manager, select update driver software, Select "Browse my computer option", then select "browse" and find the driver you just downloaded. Install that and you should be good to go!
Let me know how this goes
Click to expand...
Click to collapse
LG G2 D802 32GB International And Country Pakistan.
i uninstalled all lg drivers from device manager and restarted. DONE!
Now its showing old unknown android driver, you can see in attachments... now im stuck here... now i do whatever you say Miss Jessica.
Jessooca said:
1 other thing: Disable driver enforcement by rebooting as you normally would and press F8 to get into advanced boot options. Then select " Disable Driver Signature Enforcement", continue starting up like normal
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
What country is your phone, carrier and 16 or 32gb? which D802 do you have? Is it the 32GB International Version? what country
Click to expand...
Click to collapse
When i start Disable driver signature enforcement windows not starting...
Jessooca said:
1 other thing: Disable driver enforcement by rebooting as you normally would and press F8 to get into advanced boot options. Then select " Disable Driver Signature Enforcement", continue starting up like normal
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
What country is your phone, carrier and 16 or 32gb? which D802 do you have? Is it the 32GB International Version? what country
Click to expand...
Click to collapse
Thank for response. I follow ur steps. When i enter in fastmode pressing vol+ button it showing me:
Fastboot mode started
Reset
Portchange
Reset
Portchange
Thats all.
Jessooca said:
disabling driver signature enforcement has nothing to do with awindows. Only with you wanting to use a driver that is "unsigned" when installing something onto your computer.
Power it off and restart your computer. While you're doing so, press the button on the back of your phone and power it off. Leave it off for AT LEAST 2 minutes, WITH IT OFF, plug in the usb cable into the phone. Now hold the VOLUME UP BUTTON on the back of your G2, Do NOT let go of this button, plug in the other end of the usb into your computer and tell me what happens, wait a minute or 2 to see what it does
Click to expand...
Click to collapse
And in device manager its showing android same as i show u in last picture of my device manager.
Jessooca said:
disabling driver signature enforcement has nothing to do with windows. Only with you wanting to use a driver that is "unsigned" when installing something onto your computer.
Power it off and restart your computer. While you're doing so, press the button on the back of your phone and power it off. Leave it off for AT LEAST 2 minutes, WITH IT OFF, plug in the usb cable into the phone. Now hold the VOLUME UP BUTTON on the back of your G2, Do NOT let go of this button, plug in the other end of the usb into your computer and tell me what happens, wait a minute or 2 to see what it does
Click to expand...
Click to collapse
I have the same problem with my d801... Bt brother in pakistan phones are refurbished. The only way to chk exact model is to check on pcb.. Open up ur phone and check the exact model first '.'
Sent from my LG-D801 using XDA Free mobile app
Agree bro. I just take my g2 to mobile market and he replace 802 chip to 800. And its working now.
Thats why i hate android. Im iOS user. ?
Talha1388 said:
I have the same problem with my d801... Bt brother in pakistan phones are refurbished. The only way to chk exact model is to check on pcb.. Open up ur phone and check the exact model first '.'
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for all ur assistance i just change 802 chip to 800 no need to do anything i flash 800 stock and working fine now.
Jessooca said:
I am having difficulty trying to understand whether you just don't understand what I am saying, or what. You said when you enter "fastboot mode pressing volume+..."
Can you give me a screen shot, or a picture of your G2 what it looks like after you've unplugged it completel, powered it off.
Let it sit a few minutes, (to make sure it's fully powered off!) then plug in the usb cord into the phone, then holding Volume UP (DONT let go) plug the other end of the usb into your computer. I'd like to see a screen shot (or a picture) of what your screen shows when you do this.
Click to expand...
Click to collapse
Brother kindly tell me the adrress r cntact of the person who solved ur prob because my other g2 is also stuck in same problem.
Sent from my LG-D801 using XDA Free mobile app
Bro goto sadar mobile market find ahmer in market hes no.1 software repairing individual in that market. I dont have his number and exact address.
Talha1388 said:
Brother kindly tell me the adrress r cntact of the person who solved ur prob because my other g2 is also stuck in same problem.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
Which city brother
Sent from my LG-D801 using XDA Free mobile app
Khi bro.
Talha1388 said:
Which city brother
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
Ok jesecca . i will inform u after doing that.. Thanks alottttttt for ur coperation and support
Sent from my LG-D801 using XDA Free mobile app
Jessy i tried this all steps bfr but im stuck on erasing recovery nothing happen.
Jessooca said:
---Do the following steps exactly as follows, this should work.
Lets start over, sorry. I am going to simplify this for you.
Unplug your phone. Fully Power off your phone {just because the screen is dark doesn't mean it's fully powered off, which is why I say wait a few minutes before the next step}
Now with your phone powered off, plug in the usb into your phone. (do this first, dont plug it into your computer yet)
-Hold down the Volume UP button and while still holding it down, plug it into your computer. Do NOT let go of the Volume UP button. You should see download mode, if you still see the same screen you've been seeing, lets continue....
Looking at your "C" drive or whatever your hard driver letter is on your computer, when you open the C drive so you see a folder that says "adb" (not in program files or program files x86)?
IF you DO see a folder that says "adb" look in that folder you should see fastboot, let me know if you do or do not have it in there.
--Download this and put the file into the adb folder. https://www.androidfilehost.com/?fid=23991606952614130 (Do not rename the file, leave it as "recovery")
- If you do have the adb folder with fastboot in it, do the following:
go back into the C drive, Hold the SHIFT BUTTON (dont let go), now right click on the "adb" folder {do not open it!} and select "Open Command Window" once the black box appears, let go of SHIFT.
--type the following items into command: fastboot erase recovery
-- type: fastboot flash recovery recovery.img
and finally type: fastboot reboot
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Do what I just advised in my last post, before changing your chip out or whatever you plan on doing. It should work.
Click to expand...
Click to collapse
Yes i do have adb and fastboot and i have written fastboot commands before and unbriked 3 phone before. I am well aware of this process . bit the problem is that in this phone. When i write any command . like fastboot erase recovery.. It says erasing ...... And it do nothing.....'' to tell u the exact story m gonna do that process which u told me nd i will give u pics as well in the next hour
Sent from my LG-D801 using XDA Free mobile app
Phone is not rooted. And boot loader is locked
Sent from my LG-D801 using XDA Free mobile app
I have 2 lg g2. The one i am using. And the bricked one. Both are d801. And m already flashing d801 recovery
Sent from my LG-D801 using XDA Free mobile app
---------- Post added at 07:09 PM ---------- Previous post was at 07:06 PM ----------
Allright m gonna do that ..
Sent from my LG-D801 using XDA Free mobile app
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Follow the steps:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Same happend to me, can't even unbrick it.
Z00A bricked
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
kazzot17 said:
Same happend to me, can't even unbrick it.
Click to expand...
Click to collapse
Did you and all others who are having trouble with the zenfone make sure to flash any custom kernel for your rom?? If one is available.. Just a suggestion.. Make sure you're trying to flash the right device and exact model, any follow any guides properly. Go back over and read each step thoroughly just to rule out any steps you may have missed along the way
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
Sent from Sony Xperia Z5 E6653
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Yeah, I got that far. I'm hoping for a way to unbrick it now.
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
I was on stock rom.
TheTecXpert said:
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
[email protected] said:
I was on stock rom.
Click to expand...
Click to collapse
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
That is what I'd like to do but I have not found a way to do that.
TheTecXpert said:
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
same here
Ok ... first of all..
Do you have all the necessary files on your external SD CARD ready??
------------------If yes then continue on-------------------
1. Open up adb and fastboot with admin privileges..
2. connect your device to your PC in ADB mode
3. in ADB cmd type adb reboot bootloader
***If you have already completed step 4 below previously and you are sure you already have a custom recovery (TWRP) installed on your device, then skip straight to step 5***
4 fastboot flash recovery [nameofrecovery].img (Without the brackets and also Make sure The Recovery.img file is SPECIFICALLY for your MODEL.. ***ZE550ML***
5. While your device is still connected to your PC in either ADB or fastboot mode
in ADB just type the following command below
(if connected via adb) - adb reboot recovery or adb boot recovery
(If connected via fastboot) - fastboot reboot recovery or fastboot boot recovery
IF you device reboots in to TWRP successfully, then all you need to do from this point is...
1. wipe data/Factory reset
2. wipe cache partition
3. reboot now.
you should now be able to boot your device like normal
good luck
let the process complete.. after factory reset is complete proceed
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
t00lshed said:
same here
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
utsav.goswami1986 said:
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
t00lshed said:
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
Click to expand...
Click to collapse
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
sukhwant717 said:
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
Click to expand...
Click to collapse
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
t00lshed said:
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
Click to expand...
Click to collapse
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
sukhwant717 said:
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
Click to expand...
Click to collapse
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
t00lshed said:
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
Click to expand...
Click to collapse
can you please upload xFSTK log file
you are using windows 10 did you disabled driver signature enforcement before installing xFSTK and driver?
I somehow managed to lock myself out of the phone, no boot, no fastboot recovery mode, no access through adb (device not recognized), no nothing. Anyways just looking for assistance in this. I know there must be a way, but I haven't seen anything clear enough to precisely *unbrick* my beloved ASUS Zenfone 2 Laser ZE551KL Z00TD. I've resorted to a Samsung Galaxy S5 that I rebuilt from an old broken ones spare parts. I'm more of a hardware repairer so flashing ROMS and all that is rather new to me. But I was having some success early on when trying to flash CM.13 onto it using ADB and TWRP, which is when the trouble started. I flashed the wrong recovery.img I think and somehow locked myself out completely. I'm not sure exactly what I did wrong, but after many failed attempts to flash CM.13 Marshmallow, I tried to revert back to the stock ROM and then realized that I didn't make a backup recovery.img. Doh! So now I'm completely stuck with a really nice looking paper weight. Please help! :angel:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
crossmanx said:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
Click to expand...
Click to collapse
I did plug in the device, while the battery was still in it, and it came up as an unrecognized device when the balloon popped up at the bottom right of the PC screen. I unplugged it, took out the battery, and plugged back in, but nothing showed up this time. Although I didn't look in device manager though. But I will try that next. What's your thoughts on helping me solve this issue? I'd really like to learn how the actual company first loads their firmware onto the devices. Like what kinds of software and equipment they use. I'm sure it's on a major scale though and probably have machines doing most of the work, just like an automobile assembly line. LOL. But I really want to get this ASUS Zenphone unbricked. So any help would be awesome. Thanks very much!
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Thanks Man!!! I really appreciate the help. I'll try all this and report back. Thanks Again!
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
WormholeMatt said:
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
Click to expand...
Click to collapse
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
crossmanx said:
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
Click to expand...
Click to collapse
Well, here I am ready to upload the ROM to the phone using QFIL. The phone is identified by the port. The only thing I'm having trouble with now is finding the "RAWPROGRAMMER" file to load from the firmware.
I'm not sure what else to do, I can't find the file anywhere.
Maybe this is when they say I need to get ahold of someone else exact same phone, root it, load twrp, and backup their original stock rom? I'm not sure. I just feel soo close to getting this done, but I keep missing files. I'm trying to load CM.13 but inside the folders for the firmware, there isn't any file in there. I've already found the patch file and the .mbn file that I need. Just missing the rawprogrammer file.
This is giving me a headache. LOL
Actually the only file I need is the .xml file that it asks for in QFIL. Which I guess is supposed to be in the stock rom somewhere. But in order to get that, I'm guessing I'll have to use my wifes phone (she has the exact same model as I do). I'll just have to make sure to not delete anything or mess up her phone. lol
And I'm also thinking that I will have to install stock ROM first before flashing the CM.13. So I'll have to get that stock ROM from her phone, since I deleted mine on accident.
that xml file is basically a partition structure file for your phone emmc. i think it might be there in your firmware.zip
you just have to find rawprogrammer file, i think it is there where you find unbrick guide for all qualcomm devices.....you just try that file it might work for your phone too..and after adding rawprogrammer you can add firmware parts from firmware.zip file or you also can clone your wife's phone emmc, using emmc dump to raw extension.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
you dont need to install stock rom first, only you need to send droidboot,recovery or maybe boot partitions, if you have deleted modem and other partitions, then those will also. if you get fastboot then you can flash twrp and can flash cm13.
---------- Post added at 03:09 PM ---------- Previous post was at 03:00 PM ----------
there will be different named xml file in firmware.zip for you phone's firmware you just try try yourself available xml files in firmware. if it will be wrong xml then it will auto terminate no need to worry.
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
flash stock firmware using this tool: maybe it works
https://androiddatahost.com/326a2
crossmanx said:
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
Click to expand...
Click to collapse
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Same problem ZE601Kl
WormholeMatt said:
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Click to expand...
Click to collapse
Hi Guys ,
Same problem happened for me with my Asus Zenfone 2 laser Ze601Kl.
I have tried QFIL , QPST all the qualcomm related softwares to make it work , but everytime i am getting same error " SAHARA FAIL "
I have tried with COLOR OS for One Plus One and which was having one chinese flasher and sadly that also showing the same error ,
AS far as i know i have installed the qualcomm drivers successfully and it is showing in device manager also . I have tried with Windows 7 X64 , Windows XP SP 2 . Still no luck
My phone has been dead since 1 month Somebody please help me
ZB500KL in Qualcomm HS-USB QDLoader 9008 no fastboot
Please help
I in Russia
Asus ZenFone Go ZB500KL in Qualcomm Snapdragon 410 MSM8916 detected pc only Qualcomm HS-USB QDLoader 9008. Please help
Try this https://forum.xda-developers.com/zenfone-3/help/hard-brick-asus-zenfone-3-ze520kl-t3483874/page3
Follow last post, technically you only need adb connectivity to flash all at once with one click. Hope this will help you.
Of course, now you need the rom for your device.
Sent from my ZenFone 3 using XDA Labs
crossmanx said:
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
Click to expand...
Click to collapse
Good to see anyone talking about LINUX here! I have my ZE550KL briked and the only thing I've been able to do till now are booting in fastboot and Android Recovery modes.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
Click to expand...
Click to collapse
Wow, this helped me a lot! My Linux system was not able to recognize the device but reinserting the battery and trying volumeUP+PowerButton did the trick! Now running 'fastbood devices' lists it and of course that made it visible through Virtualbox too [Windows 7 guest OS].
Now, considering that I would really like to resuscitate my phone by using LINUX, what else should I do in order to succeed?
Thanks a lot and best regards.
crossmanx said:
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Click to expand...
Click to collapse
can you help me
same mode, manage to flash and download finish success.
Finish Download
Start Download
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download
sorry dude, i have no more info about asus devices. so can't help. remember only buy phones which have flashtools available like lenovo, mi, oppo, zuk etc.