Related
Hello I'm new here but I'm almost completly hopeless on fixing my phone at this point. I was trying to install the latest version of cognition and now my phone is permanently stuck on the At&t boot screen. I eventually got to the point where I used adb to reboot recovery and tried to load one of my save clockwork recovery. I did this and waited at the at&t boot screen for a while, and still nothing happened. The kicker is now when I get my computer to recognize the phone it is only recognized as a mass storage device, and adb won't recognize any devices. I haven't had any luck with putting it in download mode and have tried every possible combination of button commands. Neither odin or adb recognize the phone. It just sits on the At&t flash screen, but my computer does recognize a connected phone. Plz help
I897UCJF6 - Odin3 One-Click Downloader:
http://www.thevod.org/misc/captivate...l-OCD-REV0.rar
use this to flash back to stock rom.
extract this file
Run the exe file
Boot into download mode
(pull out battery, sim card, ext sd card and put battery back in, press vol up/down button together, connect ur cappy with pc)
press start at odin3
Wait till ur cappy rebooted
Good luck!!
Sent from my SAMSUNG-SGH-I897 using XDA App
tried that already. Can't get the phone into download mode in any way. The problem is windows keeps recognizing it as a mass storage device with the systems32\drivers\usbsstor.sys driver so nothing can recognize it as a samsung device cuz this driver takes priority. I saw that when it booted it wanted to use the std 3 drivers it usually uses but then usbsstor took prescendence. I'm going to try this in a linux enviorment to see if it ignores that windows system driver.
Switching to linux didn't help. I really need help here.
In case it still isn't working, I suggest trying this.
http://forum.xda-developers.com/showpost.php?p=7292801&postcount=26
You need to either reinstall the drivers for the captivate, remove the drivers you have and install others or find a different windows machine.
Or you can use linux + vm ware or linux + virtual box, @dani897 has a thread posted in the dev forum on how to get this working.
Also I have read where some of the people who have downloaded the android sdk for linux had to change the permissions of adb to get it to work
#chmod -x [your path to sdk tools directory]/adb
Also, following this exactly helped me!
forum.xda-developers.com/showthread.php?t=775911
Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance
JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks
Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!
Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....
Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
sivd said:
My Xiaomi mi5 does not turn on.
No lights, fastboot is not accessible, resetting it does not do anything.
Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead.
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fastboot in order to flash the ROM, but is there a way to get to fastboot using my pc? Or even turn the phone on with commands? At the moment ADB and Fastboot does not recognise my phone, is there a way to make it detect it from the state it is in?
Thanks
Click to expand...
Click to collapse
Do you have all the necessary driver installed? I think yes and that is why you are seeing in (COM3) port. You can do one thing, Unplug the phone from PC and Press and Hold Vol Down (-) and plug in again. If not works then you can also Press and HOLD Vol Down and Press and HOLD Power button until you see Fast boot menu. If don't work then try the same thing with Vol UP button. Then you suppose to see a MI phone logo with a USB cable.
"qualcomm hs-usb qdloader 9008" Is a signal of Hard Brick for QCOM devices (Like for LG G2);
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
As you can see here, for fix it you need all partition files, all system files, and a programm
But i dont know if it will works also on SD820, you might need all files for Mi5
Just a question: How did you bricked your phone?
EDIT:
I had an idea: maybe inside fastboot rom you can find all files you need, it might be worth a try, at least you can send it to your shop where you bought it
sivd said:
However, when I plug it into my pc, the devices shows up as qualcomm hs-usb qdloader 9008 (COM3) which is the only sign of life from the phone.
What I want to know is if it is possible for me to unbrick the phone from this situation. I understand that I need to get into fas,tboot in order to flash the ROM
Click to expand...
Click to collapse
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
I also had the same issue with black screen and no responses from vol. & power buttons. But when I notice that in device manger it showed the qcom driver, then I new that there was hope to recover the phone. I can confirm that this will unbrick your phone. I MiFlash'd the China Rom (non-dev), unlocked the bootloader, MiFlash'd MiFlash_xiaomi.eu_gemini_V7.2.13.0.MAACNDB_6.0 rom, sideload lastest stable EU rom, TRWP and SuperSU.
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here:
3: download the latest dev rom from here:
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
sivd said:
Thank you so much, this has worked perfectly and saved me a lot of money! I really appreciate your help, thank you again!
Click to expand...
Click to collapse
Glad you could salvage your device.
Now remember - from great flashing power comes great responsibility ;]
adwinp said:
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fullromdownload.php?d=gemini&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
Thanks for the guide, 1 q tho: what to do when i get the "missed hello packets, try to recover" message?, wait or restart the process?
Ok, solved by disabling driver sign (press F8 during boot)
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Isteran said:
Hello , i got the same problem as described at this topic and here is my problems :
I can't turn on my phone and i can't put it in fastboot mode ( tryed a lot of buttons combinations)
But when i plug it into my pc - it recognizes as Android
I have tryed to install drivers but windows shows mistake and can't install that
When my device connected to pc and i press volume + and power buttons - in few minutes system(WIN 10) recognizes it as ADB interface(can't install drivers too) and i have acess to mi5 internal storage ( i can download photos and so on )
But mi flash doesn't see phone in any mode and i feel that my device is still alive and i can recover it but don't know how....
I will be grateful for any help !
Click to expand...
Click to collapse
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
DrBubblewrap said:
If you can see it in adb, you might be able to see it in fastboot.
Try go in to fastboot (even though you can't see it on screen.)
And try fastboot oem device-info see if you can get anything. Then we go from there.
Click to expand...
Click to collapse
tryed a lot of time to go to fastboot , but nothing happened...
same issue
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
tkrave said:
I've been having the same problem with my MI5, 128gb running MIUI8 6.6.23CN, unlocked bootloader
It started when I did an OTA from 6.6.16, then OTA failed, I tried again this time it downloaded full rom and went into my twrp but installation started automatically. Then it rebooted but the system stayed in black screen. I forced-rebooted it, then everything was fine and I was on 6.6.23. I was using the phone normally for a few hours, then around 6hr later after I upgraded, I took phone out of my bag and it was bricked. I tried everything, no fastboot, no adb, no recovery, no led, nothing on screen. MiFlash reconizes (cuz of the 9008 status) but flash fails. I event opened it up, disconnected the 3 cables from the battery and hold onto power buttons for few seconds to try to drain whatever power it has left in system. Reconnected battery but no change.
I gave up, put phone back in case and was going to ask friend to take it back to send to china for repair the next day, but then I too it out an hour before I go meet my friend and suddenly, phone led flashed red and I see on screen out-of-battery icon. I plugged it in to charge then LED flickered quickly in red for a bit then turn solid red, then turned orange. I let it charged for 10min or so, and pressed power+Vol_Down for few seconds. Lo and behold, I got the bunny on screen and went into fastboot. I was able to re-flash 6.6.23 and phone was good to go again. (but why did removing battery cables do the same thing? Maybe I didn’t leave it disconnected long enough?)
Good story until this part… then 2 days later, I wanted to test MI Talk with friend, I click on it, and phone froze. Both touch sensor light stayed on. I waited about 15 second and forced reboot. Phone vibrates once and then went into hard brick again. Exactly same situation, nothing works.
Now I am waitng for phone to discharge by itself. God knows how many days it will take. It was 96% charged. (1st time I had about 45% and too a day to discharge)
Only if I can get back into fastboot......
Click to expand...
Click to collapse
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
vf1 said:
You don't have to go into fastboot to use miflash if you have stock recovery
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
how do you flash stock recovery if you dont need to go into fastboot? now I am unable to go into recovery or fastboot as the phone does not boot at all. connecting it to PC reconizes the phone as the infamous "Qualcomm HS-USB QDLoader 9008" device.
Its been 4 days and the damn battery hasnt run out yet as I can still plug into pc and get qualcom 9008 to come up. I think I am going to send to china to get it fixed properly if I still cannot get the red flicker of low battery power to come up by tomorrow.
It has happened to me 3-4 times already. It didnt want to boot. No signs of life either. I even sent a message to the shop for sending it back..the only thing that was telling me it wasn't completely dead, was the qualcomm driver ,while on USB connection with the PC, which you are referring to as well
Here is what you could try doing. Try pressing the power button for about 30 seconds at first. If it does not boot, try bending the phone real gently back and forth (don't break it!!). Preferably, hit it gently with your palm while holding it in your other hand.( -- I know it might sound weird --) I noticed that it's shutting down while i have it in my pocket and doing some work which squeezes the phone a bit against my leg.
I came to the conclusion that some connection must become loose when some pressure is being applied to it.. Unfortunately it has to be a design flaw of the phone. Nothing random with yours or mine , in my opinion. // I have a case and tempered glass installed as well since the first minute I got it in my hands..
Sent from my MI 5 using XDA-Developers mobile app
Thanks for the tips Takkaros. I tried what you said but nothing changed (though I was a bit scared to bend it too hard). 1st time it happened to me, I had around 40-50% battery and somehow battery completely drained 24hr later so I got the red blinking low of battery light and was able to charge the phone up and go back into fastboot, which solved everything. this time it happened when I had 96% battery(which I knew cuz I was using the phone, then clicked MI Talk and phone froze, then bricked). I wish there is a way for me to force a battery drain without opening it up. I did opened it up once(on the 1st brick) and disconnected the 3 battery cables, but it was still in brick state when I put everything back.
The qualcomm 9008 driver detection was also my concern about sending back the phone. Chances are by the time my phone reaches the repair shop, battery is completely dead and they simply charge the battery then flash a stable rom and send it back to me without changing out the motherboard or whatever. Which in such case it will be faster for me to just wait a week or two and do myself, instead of shipping it to china and wasting shipping cost and probably will take 4-6 weeks.
I am not sure whats wrong with this phone. Sometimes it turns off while i have in on charge at night, with the Green led lighting. I can get into recovery mode but all the partitions are missing. I cant wipe anything and all my files are not there. If I restart the recovery 2-3 times everything comes back to normal. Maybe there is something wrong with the flash drive. If honorbuy replied to my messages i'd sent it back to them asap. This is not a reliable phone for daily use
Sent from my MI 5 using XDA-Developers mobile app
Try using mi flash. Follow the instruction
Sent from my MI 5 using Tapatalk
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
tkrave said:
I am sending back the phone to china to have them "fix" it. Not sure what they will do, hopefully they either swap me a new phone or swap out the motherboard or something. I just hope they dont just boot into fastboot (after battery completely drained and system resets) and flash new rom and send it back to me.
Probably will take a month or so. Good thing i still have my old phone.
Click to expand...
Click to collapse
This happened to me recently. I used mi flash and the global 7.2.4 stable fastboot rom to get it going again. Wouldn't work for me with with with newer versions. Think edl has been disabled on them.
Hello everyone,
It seems that my worst nightmares came up, and got my device bricked while trying to flash it to a stock ROM (had a custom multilingual ROM installed by the chinese seller), and now it's in a strange stage, as Windows detects the Qualcomm port, but adb can't see it.
The adb devices list is in blank, and QPST detects everything, but when trying to flash the device, the error message on the screenshot appears.
Also tried to do it with MiFlash, but didn't worked too.
Any idea about how to solve this?
Thank you in advance for your help.
P.D.: My device is in black screen, so no menu or anything.
P.D.2: Already downloaded the Android SDK in order to try it's ADB, but it didn't worked too.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Zukunft said:
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Click to expand...
Click to collapse
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Noggin said:
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Click to expand...
Click to collapse
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
arif_kholid said:
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
Click to expand...
Click to collapse
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Noggin said:
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Click to expand...
Click to collapse
i've already tried xiaomi deep flash cable, and its work on my z2 plus, that's how to force phone into 9008 mode.. and also, dont add space between folder names where your firmware files there or there will always sahara fail
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Well, finally, I talked with the aftersales dpt from the shop where I got the device, and returned it, and incredibly it seems it was defective.
The guy from the tech dpt said that it wasn't supposed to die that way, so they returned me a brand new device, and fortunately it's up to date with ZUK's last official ROM.
Thank you everyone for your ideas and help, now I can enjoy this great device
My Zuk Z2 plus got stuck after TWRP, I need help badly.
sirmclord said:
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Click to expand...
Click to collapse
I will tell my issue
I bought this device this July month, I was encouraged seeing you guys did a lot of flashing, I thought I could flash myself but it became a nightmare now.
I am not that much technical so please bare my usage of words below, but I need a real help.
I was doing the basic TWRP for getting the AICP ROM 12.1 but after wiping the data from TWRP my device doesnt get recognized for the Sideload and I did whatever I can but it doesnt detect my phone, so I am having a screen with Start "Green" which is showing the device status as unlocked and when I click on Recovery it goes to the Zuk logo and doesn't have any sign after that.. stuck really
I tried using QFIL but my device detects as 900H but not 9008 also adb doesn't detect my device at all after this.
I think I really did a hard brick of my device.
I dont want to loose hope, I want your help really badly.
For those of you who had the same problem don't give up! I was in that same situation and I solved by putting my phone on EDL via this method
https://www.youtube.com/watch?v=2m44xKog-dI
After plugging the phone for the second time and QFIL recognize as EDL mode I clicked on download content as fast as I could so it started to flash the ROM that I spent like 10h trying to figure a way to do it lol. Anyways, the procedure is the same as putting into EDL via adb fastboot, the only difference is that you make it through a "fake" deep flash cable as that guy in the video shows.
An unrooting attempt gone wrong has left me with a phone that will only tell me that it is corrupt and will not boot.
Is there anything I can do?
Before I am redirected to this thread I should provice some information:
My device cannot go into fastboot mode and is undetectable by any PC (win or linux)
This happened when locking the boot loader via adb on a linux machine
I have tried xperia companion but as my phone cannot connect to any PC this has not worked
The phone is in otherwise perfect shape
A long hold on the power up and on button still lets me vibrate the phone three times in quick succsession
So, I manged to get around this with a simple driver update. It took a bit of fudging after that using flashtool but some how it worked. I wont question why. Mods feel free to delete this thread.