Custom rom question. - HTC Desire S

I recently unlocked my bootloader and rooted my phone leaving s-on cos of my hboot being 2.0002 or whatever. And need a step by step to installing a custom rom with s-on. I have installed cwm recovery but cannot access it. I spent 4 hours searching on Saturday, can some kind person explain how to do it?
Sent from my HTC Desire S using XDA App

Put the ROM in SDcard. Turn off fastboot and switch your phone off. Then, hold Vol down button and without releasing it, press and hold power button. Hold till you see a white screen, You'll be in Bottloader mode. Press Vol down to highlight RECOVERY and press power to enter recovery. You'll be in CWM (if you flashed it correctly)
In CWM,
Backup your current (stock) ROM in Backup and restore > Backup. It's not necesary, but recommended, as you may want to come back later
Go to Wipe/Format
Wipe Cache
Wipe Dalvik Cache
Format System
Format Data
Wipe Data/Factory Reset
Then, go back and select Install ZIP from SD Card > Choose ZIP from SD Card and choose your ROM. The ROM is flashed.
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen. Extract the boot.img from the ROM and do this - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Reboot. You're done

shrome99 said:
Then, go back and select Install ZIP from SD Card > Choose ZIP from SD Card and choose your ROM. The ROM is flashed.
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen. Extract the boot.img from the ROM and do this - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Reboot. You're done
Click to expand...
Click to collapse
Excellent. Couldn't have put it better myself.

Thank you so much!
However I installed cwm recovery from the rom manager but it doesn't show up when I go into recovery, I get a red exclamation point, I press volume up and power and it says something about e something recovery not found?
Also where do I put that command? That kinda stumped me too lol. Sorry for being a noob
Sent from my HTC Desire S using XDA App

OK, first you need to setup adb and fastboot. Use this guide - http://forum.xda-developers.com/showthread.php?t=1272595
Next, get CWM recovery and instruction on how to flash it here - http://forum.xda-developers.com/showthread.php?t=1122694
You'll be flashing it via fastboot. Instructions are there in the second thread. The command will be in fastboot too, along the same lines.
Feel free to ask if you have any other doubt. Everyone is a noob at some point
Sent from my iPod touch using Tapatalk

Thank you so much. I will be doing this as soon as I can access my laptop again. Lol.
Sent from my HTC Desire S using XDA App

How'd it work out? Flashed succesfully?
Sent from my iPod touch using Tapatalk

Currently working at the other side of the country. I'll have to wait until thursday to flash it.
Thank you for the follow up though. It's very appreciated.
Sent from my HTC Desire S using XDA App

Sorted thanks guys.

