Related
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.
pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
try do it on another pc
AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?
Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.
pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S
Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.
Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.
ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2
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 i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
now i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
spacebite said:
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
Click to expand...
Click to collapse
spacebite said:
no i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
Click to expand...
Click to collapse
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
x8Cooler said:
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
Click to expand...
Click to collapse
thanks i will try when i get home
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
spacebite said:
thanks i will try when i get home
Click to expand...
Click to collapse
Don't!
If you get no joy from following the instructions in the link given by @Sam Nakamura, try @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2
Sam Nakamura said:
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Aight thank you i had some suspicion it might be ...-bricked didnt know which though so thank you
If you can get in the bootloader then possibly the device is still OK. Just need to get the right ROM.
Try different TWRP versions. Sometimes, one particular version can save the world.
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...
Hi,
I want to install a custom ROM in my Note 4 and upgrade from Android 6.01 to Android 11, and I know that the first step is to unlock the bootloader to avoid issues later on in the process.
I've researched different ways of doing it, and this is what I found:
1. Enable the OEM unlocking option in the phone.
The phone does not have the option to enable OEM unlocking in the developer options of the phone.
2. Go to download mode (starting phone with Power+Home+Vol Down keys).
At this point 3 options should appear. One of them being Press Vol Up to enter Device unlock mode. Well, only 2 options appear and the one missing is Enter
Device unlock mode.
3. Start in Recovery Mode, then select Enter Fastboot.
I started the phone using Power+Volume up+Home to enter Recovery Mode, and a menu presented with several options which should have included the
Enter Fastboot option, but the option is missing in the menu.
4. Use your PC to issue adb+fastboot commands.
I successfully connected the phone to the PC and tried to issue the corresponding commands using adb and fastboot. Adb commands work well. Fastboot
commands do not "see" the phone. (just in case I've tried several different drivers)
At this point I've run out of options, and everything points to the "hard-to-believe" fact that this phone doesn't have the fastboot mode.
Is it possible that the phone does not have a way to unlock the bootloader? or at least checking that the bootloader is unlocked in a way that leaves no doubt about it? (I can't risk bricking the phone based on the assumption that the bootloader is factory unlocked)
I will really appreciate any help in working this sort of mystery out.
Thank you!!
I
rfernandez2007 said:
Hi,
I want to install a custom ROM in my Note 4 and upgrade from Android 6.01 to Android 11, and I know that the first step is to unlock the bootloader to avoid issues later on in the process.
I've researched different ways of doing it, and this is what I found:
1. Enable the OEM unlocking option in the phone.
The phone does not have the option to enable OEM unlocking in the developer options of the phone.
2. Go to download mode (starting phone with Power+Home+Vol Down keys).
At this point 3 options should appear. One of them being Press Vol Up to enter Device unlock mode. Well, only 2 options appear and the one missing is Enter
Device unlock mode.
3. Start in Recovery Mode, then select Enter Fastboot.
I started the phone using Power+Volume up+Home to enter Recovery Mode, and a menu presented with several options which should have included the
Enter Fastboot option, but the option is missing in the menu.
4. Use your PC to issue adb+fastboot commands.
I successfully connected the phone to the PC and tried to issue the corresponding commands using adb and fastboot. Adb commands work well. Fastboot
commands do not "see" the phone. (just in case I've tried several different drivers)
At this point I've run out of options, and everything points to the "hard-to-believe" fact that this phone doesn't have the fastboot mode.
Is it possible that the phone does not have a way to unlock the bootloader? or at least checking that the bootloader is unlocked in a way that leaves no doubt about it? (I can't risk bricking the phone based on the assumption that the bootloader is factory unlocked)
I will really appreciate any help in working this sort of mystery out.
Thank you!!
Click to expand...
Click to collapse
If your phone is exynos, just factory data reset and go to download mode and flash TWRP.
SweptDevUwU said:
I
If your phone is exynos, just factory data reset and go to download mode and flash TWRP.
Click to expand...
Click to collapse
Thank you for your answer!
It is Exynos indeed.
Have you tried this in a similar situation? or in case you haven't, could you please explain how you are certain that this will work well?
Because it is difficult to ignore the large number of warnings about going on with the flashing without being sure that the bootloader is unlocked.
rfernandez2007 said:
Thank you for your answer!
It is Exynos indeed.
Have you tried this in a similar situation? or in case you haven't, could you please explain how you are certain that this will work well?
Because it is difficult to ignore the large number of warnings about going on with the flashing without being sure that the bootloader is unlocked.
Click to expand...
Click to collapse
Hello, I'm using exynos as well, just like he said just install a compatible TWRP then flash a custom rom you want
https://forum.xda-developers.com/t/...xy-note-4-custom-recovery-07-28-2021.4311777/
karlsuu said:
Hello, I'm using exynos as well, just like he said just install a compatible TWRP then flash a custom rom you want
https://forum.xda-developers.com/t/...xy-note-4-custom-recovery-07-28-2021.4311777/
Click to expand...
Click to collapse
Hi!
Thank you for your answer.
Ok. I'll review/follow the procedure in the link you suggested and let you know how it goes.
Hi,
It worked!!
Thank you very much to both of you!