ZTE Grand SII LTE (S291) - ROOT , RECOVERY, install GApps - Android General

Hi, folks
I want show you a tutorial how to easy do ROOT and install RECOVERY and then gapps , with a simple tool.
The tool is in Chinese, but you need only to click few times.
Let’s start:
1. Plug your phone to your PC and on the phone choose the option Install driver:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Then install the drivers to your PC.
3. Now on your phone go to setting/ developer options and choose the option USB debugging on.
4.Download the ROOT TOOL from here: http://d-h.st/8Ma
5.Unpack it and run it with administrator rights.
6.Make sure your phone is connected and you have at least 20% battery, Click on the first option on the right site.
you will see this massage don’t click on anything
7. Now wait , your phone will restart and you should see the SUper user app in your apps.
In the tool click on OK
8.Lets continue with the RECOVERY installation. Click on the second option:
9. The same massages will appear ,do the same like on the earlier steps , just wait...
10. Your phone should now boot into recovery , click on the first option - this will reboot your phone
11. If you want google apps continue. Download gapps from here: http://goo.im/gapps/gapps-jb-20130813-signed.zip
12. Put the zip into the root of internal memory.
13. Turn your phone off and enter the recovery by holding volume up + power button until the phone vibrates , then release the power button.
14. You are in recovery now , go to the second option , than choose the first option , select your file , than choose the first option, this will install the google apps.
15. Now leave the recovery.
16. ALL done
I wish you luck
all credist go to myzte.cn
EDIT: REUPLOADED SCREENSHOTS

good,thanks
Sent from my ZTE Grand S II LTE using XDA Free mobile app

5KKKKK said:
good,thanks
Sent from my ZTE Grand S II LTE using XDA Free mobile app
Click to expand...
Click to collapse
You are welcome
BTW , when the next update is out version B07/B08 (i hope it is the big 4.4 update) , i will modify the ROM- with deleting the chinese apps , replacing chinese email , gallery, camera apps to original google one. So mostly stock

I like this phone,but the main problem is it has few ROMs,it seems that zte is not very popular
Sent from my ZTE Grand S II LTE using XDA Free mobile app

Danger ahead
Hello everybody,
I wanted to warn you, I followed this guide and after doing the root procedure my phone is bricked DEAD.
Won't turn on, won't do anything, not even charghing when power plug is connected, I just killed my phone after about 30 minutes of ownership. :/
PLEASE WAIT A LITTLE BIT BEFORE DOING THIS.
My phone is a grey ZTE Grand S II (NBA Edition, from what I see on the box...).
Does anybody here have an idea HOW I could get this back from the dead? :angel:
*** UPDATE ***
I was able to make it work!! Sorry for sounding so alarmed before... I was in panic mode.
If this doesn't work at first please try it on another PC, or switch USB port, and make yourself a big favor by using this:
http://visualgdb.com/UsbDriverTool/
to install your Android ADB driver.
The ZTE Grand S II (S291) is a GREAT handset and I hope the devs get interested because it's one of the BEST prcie/value ratio around...
Got it for 280 € on Aliexpress...
Thank You.
S.

Simmessa said:
Hello everybody,
I wanted to warn you, I followed this guide and after doing the root procedure my phone is bricked DEAD.
Won't turn on, won't do anything, not even charghing when power plug is connected, I just killed my phone after about 30 minutes of ownership. :/
PLEASE WAIT A LITTLE BIT BEFORE DOING THIS.
My phone is a grey ZTE Grand S II (NBA Edition, from what I see on the box...).
Does anybody here have an idea HOW I could get this back from the dead? :angel:
Thank You.
S.
Click to expand...
Click to collapse
Oh , that's not good , but no one bricked the phone to time...
But please look at the titile, have you the ZTE GRAND SII (s251) or the ZTE GRAND SII LTE (s291) because they're completely different phones.

Difference?
Hello Jozco,
I don't know, but I finally managed to get it back from the dead, by removing the battery and re-connecting it to the power plug, I can now turn it on again...
In About phone under model number it says ZTE S291.
I found something strange, when I issue a "adb reboot bootloader" command the phone goes off and dead, I have to detach the battery to be able to turn it on again... any ideas?
The phone has a NBA logo on the box, a gray cover, and I got it here:
http://www.aliexpress.com/snapshot/6097854185.html
Do you have any clues, I'm going crazy...
THANKS!
S.
jozco313 said:
Oh , that's not good , but no one bricked the phone to time...
But please look at the titile, have you the ZTE GRAND SII (s251) or the ZTE GRAND SII LTE (s291) because they're completely different phones.
Click to expand...
Click to collapse

Simmessa said:
Hello Jozco,
I don't know, but I finally managed to get it back from the dead, by removing the battery and re-connecting it to the power plug, I can now turn it on again...
In About phone under model number it says ZTE S291.
I found something strange, when I issue a "adb reboot bootloader" command the phone goes off and dead, I have to detach the battery to be able to turn it on again... any ideas?
The phone has a NBA logo on the box, a gray cover, and I got it here:
http://www.aliexpress.com/snapshot/6097854185.html
Do you have any clues, I'm going crazy...
THANKS!
S.
Click to expand...
Click to collapse
Oh so , that’s seems to be only a ADB driver problem, had it also , because i had a lot of phones to flash , my drivers were mixed up...
just download this: http://visualgdb.com/UsbDriverTool/
install it , open it , plug your phone to the pc , you will see ZTE Handset ADB Interface click on it and under Android ADB driver click install , this will install the universal ADB driver it should work.
I hope we get your phone rooted

