Develop Bugs

[Q] Help get to reboot into bootloader mod on Xperia Arc

HI!
I've got a little issue with my SE Xperia Arc. It's rooted, it has the bootloader unlocked and I want to install a cooked rom (cyanogenmod 7) but I don't know how to reboot into the bootloader mode (->and I can't wipe the mem and i can't install the cyanogen)
I pressed the volume rockers but the problem persists..
what can i do to get into the bootloader?

Use fastboot to boot either Doomlords kernel, or the kernel in the cm7 7zip, both have cwm.
sinkster©

Read the guides.
Sent Via LT15i - FXP47-CM7

Ive read all the guides..
What have i have to do with the kernel?
Sent from my LT15i using XDA App

tommy paradise said:
Ive read all the guides
Click to expand...
Click to collapse
Then I suggest you read them again and not skip through as most people who need to start a new thread does.
Sent Via LT15i - FXP47-CM7

6. On the computer, open terminal and run the following command:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
i can't perform this step.
fastboot.exe doesn't exist,...what folder have i to select into?
thx a lot.
ps
i believe that the problem consists in the non-installation of the kernel..i didn't install it!!

tommy paradise said:
6. On the computer, open terminal and run the following command:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
i can't perform this step.
fastboot.exe doesn't exist,...what folder have i to select into?
thx a lot.
ps
i believe that the problem consists in the non-installation of the kernel..i didn't install it!!
Click to expand...
Click to collapse
Reread the guide.
Sent Via LT15i - FXP47-CM7

HELP!!

Guys let me put this disclaimer out there, this is not my first Android device and neither my first time tinkering or modding it. I've rooted three android devices prior to this.
I upgraded from a Droid Incredible this weekend to Galaxy Nexus on Verizon and finally thought of rooting and flashing a kernel to the phone today since battery life is horrendous. I download the Rootkit that is on the forums here and went through the procedure as laid out in the thread. After unlocking the bootloader and flashing root, the phone hangs on google boot screen. I am fearing that i have bricked the phone. Does anybody else have suggestions on what should i do here? I've never had a problem with rooting a device before.

This is why I always do mines manually. It's better to do it that way and not take the faster route because you get a idea what's going on.
Is your bootloader unlocked? did that successfully work? When you turn your phone on on the bottom center.. is there a lock there?

It's not bricked. Put the phone in fastboot and flash the galaxy nexus image files to it. No big deal.

mysterioustko said:
It's not bricked. Put the phone in fastboot and flash the galaxy nexus image files to it. No big deal.
Click to expand...
Click to collapse
Exactly what I was going to say. +1

fastboot oem lock
fastboot oem unlock
Bricking this phone is nearly impossible, we have fastboot, and even Odin for when things really go to hell.

Restore to stock and start again! You should always keep these images around anyway in case you get stuck at any stage.
1) Grab the latest image for your type of phone from google:
http://code.google.com/android/nexus/images.html
2) Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files are).
3) From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”) / OR open a command prompt and CD to the folder.
4) Type the following commands, allowing each to finish before moving onto the next:
adb reboot bootloader
fastboot flash bootloader bootloader-<varies>.img
fastboot reboot-bootloader
fastboot flash radio radio-<varies>.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-<varies>.img
fastboot reboot-bootloader
fastboot -w update image-<varies>.zip
fastboot reboot-bootloader
Remember the exact image name will vary depending on which version you use. Also if you have the GSM version you won't have radio-cdma etc.
There's other guide that are specific to GSM or CDMA/LTE version if you need exact filenames.

You guys are awesome! I was able to get it back to Stock Google. Thanks a lot fellas .

what would the command prompts be for a mac user?

silverado9502 said:
what would the command prompts be for a mac user?
Click to expand...
Click to collapse
where ever you see:
fastboot ...
do
./fastboot ...

ok so im on a mac and really not too familiar with the locations for things so im tryng to figure out what to, i can get to fastboot and recovery, somehow i lost my backup and the rom that i have isnt installing, i already wiped all data and now it only reboots to the google splash screen with the lock pad unlocked. what do i need to do exactly i may need a walk through unless what is on previous posts is what i need to do?

[Q] Soft-bricked my HOX, solutions exhausted

Hi guys,
Just wanted to put it out there that I'm totally new at this rooting, custom ROM thing, and I got excited which led me to fail the number ONE rule of backing-up your phone!
Anyways, here's the situation
- Rooted my HTC One X
- Tried to install a custom ROM (IceCold Jelly)
- Phone went into bootloop, after the pink unicorn screen
Some facts
- I can get into the bootloader
- When I plug the phone into the PC, PC makes a sound, but it does not recognize the phone at all
- PC detects a "fastboot" device, but no phone
- went through a few "How to save a soft-bricked" phone tutorial to no avail
- fastboot cmd stuff don't work
- i have boot.img, fastboot.exe etc all on my pc
- drivers and htc sync up to date
I'm sorry if its been answered, but in the bunch of threads I've looked at, everything revolves around being able to use the CMD and the PC actually detecting the phone. Couldn't find any way of fixing my phone, as I said above, the PC doesn't register that theres anything connected to it.
I'd appreciate some help, its been a couple of days, and having no phone is really really hurting!
I'm really really new at this, so I apologize in advance if I don't really understand the terminologies used!
Thanks in advance!

