Develop Bugs

Help!!! Arc s s1 boot fastboot failed

Hello anyone...
I have a friend's Xperia Arc S LT18i I would like to root. I already got code to Unlock the Bootloader. I have followed all the procedures on SonyMobile. But when I hold the Menu button and plug the USB in, no Window shows up to choose the winusb driver as explained on d sony website. Instead, I just get that notification on the oc taskbar saying "installing driver...." the it fails.
I tried a trick... I ran the command to unlock the bootloder " fastboot.exe -I ..... 0x (key)" while the device was on and its says "Waiting for device" which means its waiting for the device to go into bootloader mode. So while that command is waiting... I opened a new cmd and ran "adb reboot bootloader" The first command window then said something like "InfoUnlockKey needed... " or something cos I dont have the phone with me at the moment. Thinking of getting it again when I find a solution. Who could help with what to do? Thanks

its_Khal said:
Hello anyone...
I have a friend's Xperia Arc S LT18i I would like to root. I already got code to Unlock the Bootloader. I have followed all the procedures on SonyMobile. But when I hold the Menu button and plug the USB in, no Window shows up to choose the winusb driver as explained on d sony website. Instead, I just get that notification on the oc taskbar saying "installing driver...." the it fails.
I tried a trick... I ran the command to unlock the bootloder " fastboot.exe -I ..... 0x (key)" while the device was on and its says "Waiting for device" which means its waiting for the device to go into bootloader mode. So while that command is waiting... I opened a new cmd and ran "adb reboot bootloader" The first command window then said something like "InfoUnlockKey needed... " or something cos I dont have the phone with me at the moment. Thinking of getting it again when I find a solution. Who could help with what to do? Thanks
Click to expand...
Click to collapse
Service menu (*#*#7378423#*#*), Service info - Configuration.
What does it say for Bootloader status? Which OS are you using on your computer?

Install Flashtool and on C:/Flashtool/drivers you have a exe where you can install fastboot drivers

I am using windows 10 have Xperia Arc S , i want to unlock the boot loader i have the key of it from sony but i cannot install driver for S1boot Fasboot
Please help

[Q] Unable to Get Token Identifier for unlocking

Hi all.
My HTC One X (international version) is stuck in a boot loop. If I press Volumen Down button I can see the HBOOT screen where on top it says **** LOCKED ****
I am trying to unlock it using HTCdev. But that requires me to run the command
Code:
fastboot oem get_token_identifier
But since my device is already stuck in boot loop, my computer is having trouble detecting it.
As output of the above, I only see
Code:
<waiting for device>
If I press Volume Down now, the HBOOT says "Checking SD card for updates", "Failed to open usb master mode", "Loading PJ46IMG.zip" etc. and reboots again.
When I try
Code:
fastboot devices
sometimes I am able to retrieve the serial number of my device correctly.
Any suggestions on how I can get the unlock_code.bin ?
Regards,
Amit

amit112amit said:
Hi all.
My HTC One X (international version) is stuck in a boot loop. If I press Volumen Down button I can see the HBOOT screen where on top it says **** LOCKED ****
I am trying to unlock it using HTCdev. But that requires me to run the command
Code:
fastboot oem get_token_identifier
But since my device is already stuck in boot loop, my computer is having trouble detecting it.
As output of the above, I only see
Code:
<waiting for device>
If I press Volume Down now, the HBOOT says "Checking SD card for updates", "Failed to open usb master mode", "Loading PJ46IMG.zip" etc. and reboots again.
When I try
Code:
fastboot devices
sometimes I am able to retrieve the serial number of my device correctly.
Any suggestions on how I can get the unlock_code.bin ?
Regards,
Amit
Click to expand...
Click to collapse
U haven't installed proper drivers that's what causing probs
Regards

My phone would connect fine previously and I updated the drivers too
kantry123 said:
U haven't installed proper drivers that's what causing probs
Regards
Click to expand...
Click to collapse
Hi kantry123.
My phone would connect to my laptop fine before this issue. I also updated HTCSync and tried to ensure I have latest drivers.
Is updating HTC Sync not enough to ensure driver update?
Regards,
Amit

Strange Problem On Bootloader/Fastboot

Hello Everyone,
I Have A Strange Problem When I Press Power+Down Button Then Device Goes To Bootloader/Fastboot And Mi Bunny Appears, But After 3-5 Seconds Mobile Device Automatically Switch Off Without Connecting The Cable Or Doing Anything.
Note That, I Have A Latest Build V11.0.9.0.QDLMIXM Installed Without Rooting And Device Working Properly. Since I Just Want To Root The Device And Bootloader Is Unlocked. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode.
Thanks In Advance !!!
Thanks,
MUHAMMAD Asif Qasim

Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)

