Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi,
It's not possible to use 4ext, because the phone doesn't boot. he's stop at the boot loader.
I've try with adb for mac but I think I don't do the good command to flash by adb the kernel
ADB does not work, you have to use fastboot! Just follow the instructions by astar26. Connect your phone to your PC/mac and type "fastboot reboot-bootloader" and then "fastboot flash boot boot.img"
Regards
Gesendet von meinem HTC Sensation mit Tapatalk 4
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is an Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
seamo123 said:
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is am Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
Click to expand...
Click to collapse
Usually the ROM is flashed before the kernel, this is what I did
Babyhustle said:
Usually the ROM is flashed before the kernel, this is what I did
Click to expand...
Click to collapse
I have no idea how to flash a kernel on the HTC - that's my main problem
seamo123 said:
I have no idea how to flash a kernel on the HTC - that's my main problem
Click to expand...
Click to collapse
astar26 explained how it works. If the sensation of your friend has 4ext recovery use smartflash, if twrp use htc dumlock then you don't need to flash the kernel seperately.
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Far_SighT said:
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Click to expand...
Click to collapse
seamo123 said:
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Click to expand...
Click to collapse
Ah, I see:
Power off and pull out the battery. Press Power + Vol down. Once the bootloader screen comes up it'll either say S-ON or S-OFF.
For flashing ROMs S-ON use this (also includes 4ext recovery). Read about S-ON here.
Just use smartflash (see link in 1). For the special cases I mentioned in previous post (no smartflash), just see the ROM's thread for S-ON flashing.
Note that if you want just want to flash ROMs the above method is good. For S-OFF, either use this, in case you followed above steps, or use this, in case you want to S-OFF first. S-OFF is not needed for flashing ROMs.
htc sensation z710e wifi problem
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
VS23BG said:
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
Click to expand...
Click to collapse
flash the boot.img of your current rom and see if wifi works
rzr86 said:
flash the boot.img of your current rom and see if wifi works
Click to expand...
Click to collapse
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
VS23BG said:
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
Click to expand...
Click to collapse
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Far_SighT said:
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Click to expand...
Click to collapse
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
VS23BG said:
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
Click to expand...
Click to collapse
lift up gently the antenna which is responsible for wifi in the back cover
I think I finally found the solution to the wifi problem!
The solution is in this post:
http://forum.xda-developers.com/showpost.php?p=23554125&postcount=1804
Now I use Android Revolution HD 7.3,sometimes the problem occurs again, but now I have a solution!
Just repeat the procedure described in the post and wifi working again.
When you delete a file "wpa_supplicant.conf", I have to re-enter all the router's password which I linked, but this is not such a big problem!
Related
Hi. Today I got my Desire S.
I rooted it using a tool called unlock root: http://www.unlockroot.com/
then I installed rom manager, and installed clockworkmod recovery.
Next I booted into recovery and wiped everything, but now no matter what rom im trying to install, it will just show the HTC boot screen when starting the phone, and nothing more happens.
Does anyone have a suggestion how to solve the problem?
'UnlockRoot'? Have a look at this website and you might consider better ways of rooting your phone, such as following the recommended procedures listed in many places on XDA
http://lifehacker.com/5873745/unlock-root-roots-nearly-250-android-devices-in-one-click
Also, how is this a 'Development' question? This should be in the 'General' or 'Q&A' forum can a mod please move it?
yeah I found out, I tried using htc's way of rooting it http://www.htcdev.com
but that's not possible now, because the bootloader have changed because of that unlock tool, and now htc dev won't accept it when trying to root it.
I guess i just broke my phone , and i can't unroot it, because that unlocktool require that i got usb debugging enabled, witch i can't in clockworkmod :S.
sorry for posting in the wrong section, please move it.
maybe it would be possible if I had a clockworkmod backup for desire S. If this works, I would be extremly glad, if someone could take a backup with clockworkmod, and upload it
...Is your phone S-OFF ?
Maybe it is a stupid question, but I doubt you can successfully install a custom ROM with a S-ON phone
I guess your phone is still S-ON so you need to flash the boot.img from any rom.zip you want to use manually through fastboot.
spymare said:
Hi. Today I got my Desire S.
I rooted it using a tool called unlock root: http://www.unlockroot.com/
then I installed rom manager, and installed clockworkmod recovery.
Next I booted into recovery and wiped everything, but now no matter what rom im trying to install, it will just show the HTC boot screen when starting the phone, and nothing more happens.
Does anyone have a suggestion how to solve the problem?
Click to expand...
Click to collapse
hey budd i feel your pain on this as i Myself is new to the desire s android side of things after coming from zte blade but there is an easier way for you to do thing which would be to first use the ruu that should be on android 2.1 which in turn would bring the bootloader down so its possible for revolutionary to do the rest for you after this you shouldnt have any problems should you need assistance i am more than happy to help
btw the link to the ruu for 2.1 is here http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe after a update using this use revolutionary which can be found in the main thread of the desire s forum
spymare said:
yeah I found out, I tried using htc's way of rooting it http://www.htcdev.com
but that's not possible now, because the bootloader have changed because of that unlock tool, and now htc dev won't accept it when trying to root it.
I guess i just broke my phone , and i can't unroot it, because that unlocktool require that i got usb debugging enabled, witch i can't in clockworkmod :S.
sorry for posting in the wrong section, please move it.
maybe it would be possible if I had a clockworkmod backup for desire S. If this works, I would be extremly glad, if someone could take a backup with clockworkmod, and upload it
Click to expand...
Click to collapse
If you ''unlock'' your bootloader
when you flash rom.zip from recovery, the boot.img won't be flash in.
you have you take out the boot.img from your rom,and then flash it from fastboot.
when you enter the fastboot
type the following in adb
fastboot flash boot boot.img
now you can boot your phone hope you success
tonks22 said:
hey budd i feel your pain on this as i Myself is new to the desire s android side of things after coming from zte blade but there is an easier way for you to do thing which would be to first use the ruu that should be on android 2.1 which in turn would bring the bootloader down so its possible for revolutionary to do the rest for you after this you shouldnt have any problems should you need assistance i am more than happy to help
btw the link to the ruu for 2.1 is here http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe after a update using this use revolutionary which can be found in the main thread of the desire s forum
Click to expand...
Click to collapse
Dont flash this! This one is meant for 'bravo' which is the normal desire!
Flash an ruu for SAGA. The Desire S!
Sent from my HTC Desire S
djpbx said:
Dont flash this! This one is meant for 'bravo' which is the normal desire!
Flash an ruu for SAGA. The Desire S!
Sent from my HTC Desire S
Click to expand...
Click to collapse
whoops my bad was like 2am in the morning the correct 1 is
http://shipped-roms.com/download.ph...5AU_3805.06.02.03_M_release_199890_signed.exe
If you ''unlock'' your bootloader
when you flash rom.zip from recovery, the boot.img won't be flash in.
you have you take out the boot.img from your rom,and then flash it from fastboot.
when you enter the fastboot
type the following in adb
fastboot flash boot boot.img
now you can boot your phone hope you success
Click to expand...
Click to collapse
Solved my problem, thanks alot
Hi all. I'm new in the forum and i found something really strange with my phone. my desire s is unlocked from htcdev and rooted using super one click.
The strange thing is that i'm not able to flash something like cwm or a boot.img from the phone itself. i can just flash them from pc using fastboot method everytime. i've installed several roms but i can't boot them up because of this problem. Also i tried to flash cwm from rom manager and it said that cwm is installed successfully; but i couldn't get in the cwm.
Now i need some help with this problem. How can i flash my phone without fastboot method? Thanks so much!!
Edmerf said:
Hi all. I'm new in the forum and i found something really strange with my phone. my desire s is unlocked from htcdev and rooted using super one click.
The strange thing is that i'm not able to flash something like cwm or a boot.img from the phone itself. i can just flash them from pc using fastboot method everytime. i've installed several roms but i can't boot them up because of this problem. Also i tried to flash cwm from rom manager and it said that cwm is installed successfully; but i couldn't get in the cwm.
Now i need some help with this problem. How can i flash my phone without fastboot method? Thanks so much!!
Click to expand...
Click to collapse
Do not unlock with HTCDev.com
Downgrade and S-OFF instead - there are 2 guides in the Index
thanks. but is it normal that i'm not being able to flash boot.img from the phone itself with using htcdev method? sorry for being a noob.
Edmerf said:
thanks. but is it normal that i'm not being able to flash boot.img from the phone itself with using htcdev method? sorry for being a noob.
Click to expand...
Click to collapse
The HTCDev unlocks the system, boot (kernel) and recovery partitions for custom modifications. S-ON means that your Radio and Bootloader (hboot) partitions remain locked/secured. But when in recovery (when flashing a ROM) or OS mode the kernel partition remain locked. Boot (kernel) is unlocked only when the phone is in bootloader. Then you can use the fastboot flash command to write on it.
This is wise IMO, because is preventing the people that are not familiar with the details to play. So only the ones that know what means partition, kernel, security flag, etc. to use this method. Or the ones that are reading this forum
ok. i want to ask one more question: Will something happen in the future if i flash boot.imgs and any other thing using the fastboot method?
HI
amidabuddha said:
The HTCDev unlocks the system, boot (kernel) and recovery partitions for custom modifications. S-ON means that your Radio and Bootloader (hboot) partitions remain locked/secured. But when in recovery (when flashing a ROM) or OS mode the kernel partition remain locked. Boot (kernel) is unlocked only when the phone is in bootloader. Then you can use the fastboot flash command to write on it.
This is wise IMO, because is preventing the people that are not familiar with the details to play. So only the ones that know what means partition, kernel, security flag, etc. to use this method. Or the ones that are reading this forum
Click to expand...
Click to collapse
Copy and paste is a good friend ;-)
Sent from my Desire S using XDA App
eyahl said:
HI
Copy and paste is a good friend ;-)
Sent from my Desire S using XDA App
Click to expand...
Click to collapse
If you search through my posts you will find out that I had repeated this hundreds of times to deferent users in different threads. Why typing the same over and over again...
amidabuddha said:
If you search through my posts you will find out that I had repeated this hundreds of times to deferent users in different threads. Why typing the same over and over again...
Click to expand...
Click to collapse
yea, thats exactly my point of view too.
didnt recognize you have used it that often already
Hi,
Normally, I try to troubleshoot things myself without bothering others, but I'm in need of help this time. The tricky part is, I just bought this HTC One S from a stranger, so I don't have its complete history. With that said, here's what I need help with. The phone came with Pacman installed (v18.0.0). But, I would like to install this ROM: http://forum.xda-developers.com/showthread.php?t=2082451
It's basically a stock ICS ROM (the lite version mentioned with stuff removed). In attempt to do this myself, I found this post on here:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.
So, I put the ICS ROM in the internal sdcard, did the usual wiping stuff (I've owned several HTC phones, so this part I know how), then installed the ROM. Unfortunately, it didn't work. When I rebooted the phone, it got stuck in boot loop. It would go to HTC logo screen with the development purpose only warning and just keep turning off and on. Fortunately, I was able to get back into recovery and restored it to Pacman. So, apparently, you can't just flash any ICS ROM over JB setup... Can someone help me figure out what I need to do to install that modified stock ROM please? I very much appreciate your help. My One S is S4 from T-Mobile.
Thank you,
GT
Did you flash boot.img?
Sent from my HTC VLE_U using xda app-developers app
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
dr_rick13 said:
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
Click to expand...
Click to collapse
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
goldentequila said:
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
Click to expand...
Click to collapse
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
dr_rick13 said:
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
Click to expand...
Click to collapse
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
If the Toolkit can't see your phone then you might need to install the drivers that come with it for it to work.
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Ya 4EXT is coming soon.
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Also try rebooting the computer if its still not working.
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
goldentequila said:
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
Click to expand...
Click to collapse
oops, it was late last night when I wrote that.. my bad
Sent from my HTC One S using xda premium
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
we do not have S-OFF yet, so until we do.. people with hboots 1.13+ will need to flash boot.img. But HTC still hasn't said anything about when we will get S-OFF or if we will get it.
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Darknites said:
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Click to expand...
Click to collapse
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Darknites said:
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Click to expand...
Click to collapse
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yep very good app I did use it in till I downgraded.
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
IsaacDroid said:
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
Click to expand...
Click to collapse
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Thanks!
new_convert said:
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Click to expand...
Click to collapse
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
IsaacDroid said:
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
Click to expand...
Click to collapse
It is in the zip file that you download to flash, i.e. your new ROM. So when you download CM10, open the zip file. BOOT.IMG will be there. Extract it and flash it to your phone. I believe everything was in One_S_All-In-One_Kit_v3.4. Look it up in the forum and it has all the tools you need. I admit that it was a pain and nothing was straight forward. I always root my android devices and install new ROMs. But HTC One S was particularly tricky.
Good luck!
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
seoman81 said:
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
Click to expand...
Click to collapse
When I try to flash a ROM through fastboot it sends it fine but then it says: FAILED (remote: not allowed), and I tried pushing the ROM with adb but when I tried to put it on the sdcard, it said permission denied, do you know why? I am S-ON, would that be a problem? Thanks!
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
Click to expand...
Click to collapse
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
tx -
tx for that info - ill give it a go.
I reposted because some1 there said i was in the wrong section and supplied a link for the correct section (here) - so yes, i reposted to get the correct replies.
not to digress:
but as for not reading - i can assure u ive read alot. Been a freelance developer for 15 years. That doesnt mean that rooting often requires a handful of little hacks when things dont go smooth. Just like alot of programming tuts, the rooting ones have a similar "assumption" that u know whats half potting, and what will cause what and what wont. All the articles i read i made sure were either 2012 or 2013 - there is ALOT of old non applicable info around, I stick to xda of course as i really trust this place. as usual, not all is 1-2-3. thats all.
asgardr said:
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
Click to expand...
Click to collapse
Well thats true, obvious things for me do not have to be obvious for
somebody else- one sometimes forgets that- begging your pardon
If not for XDA, i'd've known not much at all...
I've given the shortest and simpliest way that never failed me before
so, i truly hope, for you it'll turn out to be usefull as well- with no further accidents...
As for comming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Success
details details
As for coming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Success[/QUOTE]
fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
Click to expand...
Click to collapse
i think u have MDDI pannel (not the one compatible with cianogen) try to flash a sense rom
have a look of THIS
Hi
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
Click to expand...
Click to collapse
On HTC devices, the bootloader is called HBOOT. This is a 100% device-specific program whose sole purpose is to initialize the hardware so that an operating system (such as Android, i.e. Linux) can load. If your bootloader is damaged, your device is 100% bricked.
To prevent tampering with the system, HTC have locked ("S-ON") their bootloaders so that they won't accept unsigned ROM images. So, on your HTC phone, you cannot install any operating system other than what's provided by HTC. You can partially lift these restrictions by unlocking via htcdev, as you have, or you can fully lift all restrictions on your device by going S-OFF. S-OFF-ing the Desire S is done by exploiting a bug in HBOOT version 0.98 and overwriting the bootloader with a patched version ("Revolutionary") that has all write protection disabled.
In order to flash official HTC upgrade packages ("RUU"s), you can be either S-ON or S-OFF, but if you're S-ON you MUST lock the bootloader. Anything that's not a RUU can (only) be flashed without re-locking the bootloader.
Having an unlocked bootloader is only relevant when flashing new ROMs or recoveries. Having an unlocked or locked bootloader per se will not affect booting at all, with one well-known exception: if you're S-ON and htcdev unlocked, the write protection installed by the bootloader is still on for the bootloader, radio, and kernel partitions. This means that you can't flash kernels from a running OS -- only from the bootloader. This means that when you flash a custom ROM, it will not be able to flash the kernel automatically, you have to do that manually via fastboot. Failing to do that will result in your phone freezing on the white HTC screen when it tries to boot.
#S-on/Off
I have been unable to get mine to off -
Click to expand...
Click to collapse
That's expected, because you're most likely not running a ROM that has a HBOOT version that is vulnerable to the exploit used by Revolutionary.
edit: nope, your HBOOT is newer than 0.98 and is therefore not exploitable.
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
Click to expand...
Click to collapse
Only official HTC RUUs require that the bootloader be locked.
Cyanogenmod can only be installed with the bootloader unlocked, but you may always re-lock after installing it. Remember to manually flash the boot.img (that's the kernel) via fastboot directly after flashing CM through your custom recovery.
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
Click to expand...
Click to collapse
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Click to expand...
Click to collapse
The recovery is a specialized mini-Android OS that allows you to flash new software (such as unofficial ROMs such as CM) to your device. What recovery you have installed has no bearing on your main OS. If you're htcdev unlocked, the only way you can install a custom (i.e. non-stock and non-crippled) recovery is via fastboot; if you're S-OFF you can use the 4EXT updater app from Google Play.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
Click to expand...
Click to collapse
Why do you want to install stock?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
boot.img is inside the zip of the ROM you're going to flash.
I hope I've been able to answer most of your questions. If you require more help, please search first, and if you can't find what you're looking for, please do ask.
fstarockr said:
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
# bootloader
The bootloader must be locked to install an RUU (stock rom), it must be unlocked to install a custom rom.
# s-on / s-off
If you unlock your bootloader through htcdev.com, the phone stays s-on. This means you can't install a different radio or hboot (mostly not necessary anyway), or write to the /boot partition or recovery apart from in fastboot.
That means, after every rom installation, you have to reboot to bootloader (fastboot), and flash the boot.img (extracted from the rom you installed)
# recovery
A custom recovery is a must for flashing custom roms (it's where you flash the zips) , I recommend 4ext, other known recoveries are Cwm and twrp. Be aware that you can only flash recoveries in fastboot (not through an app) , if your device is s-on
1.s-off means you can flash anything you want to all partitions on the phone..
S- on (htc dev unlocked) bootloader is unlocked so you gain acces to system partition,
but neither to radio partition nor bootloader itself, so you cannot freely change them at will.
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Boot img is to bo found in the rom zip ( namely boot.img).
and is absolutely necessary to flash that particular one
or, if existing- other that is compatible with rom of you choice and phone model..
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Recovery:
To flash anything like roms or mods etc.
custom recovery is required,
stock htc recovery is been there for slightly different purpose,
and is, well.. rather useless for any device customizing...
1.when s-on: is necessary to flash recovery via fastboot-as an < .img > file
so, when it is zipped- extract the file: xxxyy_recovery .img,
change its name just to recovery.img, and flash it...
2.when s-off : is possible to update it via market app (but only when s-off)
RUU: is a stock phone image, and ussualy contains radio and bootloader itself,
flashing it, may upgrade your device's components that normally -while s-on-
you'd not be able to touch, but there is a price:
1.you must relock bootloader: fastboot oem lock
otherwise you'll always be getting an error
(but if you still keep unlock_token from htc dev-can unlock it again)
2.you must establish
A) your device's CID - Customer IDentification number (whether is generic or carrier branded)
B) your phone's software version region ( wwe or asia or..etc)
C) software version ( froyo, gb, ics )
because, normally bootloader will not let you flash lower RUU version
than itself,
( every RUU contains bootloader, so the one working on the device
will never let downgrade itself- well not without a little trick of course-this is XDA)
Bootloader:
It is advised to use only bootloaders for your device- if you try to flash something slse,
you'll end up with a dead phone ( no fastboot no nothing- paperweight)
While s-on you cannot upgrade bootloader in any other way but by flashing official RUU...
While s-off it is possible to write to bootloader partition ( but always a bit risky)
There are:
- stock bootloaders
- patched ( revolutionary )
- eng bootloaders ( modified - possible to overwrite it by different one in case it is necessary)...
...well... now, there is much more to it if one wants to know everything
if there is something you'd like to know in particular- write back...
fantastic answers and explanations last 3 chaps!!!!
Guys - excellent answers thank you SO much! i have a MUCH better idea now thanks to your no attitude clear answers! I think this should be a sticky as it clears SOOO much confusion for a multitude of users - and fills the forums with the same problems over and over - simply because ppl lack this base understanding b4 opening the darn prompt lol (like me!!)
So to recap"
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Click to expand...
Click to collapse
so by following these directions:
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Click to expand...
Click to collapse
im basically working around the S-On / kernel & partition issue i take it?
Im gonna try all this now - reason i wanted to flash stock
Why do you want to install stock?
Click to expand...
Click to collapse
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
fwiw - at this point im only downloading roms specifically for my phone - its my 1st so im going with stable ones, cyanogen for now. Once I have a better grip ill explore after that
btw:
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
Click to expand...
Click to collapse
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom - not the best question i admit!!
If your bootloader is damaged, your device is 100% bricked.
Click to expand...
Click to collapse
So if i can access fastboot etc then i can assume mine is fine right?
Thanks again guys - if there was a ribbon bar instead of just thanks id hit all of u a few times - im SURE many noobs will find all this info really really helpful. Its hard to tie the parts together and get an idea of how they all fit - its really puzzling.. and I know u gotta break something before u really understand it - but its nice to avoid this if possible!
Ill keep u posted on progress/results
no luck .... yet
got it working guys - had to flash boot img BEFORE rom, not after.
cyanogen mod 10.1 running on Desire s.
2 days of pain over
fstarockr said:
so by following these directions:
im basically working around the S-On / kernel & partition issue i take it?
Click to expand...
Click to collapse
Exactly.
Im gonna try all this now - reason i wanted to flash stock
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
Click to expand...
Click to collapse
That's a valid reason, but in that case you don't need to flash a custom rom first. You just need to use misc_version to lower your mainversion (a fastboot variable) and then you must flash an old (exploitable) RUU. There are numerous guides on how to do this.
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom
Click to expand...
Click to collapse
Correct, but only if you're S-ON and htcdev unlocked. If you're S-OFF the recovery has no problem writing the boot image by itself.
So if i can access fastboot etc then i can assume mine is fine right?
Click to expand...
Click to collapse
Hell, the mere fact that you can turn on your device means your bootloader is fine
got it working guys - had to flash boot img BEFORE rom, not after.
Click to expand...
Click to collapse
No you don't? The order doesn't matter, as long as you've flashed both.