Database Info

Rooting woes :-(

Hi all,
I have recently got hold of a Desire S and updated it a couple of months ago with the standard ota update from O2 (Or branded phone)...since then I have been getting signal errors which I have read about elsewhere.
Anyway thought I would root my phone...I S-off using revolutionary, it did not appear to work the first time, it appeared to s-off the phone but I did not get prompted for the CWM download, second attempt, it informed i was s-off and to download the CWM, I clicked yes and it tried to download but nothing happens.
So as far as I can tell I am s-off but no root. I have tried gingerbreak and superoneclick both of which stall during the process and do not root my phone.
I am very new to this and not sure where to go from here to get my phone rooted.
My Hboot was 98.002 now it shows:
-Revolutionary-
Saga PVT Ship S-off RL
Hboot-6 .98.1002
If I go into recovery I just get a red triangle with an ! and have to reboot the phone.
So I am at a point where I do not know what to do to get it rooted....or can I just get a pre rooted rom and flash that over the top?
Thanks

I'd suggest that to start you change these setting on your phone
Settings->Power->Fastboot = OFF
Settings->Applications->Development->USB debugging = ON
There are various links in my signature, they should all help. Download the adb&fastboot link and extract the files to your c:\temp\ directory on your PC. Then install the HTC drivers then continue and follow the instructions below:
You first need to download CWM recovery image file for this device to your PC into again the C:\temp directory.
Put the phone in Fastboot USB mode (by following instructions below
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Wait for sdcard scan to complete.
Plug in USB cord connected to the computer
Press power ONCE and Fastboot USB mode starts
Then run a CMD shell from the PC and then issue the commands into it from the directory where you have put the downloaded img file (c:\temp\)
fastboot flash recovery cwm-4.0.1.4-saga.img
adb reboot recovery
To root you phone then
Download and then copy su-3.0-efgh-signed.zip to your sdcard root
Start clockworkmod recovery
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Navigate to recovery with the vol down button.
Press power to select and enter recovery.
Select "install zip from sdcard"
Then select "Choose zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back
Then reboot.

Try to download the pg88img file of cwm our 4ext you find them in the index thread.
Put the pg88img in root of your sd, reboot to bootloader and flash the file. After this the easiest way to gain root would be to flash an prerooted ROM.
Don't forget to make a backup of you're current ROM if anything fails
Swyped from my Desire S

I feel your pain. I am replying to you to make sure you did all the steps required. Furthermore, in using "Superoneclick", which worked for me on my Samsung Fascinate, if I missed a step it didn't work. I.E - I didn 't re-boot!

@ben_pyett you sir are a lengend!!!
what you posted worked...the only slight thing I had to do different was install the htcdrivers first, as it would recognise my phone, then I could do the adb reboot recovery.
It said it failed but I continued to flash su-3.0-efgh-signed.zip and happy days, now to load up a rom!!
many thanks and also to those who replied

roidroid said:
@ben_pyett you sir are a lengend!!!
what you posted worked...the only slight thing I had to do different was install the htcdrivers first, as it would recognise my phone, then I could do the adb reboot recovery.
It said it failed but I continued to flash su-3.0-efgh-signed.zip and happy days, now to load up a rom!!
many thanks and also to those who replied
Click to expand...
Click to collapse
Glad to have been able to help.
Now take a backup using CWM so that you have a safe fall back position - just in case!
I'd then suggest updating the recovery to 4EXT which I personally find easier to use.
You'll then find all the ROMS linked within the INDEX thread
Enjoy!

just running a backup now....just waiting for it to finish then to hunt for a rom.
Will probably use rom manger and voidru, seems a popular choice and a good place to start.
Then pay the £1.56 for 4ext
Thanks again

roidroid said:
just running a backup now....just waiting for it to finish then to hunt for a rom.
Will probably use rom manger and voidru, seems a popular choice and a good place to start.
Then pay the £1.56 for 4ext
Thanks again
Click to expand...
Click to collapse
good call....can't go wrong with any of that!

roidroid said:
just running a backup now....just waiting for it to finish then to hunt for a rom.
Will probably use rom manger and voidru, seems a popular choice and a good place to start.
Then pay the £1.56 for 4ext
Thanks again
Click to expand...
Click to collapse
4EXT Recovery updater is free of charge

amidabuddha said:
4EXT Recovery updater is free of charge
Click to expand...
Click to collapse
But I personally think that the small amount of money isn't much and motivates the developer to continually develop and improve this quality product
Swyped from my Desire S using XDA Premium

ben_pyett said:
But I personally think that the small amount of money isn't much and motivates the developer to continually develop and improve this quality product
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
Completely agree with you. Just wanted to point that it is not necessary to pay (thanks to madmaxx82)

Yeah, I just rooted my galaxy tab, installed lagfix etc (feels like a new piece of hardware now, it so fast!)
I first coudnt do it, because i didn't have the Samsung drivers installed (just like the HTC drivers here)
I never actually rooted my desire s manually!.
I just s-offed, then installed custom roms straight away which already come pre-rooted.

ben_pyett said:
I'd suggest that to start you change these setting on your phone
Settings->Power->Fastboot = OFF
Settings->Applications->Development->USB debugging = ON
There are various links in my signature, they should all help. Download the adb&fastboot link and extract the files to your c:\temp\ directory on your PC. Then install the HTC drivers then continue and follow the instructions below:
You first need to download CWM recovery image file for this device to your PC into again the C:\temp directory.
Put the phone in Fastboot USB mode (by following instructions below
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Wait for sdcard scan to complete.
Plug in USB cord connected to the computer
Press power ONCE and Fastboot USB mode starts
Then run a CMD shell from the PC and then issue the commands into it from the directory where you have put the downloaded img file (c:\temp\)
fastboot flash recovery cwm-4.0.1.4-saga.img
adb reboot recovery
To root you phone then
Download and then copy su-3.0-efgh-signed.zip to your sdcard root
Start clockworkmod recovery
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Navigate to recovery with the vol down button.
Press power to select and enter recovery.
Select "install zip from sdcard"
Then select "Choose zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back
Then reboot.
Click to expand...
Click to collapse
Hi, I have the exact same problem, I would very much appretiate, a little more info with regards to the adb command prompts, I have "android-tools" folder in my "c:\temp" but I don't have a clue what command to use to install "clockworkmod", please could you tell me, I've been at this for weeks and my brain is fried... thank you.

It's all there above in post 2
Need info on your device, please write what your boot loader screen looks like
Swyped from my Desire S using XDA Premium

Custom rom question.

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

[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:

Recovery no longer allows me to select files from memory (twrp)

I updated now I can't do anything. Im able to book ROM and to boot into recovery but am no longer able to select anything while in recovery.. basically if i want to changes roms or whipe data and etc.. i can't do that anymore..
Is there a way to revert back to stock? ( bootloader is unlocked before this happened and rom is rooted)
Is there a way to fix this? same thing happens when i install clockworkmod recovery..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4

let it boot and set for 30 min then reflash twrp and it works same thing happened to me

toolhas4degrees said:
let it boot and set for 30 min then reflash twrp and it works same thing happened to me
Click to expand...
Click to collapse
Can you recommend which version of twrp to use ? Link?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4

I"m still trying to fix this issue.. any help would be great

dilfatx said:
I"m still trying to fix this issue.. any help would be great
Click to expand...
Click to collapse
twrp 2.5 is the only one that has no issues as of now.

FIXED!
After doing some more extensive reading and trials and errors.. these two threads where helpful
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
Click to expand...
Click to collapse
and to install recovery I used this step from the same thread
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a version of TWRP 2.5.0.0 that works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds or using
Code:
fastboot reboot
on the command line. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
Click to expand...
Click to collapse
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:

dilfatx said:
After doing some more extensive reading and trials and errors.. these two threads where helpful
and to install recovery I used this step from the same thread
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:
Click to expand...
Click to collapse
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups

frankgreimes said:
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups
Click to expand...
Click to collapse
no problem

[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