a1291762 said:
Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)
Click to expand...
Click to collapse
Thankyou For Prompt Response.
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
In Addition To That, I Can Use ADB Commands & Shows My Mobile Connectivity When I Use.
Thanks,
MUHAMMAD Asif Qasim

aasiaasi said:
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
Click to expand...
Click to collapse
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?

a1291762 said:
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?
Click to expand...
Click to collapse
Thank You Dear. Yes I Can Use The Command On ADB When Mobile Is Switched On Here Is The Example Snapshot.
The Problem Is That When I Boot To Bootloader It Doesn't Stay On Bootloader And Shutdowns Automatically With In 3-5 Seconds. As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.

aasiaasi said:
As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.
Click to expand...
Click to collapse
I don't know exactly what the bootloader does while in fastboot mode, but I'm going to guess it draws the rabbit and then gets ready to talk to the PC. And something fails and it dies.
If it's working normally, that's something... But it's going to stop you from unlocking the bootloader.
I have no idea how to fix. Maybe EDL with the test points? There are 2 aboot partitions (apparently hold fastboot).
# ls -l aboot*
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_b -> /dev/block/mmcblk0p32

I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.

Mewwo2 said:
I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.
Click to expand...
Click to collapse
Thankyou Mewwo2,
Could You Please Check Your Device ? Without Connecting The Cable , That Your Device Automatically Switched Off In Few Seconds Or Not. Please Let Me Know So I Can Figure Out Or Take A Clue For Fixation.
Secondly I Have Windows 8 And Drivers Are Properly Installed. If The Drivers Have Issue The Adb Command Doesn't Work And Doesn't Shows My Mobile (Note That I am Taking About When Mobile Isn't on Bootloader Mode)
Thanks In Advance...

Can you type another adb command like 'fastboot oem device-info' and see the output.

it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.

minicm94123 said:
it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.
Click to expand...
Click to collapse
Thankyou For Your Support. I Will Check & Respond Accordingly.

help with p3xl brick

Hey, maybe someone can help me, i have p3 xl, morning (yesterday) i just reboot my phone and when my phone is turn on, he just enter fastboot and have error "device state: error!" and "enter reason: error to preload images", i cant enter in recovery for wipe data, idk what need to do... bootloader was locked, have clean device. sorry i cant add video because newbee =\
- i try unlock bootloader from cmd (adb), but can't because developer settings
- try flash from flash.android.com, but again bootloader
- try change A/B, but again cant because bootloader
i can enter only fastboot (auto, when turn on device or when plug in charge), if i try enter recovery (from fastboot) i have black sreen ~5-10 sec and again enter at fastboot... (i think he reboot for enter recovery, but because cant... again fastboot..), idk what happend, because all was fine =\ idk so much pixel, 2 friends will buy it too... but now, idk, 2y old phone is dead =\

aresqq said:
Hey, maybe someone can help me, i have p3 xl, morning (yesterday) i just reboot my phone and when my phone is turn on, he just enter fastboot and have error "device state: error!" and "enter reason: error to preload images", i cant enter in recovery for wipe data, idk what need to do... bootloader was locked, have clean device. sorry i cant add video because newbee =\
- i try unlock bootloader from cmd (adb), but can't because developer settings
- try flash from flash.android.com, but again bootloader
- try change A/B, but again cant because bootloader
i can enter only fastboot (auto, when turn on device or when plug in charge), if i try enter recovery (from fastboot) i have black sreen ~5-10 sec and again enter at fastboot... (i think he reboot for enter recovery, but because cant... again fastboot..), idk what happend, because all was fine =\ idk so much pixel, 2 friends will buy it too... but now, idk, 2y old phone is dead =\
Click to expand...
Click to collapse
what region/carrier is your phone?

Bootloading Kyocera DuraXV Extreme

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?