Hey guys, normally I would just lurk and avoid posting threads but I need help.
I want to root my Desire S.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
When I click recovery on the bootloader screen I get taken to "Android system recovery <3e>", but when I try to apply an update through USB I get the following error message:
"Invalid operation:
reason: oem-00"
And then the phone just reboots.
If anyone can help I'd be very grateful.
Thanks.
Since you are unlocked via HTCDEV you can do...
If all you need is root then just run superoneclick, easy as that.
If you have your heart set on using recovery.... You need to flash a custom one (the stock one won't do), download clockworkmod .img and flash it in recovery.
Also if you ever choose to flash roms etc you will need a custom recovery.
If you choose to to go the custom recovery path here is a how to.
______________________________________
-Download attached file titled "android-tools.zip", it has the adb and fastboot files needed to proceed
-Extract the file to "c:\" so that the path looks like this C:\android-tools
-Install HTCDriver (Fastboot drivers) here's
-Open cmd and type "cd/"
-then type "cd android-tools"
*To test whether you have set up all the files correctly and your phone is connected correctly you can do the following;
*Plug your phone in (when plugging in select CHARGE ONLY (i.e. leave on the home screen)
*In cmd type "adb" and press enter, it should show a list of commands, then type "fastboot"and press enter, it should also show a list of commands)
*If both these commands work you have extracted the files to the right place and have setup cmd right.
*then type "adb devices"
*Should show connected phone serial if not then try get the latest HTCdrivers
-Download clockworkmod (here) for your phone and place .img in C:\android-tools folder (i.e. where the files adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe are)
*To make life easier rename the file to recovery.img
-start fastboot (boot Hboot, plug phone in "HBoot USB plug" shows once phone is plugged in and press the power button (fastboot is highlighted by default) then it says "Fastboot USB")
*(As a test to ensure you have put your phone into fastboot type "fastboot devices" in cmd, it will show your phones serial, if it shows nothing you have not put your phone into fastboot yet)
-run command "fastboot flash recovery recovery.img" in cmd
-then run "fastboot reboot"
NEXT - to get root
-Copy su-3.0.5-efgh-signed.zip to sdcard root (get latest from clockworkmod site if you wish)
-Start clockworkmod recovery (Hboot/recovery)
-Select install zip from sdcard"
-select Choose zip from sdcard
-Select copied file
-select Yes - install su-3.0.5-efgh-signed.zip to confirm
-Go back
-Then reboot.
All Done.
I would like to do the same thing, but mine says
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Does that mean that I'm f**ked ?
@kryddan
Since you are locked and hboot 2.00.0002 you can either downgrade to an older hboot or unlock your bootloader with HTCdev (may void warranty).
Both are very well discussed here.
foX2delta said:
@kryddan
Since you are locked and hboot 2.00.0002 you can either downgrade to an older hboot or unlock your bootloader with HTCdev (may void warranty).
Both are very well discussed here.
Click to expand...
Click to collapse
Downgrade sounds like going backwards. Think I'll search for HTCdev instead
It worked fine with HTCdev to unlock Ok, so it wiped the phone clean from personal data and apps, but who cares. It worked.
Thank you for your help. but go from S-ON to S-OFF seems a bit harder, without downgrade?
p.s. Have already voided my warranty. Got a new mainboard last week. d.s.
kryddan said:
Downgrade sounds like going backwards. Think I'll search for HTCdev instead
It worked fine with HTCdev to unlock Ok, so it wiped the phone clean from personal data and apps, but who cares. It worked.
Thank you for your help. but go from S-ON to S-OFF seems a bit harder, without downgrade?
p.s. Have already voided my warranty. Got a new mainboard last week. d.s.
Click to expand...
Click to collapse
the hboot is your bootloader and manages things like partitioning your volume for system, data etc.
downgrading it will never mean going backwards.
what you could have done was downgrading hboot, s-off with revolutionary and get root with superoneklick. thats what i did (but hboot was already fine for me ) then you could install new recovery and done.
its not that hard
but since you have unlocked with htcdev anything you do with your phone will be (at least a bit) harder than with s-off.
Related
So i finally decided to root my phone. i rooted it and got CWM recovery and well i tried updating the firmwire to ics so i can flash an ics rom. and when i updated the firmwire it said cid error update failed. I rebooted my phone but it was stuck on bootloop. i assumed that the firmwire update went through since my phone would't boot up. So i went ahead and flashed the virtous rom and now that doesn't boot up either. i found out that i had to SuperCID first before i flash the ICS Firmwire. But in order to SuperCID my phone has to be On The Home Screen Wich i can not do since my phone is stuck on bootloop >.< ! Help ???
Click my name find post bootloop
Sent from my HTC Sensation XE with Beats Audio using xda premium
19fonzy said:
So i finally decided to root my phone. i rooted it and got CWM recovery and well i tried updating the firmwire to ics so i can flash an ics rom. and when i updated the firmwire it said cid error update failed. I rebooted my phone but it was stuck on bootloop. i assumed that the firmwire update went through since my phone would't boot up. So i went ahead and flashed the virtous rom and now that doesn't boot up either. i found out that i had to SuperCID first before i flash the ICS Firmwire. But in order to SuperCID my phone has to be On The Home Screen Wich i can not do since my phone is stuck on bootloop >.< ! Help ???
Click to expand...
Click to collapse
You are soff?
Did you have fastboot/adb setup?
Can you go into bootloader and post the hboot, radio, son/soff status.
(to go into bootloader remove battery... Put it again then press volume down and power button together... You'll get a white screen.. Post the details from that..)
First of all if you used PG58IMG.zip for firmware update then either remove the file from sdcard via a card reader.. Or just boot into bootloader without sdcard in your phone
sent from my blazing fast pyramid through sonic waves
You can either superCID or add YOUR cid to the firmware file.
Either one is pretty simple. I'm going to assume that you have adb set up already, but if not you'll need that first.
SuperCID:
remove or rename PG58IMG.zip from sdcard
reboot into bootloader (power+vol down)
from adb/fastboot directory:
Code:
fastboot oem writecid 11111111
put PG58IMG.zip back on sdcard
boot into bootloader again and let flash complete
Edit PG58IMG.zip:
extract the zip file
locate the android_info.txt
edit the file with notepad++ to add your cid matching the format of the others listed
compress all extracted files into a new zip and flash
GROGG88 said:
You can either superCID or add YOUR cid to the firmware file.
Either one is pretty simple. I'm going to assume that you have adb set up already, but if not you'll need that first.
SuperCID:
remove or rename PG58IMG.zip from sdcard
reboot into bootloader (power+vol down)
from adb/fastboot directory:
Code:
fastboot oem writecid 11111111
put PG58IMG.zip back on sdcard
boot into bootloader again and let flash complete
Edit PG58IMG.zip:
extract the zip file
locate the android_info.txt
edit the file with notepad++ to add your cid matching the format of the others listed
compress all extracted files into a new zip and flash
Click to expand...
Click to collapse
I'm Such a noob i just got this phone today. I tried doing the Supercid Method but Command prompt isn't recognizing my phone.
and i don't understand the other method
ganeshp said:
You are soff?
Did you have fastboot/adb setup?
Can you go into bootloader and post the hboot, radio, son/soff status.
(to go into bootloader remove battery... Put it again then press volume down and power button together... You'll get a white screen.. Post the details from that..)
First of all if you used PG58IMG.zip for firmware update then either remove the file from sdcard via a card reader.. Or just boot into bootloader without sdcard in your phone
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
S-OFF
HBOOT- 1.27.1100
Radio-10.14.9035.01_M
19fonzy said:
S-OFF
HBOOT- 1.27.1100
Radio-10.14.9035.01_M
Click to expand...
Click to collapse
You need to go to fastboot from hboot screen use volume up/down buttons to browse through menu and use power button to enter it once you've selected fastboot.
Then connect your device to your pc
Your phone should read fastboot usb.. Once you've done this
Now go to you pc and
Type fastboot devices
If it shows your device serial number then good its connected
Now to SuperCID
fastboot oem writecid 11111111
This will do.. Make sure it has eight ones
Then after this you can update your firmware using the pg***file you got
sent from my blazing fast pyramid through sonic waves
ganeshp said:
You need to go to fastboot from hboot screen use volume up/down buttons to browse through menu and use power button to enter it once you've selected fastboot.
Then connect your device to your pc
Your phone should read fastboot usb.. Once you've done this
Now go to you pc and
Type fastboot devices
If it shows your device serial number then good its connected
Now to SuperCID
fastboot oem writecid 11111111
This will do.. Make sure it has eight ones
Then after this you can update your firmware using the pg***file you got
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
It Worked, Thank you so much
I have the same problem but i dont know how to connect to the computer through fastboot to supercid
BrianM23 said:
I have the same problem but i dont know how to connect to the computer through fastboot to supercid
Click to expand...
Click to collapse
You can use the tool from my signature. It has option for SuperCID.
Please read through the instructions before running the tool.
I'm trying to put 2 ROMS on an Desire S, but i get stuck. (separately from eachother)
I have the following:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
Jul 31 2012, 15:41:32
4EXT Recovery v2.2.7 RC5
Made an backup and this works in recovery.
I tried to install the following ROMS
- CM-10.1-20130808-signed.zip
- saga_PAC_JB_4.2.2-v23.0.0_20130706-232137.zip
and
gapps-jb-20130301.zip
I have wiped data/factory reset, cache, dalvik cache, battery stats.
then Install from sdcard.
CM-10.1-20130808-signed.zip
gapps-jb-20130301.zip
4EXT says installation has been completed
I reboot the phone and the screen gives first the white HTC boot screen and then there is an black screen and it 'll not proceed in the booting proces.
Am i doing something wrong? (I guess so but i don't know what the problem is) I have read several rooting guides on XDA but am a bit lost in the information.:silly:
Can somobody give me an helping hand.
Many thanks
ur S-ON and not S-OFF so u must do this:
1 open the rom.zip in your pc
2 extract the boot.img
3 put the boot.img in the folder where u have the fastboot.exe
4 in this folder hold shift button on the pc keybord and right click on the mouse and select "run windows command here"
5 put your phone in fastboot mode and connect into your pc
6 in the command line opened at point 4 write
" fastboot erase cache " and do the command.
now write
"fastboot flash boot boot.img " and do the command
this must be done everytime u change rom (otherwise u can s-off your device -> search in general topic)
Thx, i'll try this tommorow.
Send from GT-I9300 with Tapatalk
It works.
Thank you very much, it works like a charm.
Edit: solution to the problem in post #4
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
ilchkai said:
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
Click to expand...
Click to collapse
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
nelvinchi said:
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
Click to expand...
Click to collapse
excellent - thanks, pm sent
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Links
A little late, but:
SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
Stock Flashable zip: https://mega.co.nz/#!8d0jhQTS!N2V5KTty4spxzNOwU-43vzqd3BF_ektVbH_TuHec26c
TWRP: http://forum.xda-developers.com/showthread.php?t=2418938
ADB: http://forum.xda-developers.com/showthread.php?p=42407269 (i think you ment this one, right?)
Yaaay, fixed my mini. Thx for these instructions!
:laugh:
ilchkai said:
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Click to expand...
Click to collapse
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
please help
romy134 said:
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
Click to expand...
Click to collapse
I'm having the same problem.
I've followed those instructions over and over with different roms but TWRP always tells me that there is no OS installed when I do the final reboot. I am stuck at the white HTC screen and can't get any rom to load up. Please help.
This is what my bootloader says:
--TAMPERED--
--UNLOCKED--
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.25.40G.00.19
OPENDSP-V19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024mb
I can flash recoveries and boot.img. ADB works to push roms into /sdcard/, can also sideload. I'm suspecting my filesystem/ partition data is all screwed but but can't figure out why Roms won't load.
I got the phone yesterday and it was untouched, stock. I tried to follow this guide (http://forum.xda-developers.com/showthread.php?t=2789272) to get it rooted and install a custom rom. I got stuck at getting S-OFF. rumrunner was giving me the "Fatal: download latest package" error. I also could not get su in the shell to try firewater. At this point I was reading that people had luck getting S-OFF after installing JmzM4StockRootedOdex-WWE-1.22.401.1 custom rom and kernel. I tried to do that but I wasn't sure what I was doing and ended up with no OS and a bootloop at the white HTC screen. I have a bit of Android experience from messing with the HP touchpad tablet but I'm rusty and this phone has me beat right now.
Thanks for your help.
...
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
ilchkai said:
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
Click to expand...
Click to collapse
Thanks.. I've been using TWRP 2.7.1.0 because I read that I have the newer partion scheme with HBOOT 2.22 but I'm not really sure.
When I try TWRP 2.7.1.1 ADB doesn't work and I get a different /sdcard/ than in 2.7.1.0. Not sure what's going on there either.
The only reason I tried S-off is because I blindly followed that guide on how to get the HTC one mini up to date and that was the 2nd step. I should have skipped it and paid more attention to the custom rom flashing aspect.
I'll try TWRP 2.6.0.0 as I don't have many other options at this point.. I also tried to use CWM recovery but it couldnt flash a rom either.
Thanks for your input.
Hi I had a struggle yesterday because I know nothing about phones so I followed a guide to updating your phone, so I did it through bootloader/recovery and after installing the custom RUU it actually worked, but after loading up on the screen it shows instructions and shows that it's loading the page/phone and i thought maybe it was but it's been like that overnight so is there anyway around this? (I can get on the power off menu with restart etc but thats about it I cant x off the instructions or anything telling me the updates to the phone)
We need more info.
What guide you follow?
Bootloader info?
Hboot?
HTCDev unlock S-ON or revolutionary S-OFF?
What recovery you use?
Did you wiped all except sd?or just installed zip from sd card?
And what RUU you used(post link)?
SKENER said:
We need more info.
What guide you follow?
Bootloader info?
Hboot?
HTCDev unlock S-ON or revolutionary S-OFF?
What recovery you use?
Did you wiped all except sd?or just installed zip from sd card?
And what RUU you used(post link)?
Click to expand...
Click to collapse
i'm a noob to all this stuff so i'll link you the guide i followed and ill just post what comes up in bootloader
UNLOCKED
SAGA PVT SHIP S-ON RL
HBOOT-2.00. 0002
RADIO-3822.10.08.04_M
eMMC-boot
don't think i can post links as i'm new but i used a guide off this forum called [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 and the custom ROM I used is off this site too the title of the thread is called [ROM] [02-06] Primo-S - v4.1 [HTC One V port] Android 4.0.3 [Kernel 3.0]
I just read about [ROM] [02-06] Primo-S - v4.1 [HTC One V port] Android 4.0.3 [Kernel 3.0] and it works fine on HTC Desire S.
First of all it's rom not RUU. if you want to know difference read tutorials and guides here.
You have HTCDev unlocked bootloader and installed 4ext recovery.My recommendation is to flash new 4ext recovery first(touch one) that I uploaded.
Check MD5 : ADA2A56547EF258638AF94445744583B
Click to expand...
Click to collapse
of that zip file.
To do this follow step 3. in [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 just use recovery.img from attachment down here.
And now for your problem.From what I know this is common problem on S-ON HTCDev unlocked phones.
After flashing new rom you have to flash boot.img from fastboot.
First open your PrimoS-v4.1.zip then you will see file boot.img.Extract it to C:\android-tools.Get in boot by holding power button and volume down together.Connect USB and enter fastboot. (fastboot usb)
Go to start->run-> type cmd and press enter. A command prompt will now appear.
(just like step 4 in guide)
Type:
Code:
cd c:\android-tools [press enter]
fastboot devices [press enter]
this show if your phone is connected to computer
if you get nothing you are not connetced
if you get some info like ST9212IJKL then you type
fastboot flash boot boot.img [press enter]
you will see blue loading form in right upper corner of screen
very fast but that mean you flashed boot
When all this done reboot phone and you should get your rom started.Sometimes it takes up to 10min but no more then that.
If you don't get in like this then you have to go to recovery and wipe all except sd and flash rom again and follow step 4 in guide.
Try this then tell what you got.Good luck.
SKENER said:
I just read about [ROM] [02-06] Primo-S - v4.1 [HTC One V port] Android 4.0.3 [Kernel 3.0] and it works fine on HTC Desire S.
First of all it's rom not RUU. if you want to know difference read tutorials and guides here.
You have HTCDev unlocked bootloader and installed 4ext recovery.My recommendation is to flash new 4ext recovery first(touch one) that I uploaded.
of that zip file.
To do this follow step 3. in [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 just use recovery.img from attachment down here.
And now for your problem.From what I know this is common problem on S-ON HTCDev unlocked phones.
After flashing new rom you have to flash boot.img from fastboot.
First open your PrimoS-v4.1.zip then you will see file boot.img.Extract it to C:\android-tools.Get in boot by holding power button and volume down together.Connect USB and enter fastboot. (fastboot usb)
Go to start->run-> type cmd and press enter. A command prompt will now appear.
(just like step 4 in guide)
Type:
Code:
cd c:\android-tools [press enter]
fastboot devices [press enter]
this show if your phone is connected to computer
if you get nothing you are not connetced
if you get some info like ST9212IJKL then you type
fastboot flash boot boot.img [press enter]
you will see blue loading form in right upper corner of screen
very fast but that mean you flashed boot
When all this done reboot phone and you should get your rom started.Sometimes it takes up to 10min but no more then that.
If you don't get in like this then you have to go to recovery and wipe all except sd and flash rom again and follow step 4 in guide.
Try this then tell what you got.Good luck.
Click to expand...
Click to collapse
Hi thanks for the reply I did a few things earlier just messing about on recovery mode and it's sorted and it didn't even wipe my phone I still have all my contacts and stuff maybe they were saved on my sd card idk but yh works perfectly now cheers for your time and help.
Hi,
I had the same problem at the beginning as I was unlocked the bootloader with HTCDEV.
If you unlocked the bootloader with HTCDEV, you should flash the boot.img manually with fastboot to get it fixed.
1). Switch off the phone and trun it on to bootloader and go to the fastboot
2). Connect the device to the pc and connect it with fastboot (CMD)
3). extract the custom firmware (.zip) file and find the boot.img file
4). copy it to the location where your fastboot.exe located at (ex: C:\sdk\platform-tools\)
then flash it with
HTML:
fastboot flash boot boot.img
Hope this help you
Regards..
A friend has given me his Desire S to fix what I originally thought was just a stuck power button that prevented it from starting up. But the button is now fixes and I've been trying the last few days to get it to start up.
What I have tried so far is to enter Recovery mode, but upon choosing it, the phone would just go to the HTC logo screen, fibrate once and then fibrate agian after a second or two for a few times and the screen would go blank. The same happens with normal bootup. It also seems that the phone is still running with the blank screen because I have to pull the battery to startup again.
I then tried to use the latest RUU (Android 4.0) from HTC but the phone is not recognized by the computer (I think it is because it didn't startup enough to be able to present itself to the computer). So I unlocked it and used fastboot (from Ubuntu as OS) to flash the recovery (recovery_signed.img) and boot (boot_signed.img) from the RUU. With this recovery and normal startup would remain at the HTC screen and wouldn't go blank as before - still fibrates a few times.
I also tried to rename the rom.zip to PG88IMG.zip and putting it on a SD and the bootloader does detect it, but presents the normal boot screen afterwards (I think it complains about it being incorrect - the display is too quick for me to see the error).
Now I also have a Desire S and made a backup of it before I installed a custom ROM. So I also tried the recovery.img that I have from this backup, but then recovery is stuck on the blank screen again.
Is there anything that I did wrong, missed or may not have tried yet? And how can I go about to fix it?
PHONE DETAILS (from bootloader screen)
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
The PG88IMG wont work coz ur s-on. Ul need to extract the zip file and put the recovery.img in ur fastboot folder and then flash it from fastboot, volume down + power then select select fastboot then plug ur phone into pc and open a fastboot command window and type
fastboot flash recovery recovery.img
Also a ruu u run from fastboot and u need to relock ur bootloader.
(i dunno how all this is done using ubuntu but thats how on windows so im sure ul know or figure it out)
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
(On Ubuntu fastboot is installed as a program so I can call it after I CD to the extracted rom folder and I assume it is working since I didn't get any errors)
Pieter2627 said:
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Click to expand...
Click to collapse
Well it depends, could be 4ext recovery, CWM, or TWRP. But as far as the name, could be called peterpan.img and it wouldnt matter haha
Pieter2627 said:
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
Click to expand...
Click to collapse
Yh boot ur phone into fastboot, connect it to pc, relock bootloader and then run ruu. The ruu should be exe file so just double click it to run.
Ok, relocked it and went into fastboot mode and then opened the RUU, but was not recognized. Then followed this (droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/) since I used Win 8.1 for the RUU and it flashed successfully.
But it is still stuck on the HTC screen - gave it 30 minutes for the first boot after flash. Recovery is also still stuck, so I reflashed and same issue.
Radio is now 3831.19.00.110