Uppy said:
Hi again, i'm really sorry for being annoying but i dont get this bit.
I extracted android-win-tools to C and put the recovery image in the android-win-tools folder but what am i navigating to? c:\android-win-tools? Its specifically 4. that I'm stuck on.
This is slightly embarrassing!
this was so much easier on my Blade lol.
Click to expand...
Click to collapse
No need to be embarrassed buddy.
What point no. 4 means is that you need to move the file you want to flash (recovery.img in this case) to the folder that contains your adb files (android-win-tools, or whichever folder that you have extracted the android-win-tools that you downloaded). The rationale behind this is that when you enter the command fastboot flash recovery recovery.img, the fastboot will look for recovery.img in its default folder (android-win-tools, or whichever folder you've extracted the adb files to).
So here's what you need to do. For example, if you downloaded the adb files and extracted them to a folder named, let's say, xxxx, which is located in your C: then you need to take the recovery.img file and copy-paste it to the folder xxxx.
Before starting any of the procedures outlined here, first make sure adb can detect your device. (adb devices... sound familiar?)
Now boot phone into fastboot.
Now enter the following commands at the cmd prompt:
C:\Users\UPPY(or whatever)>cd\
Now you'll get the following:
C:\>
Next, you need to enter:
C:\>cd xxxx
You'll now get:
C:\xxxx>
Finally, enter the following:
C:\xxxx> fastboot flash recovery recovery.img
You should be done. I know the above looks over simplified... but i'm just trying to be extra nice here
I hope that clears your doubts.

Done! Thank you for all your help, you made it so much easier for me. its all up and running now.

Uppy said:
One last question though, where do i extract the boot image, do i put it in the root of my sd card and finally if thats the case what is the exact thing i type?
Click to expand...
Click to collapse
After you've flashed your custom recovery, boot into recovery and choose install from sd card, select zip from sd card, then navigate to your rom.zip file, and confirm to flash it using the recovery (on your phone)
But since you've unlocked using HTCDev, this will not flash the kernel as the boot is still locked. You have to bypass this by flashing the kernel manually using fastboot, otherwise you'll be stuck at the white HTC splash screen (Oh! how i hate that screen!!)
The kernel is contained in the boot.img.
The boot.img is contained within the zip file of the ROM you want to flash. So when you open up a ROM.zip (for example Reaper_v1.6.zip) with winrar, you'll see various files inside. Extract the one called boot.img. This is your kernel. Copy-paste this boot.img in your adb folder (like in the previous post)
To flash it, since you've already set up fastboot, just do what you did for flashing recovery.img, and follow the instructions i gave you exactly the same way, except the last part, where instead of recovery.img, you need to type:
fastboot flash boot boot.img
now type adb reboot, and boot into your shiny new custom ROM!!
You're done.

I'm getting an error when i try to connect to wi-fi, it just says error, what have I done wrong? grrr.
I think i didnt register the 3.4 boot image, will report back in a minute.
-edit- yeah i typed the command wrong thats all.

Uppy said:
Done! Thank you for all your help, you made it so much easier for me. its all up and running now.
Click to expand...
Click to collapse
Happy to help

shrome99 said:
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen.
Reboot. You're done
Click to expand...
Click to collapse
I have first read the install instructions from MIUI (saying: full wipe, flash rom) and now I have exactly what you have warned: Phone doesn't proceed, it ist stuck on the white HTC Screen.
UPDATE:
I was afraid of taking out the battery, as this may cause problems, and vol up + vol down + power just rebootet into white htc screen. The only way was indeed pulling the battery (after the vol up vol down power-reboot-gap). Then I could enter into the bootloader the regular way (vol down + power), and change to fastboot, and flash boot.img. Everything is fine now!!!

No-New-Phone said:
I have first read the install instructions from MIUI (saying: full wipe, flash rom) and now I have exactly what you have warned: Phone doesn't proceed, it ist stuck on the white HTC Screen.
UPDATE:
I was afraid of taking out the battery, as this may cause problems, and vol up + vol down + power just rebootet into white htc screen. The only way was indeed pulling the battery (after the vol up vol down power-reboot-gap). Then I could enter into the bootloader the regular way (vol down + power), and change to fastboot, and flash boot.img. Everything is fine now!!!
Click to expand...
Click to collapse
Was already typing a solution for you, but if you can solve a problem by yourself it's even better ;-)
Sent from my Desire S using XDA App

I'm glad this thread is helping more people than just myself. I'm not exactly a Technophobe but this was far more complicated than rooting my blade, Europa or racer or indeed writing the CSS files I used back on windows mobile 6.5 on my old touch 2.
I certainly needed my hand held through the first time doing this.
Sent from my HTC Desire S using XDA App

Related

[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002

Hi, A short but effective guide for people who want to root their Desire S while keeping HBOOT 2.00.0002 and S-ON. This is what I did with my phone yesterday, but took me a lot of time to figure things out, so I'm writing this for myself and other people.
1) First of all set up ADB and Fastboot. [GUIDE] Easy and simple adb and fastboot setup for newbies (Windows only)
Also download the ROM you wish to install on your Desire S and put it on your microSD card. For this tutorial I choose Reaper v2.1 rom by lowveld.
2) You have to unlock your bootloader first via HTCdev so that you can install EXT4 recovery and custom roms. In the dropdown list select ''All other supported models'' and follow the instructions.
If you successfully finished the HTCdev unlock tutorial, your phone has a unlocked bootloader.
3) We're going to install EXT4 recovery. But first download ''4EXT_Recovery_v2.2.7_RC5.zip'' and extract the recovery.img file to the folder where you installed fastboot and adb. If you followed the tutorial in step 1 the folder will be ''C:\android-tools''
Now make sure Fast Boot is turned off on your phone. Go to ''Settings > Power > Fast Boot'' to turn it off. Unplug your phone from your computer, it's time to turn of your phone and boot into your bootloader.
Press Volume Down Button and Power Button at the same time to boot into recovery. Now connect your phone to your computer and select fastboot.
(Power button to select, Volume Down/Up to navigate)
Go to start->run-> type cmd and press enter. A command prompt will now appear.
Type:
cd c:\android-tools [press enter]
fastboot flash recovery recovery.img [press enter]
Click to expand...
Click to collapse
EXT4 recovery is now installed on your phone. Turn off your phone in bootloader menu.
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools''
If you followed this tutorial correctly, you already copied your desired rom your onto your MicroSD card.
Now we boot into the bootloader again, this time we select recovery.
Go to: wipe | format>and select: wipe data/factory reset (this may take a while), then select wipe cache and wipe dalvik cache.
Go back to main menu in EXT4 recovery and select ''install from sdcard'' select ''Reaper_V2.1.ZIP''. After the rom is installed turn your phone off again.
Boot into recovery, connect your phone to your computer and select fastboot on your phone.
Go to start->run-> type cmd and press enter. A command prompt will now appear.
Type:
cd c:\android-tools [press enter]
fastboot flash boot boot.img [press enter]
Click to expand...
Click to collapse
After it's successfully installed, turn of your phone and just boot normally. It may take a while for your phone to boot up.
Your phone is unlocked,rooted and has a custom ROM.
Enjoy
Note: Some new ICS roms require different kind of HBOOT. I use Fallout v5.0.0 without any problems.
Just press the 'Thanks' button instead of saying thanks.
Changelog:
*03-03-2012 Updated guide
*14-03-2012 Updated guide
*12-09-2012 Added Notes/updated guide
Click to expand...
Click to collapse
Tx!
Was thinking about rooting/unlocking but wasnt really sure of myself doing it without bricking it. Most of this guide i already knew but it gives me confidence before making the jump
Sent from my HTC Desire S using xda premium
Why did you temp root at step 2? As soon as you restart your phone it'll be gone.
foX2delta said:
Why did you temp root at step 2? As soon as you restart your phone it'll be gone.
Click to expand...
Click to collapse
So it's not permanent? meaning step 2 is unnecessary?
@n0elite
Yeah, if your phone is locked (2. hboot) or s-on (0.98 hboot) if will just give you shell root, useful but not required for what you doing.
this looks promising, i think i'll try it someday
so i'll be root after i finished this procedure, or just temporary?
Finally. This was the missing link in this forum!
I had the intention do write one, but I am S-OFF and cannot verify the steps without going to Stock then doing the steps and then downgrade and S-OFF again. Too many things to do just in the name of a correct tutorial. Anyway thanks I am glad that somebody finally wrote it!
P. S. : please notify ben_pyett to include it in the Index thread
Sent from my Desire S using Tapatalk
foX2delta said:
@n0elite
Yeah, if your phone is locked (2. hboot) or s-on (0.98 hboot) if will just give you shell root, useful but not required for what you doing.
Click to expand...
Click to collapse
Wouldn't swapping step 2 and 3 fix that?
Sent from my HTC Desire S using xda premium
@dan-fish
Yip
Guide updated. Thanks for the comments
I've followed your Guide ... but i stuck on the bootscreen
i installed the ROM via recovery ... and then the phone restarted and started to boot, i just pulled out the battery to turn off the phone and then to flash "boot.img" via fastboot, but now i stuck on the bootscreen ... anybody knows what to do?
yxsunnyxy said:
I've followed your Guide ... but i stuck on the bootscreen
i installed the ROM via recovery ... and then the phone restarted and started to boot, i just pulled out the battery to turn off the phone and then to flash "boot.img" via fastboot, but now i stuck on the bootscreen ... anybody knows what to do?
Click to expand...
Click to collapse
Damn, where did you read to pull the battery? NEVER PULL BATTERY AT RUNNING OR BOOTING SYSTEM EXCEPT YOUR AWARE OF THE POSSIBILITY TO GET A PAPERWEIGHT AND DON'T MIND IT!!
Did really take a look at the recovery? What is written as last line?
Ok, but your phone is off now, if not reboot to bootloader with
adb reboot bootloader
at the command line.
Otherwise start it with vol down and power.
There use the fastboot command to flash the boot.img, if you're lucky it will work.
Swifted from my Desire S far away from my PC
Tectas said:
Damn, where did you read to pull the battery? NEVER PULL BATTERY AT RUNNING OR BOOTING SYSTEM EXCEPT YOUR AWARE OF THE POSSIBILITY TO GET A PAPERWEIGHT AND DON'T MIND IT!!
Did really take a look at the recovery? What is written as last line?
Ok, but your phone is off now, if not reboot to bootloader with
adb reboot bootloader
at the command line.
Otherwise start it with vol down and power.
There use the fastboot command to flash the boot.img, if you're lucky it will work.
Swifted from my Desire S far away from my PC
Click to expand...
Click to collapse
I tried it, but it will still stuck on the HTC Splash screen ...
When i'm flashing the ROM everything works and in the end it starts restarting ... and i have no chance to stop the restarting? Or i'm blind
Update: Found the solution ... noob mistake
yxsunnyxy said:
I tried it, but it will still stuck on the HTC Splash screen ...
When i'm flashing the ROM everything works and in the end it starts restarting ... and i have no chance to stop the restarting? Or i'm blind
Click to expand...
Click to collapse
What rom do you use? Maybe the recovery script forces a restart, sry, but anyways use vol down vol up and power or adb reboot bootloader to force a reboot.
If it's really needed only pull battery in between the small gap after shutdown and boot, but not at running system.
Try it the other way round, first flash the boot.img, afterwards flash the rom.
Swifted from my Desire S far away from my PC
Please help .
I am new to android and I did know a great stupidity, I removed the battery while charging the 4EXT Recovery image I thought was locked and now i do not know what to do, please teach me download it another rom as it related to furniture.
stroescu76 said:
I am new to android and I did know a great stupidity, I removed the battery while charging the 4EXT Recovery image I thought was locked and now i do not know what to do, please teach me download it another rom as it related to furniture.
Click to expand...
Click to collapse
So what is the problem? Phone doesn't boot or what?
Locked in HTC logo.
He remained in the HTC logo, and nothing happens, I would be very grateful if you help me, I think not uploaded image.: (
stroescu76 said:
He remained in the HTC logo, and nothing happens, I would be very grateful if you help me, I think not uploaded image.: (
Click to expand...
Click to collapse
What did you do before the phone wouldn't boot?
I followed your directions, I installed version Reaper_V2.1'''' I closed, I opened the phone and I gave in "Fastboot", give the command:
cd c: \ android-tools [press enter]
fastboot flash boot boot.img [press enter],
but it says "error: can not load boot.img", if I saw a video where I realize I'm wrong or my phone failed.
Put boot.img in c:\android-tools and then run the command again
Sent from my HTC Desire S using XDA

[Q] home to root

please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

[Q] Problems with Leedroid 2.0

Hi,
i came to the screen install form zip on sdcard
but then it starts installation
and shows : installation aborted
now i cant start the phone i always get tothis screen
with the red text this build is for ....
what can i do?
edit: now i am again there where i can install zip from sdcard, but now it doesnt recognize the sdcard. What can I do, because i the phoen does not take a microsdcard where I could put a new rom.
how can i get access to the internela storage now wihtour a os?
How did this happen ? Selecting a ROM to flash in recovery cant really cause so much damage if it fails. They usually fail because of a md5 mismatch or something.
try to mount the sd card and you can use adb to push files to it..
you could also try a full wipe..
I did several things. I rooted and unlocked the device
and now it does not boot.
Everytime I tired to flash leedroid or stock rom with choosing install form zip
installation get aborted.
I am only able to get into the boolloader and into the recovery.
how can i restore the phone?
wipe and recovery is not possible i always end in this screen
with the red text.
edit: i think i try to get into booloader and copy another file version with adb to the sd card and hope it was a download error.
but why the hell then did both the leedroid 'AND the stock rom fail?
did you flash the boot.img BEFORE flashing leedroids ROM ??
If not i suggest trying that, If that fails, Just run an RUU and start from the beginning
Thanks for the Idea,
my problem is that i cant get access to the memory wihtout a working rom
on it And now i also dont get into the recovery CWMS.
I thouzhg power+vol up would do it but it doesnt work
I think i destroyed my brand new phone.
but thanks for helping.
It's not broken.
Try Power + Vol. down. Possibly you need to retry this several times to get into the bootloader.
its not destroyed dont worry..
Run an RUU and all will be good again. Whats your CID ?
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Click to expand...
Click to collapse
You run it from your Windows desktop. Download your appropriate RUU here for example (as it takes a loooooong time).
Connect your phone to your computer via USB.
Double Click the RUU-file.
Answer the Questions and the update will start.
Remember: Your device will be reset to factory default and your data on sd card will be gone so.
Edit: You will still have to start it with power + vol. down buttons pressed (as far as I remember).
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
Click to expand...
Click to collapse
To get into the bootloader try this.
Press and hold volume down, then power. Hold both down together for 5 secs, let go of the power button then press the power button several times. This always works for me.
If this works then your phone is easy to fix.
Maybe you could try to reflash the boot.img from leedroid via fastboot.
Then flash a proper recovery.img via fastboot (I use clockworkmod)
As I heard you could then push the rom.zip via Adb the sdcard while in recovery. Last step would be install zip from sdcard.
Sent from my HTC One S using XDA
Have you installed supersu via install ZIP from sdcard? I think this needs go be installed before installing the Rom. I Don't Know it exactly. But like this it worked for me when coming from stock rom. Thats how it worked for me:
1. Unlock bootloader via HTCDev
2. flash recovery image via fastboot
3. Install SuperSU from zipfile in recovery
4. Flash boot.img from Leedroid
5. Install Leedroid from sdcard
So maybe you missed one of the steps.
Sent from my HTC One S using XDA
to get CID go into fastboot and type in cmd window ''fastboot getvar cid''
If your phone is branded, you will need that branded RUU, So i assume you will need o2 Germany RUU
Reflash recovery in fastboot, should give you access to sdcard back.
Sent from my HTC One S using xda premium
i did the same thing to my one s yesterday... followed all the steps for leedroid n got same frustration u have...
theres a nandroid file in the dev section... fastboot the boot.img and the recovery.img
ya phone WILL boot back up
ok guys ty for cheeering me up.
i wil try it with a ruu, where can i find a ruu for my htc one s.
the link in the previuos post ist offline.
i think it was 1.78.407.x when i looked the last time in my handy.
thanks
so my cid is
C:\Android\android-sdk\platform-tools>fastboot.exe getvar cid
cid: O2___102
finished. total time: 0.003s
Like i said it is a O2 i hope this helps finding the ruu
well check the Shipped ROM thread.. If its not there you can ask the OP Football if he has it or can get it..
Some RUU's cost $13 so if you know someone else who wants it, you could split the cost ?
so far, now am in the recovery flash but it is the same
count mount /sdcard
how can i put a file onto the sdcard when i have no access?
partionoing sdcard doesn't help
i was looking for this boot.img and recovery.img which was posted before
i dont find it can someone link me to it if he knows what was meant?
thanks
edit: i was desperate and tried:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
but the second order was not successful
ist there another way to fix this usb brick
and to get access to /sdcard
new edit: now i write also in the help thread (noob friendly) i hope that is ok.
Did you already try this
http://forum.xda-developers.com/showthread.php?t=1667929
Or this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using XDA

[HOW-TO] Unbrick Your Android Phone (HTC ONE S)

(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up or go to recovery… well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, have found a way to unbrick your device! after bricking my phone and finding different ways how to do it...
Because we are not able to swap or get the sdcard out from the phone, it makes it difficult on how to add a ROM.zip and re-install. Another issue I found is that CWM will not be able to read the sdcard if you do an adb push ROM.zip /sdcard/ROM.zip or by mounting the sdcard adb shell mount /sdcard . If you have this issue will explain later
So let's get started.
Step 1: Turning Off Your Phone and Reboot to Boot-Loader
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to turn off by pressing the volume down + power button until the phone shuts off then turn on to boot-loader by pressing volume down and press for 3 seconds the power button. once in boot-loader select fastboot.
Step 2: Adb push to SD card
I assume that you have install CWM, if you don't you can download it from HERE. Once downloaded install CWM fastboot flash recovery CWM.TOUCH.5.8.3.1.img, where your done go back to boot-loader and select recovery. Once in recovery do an adb push of a ROM, in this example I used "Energy ROM" you can get the ROM from HERE. Once you have your ROM rename ROM.zip and push adb push ROM.zip /sdcard/ROM.zip, you will get a message stating the size of the the push.
If you can't do a push because you got an error message will explain later.
Step 3: Wipe The Phone
Make sure to do a Factory Reset / Wipe before installing ROM
Step 4: Reboot back to fastboot
Once you install the room you will need to make sure you have a boot.img for the ROM your using.
adb reboot bootloader
fastboot flash boot Recoveries/boot.img
YOUR DONE
If your the unlucky one's that can't do an adb push to the SD card do the following.
- Reinstall STOCK Recovery fastboot flash recovery recovery.img
- Lock OEM fastboot oem lock
- Unlock OEM fastboot flash unlocktoken Unlock/Unlock_code.bin
- Reinstall CWM Recovery fastboot flash recovery CWM.TOUCH.5.8.3.1.img
That should fix the problem on how to push back to the sdcard
If you have other methods post them below...
Sticky!!
But this won't work if you flash a wrong radio, will it? I thought that if you flashed a wrong radio, you couldn't get anything done, even not booting into bootloader, because it boots the radio first?
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
This tutorial already exists as a sticky in the Q&A section:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC VLE_U using Tapatalk 2
Nice writeup.
For every new Phone I own, the first thing I do after flashing a Custom Recovery is Making a Nandroid Backup of the stock Rom. If something goes wrong after flashing a bad rom I just restore to Stock rom.
A real life Saver for me.
snwman said:
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
Click to expand...
Click to collapse
It worked for me when I bricked my phone and had to find ways how to be able to load a ROM back to the SDcard and reflash it...
This is a combo of a tutorial cannondale wrote and one I wrote myself.
His is stickied in Q&A section, mine is in Android Dev section...
Not sure why this is here lol.
i get the error 155 when trying to install the RUU
420haxr said:
i get the error 155 when trying to install the RUU
Click to expand...
Click to collapse
Try to relock your bootloader first.
In fastboot:
fastboot oem lock
Sent from my HTC One S
Issue
Ok, still running into an issue. No errors when I push, I locked, unlocked, tried everything again. Reset everything, installed fresh CWM, tried it all over...
What's happening is that it's saying it pushed the file over, but I can't find it anywhere after it's done. This happened the first time I installed custom...I just can't remember what I did to get it to work...
Anyone has the link of stock recovery for HTC One S z560e(ville c2)?? i get error 155 when i try to install with RUU.
After i flash the cwm touch recovery I cant boot into recovery... my phone is stuck on the HTC boot logo with the red text underneath. Is it a problem with recovery or should i try install an RUU. My phone is HTC One S villec2 (S3).

[Q] Flashed boot.img, did a reboot, but phone keeps restarting after splashscreen

I'm trying to load the CM ROM to my HTC One S device. I was able to unlock and root the device. Next, I flashed the boot.img (fastboot flash boot.img) from the ROM zip file to the device and restarted it (cm-10.1-20130304-EXPERIMENTAL-ville-M2). Now my device just cycles through the HTC splash screen with the red letters "this build is for development purposes only..." -> Android Splash Screen. Phone does not properly boot up. I think I missed a step in the flashing process. Any ideas on how to proceed?
fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.
tivofool said:
fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.
Click to expand...
Click to collapse
Sorry, the command I used was "fastboot flash boot boot.img" The CM boot.img definitely got written to the device. I missed the step of copying the ROM to a folder on my device. I wasn't clear on this step since I'm not sure how to view folders on the device. Is there a way to load the ROM from my PC instead of copying the files to the device first?
I'm using TWRP 2.6.0.0. I'm also not clear on the back up portion since there is no SD card on this device. Is it possible to perform a backup? I thought I did one during the initial step, but now that I'm trying to restore, I don't see a backup available.
yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)
tivofool said:
yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)
Click to expand...
Click to collapse
Thanks for clarifying. I successfully loaded the ROM on my device.
My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens
Mhord said:
My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens
Click to expand...
Click to collapse
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.
tivofool said:
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.
Click to expand...
Click to collapse
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen
Mhord said:
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen
Click to expand...
Click to collapse
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.
tivofool said:
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.
Click to expand...
Click to collapse
mmm yeah tried what you said, and still got stuck in "entering recovery".
I used eyeballer recovery which is the one CM recommends on their wiki
EDIT: My HBOOT says VilleC2 in that case S3 recovery would be the correct one?
EDIT: Yep found the correct recovery back in business, many thanks Tivofool

Categories

Resources