Hello! I have been trying to root my Xperia XZ2 Compact. However, I am stuck at the first step - unlocking the bootloader. I am able to use ADB on my computer, but when I attempt to reboot the bootloader and enter fastboot, the phone just stays on a black screen. Is there anyone that could be kind enough to help? Thanks! (If necessary, I can take a video of what occurs. However, the actions my phone takes are nearly identical to the first message in this thread.)
Related
I unlocked and rooted my Nexus 7 and installed TWRP. However, I can't get back to the bootloader or recovery. I've tried a couple things.
1) The basic power button + vol up/down. It doesn't boot at all. Even when I was unlocking the bootloader originally, that was a strange task. I would hold the buttons, it wouldn't do anything, and then a minute or two later, the bootloader would show up. However, it doesn't work at all now.
2) ADB. I tried to, first, do ./adb reboot recovery and ./adb reboot bootloader. At first, I received "error: device not found". After I turned off MTP, I've been finding the device, but it's been offline as far as the Terminal (Mac user) is concerned and I have been unable to find a way to make adb recognize the device.
Can someone please tell me why stuff is not working correctly? I was able to root my Galaxy Nexus easily, but this seems a bit ridiculous.
You are pushing the wrong button combination. See this post:
[Info] Guide to entering safe mode, bootloader, stock recovery
Regarding your adb device offline issue, you need to upgrade to the latest 1.0.31 adb and then acknowledge the RSA fingerprint on the tablet screen.
I have a rooted Xperia Arc S running ICS 4.0.4 and it's not booting. The "SONY" and "XPERIA" logos appear, then the phone shuts down and restarts doing the same thing over and over again(showing the logos and restarting). The only way to stop it is to take out the battery. This happened after I took a photo, then the phone shut down.
(I had free memory, photos are saving on the SD card)
I found similar posts, explaining even for noobs what to do but bootload isn't unlocked and from 10+ threads(on different forums) I've learned that the only way to unlock it is from safe mode/diall pad.
I tried to update/reset/repair from PC Companion but it sais I don't have PC Companion components on "card" and the program can't run properly without those. Now I know from past when I wandered in the root(without touching anything) i saw the PC Companion components. Does that mean my phone is bricked?
I tried fixing it with Fastboot and Flashboot but as far as I know bootload must be unlocked.
Another option I found was to run Emma from SONY but I tried multiple times to register, even with different emails, and it won't send registration mail neither on gmail nor ymail.
What should I do?
(Phone is only rooted, no other changes were made.)
I recently replaced my Cracked Screen on a Verizon m8. I was on a custom rom with twrp installed. After the initial boot, I was having problems with a speaker and went to try to boot to the bootloader to do a RUU, when I noticed that I can no longer access the bootloader screen. It was then when I noticed that not even my computer was recognizing the phone no more. It's as if the phone won't debug no more. I can still access my TWRP by rebooting straight to recovery thru a app or the apm it has on the custom rom im using. I've tried to flash other roms with no success to get access to these two things. I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms. Or if anyone has had this problem before or if any suggestions im open to anything to try and get to the bootloader screen. It also doesn't even boot the two or 3 second boot up screen until you get to the roms boot up screen. It also doesn't goto the bootloader screeen when it try's to access the bootloader. Even when booting straight to recovery stays black until twrp actually shows up. So it's as if bootloader is completely being bypassed. You cant use the volume keys to access the recovery cause everything is blank. Although on first attempt to access bootloader screen when I was stuck there in black. I had to figit the keys a bunch of times to reboot, hoping that I didn't activated something in that screen that caused the phone not to debug. Any suggestions is more then welcome and if someone has a stock twrp of recent stock rom 4.605.9 I believe it is would be more then great. Cant find one other then in zip or exe version. Hoping maybe that might reactivate those two things. Thanks for taking the time to read my problem.
Debugging or adb works within OS, and its not a mode in itself. I think you mean you can't access bootloader-fastboot mode.
Casetheace said:
I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms.
Click to expand...
Click to collapse
You mean stock recovery. TWRP is a specific custom recovery, therefore always a custom one.
I don't think stock recovery will change anything. Bootloader is on a completely different partition.
Its odd that you can't access bootloader. It must still abe intact, otherwise the phone would not work at all.
Did you try (in OS): adb reboot-bootloader
Are you s-off or s-on?
The phone is S off. I was able to get the phone to USB debug. I took it out of the shell and plugged in the USB cord and it debug instantly . So I'm guessing with that I had to damage something when I either took the phone out of the shell originally or when I replaced the screen. Cause you literally have to take every piece of the phone off and then reasamble the phone from scratch. Once i put the phone back in shell, i couldnt get it to usb debug no more. But I still can't access the bootlader, nor is the first boot screen on power up before the main boot up screen starts. Also has no display if I reboot to recovery using a app from the phone. You don't see the screen where the red text would show up saying rebooting to recovery, display starts when it begins to show twrp on display. But when I had the shell off, and was able to access USB debug, I was able to use adb commands from my computer from fastboot mode , but phone had no display. Was able to run a RUU, was able to use adb to reboot to boot loader, then was able to fastboot get varall command. Even flashed a twrp recovery install in fastboot under command prompt . So that tells me that the boot loader is operational. That it has to be some sort of power failure in booting that nots powering the display on initial boot for 2 to 3 seconds , no power on bootliader display, no power rebooting to boot loader or rebooting to recovery until it boots recovery. Any ideas what would cause this failure of power of display during boot loader processes? By the way , have twrp 2.87 . Its a Verizon build, but I'm on a T-Mobile sim.
I've installed live boot and attached a log. If anyone can help or maybe know why this might happen. Believe there is two boots, each with a separate power. Main boot is the initial power up last two or three seconds, and then system boot.. Believe main boot is sending power off display and then power on display on system boot.
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
I assume you didn't have OEM Unlocking enabled before this happened. Without an unlocked bootloader, there is nothing you can do to fix it, because the bootloader will reject any of the necessary commands to reflash the device. If you're still under warranty, seek warranty repair; this is going to require replacing the mainboard, because no one has the necessary tools to perform a low level reflash.
If the bootloader was unlocked, fixing this would be fairly simple because you'd just have to reflash the boot image. But, as I described above, a locked bootloader rejects all the commands that would help in this situation, and there is no way to unlock the bootloader if OEM Unlocking was not enabled.
dch29 said:
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
Click to expand...
Click to collapse
Kind of sounds like a stuck hardware button, either power and volume that's makes the phone think you are holding down buttons during boot to get into bootloader
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Juuuuune said:
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Click to expand...
Click to collapse
Thanks but no change sadly, still completely booked.
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
jonas.sj said:
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
Click to expand...
Click to collapse
My comments below are based on the belief that you are trying to unlock the bootloader.
I am not familiar with this phone but generally the two steps mentioned by you are not enough to unlock the bootloader. After those steps, you'll have to issue a command via adb to unlock the bootloader and if successful, then you can boot into it for further operations. The command will vary between devices, so search and profit.
Thanks, this cleared it up a bit, you are right, I'm trying to unlock it.
I'm trying the command fastboot flashing unlock but only getting the message < waiting for any device >. I read somewhere that I might need some USB drivers but I don't know where to find them. I have the latest version of the standard USB drivers for the phone, but as I understand it I need special drivers for this?
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
jonas.sj said:
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
Click to expand...
Click to collapse
It should be a driver issue. When the phone is on and you connect it to the PC/laptop and send the command 'adb devices', does it show an alphanumeric value? Likewise, when you are booted into the bootloader by key combination and send the command, 'fastboot devices', does it show the same alphanumeric response? If so, the drivers are installed properly. If not, either you don't have the correct drivers or they are not installed properly. Try installing the drivers again after disabling driver signing in Windows on your PC (search for it on Google).
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
jonas.sj said:
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
Click to expand...
Click to collapse
Are you sure that the key combination for booting into bootloader is what you described in the first post?
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
Click to expand...
Click to collapse
I see Power plus Volume Up as the suggested one from a Google search. Try that.
If you can't even boot into the bootloader with the correct key combination, I don't know how to help you further since we are starting to go in circles. I am sorry.
Hello, thank you so much for trying to help me. It seems I can't boot into bootloader. Volume up + power gives the same result as what I did before.: It opens a "Recovery" menu where I can choose reboot to bootloader, but this option just reboots the phone.
I've been in contact with Kyocera and they say:
Thanks for contacting the Kyocera Customer Support. We will be more than happy to assist you with your concern
In this case allow us to inform you that since this device is a basic phone , it doesn't have the option to activate fastboot mode. By installing something that will change the way the phone works , that will void the warranty that came with the phone. We as manufacture can not help you to modify the software that came with the phone.
So the phone's fastboot mode has been deactivated. But since it's an android I guess it should still be possible with some workaround. I just don't know whee to start, I've been researching for a week with no result.
Something interesting ehre, maybe someone with more coding knowledge can tell what's going on.
I found the source code for the phone and located a file called recovery.c which I guess handles the menu I see when I press volume up + power button. Maybe some clue to why the phone isn't going into fastboot mode?