Related
Hello Everyone,
I was running fairly stock with root and kept getting the upgrade firmware message, I decided to finally upgrade it using Kies through Windows 7 on another computer and it's all loaded up nicely. Problem is now I can't use Titanium Backup to restore my files and apps. I'm now using Ubuntu.
Can anyone guide me through gaining root on the T-Mobile Samsung Galaxy Note 1 SGH-T879 using Ubuntu only?
This phone was rooted before. Previously I had attempted to load a ROM and didn't full wipe per instructions and was stuck on the loading screen. I used Kies on windows to emergency repair all that jazz. Now I have the most up to date official ROM from T-Mobile/Samsung.
I've had minor successes, this is what I"ve done so far:
a. I installed/updated the android SDK
b. I'm fairly certain I updated libusb correctly as well
c. When the phone is on and in developer mode I am able to use 'adb devices' to get a positive listing of the device. 'fastboot devices' does nothing.
d. I installed heimdall 1.3.1. I didn't not install 1.3.2 because others were having issues and even the developer says to stick with 1.3.1.
e. 'adb reboot-bootloader' just reboots the phone. Same with 'adb reboot bootloader' and 'adb reboot recovery'
f. To put into download mode I had to mess around as the standard instructions don't work. This is what I did:
pull the battery and power cable, with everything out press the power button to dissipate any power
put the battery in and plug in the micro usb cable
wait until the BIG pretty battery icon on the screen shows that it is charging
hold the Volume Down button securely
Press and hold the Power Button until the phone vibrates, release the Power Button but continue to hold Volume Down
the Warning screen pops up, press Volume Up to Continue
g. From here 'adb devices' doesn't show a device connected.
h. I tried to make the flash happen anyways. With and without 'sudo' I entered 'heimdall flash --recovery recovery.img' using the CWM recovery listed in the Goodies thread.
Any other suggestions as to why this wouldn't work?
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.
i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second
aljthab said:
i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second[/QUOTE try connecting it to the PC, if it doesn't show anything on PC then just hand it over to the lenovo service center and blame it on the device that it stopped booting :silly:. I thought i had bricked my device but they did something and gave it to me in 3 to 4 days and that was done under the warranty no extra charge and don't confess that I had rooted ur device , If u tell them that they will try to extort money from u :crying:
Click to expand...
Click to collapse
aljthab said:
i did something Stupid and my Z2 Pro dead
e LED there is flash yellow for 0.1 second
Click to expand...
Click to collapse
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english
kerei said:
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english
Click to expand...
Click to collapse
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
same issue with zuk z2
adriano1593 said:
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
Click to expand...
Click to collapse
Hello there... Any solution you found? I am stuck with my zuk z2 in same situation ?? any help ?
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk
eryenakgun said:
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your quick response.
The Hardware ID: USB\DEVICE_DESCRIPTOR_FAILURE
"Error Message": This device has been stopped because it has reported errors. (Code 43)
An error occurred while requesting the USB device descriptor.
m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot
OtakuLi said:
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot
Click to expand...
Click to collapse
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"
m_atze said:
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"
Click to expand...
Click to collapse
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them
OtakuLi said:
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them
Click to expand...
Click to collapse
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I don't want to destroy my PC (3000 bugs)
m_atze said:
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I won't destroy my PC (3000 bugs)
Click to expand...
Click to collapse
oh well, good luck
OtakuLi said:
oh well, good luck
Click to expand...
Click to collapse
I will report the result.
OK. I made the deepflash cable.
After using it there is no difference between pressing one of the button combinations I recently mentioned (VOL+ or VOL- or PWR).
The phone will be detected as Unknown device. After intalling my modified driver to match the unknown ID, QFIL don't detect the COM Port.
Hello had the same problem, only with the difference that my battery was not completely discharged.
What has helped:
1 Start QFIL Tool
2 Press the volume +
3 Connect the original cable to the PC
4 QFIL Tool recognized the phone and I could play an original Rome.
Mfg
Ps. Is now the battery cover (glass) broken?
No, I used a hairdryer, a razorblade, plastic tool and a suction cup to lift the backcover glass.
The glass is fully intact no damages.
You have good nerves. I would not have expected that.
But in the end, it does not matter if it does not start anymore.
Thank you again for your great instructions for playing and rooting the mobile phone.
I hope you get your phone back.
Mfg
Good and bad news
The guy unbricked the phone successfully, I received it today.
Now I have an other problem:
The phone is very very slow and laggy now.
The problem occurs everywere, Recovery, boot (the bootlogo laggs), booted System, also the test mode laggs now
Furthermore the sceen flickers sometimes and at the right side the sceen is mirrored sometimes.
Did anyone has an idea?
What I did today:
reflash through qfil
1.9.104_ST
2.3.044_ST
ZUI_2.5.335_ST
Hi m_atze, I am exactly in the same situation as You. After using deep flash cable method, I got "unknown usb device (device descriptor request failed)". Could You tell me what was the solution to unbrick the phone?
Hey all,
I have Zuk z2pro z2121. I wanted more than stock ROM so I downloaded zui 2.5.344. I unlocked bootloader n rooted my phone as well as installed TWRP. "Tool All in one" PC software helped me to carry out above with ease.
While playing around I clicked "Lock Bootloader" and phone got switched off with indicating continuous blue light. I tried pressing vol down + power + Home button, and several other combination but didn't help. When I pressed power button for long, I got Zuk logo onscreen with a white flash on indicator for 1 sec and then again the blue light indicator.
After a little RnD after pressing power button till I got white flash for 3 times and the blue light got completely off. I don't know what to do further. I have backup of my boot , recovery and ROM. Kindly suggest.
Shoaib
Press and hold volume - and power . Release power, after vibration you can release the volume -. You will be in that menu https://ibb.co/f3vOHm . Go to device manager and check if pc recognize your phone https://ibb.co/bHqZOR . Open CMD in adb folder and write adb devices https://ibb.co/cwCg3R . Then adb reboot edl . You are i EDL https://ibb.co/cvjiHm . Use Qfil to flash stock rom
Didn't work...
Thanks for responding. As said, tried pressing Vol + Power and never got any vibrations. Tried Up vol + power, tried Down vol + power. No vibrations.
When I press power button with any combination, this is what happens,
After Approx 15 secs - 1 white light flash in place of blue along with ZUK pic on d display (stays approx 1 sec)
Still keeping power button pressed
After approx 7-8 secs - same as above
Still keeping power button pressed
After Approx 15 secs - 1 white light flash in place of blue along with ZUK pic on d display (stays approx 1 sec)
But now after this third time of flash, blue light appears and after 4-5 secs disssappears. If I leave the button only at this time, the blue light doesn't comes back.
If I leave the power button before or after this sequence, the blue light doeanon the indicator doesn't goes off at all.
What is happening when you connect phone with pc ? Is there any reaction ?
No reaction from PC.
I tried connecting to PC, earlier Tool all in one immediately use to detect, n now there is no response from the PC or the software after making USB connection.
Sir,
As I said earlier, I clicked lock bootloader, n when the screen went off, I disconnected the phone from PC. There is a possibility of the boot partition getting damaged or so. Kindly assist.
Rgds
There aren't any ways to enter in fastboot or recovery , even in service menu . I think you should try deep flash cable to enter in EDL .
Will do as u say. Just one last thing, when I checked device manager in my PC, it showed the phone as other devicez "QUSB XXXX". Question is,
1. Any possibilities of recovery without going for a deep flash, as I got to learn it first.
2. Other part is, my phones battery seems to be drained now. So, it won't be a problem for a deep flash.
Could you give some print screen ?
The matter is that you must switch your phone to edl . Try this yet . Your phone must be turn off .
Press only volume up button for 10 sec and while keeping it pressed,connect phone to PC . Hold volume up until your PC finds a new hardware . It should be android phone - ShenQi composite adb interface . If it doesn't work I have no more ideas apart from df cable . This cable works on Zuk z2 and I think it should works on our Zuk z2 pro
Sir,
I managed to connect the phone via USB as 9008. Miflash not supporting my ROM. Will download Stock ROM n then try with QFIL and MiFlash as well. Thanks for all your support. Will keep u posted about the progres. XML file is not found in any ROMs I have. Miflash some error also but detecting the device. Is there any other tool similar to Miflash, which I can try..
Rgds
First use QPST/Qfil . Follow this guide https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Do all steps .
Good day.
I tried QFIL as well as Mi flash tool. Both showing errors. QFIL displaying Qualcomm HS USB QLoader 9008. But when downloading content , it shows Sahara error with even initiating the installation. After browsing a bit, started eMMC software download, and found displaying COM20 No phone connected. Can u assist me to fix this. I mean the phone must be in download mode. But how ?
Miflash, on the other hand shows Hello packet error. Don't know how to fix.
Things I did to fix above errors,
1. Copied ROM to Qualcomm/ bin file
2. Copied ROM to C:/
3. Tried using different USB ports
4. Tried different USB cables
5. Uninstalled n reinstalled USB driver, adb n fastboot, qpst, n miflash many a times along with restarting my PC.
None of the above helped.
I think, if eMMC software download starts displaying COM20 Phone connected, then the issue might be sorted out.
Kindly assist.
Rgds
DrTahseen said:
Good day.
I tried QFIL as well as Mi flash tool. Both showing errors. QFIL displaying Qualcomm HS USB QLoader 9008. But when downloading content , it shows Sahara error with even initiating the installation. After browsing a bit, started eMMC software download, and found displaying COM20 No phone connected. Can u assist me to fix this. I mean the phone must be in download mode. But how ?
Miflash, on the other hand shows Hello packet error. Don't know how to fix.
Things I did to fix above errors,
1. Copied ROM to Qualcomm/ bin file
2. Copied ROM to C:/
3. Tried using different USB ports
4. Tried different USB cables
5. Uninstalled n reinstalled USB driver, adb n fastboot, qpst, n miflash many a times along with restarting my PC.
None of the above helped.
I think, if eMMC software download starts displaying COM20 Phone connected, then the issue might be sorted out.
Kindly assist.
Rgds
Click to expand...
Click to collapse
U need ufs flash not emmc. Change programmer in qfil.
I have a some experience with miflash but I use it for xiaomi . I've never flashed my zuk z2 pro by miflash . If you want to use miflash use 2016.03.30 and run it on PC with win 64 . Create a folder on c: for example "zuk" and copy to that all contents of unrar Qpst/Qfil zui rom . If you have Qualcomm hs usb 9008 that means your phone is in edl ( download mode ) . Good luck
I appreciate all ur support....
As suggested, tried Miflash 30.03.2016 also. This ones showing class not registered.
No of things i did to overcome this errors.
1. Changed my PC to developer mode. Allowed portable device connections n stuff.
2. Visual studio C++ 2010 was installed along with Qualcomm driver, i believe thats sufficient.
3. Disabled my Firewall.
4. Downloaded n copied some atl70.dll file to my syswow64 folder as well as sys32 folder.
Tried all flash tools again after these changes....Same negative results.
Any further advices !!!
Regards
It's fault of drivers . Go to device manager and chose qualcomm hs usb 9800 and update driver automaticly . The second matter concerning of flashing by qpst/qfil - why did you put rom in qpst location ? . It must be for example on desktop in one folder . The simplest path is better . Don't use spacebar . Load content you must chose from that rom . Don't use other location . It's not necessary . Could you give some screenshots with qfil errors
DrTahseen said:
I appreciate all ur support....
As suggested, tried Miflash 30.03.2016 also. This ones showing class not registered.
No of things i did to overcome this errors.
1. Changed my PC to developer mode. Allowed portable device connections n stuff.
2. Visual studio C++ 2010 was installed along with Qualcomm driver, i believe thats sufficient.
3. Disabled my Firewall.
4. Downloaded n copied some atl70.dll file to my syswow64 folder as well as sys32 folder.
Tried all flash tools again after these changes....Same negative results.
Any further advices !!!
Regards
Click to expand...
Click to collapse
Did u use ufs flash in qfil instead of emmc?
Starchm said:
Did u use ufs flash in qfil instead of emmc?
Click to expand...
Click to collapse
Yups !!! I already did with Meta Build Type selection. Didnt Help. I tried to search for mbn file also to try emmc but cudnt find so was stuck with ufs....
mar.ur said:
It's fault of drivers . Go to device manager and chose qualcomm hs usb 9800 and update driver automaticly . The second matter concerning of flashing by qpst/qfil - why did you put rom in qpst location ? . It must be for example on desktop in one folder . The simplest path is better . Don't use spacebar . Load content you must chose from that rom . Don't use other location . It's not necessary . Could you give some screenshots with qfil errors[/QUOTE
https://forum.xda-developers.com/attachment.php?attachmentid=4339940&stc=1&d=1511421690
https://forum.xda-developers.com/attachment.php?attachmentid=4339941&stc=1&d=1511421690
https://forum.xda-developers.com/attachment.php?attachmentid=4339942&stc=1&d=1511421690
Click to expand...
Click to collapse
I've searched and tried most guides/fixes for adb but it fails to work when i start the phone up while holding the volume up button. The light will turn blue, and one sony fastboot driver will show on device manager but nothing else. If i turn the phone on, there is a sony adb tab with the driver and the device will show up on adb devices, but as soon as i use adb reboot fastboot it just reboots normally without going into fastboot.
latest firmware, installed android sdk,android studio, reinstalled every usb driver multiple times, downloaded xperia compact drivers from sony themselves etc. It's a ***** on a computer without a ssd.
Will provide pictures and/or videos if problem isn't apparent from description. Thanks in advance