I tried all methods ( PC / Apk Software ) But phone is unable to root.Also tried with fasboot process but it shores device not found.Kingroot is also not working.Please make a software in which i can root ZUK Z1 .... My device have CYANOGENMOD 12.1-YOG4PAS9IG
.
Please i really need to root.Help me experts.
AkshaySungat001 said:
I tried all methods ( PC / Apk Software ) But phone is unable to root.Also tried with fasboot process but it shores device not found.Kingroot is also not working.Please make a software in which i can root ZUK Z1 .... My device have CYANOGENMOD 12.1-YOG4PAS9IG
.
Please i really need to root.Help me experts.
Click to expand...
Click to collapse
Hello, if your phone cannot be recognized by fastboot you need to turn on oem unlock from dev options and make sure you have the right drivers on your pc and firewall is off.
Try this drivers https://drive.google.com/file/d/0B4Zy8uoEfFKLbDlYS0lOYlJPd2s/view?usp=drivesdk
Or this
https://drive.google.com/file/d/0B4Zy8uoEfFKLSC0wNXhaRVRWWEk/view?usp=drivesdk
The fastboot method works flawlessly :good:
AkshaySungat001 said:
I tried all methods ( PC / Apk Software ) But phone is unable to root.Also tried with fasboot process but it shores device not found.Kingroot is also not working.Please make a software in which i can root ZUK Z1 .... My device have CYANOGENMOD 12.1-YOG4PAS9IG
.
Please i really need to root.Help me experts.
Click to expand...
Click to collapse
Just start your computer with 'Disabled driver signature reinforcement'. Then install adb. I guess, your computer is not taking ADB drivers due to it's signature.. So disable driver signature reinforcement and see if the fastboot method works.
Ps- It's just a "might work"- solution!!
Related
Hello, I've tried posting my problem elsewhere on xda without response so I'll give it a try in here. My phone shows the sony logo then reboots infinitely after rooting it and I searched everywhere for a solution but all I could do is get this message on flashtool:
06/056/2015 17:56:00 - INFO - Loader : S1_Root_2f8b - Version : MT6582_15 / Boot version : S1_Boot_MT6582_TC9SP_11 / Bootloader status : ROOTED
06/056/2015 17:56:00 - INFO - Transfer buffer size : 262144
06/056/2015 17:56:01 - INFO - You must have the according fsc script to flash this device.
06/056/2015 17:56:01 - INFO - Flashing finished.
06/056/2015 17:56:01 - INFO - Please unplug and start your phone
06/056/2015 17:56:01 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
It should be a driver problem but I have already installed adb drivers, specific drivers for e4 from sony website and flashtool, fastboot and jdm drivers from flashtool. I also tried switching usb ports and trying on other computers with the same results, and I'm 100% sure unknown sources and debug mode were checked last time the phone was in working condition.
I tried installing all drivers from flashtool's driver folder as well, still nothing. I dunno if it's relevant but the device is recognized as somc flash device in device manager. I'm using flashtool 0.9.19.0 as I read somewhere it works better for the e4 dual (even if it doesn't for me) and the latest version gives an IO exception error.
Any expert who can help me with the problem?
Edit: Bootloader is unlocked but the problem was the same before unlocking
Is there really no way of fixing my phone? Please help. . .
Anyone?
Can someone enlighten me? Now the battery is dead too... phone won't charge anymore.
ZeroJoe said:
Can someone enlighten me? Now the battery is dead too... phone won't charge anymore.
Click to expand...
Click to collapse
too bad i didn't see this thread previously.
hello friend,
I too have the same problem now.
i tried to change the build .prop and ended in bootloop today.
i have a similar message
"16/028/2015 15:28:57 - INFO - Please connect your device into flashmode.
16/029/2015 15:29:08 - INFO - Device disconnected
16/029/2015 15:29:13 - INFO - Bootloader unlock canceled
16/029/2015 15:29:50 - INFO - Device connected with USB debugging off
16/029/2015 15:29:50 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I tried to change the usb debugging settings through adb ,it is not working.
the internal storage and sdcard are not mounting. :crying::crying:
I think we will have to get help from sony support and the thread Xperia E4 Development by LeonXperiaXC
Did you try out the sony pc companion ? it is supposed to work as my device has a locked boot loader . but it is not working either.
dushandiaz said:
Did you try out the sony pc companion? it is supposed to work as my device has a locked boot loader . but it is not working either.
Click to expand...
Click to collapse
Yes I did that, device not supported, and that was even before I unlocked the bootloader.
I gave up fixing it some days ago, seeing that neither sony nor xda helped, and I can't afford a new one for now. Please let me know if you do manage to fix it, as I will check here from time to time, good luck to you.
ZeroJoe said:
Yes I did that, device not supported, and that was even before I unlocked the bootloader.
I gave up fixing it some days ago, seeing that neither sony nor xda helped, and I can't afford a new one for now. Please let me know if you do manage to fix it, as I will check here from time to time, good luck to you.
Click to expand...
Click to collapse
As i couldn't fix the device,I gave the phone to the service center.they had fixed it .I will be getting the device on moday. :fingers-crossed:
By the way,i found some interesting fact why unbricking didn't work for our E4.
sony pc companion unbricked my previous device xperia E1,it is a snapdragon device.
I think mediatek devices can't be unbricked by sony pc companion and also flashtool by androxyde.
Xperia C cannot be unbricked by the both as well.it is a mtk 6589 device.
Xperia C has an unbrick method using a tool/software called WMshua perfect flash.
https://www.informationlord.com/ultimate-guide-to-fix-bricked-xperia-c/
I didn't try it because i was scared of hard bricking the device.
I think it might work.
plus for chinease mediatek devices there is another tool called spflashtool.
also learn to use the spflashtool .there is a begineers guide at mtkroms.com
http://www.mtkroms.com/2015/02/how-...howComment=1447795342637#c6494565355265496004
give it a try.
If you have warranty definitely get it repaired by the service center.
or try the above methods if you have no choice.
I hope you will get your device working as soon as possible. :good::good::good::fingers-crossed::fingers-crossed::fingers-crossed:
Good luck.
ZeroJoe said:
Is there really no way of fixing my phone? Please help. . .
Click to expand...
Click to collapse
Did you try to restore with pc companion
1.Open back case and found OFF lockup using pen shutdown the bootloop
2.Open pc companion then support zone
3.click update my phone
4.click restore phone/tablet
5.then choose Sony Xperia E4 dual (E2115) because i connected
or if you not connected preess other phone/tablet then Choose E2115
6.after downloading firmware and getting ready
7.Make sure you have 80 % of charge
8.Start you phone in Flashmode PWR+VOL-
9.Wait
10.prrrrooooffffiiiiiitttt!!!!!!
AND NOTE SP FLASH TOOL NEVER FLASH SONY XPERIA WITH MTK EXPECT FAKES
Hi! I have sony xperia e4 E2105 and yesterday it went into bootloop. I tried to flash stock firmware but the version I have doesn't see the tft file so I downloaded older version of flashtool and it recogniznes tft file but when I try to flash it says that it can't open bundle . I dont have custom recovery .Please help me!
Thank you
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
racker16 said:
Click to expand...
Click to collapse
Which commands you using for bootloader unlock?
strongst said:
Which commands you using for bootloader unlock?
Click to expand...
Click to collapse
fastboot -i 0x2b4c oem unlock- go
I was using right command
racker16 said:
fastboot -i 0x2b4c oem unlock- go
I was using right command
Click to expand...
Click to collapse
Without the space between oem and go?
fastboot -i 0x2b4c oem unlock-go
strongst said:
Without the space between oem and go?
fastboot -i 0x2b4c oem unlock-go
Click to expand...
Click to collapse
Yeah I have used this also but same ,
Waiting for device
racker16 said:
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
Click to expand...
Click to collapse
in developer options (in settings) make sure both oem and usb debug are ON
CoreKido said:
in developer options (in settings) make sure both oem and usb debug are ON
Click to expand...
Click to collapse
Its already on that time
racker16 said:
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
Click to expand...
Click to collapse
Buddy try this tool
http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563
It's been years for you to hear this problem (hard brick)
I have a hard bricked yureka .I have gone through the thread which have posted in in xda and yu forums
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://forums.yuplaygod.com/threads/project-reviving-hard-bricked-yu-qloader-9008-mode.10236/
my problem is different form the cases that I read in these threads
In my case the mobile
* is not deducting in Windows*
*it goes to fastboot mode*
*it gets rebooting when connected to windows or charger*
*stable when connected to Windows in fastboot mode*
*during normal start up it goes to fastboot mode and starts rebooting *
*when connected to Windows in fastboot mode the device manager shows it as unknown device under USB*
anyone plz guide me to understand brick my yu....
plz help me .....I'm ineeded of help
I have attached the picture and videos for ur consideration
the link of the Google drive
https://drive.google.com/folderview?id=0B3JWgilAzvw0TjZRb0ZyZDB1Qkk
Install drivers
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Santhosh Rasa said:
It's been years for you to hear this problem (hard brick)
I have a hard bricked yureka .I have gone through the thread which have posted in in xda and yu forums
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://forums.yuplaygod.com/threads/project-reviving-hard-bricked-yu-qloader-9008-mode.10236/
my problem is different form the cases that I read in these threads
In my case the mobile
* is not deducting in Windows*
*it goes to fastboot mode*
*it gets rebooting when connected to windows or charger*
*stable when connected to Windows in fastboot mode*
*during normal start up it goes to fastboot mode and starts rebooting *
*when connected to Windows in fastboot mode the device manager shows it as unknown device under USB*
anyone plz guide me to understand brick my yu....
plz help me .....I'm ineeded of help
I have attached the picture and videos for ur consideration
the link of the Google drive
https://drive.google.com/folderview?id=0B3JWgilAzvw0TjZRb0ZyZDB1Qkk
Click to expand...
Click to collapse
Parkadhe Anna said:
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Click to expand...
Click to collapse
thanks ... I will try and reply the results ...
Parkadhe Anna said:
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Click to expand...
Click to collapse
thanks ... I will try and reply the results ...
Hy bro.
I m having same problems two days ago.
I found the solution which issuccessfully working for me. First : downloade the universal necked driver (google it mostly found on google nexus 5 thread).
Second : change ur phone's battery. Get a new battery.
Third : remove ur batterry. Reinsert ur battery. Press volume down & connect USB cable u see the fastboot mode release volume down. Then go to device manager in ur computer and search unknown driver. Right click on it and select update driver update it manually ( google it how to manually update driver) browse the necked driver & select winusnb.inf then select Asus fastboot interface ur device got connect. Now flash official stock cm11 firmware through ygdp tool. That's it. Sorry for my bad English.
I am facing an issue. I want to flash twrp into my coolpad cool 1 dual but my fastboot can't detect my device. ADB is able to detect it but as soon as I run the command "adb reboot bootloader" to boot my phone into fastboot mode fastboot doesn't detect my device any more.. I have tried updating the "android bootloader interface", " android adb interface" drivers but still nothing does work.. Tried a various types of usb driver available at xda in various threads but none work. What to do now? Please give me a solution to install twrp~
I got the same problem here, I installed a lot of several drivers and nothing. I keep surfing on the web trying to find a solution. If i get one I will notice you.
Gausskun said:
I got the same problem here, I installed a lot of several drivers and nothing. I keep surfing on the web trying to find a solution. If i get one I will notice you.
Click to expand...
Click to collapse
Good luck! My coolpad is already dead.
souvik095 said:
Good luck! My coolpad is already dead.
Click to expand...
Click to collapse
Same here.
Now i have no recovery, no system (ROM), and no EDL mode too.
Fastboot mode runs partially, with errors (REMOTE ERROR blablabla).
sad :crying:
I have already ripped apart the device. Took out the battery made an led emergency lamp out of it. The rest of it lies in some corner of my workshop!
Install pdanet in pc and mobile both
Hey guys i just updated to firmware 327 from 326.. I am using fully stock rom with locked bootloader.. I wanted to unlock bootloader but was unable to do so.. Whenever I try to run the unlock.bat file the black cmd screen remains stuck and nothing happens.. Plz help me i wanna try few roms so help me to unlock bootloader (6gb variant)
Is this because of the latest firmware??
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
andriyhar said:
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
Click to expand...
Click to collapse
Bro official unlocking method will void warranty even after i relock my bootloader later right? So i wanna do it the unofficial way so i can relock bootloader and go back to stock if I wish and would get ota updates
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
Yes it's detected.. Bt the black cmd screen gets stuck while unlocking
Any solution guys plz need help
try using cmd prompt in administrator mode....
ujilraj said:
try using cmd prompt in administrator mode....
Click to expand...
Click to collapse
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Well, I am not an expert in this. It should just work. And the Windows 10 thing is absurd. I am using Windows 10. Plus, development mode is not enabled in my laptop.
Credits to the following -
@Sudeep Duhoon for this guide - [UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
ASUS for phone, drivers, rom, this and that
Mod edit. Link removed. Reference: https://forum.xda-developers.com/one...rward-t3765018
@Saktis_STi for raw factory rom
@Shivam Kumar Jha for fixing the script
@Sujeet Ranipa for drivers link
@esashwin for testing
Use unlock.sh instead of unlock.cmd
If the phone is indeed detected in fastboot mode using
Code:
fastboot devices
, try running the script from unlock.sh instead of unlock.cmd.
I have not been unable to flash fastboot stock ROM from this laptop using the .bat file but for some reason, .sh file works fine.
Just install Git on windows. It will give you a wrapper to run shell scripts on your windows machine (Git BASH).
Again, I am not an expert. This might not work but at least it won't corrupt anything.
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
_uchihaitachi_ said:
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Click to expand...
Click to collapse
Try anyother pc
Many users solved unlock problems by changing pc
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
Ok bro thanks for help.. Will try on another pc coz my pc has only 3.0 and 3.1 ports ?
iamfarhanansari said:
Try anyother pc
Many users solved unlock problems by changing pc
Click to expand...
Click to collapse
Ok bro thanks for help
Phone is not detected.
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
I have this same issue my phone is not detected.
Please help.
I too have same problem
C:\>cd unlock
C:\unlock>fastboot devices
J7AAGF02D693CWW fastboot
C:\unlock>unlock
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
Solution to unlocking bootloader where screen blacks out on flashing
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
I had the same issue, after reading to many webpages, stumbled on this official unlock tool apk. Once the bootloader is unlocked using the app, the phone reboots into ASUS UNLOCK MODE with device status as unlocked and message to restart the phone. Heres the catch this is already the fastboot mode so flash TWRP at this stage. If you restart the phone in fastboot before flashing twrp, on running the flash cmd the screen of your phone would black out with a message "press any key to shutdown". Hope this helps.
unlock tool apk
then how do I install that official unlock tool in fastboot mode. since I can only access CSC FASTBOOT MODE.