Hi, I just got my Arc S, and of course I want to unlock the bootloader. I followed the instructions, and when it tells me to boot into fastboot mode, and start up the cmd panel, my Arc goes to a state, where there is some kind of a battery icon, and nothing happens. I do understand the guide for the most part, but stuck in this one. Is the battery icon thing fastboot mode?
Phone state says, bootloader unlocking : Yes, so that's not a problem.
I'd appreciate some help! TY
E: And the cmd window reads: "waiting for the device..." did not return anything.
You must press the MENU button while connecting it with the USB.
If connected correctly,the LED above the usb port turns BLUE.
It is red. I have been strugling with the drivers for an hour and still nothing. What is the problem? Drivers or something else?
If it's done correctly, should there be a battery icon?
switch your arc off. Put the USB into laptop/PC. Hold menu while putting micro usb into phone. The led should be blue, fastboot should be sorted. If not then try again from scratch, same code for unlocking bootloader
Hell yeah! Got it. The problem was, that I always pressed the power button at the same time with the menu button
Thanks guys!
whoops, failed with the title
Ok, now I have another problem. Rooting and unlocking is done, but for some reason, I can't install any roms or kernels(besides Advanced Stock, which I'm running right now).
The problem is, that everytime I boot with the new kernel(after installing with fastboot) it stucks into the bootscreen. I can go into recovery and install a rom, but again, it'll stuck. And I don't know why, but Advanced Stock does work.
E: Arconium does work, but it was still all weird because I installed/uninstalled kernels after that.
Also, it now shows I have LT15i, although it should be LT18i. Why is that?
There's a file in the arconium thread that you flash to correct the id for Arc S.
sinkster©
I got problem here. command still shows "waiting for device" while I'm trying to unlock bootloader eventhough I press menu button. I also try the other way by pressing menu + power button in the same time but it doesn't work. help me please..
76
adb drivers should be installed..
Your thread says that you NEED a problem with unlocking the bootloader? LOL!
I've found the solution! got problem with installing S1 boot driver and my bootloader is still locked. By the way, problem solved after installing boot driver successfully and unlock bootloader.
Related
I have flashed many Custome ROM's before. I have HardSPL installed on my phone.
I tried flashing to a ROM (I forget which one now, I think Cloudfa or something) and it stopped at about 15%. The Update utility stopped as well.
I cannot connect to bootloader at all. I tried holding down on Volume down/Reset to enter bootloader, but the thing is that it's already in bootloader with the message "Upgrade ROM code error, Please try again"
ActiveSync doesn't see my phone either. In fact all it does is just sit on the bootloader screen with that error...
Please Help... Thanks You...
A normal soft reset still brings you back to Bootloader?
What happens when you plug in your device? Does it not change from serial to USB at the bottom?
band27 said:
A normal soft reset still brings you back to Bootloader?
What happens when you plug in your device? Does it not change from serial to USB at the bottom?
Click to expand...
Click to collapse
Sorry. Yes it does show USB when plugged in, but won't respond to anything that I have tried software wise. It does not switch from this bootloader/error screen at any point. Even after I pull my battery and turn it back on...
I have yet to come across a thread which has this exact problem...
jzalapski said:
Sorry. Yes it does show USB when plugged in, but won't respond to anything that I have tried software wise. It does not switch from this bootloader/error screen at any point. Even after I pull my battery and turn it back on...
I have yet to come across a thread which has this exact problem...
Click to expand...
Click to collapse
Have you tried flashing a different ROM while in bootloader?
^^ Yes. It give me an error on my computer...
I would like to try the internal flashing method but I don't seem to have a way of getting at my Storage Card.
I found this thread with a similar problem
http://forum.xda-developers.com/showthread.php?t=480022
I WAS just able to get off of that screen I was talking about, but the best I get is to the Touch Diamond Screen that lists my ROM and such. So no real progress.
I have a feeling that I would resolve my problem if I could Flash from the Interanl Storage...
Have you tried hard resetting the device?
Pull out stylus and Holding....1) Vol. Down 2) Center Round button 3) then press red button aka soft reset with stylus
Nothing...
im stuck
hi all i am very new to this im not sure what i have done or how to fix the problem i download these this morning and they worked
rom version 1.57.831.1(47324)wwe
radio version 1.14.25.24
protocol version 52.64.25.34u
when i bootload in tri colours screen it shows
BLAC100 32M
SPL-1.56.OliNex
MicroP-Blackstone (led)v6
if it shows that i must of done something right i think of what ill read
and i have windows 7 ulitmate and i have Miri_WM65_21815_V19.0_Premium
when i double click on the BLACKSTONE RUU WRAPPER it crashes then i rename a new folder and done it from there and it works but it comes up wit error 208 file open? then i got told to rename to ruu_signed.nbh file to blacimg.nbh and to store it in the root of my sd card done that then somehow i got it to come up to the screen by Turn off the phone, press and keep pressed volume down button and while keeping it pressed turn on the phone then i see a message "Press power to flash your device" and i press power to flash got to 0% and it crashed and come up with Upgrade ROM code error plz try again and stuck in bootloader mode but now it wont even turn on its dead it wont turn on no matter what i do can someone plz help
all i want to do is get windows mobile 6.5 working i cant understand that it can be so hard to do
thanxs blueboys25!
Hey
im trying to unlock my bootloader again (had to lock it because i did a OTA on unlocked stock firmware)
im currently on stock ics, if that has anything to say. but the problem is when trying to install the fastboot drivers in windows device management
as far as i have read, when going into fastboot, is powering of the device, press and hold the menu button and connect the usb cable to the phone then u will get a blue light, find the drivers and install
but my menu button does not work anymore, idk why but it wont work when running android either. i have also tried getting in fastboot mode by holding the back button, then i get a green light as usual.
is there any way to enter fastboot without holding the menu button, or do i need to order a new keypad board for my phone
Thanks, Joakim
EDIT!!!!: i dont know what i have been thinking about, as you could enter fastboot, by typing adb reboot bootloader in adb, sorry
good you found out... there's also an option in flashtool inside fastboot window called "reset to fastboot through ADB"... also works... obviously your phone but be turned on and connected to PC through ADB.
Hello guys,
I am new here and thats my first post, please tell me when I do something wrong. But I think this is the best forum to ask :
I had a well-functioning HTC One X. But at once it doesn´t start and stuck in the HTC bootlogo. I googled it and after many days I try to unlock the bootloader. The bootloader starts only after many trys and then shows a red field "battery level is too low to flash"(connected to PC). The red led doesn´t lights up. I leave it in the bootloader and after many hours it starts normally (bootloader still locked). I set the phone back to factory settings (not in the bootloader). I used it like every day, but after hours when I switch to the normal menü it was stucked for 5 seconds and then the screen become black and it wont restart. I buy accumulator for the phone and exchange it (I have a little bit "hardware skills"). I connected it with loading cable to the socket (not the PC!). The red LED flashes for a second and then happens nothing. After many trys the bootloader shows up (connected to my PC) and I googled for almost hours to find a solution. "I have to install a custom ROM". I unlocked the bootloader with the programm "One X All-In-One Kit v2.3". I don´t know why but I shut the phone down. I try to start the phone or the bootloader but it doesn´t work. I try it now for weeks but it is dead (but I´m very sure the problem that it doesn´t starts is not due to the unlocked bootloader, because it is the same problem with the "not starting" like the time before I unlocked it). But the strange thing is... and now comes the important part... when I connect the phone with my PC the PC make the "USB connected"-sound and says that there is a unrecognized device connected. And when I try to start the bootloader the PC makes the "USB disconnected"-sound and a second later the "device-driver software not installed"-sound (I hope you know what I mean) and when I keep trying to start the bootloader it happens again and again the same. I tried almost everything, I use a loading.bat file but it can´t detect the phone (you know "unrecognized device"). Is it the accumulator ? Is the hardware dead ? Or what is the problem ?
I hope you understand this text (I´m sixteen and from germany). If you don´t please ask me every question you have. I really hope you can help me with my really long-term problem.
Thanks for every question, reply, solution or improvement proposal for me
XilentMe
So, what i have deduced is that
1. You are stuck on fastboot with low battery.
2. Your PC does not recognize your device.
For this purpose, first download and install the htc usb drivers. These should work: http://forum.xda-developers.com/showthread.php?t=2211791
Then visit this thread: http://forum.xda-developers.com/showthread.php?t=1658084
follow the instructions, once your phone is charged enough, unlock the bootloader, flash a custom recovery, boot into recovery and let it charge for a while, then flash a new rom.
Dont forget to press the Thanks button if i helped
Okay thanks for your proposal, but the problem is now that I can´t boot into bootloader, the phone does nothing. No reaction, no charging LED, no normal boot, no bootloader...absolutely nothing. Only when I connect the HTC to the PC the PC make the "USB-device connected" sound, as if you connect a USB-stick to your PC, but nothing else happens.
Any ideas or similar problems ?
XilentMe
So try to charge via pc. Leave for some time connected to pc and try to power up.
Hey,
I tried it, but it didn´t work. Nothing happens, only the "plug off-sound" when I want to start the bootloader via volume down+power button, while it is connected to the PC. I have no idea what to do.
XilentMe
Hey guys, so my Xperia Z's screen broke and the touch is unresponsive, so I took out my old Arc S out of the box and decided to boot it up, apparently I had gotten a new phone because this one had a booting problem.
Things I know:
It's been rooted, bootloader is unlocked, current ROM is Legacy Xperia, can't go into CWM recovery, connecting phone to PC and trying to flash new kernel won't work because flashtool doesn't recognize the device.
In device manager the phone comes up as an unknown device, downloaded the drivers from Sony's site, no luck, get error message saying "this file is not compatible with your version of Windows" or something.
I'm on W10 64bit.
So basically I'm kinda stuck, tried Google and other forums and nothing, I can't seem to get anywhere.
Could you guys help me out?
EDIT: Tried installing Android Studio, launching cmd from /appdata/roaming/android/sdk/platform-tools but when I enter the command line it says "waiting for device".
So I'm thinking this has to do with my PC not detecting my phone in fastboot mode or anyother mode.
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
bsevcenk said:
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
Click to expand...
Click to collapse
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Wolfarm141 said:
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Click to expand...
Click to collapse
Glad to know I helped!
Everything works fine now! Thanks sooo much!
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?