I did the steps you suggested but that didn't change anything
The driver situation is ok, as you can see from the screenshot, yet, it WON'T reboot in the bootloader.
Whenever I issue a "adb reboot bootloader" it simply dies... and I have to remove battery.
Obviously I can't make fastboot work this way, therefore I can't move further, any tips?
Thank You!
S.
---
jozco313 said:
Oh so , that’s seems to be only a ADB driver problem, had it also , because i had a lot of phones to flash , my drivers were mixed up...
just download this: http://visualgdb.com/UsbDriverTool/
install it , open it , plug your phone to the pc , you will see ZTE Handset ADB Interface click on it and under Android ADB driver click install , this will install the universal ADB driver it should work.
I hope we get your phone rooted
Click to expand...
Click to collapse

Simmessa said:
I did the steps you suggested but that didn't change anything
The driver situation is ok, as you can see from the screenshot, yet, it WON'T reboot in the bootloader.
Whenever I issue a "adb reboot bootloader" it simply dies... and I have to remove battery.
Obviously I can't make fastboot work this way, therefore I can't move further, any tips?
Thank You!
S.
---
Click to expand...
Click to collapse
I mean this:
BTW did you checked USB debbuging , when you have connected your phone in the connection type have you checked Connect to PC software
?

jozco313 said:
I mean this:
BTW did you checked USB debbuging , when you have connected your phone in the connection type have you checked Connect to PC software
?
Click to expand...
Click to collapse
Yes, that's what I did! Then the software asked me to replace adb_usb.ini and perform adb kill-server, which I did...
C:\Windows\system32>adb kill-server
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d70ec4e0 device
I can confirm USB debugging is enabled and my connection mode is "Connect to PC software".
I checked and re-did everything twice and still, adb reboot bootloader makes my phone die: screen black, no lights and won't even turn on unless I remove the battery...
If I'm doing something wrong, I really don't know what it is
Ideas?
S.

Simmessa said:
Yes, that's what I did! Then the software asked me to replace adb_usb.ini and perform adb kill-server, which I did...
C:\Windows\system32>adb kill-server
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d70ec4e0 device
I can confirm USB debugging is enabled and my connection mode is "Connect to PC software".
I checked and re-did everything twice and still, adb reboot bootloader makes my phone die: screen black, no lights and won't even turn on unless I remove the battery...
If I'm doing something wrong, I really don't know what it is
Ideas?
S.
Click to expand...
Click to collapse
I really don´t know :/ , when you can try it on another PC...

jozco313 said:
I really don´t know :/ , when you can try it on another PC...
Click to expand...
Click to collapse
Later today I'll do another attempt with another PC I have at home, but I tend to believe this is related to the ZTE device itself, it's actually very strange that the bootloader is not responding, could it be faulty or simply that the bootloader has been wiped in some way?
I know it doesn't make a lot of sense since the phone itself is booting into ZTE Android just fine... but I'm left wondering, if things continue this way I'm gonna return it and ask my money back...
I'll let you know as soon as I can do some more testing, Thanks a lot for now!
S.

no way...
Simmessa said:
Later today I'll do another attempt with another PC I have at home, but I tend to believe this is related to the ZTE device itself, it's actually very strange that the bootloader is not responding, could it be faulty or simply that the bootloader has been wiped in some way?
I know it doesn't make a lot of sense since the phone itself is booting into ZTE Android just fine... but I'm left wondering, if things continue this way I'm gonna return it and ask my money back...
I'll let you know as soon as I can do some more testing, Thanks a lot for now!
S.
Click to expand...
Click to collapse
I tried again, from another PC with windows 7 32bit but same story again... after reboot it's dead and I must do the battery trick.
Here's my plan:
On my phone there's OS v B04 (please see screenshot)
So I'm planning to install v B06 which I got from ZTE support website...
What do you think? I'm hoping this will fix my broken bootloader!
Thanks!
S.

Simmessa said:
I tried again, from another PC with windows 7 32bit but same story again... after reboot it's dead and I must do the battery trick.
Here's my plan:
On my phone there's OS v B04 (please see screenshot)
So I'm planning to install v B06 which I got from ZTE support website...
What do you think? I'm hoping this will fix my broken bootloader!
Thanks!
S.
Click to expand...
Click to collapse
This is the exact file (ROM) I plan to flash on my device, should I do it?
(please see attach).
Thanks!
S.

Simmessa said:
This is the exact file (ROM) I plan to flash on my device, should I do it?
(please see attach).
Thanks!
S.
Click to expand...
Click to collapse
LATEST update:
I don't know why but I re-did the whole procedure with the second PC and WITHOUT explanation this time it worked like a charme... SORRY for wasting your time, but I'm not even sure WHY this time it worked... the only thing I did was switching a couple of usb ports and using the driver supplied by USBdrivertool (The link can found above in this thread)
So, if you have problems with this procedure PLEASE KEEP THE FAITH and you'll eventually do it!
THANK YOU everybody and especially jozco313 for the help and assistance!
S.

Simmessa said:
LATEST update:
I don't know why but I re-did the whole procedure with the second PC and WITHOUT explanation this time it worked like a charme... SORRY for wasting your time, but I'm not even sure WHY this time it worked... the only thing I did was switching a couple of usb ports and using the driver supplied by USBdrivertool (The link can found above in this thread)
So, if you have problems with this procedure PLEASE KEEP THE FAITH and you'll eventually do it!
THANK YOU everybody and especially jozco313 for the help and assistance!
S.
Click to expand...
Click to collapse
You are welcome I help when i can.
But i told you it can’t be the bootloader , because without it would be the device totally broken , you wouldn’t be able to turn on your phone.
BTW you can Update/Edit your first post in this thread , you know some people maybe get scared of buying this phone , and remember when the number of users will raise the development will be also better.

