Database Info

[Q] Reset encryped phone with debug mode off and bootloader broken

Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele

Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks

Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.

I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.

sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.

Can't unlock bootloader after upgrade

Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks

Try to get ur unlock code from huawei website maybe this can help.

Did you run the bootloader unlock command with your unlock code again?

Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone

gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC

Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks

pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202

grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...

Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.

Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore

pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.

It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.

grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode

gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...

Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.

timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....

pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".

timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.

gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.

timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.

Struggling to unlock XZ bootloader (Windows 10)

Hi guys
Im having a hard time unlocking the bootloader of my XZ
D:\Users\James\Desktop>fastboot devices
CB512C43QU fastboot
D:\Users\James\Desktop>fastboot -i 0x0fce oem unlock 0x74624F5F04DD1640
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
Anyone know the reason for this error?
Under the service menu its listed as the bootloader unlock is allowed

Have you ticked the option to unlock in settings developer options

gregbradley said:
Have you ticked the option to unlock in settings developer options
Click to expand...
Click to collapse
I didn't even know this was an option! I'm coming from an Xperia Z3 and that sort of security wasn't included.. so it must have been a thing with the more recent devices.
Thank you, I didnt know the solution was so simple (I feel so nooby) :silly:

No problem....

Can't get into FASTBOOT
I can't get my Xperia XZ into FASTBOOT! I've tried holding the volume down and power, holding the volume up and power. ADB can issue adb reboot bootloader, but it doesn't reboot. I've also tried the powered off with volume button and plugging into USB.
Windows 10 64bit. Android 7.0

zobisch said:
I can't get my Xperia XZ into FASTBOOT! I've tried holding the volume down and power, holding the volume up and power. ADB can issue adb reboot bootloader, but it doesn't reboot. I've also tried the powered off with volume button and plugging into USB.
Windows 10 64bit. Android 7.0
Click to expand...
Click to collapse
Do you get any response from fastboot devices. Did you replace the google usb driver in the guide, I had nightmare getting mine to get detected and issuing command

I've tried the Google and the Sony USB driver. I show S1boot with an exclamation mark beside it in Device Manager when it's in "fastboot"

zobisch said:
I've tried the Google and the Sony USB driver. I show S1boot with an exclamation mark beside it in Device Manager when it's in "fastboot"
Click to expand...
Click to collapse
I did a search for the USB driver and removed any instance of it so it did not auto install when the phone was plugged in. I diabled the driver signature on boot check so that I could deffo install the sony driver as it said had invalid checksum. Once installed I then was able to proceed with the unlock. Check your driverstore for any android drivers as these will be auto installed and I have to remove them also

zobisch said:
I've tried the Google and the Sony USB driver. I show S1boot with an exclamation mark beside it in Device Manager when it's in "fastboot"
Click to expand...
Click to collapse
you need to follow the instructions in the "Unlock the boot loader" page after receiving email from Sony Developer World Mobile. By following it you'll download an .inf file and replace an Android studio sdk file with it.

To get your device to show up in fastboot, hold volume down when you insert your USB in your device. Type fastboot device and you should get an answer whit a bunch of number.

No green android when using flash or fastboot mode

Hi,
First of all the bootloader is already unlocked.
Two problems:
1. - I was trying to flash twrp.img on my mobile but I am not getting that green android to show up in my screen all I get a black screen with blue led light, I usually power off the mobile, hold volume up and then connect the USB cable to my mobile.
2. - Can't find mobile device while using flash or fastboot, my mobile Developer option and USB debugging are turn on, mobile drivers and adb-setup-1.4.3 are installed, I have access to my mobile on my PC , when I do the process of flashing or fastboot I turn off the mobile and I unplug USB cable from my mobile, I press the keys to do flash or fastboot (I don't see no green android just a led light turn on) and connect the USB cable, problem is my PC can't find the mobile device, I use adb function eg. adb devices or fastboot devices I get nothing no device no info.
Is this problem with Win 10?
Was my problem understood in 2. - ?

Sa9aX said:
Is this problem with Win 10? Was my problem understood in 2. - ?
Click to expand...
Click to collapse
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers

Didgesteve said:
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Click to expand...
Click to collapse
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip

Sa9aX said:
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Click to expand...
Click to collapse
Back again...
I figured all out:-
twrp-3.2.1-0-maple.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img (latest firmware)
Magisk Manager

Mi unlock tool issue

Hi,
I have faced a problem trying to unlock my bootloader.
On the Mi unlock tool I have pressed the button "unlock". after one week the time required passed, but opening the app on the PC and connecting the phone in fastboot mode anything happens! You can see attached a capture of my PC screen with the phone connected in fastboot mode.
How I can fix it?
Thanks

Is this Windows? Does the OS see the device? (Check "My Computer".) Are the correct drivers installed?
If not, click the cog wheel and install driver, then reboot.

pnin said:
Is this Windows? Does the OS see the device? (Check "My Computer".) Are the correct drivers installed?
If not, click the cog wheel and install driver, then reboot.
Click to expand...
Click to collapse
Yes, it is Windows. not in fastboot mode the computer see my phone. in fastboot mode no.on the unlock tool the refresh and unlock buttons seem to be frozen.
How I can install the driver? on the cogwheel I can see only this (picture attached)...
It is really strange, why one week ago everything was ok? same computer, same phone of course!

In my experience, it's normal to not have any button feedback when the device is in fastboot mode -- only long-press power button to shutdown.
Sorry, can't help you on the rest, never faced this myself.
This is what comes up on the cog in the version I have (just pressed check to install the "drive", before rebooting the phone into fastboot)...

It is really frustrating this.
Any piece of advice?

Hi. I know it might sound silly but have you tried a different USB port on your PC? Preferably a USB 2.0 port.

finally done!
mybe the cable not working I don't know why!
Thanks