Related
I cannot unlock my bootloader. I have a Nexus 16 wifi with 4.2.1 and no other hacks or mods applied. Bone stock.
When attempting this through the Nexus root toolkit or Nexus 7 tool kit or through a fastboot command line device says unlocking now but does not reboot afterwards. When manually rebooting device is not unlocked. I will also add that my device is encrypted through the software provided on the device. Also I cannot factory reset the device through the UI or through the bootloader. Again it says it's doing these tasks but upon boot up I am still asked for my storage unlock password and the device is still back the way it was pre wipe attempts.
Other strange behaviors indicating a wipe attempt are random reboots, Andriod OS process consuming > 40% of my battery. Also device installs the same app updates every time I reboot or if the device reboots on it's own.
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
No dice
duffieldj1 said:
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
Click to expand...
Click to collapse
Unfortunately the only way to un-encrypt device is to reset it to factory spec again which it will not do no matter the method tried. The drivers are correctly installed via the toolkit. The tool kit shows that device serial number. I have installed the SDK and have tryed that method via fastboot 'fastboot oem unlock'. I then follow the directions on device and press the power button. Device is stuck at 'Unlocking now.....' However nothing happens. It does not automatically rebooot or wipe device. When I push the power button the device boots normally as if nothing had happened. Also bootloader is still locked. If I can get it unlocked I think I should be able to wipe it.
Output from command:
C:\Users\Scot\Downloads\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platfo
rm-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 31.029s
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
bftb0 said:
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
Click to expand...
Click to collapse
Wondering too if this is an unintended consequence of encrypting the device. So now that it is encrypted if the device is lost or stolen it's no good to anyone as there is no way to reset it back to a functional device. There has got to be a way to around this. I travel quit a bit for work and that is the only reason I chose to encrypt was in the event it was lost or stolen.
I have an RMA number open with Asus in the event that this cannot be figured out. Really though it is not a hardware issue, it's definitely software related.
Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!
Nexus Tool Kit
rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.
Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.
Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257
I have tried all those methods and none of them worked for me
pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.
I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem
Can anyone please help me with this?? :'(
pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??
eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?
pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password
eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953
pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me
Problem Solved
Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.
Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.
FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...