jozco313 said:
You are welcome I help when i can.
But i told you it can’t be the bootloader , because without it would be the device totally broken , you wouldn’t be able to turn on your phone.
BTW you can Update/Edit your first post in this thread , you know some people maybe get scared of buying this phone , and remember when the number of users will raise the development will be also better.
Click to expand...
Click to collapse
Hi Jozco,
sure you're right, I edited my post 'cause all is doing good now, this phone blows my mind!
The only issue I'm having is that Google Sync isn't updating my contacts... so I had to migrate them manually from my old phone, is it like that for you?
Thanks!
S.

Simmessa said:
Hi Jozco,
sure you're right, I edited my post 'cause all is doing good now, this phone blows my mind!
The only issue I'm having is that Google Sync isn't updating my contacts... so I had to migrate them manually from my old phone, is it like that for you?
Thanks!
S.
Click to expand...
Click to collapse
I really don´t know but i think yes i had duplicite contacts , because i updated from .vcf file from my old phone.
BTW you are right the phone is just great

ROOT
Hi, can help me anyone? I can´t provide root because the file for rooting seems to be damaged. I download ok, but unpacking is not possible. It appears note about corrupt or damaged file. Is it possible to download from different link? Thanks for help and answer
It´s ok now. Root was success

Related

Help with fixing my phone (Please help)

I am going to give you the complete situation so you guys can help with the best of your ability. Over the summer I was at my Grandmas house with my cousins and we were playing Minecraft on the iPod and iPad. I knew that they had it in the Android market and tried to get it. No luck because it was not compatible with my device (Motorola Fire XT 530). I read up on a tutorial to get any app in the store and that was to change the build.prop settings to nexus x or something so I could get it. I rooted my phone and tried it but it screwed up my keyboard and an error occured on screen. So I went into this program I had and completely deleted the file(build.prop, still have a back up though). I tried to turn on the phone but it was stuck in a boot loop . So it is still in the boot loop and I cant turn on my phone.
Things I have tried so far:
1. Plugging it into my computer (wont show up)
2. Clearing my memory and cache in recovery mode (still wont turn on)
3. ADB (wont show up, not even in recovery mode)
4. Using this tutorial http://forum.xda-developers.com/showthread.php?t=1920446 (Was able to get into the flash mode but MSM Flash 7227 wont install correctly for some reason (have updated drivers))
5. Cant use ODIN because my phone cant go into download mode
6. Using default recovery (not clockwork, dont think I can get it because I cant turn on phone) to update the file (didnt work because apparently Motorola locks there bootloader)
I dont think I left anything else out and am looking for a solution. I also have default recovery which may be an issue.
Thanks a lot for reading
FroggyWoggy25
Edit: Disregard my post
Froggywoggy25 said:
I am going to give you the complete situation so you guys can help with the best of your ability. Over the summer I was at my Grandmas house with my cousins and we were playing Minecraft on the iPod and iPad. I knew that they had it in the Android market and tried to get it. No luck because it was not compatible with my device (Motorola Fire XT 530). I read up on a tutorial to get any app in the store and that was to change the build.prop settings to nexus x or something so I could get it. I rooted my phone and tried it but it screwed up my keyboard and an error occured on screen. So I went into this program I had and completely deleted the file(build.prop, still have a back up though). I tried to turn on the phone but it was stuck in a boot loop . So it is still in the boot loop and I cant turn on my phone.
Things I have tried so far:
1. Plugging it into my computer (wont show up)
2. Clearing my memory and cache in recovery mode (still wont turn on)
3. ADB (wont show up, not even in recovery mode)
4. Using this tutorial http://forum.xda-developers.com/showthread.php?t=1920446 (Was able to get into the flash mode but MSM Flash 7227 wont install correctly for some reason (have updated drivers))
5. Cant use ODIN because my phone cant go into download mode
6. Using default recovery (not clockwork, dont think I can get it because I cant turn on phone) to update the file (didnt work because apparently Motorola locks there bootloader)
I dont think I left anything else out and am looking for a solution. I also have default recovery which may be an issue.
Thanks a lot for reading
FroggyWoggy25
Click to expand...
Click to collapse
First of all you cant use Odin to flash Motorola Devices because it is meant for Samsung phones.
Secondly answer these questions:
1. In PC which OS are you using?
2. Have you tried reinstalling RSD lite then rebooting?
Having stock recovery is no issue because you can't get any other in this phone.
It is easy to get it back working.
I suggest you to try some other PC.
OR
Follow these steps as in order.
1. Uninstall RSD lite.
2. Uninstall Motorola Drivers.
3. Now first install Motorola Drivers the RSD lite.
I think this may work for you.
I am using windows 7 on a laptop which may be the problem because it may be a hub not directly connected to the mother board. Thank you and I will try your suggestion.
Btw thanks for all your help over the last couple days.
I also used this on two other laptops but the MSM Flash still wont install for some unknown reason. So I dont think using RSD lite is the problem.
Here's the solution
I found the solution to your problem.
Download the attachment.
Extract it.
Copy the file in the extracted folder and paste it in C:/windows/system32/drivers
Reboot your PC
And yes you must connect it directly without any hub or something.
Actually these are the RSD lite drivers which I think your PC was unable to install correctly.
Okay I will try this when I get home from school. If this doesnt work could you try sending me the MSM Flash7227 driver?
Froggywoggy25 said:
Okay I will try this when I get home from school. If this doesnt work could you try sending me the MSM Flash7227 driver?
Click to expand...
Click to collapse
It is that one only.
Sent from my XT530 using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my problem after I plugged in my phone in flash mode
Froggywoggy25 said:
This is my problem after I plugged in my phone in flash mode
Click to expand...
Click to collapse
So locate that to C:/windows/system32/drivers/the-file-i-gave-you
It will install its drivers.
OR
Alternate way is to install Motorola Software Update from here
It will install drivers automatically as it also needs phone to be switched in flash mode(i.e. through flash drivers) to update phone software.
aweosomeabhijeet said:
So locate that to C:/windows/system32/drivers/the-file-i-gave-you
It will install its drivers.
OR
Alternate way is to install Motorola Software Update from here
It will install drivers automatically as it also needs phone to be switched in flash mode(i.e. through flash drivers) to update phone software.
Click to expand...
Click to collapse
This didnt work because to update drivers my computer has to recognize the phone which it cant. I would need the driver Flash MSM7227 for it to work. If you could find that EXACT file on your computer and send it to me that would be great. I tried the two things you stated but it says the phone is not connected so I cant download the updates.
This must be very frustrating for you but thanks for your help.
Sorry to say, but you kill boatloader of your phone. That mean msm7227 device.
Sent from my XT530 using xda app-developers app
If any one wants to send me the download of the drivers use this to find them.
http://www.youtube.com/watch?v=jv60G3wH1N8
Froggywoggy25 said:
This didnt work because to update drivers my computer has to recognize the phone which it cant. I would need the driver Flash MSM7227 for it to work. If you could find that EXACT file on your computer and send it to me that would be great. I tried the two things you stated but it says the phone is not connected so I cant download the updates.
This must be very frustrating for you but thanks for your help.
Click to expand...
Click to collapse
Don't know about the problem.
Maybe 64-bit system.
And don't download moto update. Download and install only Moto software update "tool".
I sent you the same drivers. But I think the problem is my 32-bit system or your 64-bit.
No, I am not frustrated, don't worry. :laugh:
Sent from my XT530 using xda app-developers app
---------- Post added at 04:45 AM ---------- Previous post was at 04:42 AM ----------
nesham said:
Sorry to say, but you kill boatloader of your phone. That mean msm7227 device.
Sent from my XT530 using xda app-developers app
Click to expand...
Click to collapse
Is it so?
I don't think so.
Have you experienced the same?
Sent from my XT530 using xda app-developers app
Check the link how to obtain the right files for the drivers. Second post from the top of page 2
And its unfortunate we are in very different time zones so its one to two posts per day and we have to wait
And Ive been frustrated since July because I still cant believe I deleted that file xD
Froggywoggy25 said:
Check the link how to obtain the right files for the drivers. Second post from the top of page 2
And its unfortunate we are in very different time zones so its one to two posts per day and we have to wait
And Ive been frustrated since July because I still cant believe I deleted that file xD
Click to expand...
Click to collapse
I know that I have given you the same file.
Don't know why it isn't working.
Sent from my XT530 using xda app-developers app
Are you sure? Because a lot of my things had two different files. Mind quickly checking again?
Froggywoggy25 said:
Are you sure? Because a lot of my things had two different files. Mind quickly checking again?
Click to expand...
Click to collapse
See yourself.
This is when my phone is connected in flash mode.
Okay well thanks for checking
Im thinking about getting another phone because this one is bust.
Im thinking about getting this phone again or getting the mytouch 4g non-slide.
Which one would be better?
Froggywoggy25 said:
Im thinking about getting another phone because this one is bust.
Im thinking about getting this phone again or getting the mytouch 4g non-slide.
Which one would be better?
Click to expand...
Click to collapse
Don't buy this crap again
Sent from my XT530 using xda app-developers app