What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?

Michealtbh said:
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Click to expand...
Click to collapse
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing

appasionata said:
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
Click to expand...
Click to collapse
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.

Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
I tried flashing it, the result on the cmd said something about not recognizable internal or external command

appasionata said:
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
Click to expand...
Click to collapse
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course

Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
Michealtbh said:
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Click to expand...
Click to collapse
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks

appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
Go to the folder with boot.img and fast boot exe, hold shift and press right mouse button on this folder. Than choose run cmd here (or smthng like this, I don't know how it called in English). Than type commands
Sent from my HTC One X using xda app-developers app

If you'd like a hand, I could help you do it remotely via TeamViewer.

appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.

Michealtbh said:
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Click to expand...
Click to collapse
Thanks for the help guys, I'll keep trying and will let you guys know. I think the root of the problem is that I'm inputting the fastboot commands right as I enter the cmd prompt from the windows search bar.
Will keep you guys posted, thanks for the help so far. Don't have my phone on me this minute as its with my friend whos trying to fix it too, will get it back in the morning!

Alright,
I've tried it now, and now theres a different problem. When I try to get into recovery from the bootloader, a picture of a htc device and red triangle and exclamation mark appears. And the custom rom load screen no longer appears. PC still does not recognize the phone.

Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium

incident said:
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?

appasionata said:
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
Click to expand...
Click to collapse
I think he means that have you unlocked your bootloader via the htcdev.com website?
Sent from my HTC One X using xda premium

OP's first post states that he tried to install a rom, so his bootloader must be unlocked and a custom recovery must have been installed at some point.
@OP - all you have to do is download a custom recovery (CWM or TWRP) then flash it using "fastboot flash recovery nameofrecovery.img", then follow the steps previously explained to you in this thread.

Problem is though he says he rooted HOX he has no idea about unlocking bootloader at HTC Dev? So when he says he's rooted did he unlock the bootloader? He mentions he has an "operator" unlocked phone, and I think this is where he's getting confused. Otherwise suggesting further flashing will make a bad problem worse.
Also it sounds like he's trying to run CMD from start menu. He needs to run it from from where the fastboot file is located, or at least "point" to it in CMD.
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
If you can get into bootloader as you stated have you tried a factory reset?

appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.

andyharney said:
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
Click to expand...
Click to collapse
Thanks, I really appreciate it, I think I might have to resort to this. How do we go about it? shall we talk about it via PM? I'm pretty busy this whole week, so we can do it on the weekends?

Looks like you have a stock recovery, try to install the correct RUU (stock ROM for your phone, manuals, can be found in a sticky post of the ROMs thread). So first get back to stock, then start over and read the f**king manuals very carefully. no offence.
If you don't know what you are doing, please don't start at all.
Manuals: http://forum.xda-developers.com/showthread.php?t=1832891
Sent from my HTC One X using xda premium

[Q] Arc S, fastboot stuck at " sending 'boot' "

Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen

First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i

The file from the zip file is called "boot.img". I have copied it to the fastboot folder, and I am running "fastboot flash boot boot.img", as the "how to-" says.

Reinstall drivers
Sent from my LT15i using xda premium

espenta said:
Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen
Click to expand...
Click to collapse
did you make the phone enter fastboot mode?
you should run "fastboot devices" to see.

Thanks for the replies!
I tried on a different computer this morning, and here it worked immediately. Not sure what was wrong on the other one, because I installed the same SDK packages and USB driver. Installing ROM at the moment.
[Edit]: Everything seems to be working fine. Very happy with CM10 at the moment

dewa999 said:
First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i
Click to expand...
Click to collapse
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...

Tech-G.ONE said:
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...
Click to expand...
Click to collapse
You already asked for help in another topic, why here again?

Someguyfromhell said:
You already asked for help in another topic, why here again?
Click to expand...
Click to collapse
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....

Tech-G.ONE said:
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....
Click to expand...
Click to collapse
i dont like flashing kernel by flashtool, as far i done several 2011 devices the best method allways was over adb:good: & it pretty easy.
download android sdk & open the exe. leave all like it is (only may make sure google usb drivers are checked) & press on install.
after install place the boot.img here: ...\sdk\platform-tools
2. connect device into fastboot mode (blue led)
3.click in a empty space in the folder. now HOLD SHIFT & right click, choose ''open command line window here'' (<-- or sth like that sorry my setup is german)
4. enter 'fastboot devices' --> your device should be recognized as a bunch of numbers.
5. flash kernel by entering ''fastboot flash boot boot.img'' it tells you all done.
6. ''fastboot reboot''
7. enjoy new kernel

Can't flash kernel via fastboot

I am having problem flashing kernel through fastboot.I get an error "unknow partition .......img" when flashing kernel via fastboot from my laptop.Flashing kernel via my desktop is fine though.Since i am having problem with my desktop i wanted to use laptop to flash kernel to be safe.I have installed drivers,flashtool drivers,fastboot driver,google usb driver,android sdk etc.My laptop is 64 bit windows 7.In device manager it shows android device >> adb device inteface.
Fastboot shows device number with "fastboot devices" and i can reboot my phone as well with "fastboot reboot" command but when i tun fastboot flash xxx.img it gives "unknow partition .."error.I have tried different kernels to flash but can't flash them.However same kernel flashing command works on my desktop with 32 bit win7.
My device is bootloader unlocked and i have flahsed many kernels and ROMs via my desktop.What might be missing to install in my laptop?

Anybody around to help solve this problem? When i connect my device is fastboot mode(bootloader). It recognizes it has 'S1 fastboot drive",there is also ADB android device shown in device manager.I can run fastboot commands like "fastboot device","fastboot reboot".They work fine but i can't flash kernel for some reason.I have my kernel file places in same folder as fastboot.exe and running command prompt from same folder.
What might i have been doing wrong?

shoeseat said:
Anybody around to help solve this problem? When i connect my device is fastboot mode(bootloader). It recognizes it has 'S1 fastboot drive",there is also ADB android device shown in device manager.I can run fastboot commands like "fastboot device","fastboot reboot".They work fine but i can't flash kernel for some reason.I have my kernel file places in same folder as fastboot.exe and running command prompt from same folder.
What might i have been doing wrong?
Click to expand...
Click to collapse
What are the commands you used?
Rename the kernel if you have to since fastboot cannot read spaces.

popthosegaskets said:
What are the commands you used?
Rename the kernel if you have to since fastboot cannot read spaces.
Click to expand...
Click to collapse
Thankx for the reply.I have tried to flash different kernels which i have flashed from my desktop.In fact there are more the 10+ kernels which i can flash successfully from desktop.Kernels and fastboot files are all in same folder and i have copied them to my laptop.The names are like boot.img, 5_4fusion_2.img, LuPuS_anzu_jBv12-ram.img etc as they are when i download them.
i think fastboot is working since fastboot devices shows my device serial and fastboot reboot reboots my device but somehow i can't flahs kernel.i even installed adb intaller from this http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/ but still having problem.
If my computer crashed during kernel flash, does it brick my mobile?

shoeseat said:
If my computer crashed during kernel flash, does it brick my mobile?
Click to expand...
Click to collapse
It shouldn't, you will just need to reconnect the phone to the computer in fastboot mode and flash the kernel again. Did you try using flashtool in fastboot mode rather than command line?
僕のLT18iから送られてきた

You missed a part of the command, you need to use this:
fastboot flash boot yourboot.img
Sent from my Xperia C using Tapatalk

popthosegaskets said:
It shouldn't, you will just need to reconnect the phone to the computer in fastboot mode and flash the kernel again. Did you try using flashtool in fastboot mode rather than command line?
僕のLT18iから送られてきた
Click to expand...
Click to collapse
I did run flashtool when connected in fastboot.Flashtool gies message as device connected to fastboot mode but the "kernel" button is disabled i think.Not sure but some buttons are greyed.

devstaff said:
You missed a part of the command, you need to use this:
fastboot flash boot yourboot.img
Sent from my Xperia C using Tapatalk
Click to expand...
Click to collapse
In desktop i always used "fastboot flash yourboot.img".I have command saved in notepad as well.i will try "fastboot flash boot yourboot.img" today,is it due to 64 bit OS i have to use "fastboot flash boot"?

"fastboot flash boot yourboot.img" was right command."boot" was missing from my command but "fastboot flash yourboot.img" was working on my desktop.Is it due to 64 bit OS i have to add "boot" in command?
Anyway thankx for help.

shoeseat said:
I did run flashtool when connected in fastboot.Flashtool gies message as device connected to fastboot mode but the "kernel" button is disabled i think.Not sure but some buttons are greyed.
Click to expand...
Click to collapse
Try Clicking on the lightning bolt (Flash) and then choose the fastboot mode... From here on out you can hotboot or flash your new kernel. BUT ... make sure you click on reboot into fastboot mode first (ADB)
Let me know if it worked for you

shoeseat said:
In desktop i always used "fastboot flash yourboot.img".I have command saved in notepad as well.i will try "fastboot flash boot yourboot.img" today,is it due to 64 bit OS i have to use "fastboot flash boot"?
Click to expand...
Click to collapse
Nope, it is not due to 64 bit OS, it is like this for every OS (at least for Windows PC, not sure about Linux). The command tells computer, how the process must be done.
If you use
Code:
fastboot flash boot.img
then it is understood as fastboot has to flash nothing to partition named "boot.img". Using
Code:
fastboot flash boot boot.img
is the proper way, then fastboot knows, that it must flash boot.img to 'boot' partition.

MrMaddTraxx said:
Try Clicking on the lightning bolt (Flash) and then choose the fastboot mode... From here on out you can hotboot or flash your new kernel. BUT ... make sure you click on reboot into fastboot mode first (ADB)
Let me know if it worked for you
Click to expand...
Click to collapse
Thankx for the suggestion but it's already working now with fastboot command.