Fastboot: Stuck at "waiting for device"

Hi all,
today I wanted to install Andromadus in my Desire S. I have to do the whole thing and was looking forward to use http://forum.xda-developers.com/showthread.php?t=2088385 for it. Sadly I am stuck at "waiting for device" when I am trying to get the TokenID via this tool.
So instead, I did the whole run as described on HTCdev. The following was done:
1. Installed Android SDK
2. Installed Google USB Driver
3. Installed HTCSync including HTC BMP USB Driver and HTC Driver Installer
4. Deinstalled (only!) HTC Sync
5. Activate USB Debugging (as suggested in some threads I have found)
6. Remove battery
7. Boot into Hboot
8. Select Fastboot
9. Connected Desire S via USB cabel (Fastboot USB in red visible)
10. Started cmd with adminstrator privileges
11. Executed "fastboot oem get_identifier_token"
12: *see Screenshot below*
I figure, that in the end I did exactly the same as hasoon2000's tool was and was stopped at the same point. I just wanted to make sure that it was not the tool that caused the troubles... I also tried different versions of fastboot.exe. The one provided by hasoon2000 and the one suggested on htcdev from the android-sdk_r13-windows.zip.
I do not have an idea how to go on. Does anyone know?
Just to add some specs:
- Desire S
- Android 4 RUU by HTC
- HBOOT 2.02.0002
- Windows 7 64Bit
Help anyone?
Cheers!
Today, I had some more time to play around with my problem... and was able to get the TokenID.
Solution: Tried different USB ports. This works at my USB 2.0 port, the other was a 3.0.
I will go on now, hopefully, everything will work out fine.
Everything worked out fine.
Thanks much for all the efforts people are doing to run such an awesome community!
I didn't see this post when it first went up, but problems using USB v3 ports are fairly common and fairly well-known.
Well, since I started with all the CustomROM stuff three day ago, I did not know. And even after 80 views of this thread nobody told me.
But now I know.
Another good thing about this: I pushed myself and tried everything by hand instead of using hasoon2000's tool. Thats great actually. Better than pressing some buttons.
No offence to hasoon2000's tool, that great, but sometimes duing such stuff on your own is more fun. Just like setting and building a Desktop PC on your own, istead of buying on in a store.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
afraaa said:
install PDAnet on your device ..
Click to expand...
Click to collapse
See above, that would not help.
But thanks for replying after almost a year...
eschtak said:
Solution: Tried different USB ports. This works at my USB 2.0 port, the other was a 3.0.
I will go on now, hopefully, everything will work out fine.
Click to expand...
Click to collapse
i replied becuase sure there will be ppl visiting this QA thread . man this works for me every time . and specially wit windows 8 .
pay attention that u should boot phone to android and then install PDA last version and turn the debugging mode . and then it will ask on your phone that always alow this computer use pda on phone and u says yes . in nexus when u open bootloader on phone , phone will be recognize by windows ( green check icon in system try appear ) showing windows know your device in boot loader screen . then u can proceed with ADB command . maybe bootloader of htc is a hard ass one like LG phone that is pain in ass to unlock .
then when i finished . u should boot in bootloader . maybe its not working with HTC but sure works with nexus devices . it pity didnt worked for u . hope it help ppl who read this later . u should get a nexus 5 man . its cheap and amazing
afraaa said:
i replied becuase sure there will be ppl visiting this QA thread . man this works for me every time . and specially wit windows 8 .
pay attention that u should boot phone to android and then install PDA last version and turn the debugging mode . and then it will ask on your phone that always alow this computer use pda on phone and u says yes . in nexus when u open bootloader on phone , phone will be recognize by windows ( green check icon in system try appear ) showing windows know your device in boot loader screen . then u can proceed with ADB command . maybe bootloader of htc is a hard ass one like LG phone that is pain in ass to unlock .
then when i finished . u should boot in bootloader . maybe its not working with HTC but sure works with nexus devices . it pity didnt worked for u . hope it help ppl who read this later . u should get a nexus 5 man . its cheap and amazing
Click to expand...
Click to collapse
WOW I cannot believe that this worked. I was seriously losing up, I tried thousands of ways posted on XDA and many other websites, none worked but the one that you posted here worked perfectly on my Xperia Mini. THANKS A LOT! You saved me a from a severe headache. Cheers
XPMSU said:
WOW I cannot believe that this worked. I was seriously losing up, I tried thousands of ways posted on XDA and many other websites, none worked but the one that you posted here worked perfectly on my Xperia Mini. THANKS A LOT! You saved me a from a severe headache. Cheers
Click to expand...
Click to collapse
im glad it helped man i found this trick among 1000 comment on one of solution post ) . i was searching for months to find it . glad u are happy . even on xda back the time couldn't help me . still doing this trick ,
afraaa said:
i replied becuase sure there will be ppl visiting this QA thread . man this works for me every time . and specially wit windows 8 .
pay attention that u should boot phone to android and then install PDA last version and turn the debugging mode . and then it will ask on your phone that always alow this computer use pda on phone and u says yes . in nexus when u open bootloader on phone , phone will be recognize by windows ( green check icon in system try appear ) showing windows know your device in boot loader screen . then u can proceed with ADB command . maybe bootloader of htc is a hard ass one like LG phone that is pain in ass to unlock .
then when i finished . u should boot in bootloader . maybe its not working with HTC but sure works with nexus devices . it pity didnt worked for u . hope it help ppl who read this later . u should get a nexus 5 man . its cheap and amazing
Click to expand...
Click to collapse
YOU SIR ARE A LEGEND!
I was going crazy as nothing worked when rooting my tablet. Spent 2 days trying to figure it out. I'm so glad you posted this even when the user above solved his own issue.
Thankssss
dreamville said:
YOU SIR ARE A LEGEND!
I was going crazy as nothing worked when rooting my tablet. Spent 2 days trying to figure it out. I'm so glad you posted this even when the user above solved his own issue.
Thankssss
Click to expand...
Click to collapse
OH i'm happy it was helpful , cheers
HTC Sync error = -1 ;(
afraaa said:
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone . ...the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links ...... snip
Click to expand...
Click to collapse
.....
I was forced to try your solution proposal, but I could not get PdaNet to connect to via WiFi hotspot, USB or Bluetooth even though it recognised my xperia but failed to pair with it. ;(
Still no root for my xperia ;(
Any fix if only USB 3.0. Ports available? Have no other USB Port to change.
4r44444 said:
Any fix if only USB 3.0. Ports available? Have no other USB Port to change.
Click to expand...
Click to collapse
If you have a USB 3.0 only, also you have the ability to run Linux from a USB stick.
http://www.pendrivelinux.com/
In case this is helpfull: I got the same issue on Windows 10 :
Desire S, HTC Sync Manage installed ("adb devices" is working), but not way to make work the "fastboot devices".
And I have only USB3.
And finaly I found one topic providing the solution for me: set a registry key...
Write the following in a .reg file:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
Launch regedit in administrator mode, import the reg file. Reboot, and that's all !!
afraaa said:
im glad it helped man i found this trick among 1000 comment on one of solution post ) . i was searching for months to find it . glad u are happy . even on xda back the time couldn't help me . still doing this trick ,
Click to expand...
Click to collapse
So I installed PDA on windows 10 and on Phone apk.
No what ?
It makes connection between phone and computer. I already have this. If i type in ".\adb reboot bootloader" it will load bootloader. from there .\fastboot flash recovery recovery.img , it wont do anything Waiting for device.
PDa only works when you are in the Android OS,not Bootloader. It makes connection between the os's windows + Android.
WHat I am trying to do is install an update to my Asus Zenfone 3. I have TWRP it wont work with hat.I need stock rom. I have it. I cant install it,reason: waiting for device.
I did this many times, but its never easy,its always luck or God knows what.
What I do is, install stock recovery (not twrp). With stock recovery I install official updated ROM 8.01. and then get back TWRP. You need TWRP to flash SuperSu so you can have root.
I did this before with 7.0.1 .....now I cant get this stock recovery...waiting for device. It only listens to the first command,after it goes int Fastreovery or whatever it is...it wont go to the next command.

[Q] Real HELP NEEDED..Everythings dead

Guys I REALLY NEED your HELP.
Here's What I did..
1. Installed CWM on my NOKIA X
2.Got into Recovery mode(It's Cool actually)
3.Thought of installing minirom kitkat on it..(I had already copied it to my removable sd card.)
4.Went through all the menus,,, did nothing,,, and somewhere I saw advanced,, got into it (I didn't know what I was thinking) I cleared every option that it had including cache, memory,sd card, emmc and also some boot related stuff..
5.All of a sudden I couldn't move the options so I just removed the battery and tried to power it on....(**** Happens)-Phone is not powering on.... no boot no light just A DEAD PHONE.
plz gus I Really NEED HELP. How Can I Solve this Problem.........................................................................................Plz plz plz plz.......:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
•axe• said:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
Click to expand...
Click to collapse
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Aztile said:
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Click to expand...
Click to collapse
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
•axe• said:
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
Click to expand...
Click to collapse
Sorry buddy...... Tried it... but no use
All we can do is to refer you to a service center. Sorry.
Moderators, please verify my account. I am sick of the five-minute post wait.
Sent from my XT1022 using the XDA Premium 4 app.
Try this..power the phone off, wait 5 mins, then press and hold power for 60 seconds, and check if you see any signs of the phone coming back to life. If not, then the next option is the service center
that too is not working.................Is there no one inthis whole XDA Universe who can help me..... come on guys there must be someone................:crying::crying::crying:
tech_master said:
Moderators, please verify my account. I am sick of the five-minute post wait.
Click to expand...
Click to collapse
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
Dude This is crazy
thenookieforlife3 said:
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
May I have a post thank for helping?
Click to expand...
Click to collapse
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Aztile said:
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Click to expand...
Click to collapse
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Aztile said:
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
You said you've cleared eMMC and also some boot related stuff.
Well, messing with your eMMC and boot partition isn't a good idea, if you wiped your entire eMMC partition it means you've also wiped bootloader stuff...
I'm sorry but looks like your phone is totally bricked....
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
root-expert said:
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
Click to expand...
Click to collapse
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Aztile said:
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Click to expand...
Click to collapse
If your phone won't turn on at all, it's totally bricked. Only a motherboard replacement will fix it...
As you know your phone has hard bricked buddy
then you should also know you cant fix it
try odin and flash bootloader (if u can without open download mode)
or Nokia care is the best way...

[Q] Bricked Phone after installing Xposed Module?

Hi, before everything, i'm sorry for my terrible english, I speak Spanish, if you can't understand something, please tell me.
My Xperia L bricked after I installed a Xposed Module, I had intalled many others before and it worked perfectly.
I wanted to install "MaxUnlock", before that, I had installed "MinMinLock" and then "MaxUnlock", I don't know if it does make the phone brick or if I wasn't suposed to install both.
Here's a list of root apps that the phone have installed:
-ROM Toolbox: Just changed bootanimation, a lot of times, but since yesterday I had the same and nothing happened.
-Xposed Installer with:
-Gravity Box: Changed Clock to the center of the notification bar, changed JB icons for KK icons on the notification bar & putted Facebook and Whatsapp to the app ring (holding the home button on the navbar.).
-Unicon: Changed UI Icons for other pack.
-Xperia Flip.
-APM: Added Reboot button.
-A module to see the Wifi password, don't remember the name.
-MinMinLock & MaxLock (both installed after brick, I think this is what bricked the phone, Wasn't I suposed to have both?)
-ScreenOffAnimation.
I Repeat, everything was ok after I installed MaxLock, but I listed all of the root things that I installed just to know if any of these could make a incompatibility or something. (I know, my english is terrible, sorry, if you can't understand something please ask me, I speak Spanish.)
Thanks Everyone! I hope it have a solution.
hi. did you tried to flash your rom once again? mabe by all the system tweaking that you had, you just got your rom broken..
and your english is very good man, don't think bad about it at all. it's better than mine, at least
Sent from my C2105 using Tapatalk
EternalXDA said:
hi. did you tried to flash your rom once again? mabe by all the system tweaking that you had, you just got your rom broken..
and your english is very good man, don't think bad about it at all. it's better than mine, at least
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Ok... So, how can I do that?
Because I don't have a backup of my ROM, and I don't know if I am doing something bad but Pc Companion doesn't recognize my phone and when I plug the phone on my PC it says that an unknown device has been connected
Oh, and for bricked I mean that the phone just keep on the bootanimation
Sorry if I do something bad bit I have never flash a ROM or something like that.
I assume that you're on stock firmware. download the latest firmware (its biuld number is X.X.17, search for it here on xda...)
download and install the FlashTool on your pc, then use it to flash the downloaded firmware into your phone. (there's few threads on how to do so.)
Sent from my C2105 using Tapatalk
EternalXDA said:
I assume that you're on stock firmware. download the latest firmware (its biuld number is X.X.17, search for it here on xda...)
download and install the FlashTool on your pc, then use it to flash the downloaded firmware into your phone. (there's few threads on how to do so.)
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Could you please link me one of those threads? Because I don't have much time...
I thank you a lot form the help, hope that my phone can be fixed
PeterLda said:
Could you please link me one of those threads? Because I don't have much time...
I thank you a lot form the help, hope that my phone can be fixed
Click to expand...
Click to collapse
Download the 15.3.A.1.17 firmware from here and here's the guide on how to flash it into your phone. and hit the thanks buttons. if you have time!
EternalXDA said:
Download the 15.3.A.1.17 firmware from here and here's the guide on how to flash it into your phone. and hit the thanks buttons. if you have time!
Click to expand...
Click to collapse
Hi, sorry but In the thread no one answers, and when I connect my phone holding vol-, Windows doesn't recognize it, also after the first time y holded vol- and plugging the phone, it stopped showing any light on the LED, when I plug the USB, it shows Red light, then green light and finally orange light it changes very fast and then it stop showing any light, what should I do? thanks for the help!
-----------------------
Oh, and I forgot, for a little time when I tried to turn on the phone or to charge, it didn't turned on or charge, just... didn't do anything
Know it turns in, obviously still bricked, stuck at bootanimation and charges normally.
So... how can I make flashtool work? Or at least make Wiindows recognize my phone
Thanks!
u wer going correct
PeterLda said:
Hi, sorry but In the thread no one answers, and when I connect my phone holding vol-, Windows doesn't recognize it, also after the first time y holded vol- and plugging the phone, it stopped showing any light on the LED, when I plug the USB, it shows Red light, then green light and finally orange light it changes very fast and then it stop showing any light, what should I do? thanks for the help!
-----------------------
Oh, and I forgot, for a little time when I tried to turn on the phone or to charge, it didn't turned on or charge, just... didn't do anything
Know it turns in, obviously still bricked, stuck at bootanimation and charges normally.
So... how can I make flashtool work? Or at least make Wiindows recognize my phone
Thanks!
Click to expand...
Click to collapse
u wer doing the right thing, the red to green light change signifies that u are in flashmode
the light goes off, dont worry u are still in flashmode
u will be out of flash mode after u have disconnected ur phone from ur pc
Have you installed xperia l drivers?
Check it. If it doesn't work after this, try it on an other pc.
Tidzsi said:
Have you installed xperia l drivers?
Check it. If it doesn't work after this, try it on an other pc.
Click to expand...
Click to collapse
How can I install them? I tried but I can't install the drivers, don't know how
Flashtool
Installed them from flashtool drivers setup.
But windows is still not recognizing them, so... I still have to try on another pc but I don't know if it will work.
Also, I was trying to install them manually but I don't really know how to make it work
PeterLda said:
Installed them from flashtool drivers setup.
But windows is still not recognizing them, so... I still have to try on another pc but I don't know if it will work.
Also, I was trying to install them manually but I don't really know how to make it work
Click to expand...
Click to collapse
bro insert the battery and wait ten seconds and try to this :
if your pc doesnt recognise your phone try to plug other usb hub
and press vol.down and plug your phone to pc
edit: did you hear that any sounds when your plug your cable to pc ?
rethinkk said:
bro insert the battery and wait ten seconds and try to this :
if your pc doesnt recognise your phone try to plug other usb hub
and press vol.down and plug your phone to pc
edit: did you hear that any sounds when your plug your cable to pc ?
Click to expand...
Click to collapse
Any sounds from the phone? Nope, just the light turned red like always, and showed the charging icon, then turned off (like it does normally) and Windows shows "Unknown USB".
Thanks for the help!
PeterLda said:
Any sounds from the phone? Nope, just the light turned red like always, and showed the charging icon, then turned off (like it does normally) and Windows shows "Unknown USB".
Thanks for the help!
Click to expand...
Click to collapse
No bro from the pc when your phone connect to pc.did you try hold vol.up button and connect to pc, anything was changed?
rethinkk said:
No bro from the pc when your phone connect to pc.did you try hold vol.up button and connect to pc, anything was changed?
Click to expand...
Click to collapse
I just hear the sound windows make when a non-recognized device is connected like a negative sound? xD (don't know how to explain sounds~~~)
PeterLda said:
I just hear the sound windows make when a non-recognized device is connected like a negative sound? xD (don't know how to explain sounds~~~)
Click to expand...
Click to collapse
ı understood bro,never mind did you install twrp or Custom recovery?
rethinkk said:
ı understood bro,never mind did you install twrp or Custom recovery?
Click to expand...
Click to collapse
No, I didn't, just the things that I listed in the original post, my problem now is that windows doesn't recognize the phone... is that normal? do I have to do anything with flashtool or something?
Thanks for the help bro, I do really apreciate it!
PeterLda said:
No, I didn't, just the things that I listed in the original post, my problem now is that windows doesn't recognize the phone... is that normal? do I have to do anything with flashtool or something?
Thanks for the help bro, I do really apreciate it!
Click to expand...
Click to collapse
it is not normal bro,but your device didnt brick too I think.if your bootlader locked,you can try sony update servıce program dude
rethinkk said:
it is not normal bro,but your device didnt brick too I think.if your bootlader locked,you can try sony update servıce program dude
Click to expand...
Click to collapse
With brick I mean that it's stuck at the bootanimation D:, it just loops (the bootanimation, the phone it's not in a bootloop)
So, you mean Sony PC Companion? It doens't recognize my phone :crying: Is there a way to make it work?
PeterLda said:
With brick I mean that it's stuck at the bootanimation D:, it just loops (the bootanimation, the phone it's not in a bootloop)
So, you mean Sony PC Companion? It doens't recognize my phone :crying: Is there a way to make it work?
Click to expand...
Click to collapse
no bro but sony had removed it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which windows version do you use ?
EDİT:try this steps http://forum.xda-developers.com/showpost.php?p=43439187&postcount=6

Sony Xperia Z3 D6616 possibly hard bricked?

Hi all! I have a Sony Xperia Z3 I recently acquired, it seems to be bricked, possibly hard bricked I'm not sure, but the phone refuses to boot into fastboot or flashmode. Here's what I've noticed so far:
EDIT: The bootloader on the device was never actually unlocked! After getting in contact with the previous owner, all he did was use KingRoot to gain root access on the phone, then installed SuperSU and Clockworkmod recovery respectively. After installing the custom recovery the previous owner had then attempted to flash a variant of Cyanogenmod but the flash failed, since the bootloader wasn't unlocked, resulting in the bricked state the phone is currently in.
The phone shows a red LED when left plugged in to charge overnight
If power button + volume up buttons are held, the red led turns off and the phone vibrates 3 times, but nothing else happens
When connected to the computer via USB, the red led will appear again for a couple seconds, then disappear, then appear, and repeats this process until unplugged. While this is happening you can hear the computer recognizing the phone being constantly plugged in and unplugged.
When plugged into the PC, flashtool recognizes the phone as "Device Connected with USB debugging OFF"
Booting into fastboot or flashmode doesn't work, no matter what button combinations I've tried none of them worked to put the phone in either of these modes.
Is there any way I can unbrick the phone? I don't think this is a driver issue as the computer is recognizing the device in device manager and flashtool sees it, however shows "Device Connected with USB debugging OFF". Is there anyway to somehow enable USB debugging in this state?
I've also tried using adb commands to reboot into fastboot, however this is pointless as the phone is not recognized as an ADB device, when you type "adb devices" there is no devices listed.
HUGE thanks to anyone who has any input on my situation, any help is gladly appreciated! Thank you everyone!
I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked
lavin40 said:
I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked
Click to expand...
Click to collapse
EDIT: I just got in contact with the previous owner, the bootloader was actually not unlocked, the phone was simply rooted via KingRoot, after that SuperSU was installed, then Clockworkmod recovery. After that the previous owner had attempted to flash a new custom rom from clockworkmod but it failed, resulting in the brick. So as it turns out the most probably reason for the brick was because the bootloader was never unlocked, causing the flash to fail, putting the phone in this bricked state. Does anyone have any suggestions on what I can do at this point to unbrick it, now knowing the bootloader was never unlocked? Thanks!
If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.
Omario-242 said:
If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.
Click to expand...
Click to collapse
When I try to go into flash mode or fastboot, nothing happens except for the phone vibrating 3 times and getting the red LED. I've also tried plugging it in and running EMMA however it's not recognized at all by it.
Flash tool recognizes the phone, but throws this message everytime its connected
"Device Connected with USB debugging off"
Is there anything I can do with Flash Tool with the phone being recognized in this state?
I guess as a last option I could try to get in contact with a repair service and ask if they'd be able to unbrick it, however I do not know of any as I've never been to one, hopefully theres another way to unbrick it without having to go here.
Thank you everyone so far who has replied to my thread so far! Please let me know if anyone has the same issue or has an idea for helping unbrick my phone, I appreciate all the tips I've gotten so far.
I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.
Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick
Omario-242 said:
I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.
Click to expand...
Click to collapse
Hi, thanks for the tips, I just tried downloading and installing the Sony Update Service program however it terminates immediately after opening and checking for updates as Sony has discontinued the program since Sony PC Companion replaces this program.
If I type "ADB devices", the phone does not appear on the list, as for some reason ADB is not finding the phone in the state that it's in. I've tried repeatedly typing in this command numerous times when its plugged with no luck.
I've also even tried holding down the volume down/up buttons with a rubber band as i plug the device into the computer however no change, I still get the same result.
Thanks for the tips though!
tz16 said:
Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick
Click to expand...
Click to collapse
I've already tried using Sony PC Companion however it does not detect my phone at all in the current state for some reason. I've tried everything the program told me to do, pressing and holding numerous button combinations however the program will not recognize the phone. Thanks for the tip though.
when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs
tz16 said:
when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs
Click to expand...
Click to collapse
I've tried this exactly as you showed above, however this is the screen I get stuck on, since Sony PC Companion does not recognize my phone. Look at the picture below. Please let me know if you know how to get past this/get Sony PC Companion to recognize my phone, thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
Hi, thanks for the link and instructions, I just installed the drivers successfully, however Sony PC Companion still isn't recognizing my Xperia Z3.
Anything else I can try? Please let me know, thanks
Unplug your device
Hold Volume+ ....and plug in back till your pc load device " flashmod"
I remember this way, when i do it my pc reconized my device with other name
tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.
Omario-242 said:
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.
Click to expand...
Click to collapse
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks
sebzter said:
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks
Click to expand...
Click to collapse
Ok I think I'm out on this point as I honestly have no idea about the whole test point procedure. About repair service though, I guess they don't repair it because they may have to give warranty on their repaired products. Maybe try a mobile repair service in your neighborhood if there's one, but like you said I don't know if the price for a repair exceeds the devices worth.
I guess if you can find this test point it would be a reasonable option for you and I really wish you good luck with that and your phone.
Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers
sebzter said:
Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers
Click to expand...
Click to collapse
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.
ndmuni said:
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.
Click to expand...
Click to collapse
Hi, thanks for the tip, however the phone doesn't seem to be recognized in fastboot devices either. Heres a screenshot of what I get when I type in adb devices and fastboot devices. Thanks
Try installing Minimal adb with fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790
If youconnect your device in fastboot mode....power off, hold vol up ..does your pc sees it?

Categories

Resources