hi every time i start my HTC desire s after flashing a new rom it gets stuck on the white htc screen. i follow this guide to root and flash and for months its been going well, ive changed my roms many times, but now after trying to install a new jelly bean rom. evreytime i boot up the phone it gets stuck on the htc boot screen.
here is what i do when i flash a new ROM
extract the boot.img from rom i want to android tools folder (adb,fastboot folder)
wipe data/factory reset
wipe cache
wipe dalvik cache
install the rom i want
reboot into bootloader and enter the code: fastboot flash boot boot.img
it tells me its finished in cmd and then i reboot to get the same stuck white htc screen.
i can still access 4EXT Recovery
please help :[
smiah789 said:
hi every time i start my HTC desire s after flashing a new rom it gets stuck on the white htc screen. i follow this guide to root and flash and for months its been going well, ive changed my roms many times, but now after trying to install a new jelly bean rom. evreytime i boot up the phone it gets stuck on the htc boot screen.
here is what i do when i flash a new ROM
extract the boot.img from rom i want to android tools folder (adb,fastboot folder)
wipe data/factory reset
wipe cache
wipe dalvik cache
install the rom i want
reboot into bootloader and enter the code: fastboot flash boot boot.img
it tells me its finished in cmd and then i reboot to get the same stuck white htc screen.
i can still access 4EXT Recovery
please help :[
Click to expand...
Click to collapse
Your problem is that you're on the wrong hBoot - now go and do some searching and reading before coming back with any more questions that have been asked and answered 10 times in the last week alone :banghead:
SimonTS said:
Your problem is that you're on the wrong hBoot - now go and do some searching and reading before coming back with any more questions that have been asked and answered 10 times in the last week alone :banghead:
Click to expand...
Click to collapse
im on the wrong hboot? ive been on hboot 2.00.002 for 4-5 months why would it give me problems now ?
smiah789 said:
im on the wrong hboot? ive been on hboot 2.00.002 for 4-5 months why would it give me problems now ?
Click to expand...
Click to collapse
In that case, still searching would have revealed the likely cause;-
[OFF-TOPIC] Non-Sony screen panel DS users lounge
SimonTS said:
In that case, still searching would have revealed the likely cause;-
[OFF-TOPIC] Non-Sony screen panel DS users lounge
Click to expand...
Click to collapse
I still cant find the solution as installing any rom such as ice cream sandwich doesn't work, i still get the frozen htc screen. I tried searching for other methods but cant find the solution
smiah789 said:
I still cant find the solution as installing any rom such as ice cream sandwich doesn't work, i still get the frozen htc screen. I tried searching for other methods but cant find the solution
Click to expand...
Click to collapse
There are only three causes I can think of for the problem you have described;-
1) You aren't flashing the kernel
2) You have the wrong hBoot and it doesn't include the partition required for the new ROMs
3) You have the 'other' type of panel and need to use the specialist kernel
SimonTS said:
There are only three causes I can think of for the problem you have described;-
1) You aren't flashing the kernel
2) You have the wrong hBoot and it doesn't include the partition required for the new ROMs
3) You have the 'other' type of panel and need to use the specialist kernel
Click to expand...
Click to collapse
Actually, none of those seem to be the case here:
1. If the op is following the procedure he outlined in the first post, he is flashing the kernel
2. The op has already specified, that he is on hboot 2.00.002, any rom will work with that
3. If the op can't install ics roms either (as specified in his last post), then it can't be (only) the panel issue.
Please read before responding, SimonTS
That all being said, I can't think what the problem might be.
teadrinker said:
Actually, none of those seem to be the case here:
1. If the op is following the procedure he outlined in the first post, he is flashing the kernel
2. The op has already specified, that he is on hboot 2.00.002, any rom will work with that
3. If the op can't install ics roms either (as specified in his last post), then it can't be (only) the panel issue.
Please read before responding, SimonTS
That all being said, I can't think what the problem might be.
Click to expand...
Click to collapse
Excuse me for upsetting you in such a monumental way oh great one. I originally suggested (maybe a little abruptly, but given the majority of the posts on here and the total lack of information provided by the OP it was fair) that it was the hBoot as this is by far the most likely cause - he said he was running v2.00.002. I then suggested he look at the panel issue - he then decided to say that it wasn't just JB ROMs, but also ICS ones which had a problem. I then said I could only think of three possible causes - the same three that you can think of.
What, EXACTLY, did I say in there that caused you such upset?
The fact is that the OP STILL hasn't provided any useful information about his phone to help us help him - and he should still check his panel as a possible issue; maybe by trying to flash JB ROMs on the wrong type of panel he has caused further problems? I don't know and am just stood there with my manhood flapping in the wind to try and suggest anything else without further information from the OP.
SimonTS said:
Excuse me for upsetting you in such a monumental way oh great one. I originally suggested (maybe a little abruptly, but given the majority of the posts on here and the total lack of information provided by the OP it was fair) that it was the hBoot as this is by far the most likely cause - he said he was running v2.00.002. I then suggested he look at the panel issue - he then decided to say that it wasn't just JB ROMs, but also ICS ones which had a problem. I then said I could only think of three possible causes - the same three that you can think of.
What, EXACTLY, did I say in there that caused you such upset?
The fact is that the OP STILL hasn't provided any useful information about his phone to help us help him - and he should still check his panel as a possible issue; maybe by trying to flash JB ROMs on the wrong type of panel he has caused further problems? I don't know and am just stood there with my manhood flapping in the wind to try and suggest anything else without further information from the OP.
Click to expand...
Click to collapse
Sorry!! Didn't mean it to come across like that. I have as little idea as you what's causing this problem.
Come on you two we actually have a good question here, please let's not argue.
Can the op please post the contents of his bootloader screen.
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.
Albert Einstein
jugg1es said:
Come on you two we actually have a good question here, please let's not argue.
Can the op please post the contents of his bootloader screen.
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.
Albert Einstein
Click to expand...
Click to collapse
yeah, sure! no problem
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
ive also taken a picture of the bootloader
http://imgur.com/00TAn
This is going to sound a stupid question, are you turning off fastboot first and then pushing the img.
“Any fool can use a computer.* Many do.”
(Ted Nelson)
jugg1es said:
This is going to sound a stupid question, are you turning off fastboot first and then pushing the img.
“Any fool can use a computer.* Many do.”
(Ted Nelson)
Click to expand...
Click to collapse
After i install a rom i power it down and boot into the bootloader, connect the usb, click fast boot then push the roms img file
Ok, I'm at a loss. Anyone else?
“Any fool can use a computer.* Many do.”
(Ted Nelson)
anyone have any other ideas? :[
smiah789 said:
anyone have any other ideas? :[
Click to expand...
Click to collapse
Can you still flash GB roms?
“Any fool can use a computer.* Many do.”
(Ted Nelson)
smiah789 said:
anyone have any other ideas? :[
Click to expand...
Click to collapse
If I was in your situation then I would be starting from basics;-
Full wipe - EVERYTHING
Re-install 4EXT Touch Recovery (latest version) - Check MD5 after downloading
Re-flash hBoot - Check MD5 after downloading
Full wipe - EVERYTHING
Format all partitions to EXT4 (not EXT3)
Full wipe - EVERYTHING
Install an ICS or JB ROM - Check MD5 after downloading
If this fails then do all the above but with a known solid GB ROM - Reaper or Endymion to make sure there's not something worse going on.
Also, regardless of your previous answer, do the test to ensure which panel your DS has - better to waste 2 minutes and be proved right than waste 2 days if you are wrong.
SimonTS said:
If I was in your situation then I would be starting from basics;-
Full wipe - EVERYTHING
Re-install 4EXT Touch Recovery (latest version) - Check MD5 after downloading
Re-flash hBoot - Check MD5 after downloading
Full wipe - EVERYTHING
Format all partitions to EXT4 (not EXT3)
Full wipe - EVERYTHING
Install an ICS or JB ROM - Check MD5 after downloading
If this fails then do all the above but with a known solid GB ROM - Reaper or Endymion to make sure there's not something worse going on.
Also, regardless of your previous answer, do the test to ensure which panel your DS has - better to waste 2 minutes and be proved right than waste 2 days if you are wrong.
Click to expand...
Click to collapse
THANK YOU EVREYBODY SOO MUCH , IT WORKS!!
after seeing his suggestion to reflash the recovery, i flashed clockwork recovery via fastboot,picked a ics rom, did the usual steps and it worked!!
smiah789 said:
THANK YOU EVREYBODY SOO MUCH , IT WORKS!!
after seeing his suggestion to reflash the recovery, i flashed clockwork recovery via fastboot,picked a ics rom, did the usual steps and it worked!!
Click to expand...
Click to collapse
Glad to see that the old engineering principle I learnt years ago still works - KISS (Keep It Simple Stupid)
smiah789 said:
THANK YOU EVREYBODY SOO MUCH , IT WORKS!!
after seeing his suggestion to reflash the recovery, i flashed clockwork recovery via fastboot,picked a ics rom, did the usual steps and it worked!!
Click to expand...
Click to collapse
Could you mark the op as solved, glad your back up and running.:thumbup:
“Any fool can use a computer.* Many do.”
(Ted Nelson)
Related
So I can't figure out how to fix this, and have a completely useless phone at the moment, unfortunately.
I wanted to install Virtuous Inquisition. I was coming from ARHD 4.1.10 Gingerbread. This is the process I followed:
1. Downloaded Firmware and ROM from website.
2. Loaded both onto SDCard
3. Rebooted into recovery, PG58IMG did it's work.
4. Formatted / Wiped all Data
5. Installed Virtuous Inquisition
At this point I was thrown into a continuous boot loop. Read up on the forums, apparently Virtuous is only tested for CWM.
Tried installing CWM - downloaded the zip, renamed it PG58IMG.zip, tossed it onto the phone, gets stuck at "Parsing," and fails.
Tried reinstalling firmware again - Creates error "Wrong CID"
Tried installing CWM from the 1st post of the Sensation Rooting Thread, said "Wrong Version."
Completely confused as to how to fix my phone now.
Please, PLEASE help.
Thanks XDA.
Delete all pg58img.zip from SD card, try to reboot and post result.
Leaving the firmware zip in SD root after update causes boot loops.
Sent from my Pyramid-T
Unfortunately I still get the boot loops -
I get the Virtuous Boot Animation, then it just kills itself.
OK does fastboot work?
Sent from my Pyramid-T
gotpriest said:
Unfortunately I still get the boot loops -
I get the Virtuous Boot Animation, then it just kills itself.
Click to expand...
Click to collapse
Try the virtuous 2.23 thread. It's a 2.3.4 Rom but it comes with its own firmware. See if that boots up before trying anything else.
stringer7 said:
OK does fastboot work?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Unfortunately I'm rather unfamiliar with this term - if you mean can I get into the bootloader, yes, and I can get into 4EXT.
I vaguely remember when rooting my phone that I had to connect it to the computer to do some adb things, but have not tried / done that since.
Currently I have a spare SDCard, and am trying the entire process over real quick, then going to try TC's idea.
Update: Loading the Firmware again still gave me the "CID Incorrect!" error in the bootloader.
Update 2:
tropical cactus said:
Try the virtuous 2.23 thread. It's a 2.3.4 Rom but it comes with its own firmware. See if that boots up before trying anything else.
Click to expand...
Click to collapse
Going to that thread points you to the Virtuous Site - 2.2.0 Rom is Listed, but the Firmware is not bundled. Trying it anyway right now.
gotpriest said:
Unfortunately I'm rather unfamiliar with this term - if you mean can I get into the bootloader, yes, and I can get into 4EXT.
I vaguely remember when rooting my phone that I had to connect it to the computer to do some adb things, but have not tried / done that since.
Currently I have a spare SDCard, and am trying the entire process over real quick, then going to try TC's idea.
Update: Loading the Firmware again still gave me the "CID Incorrect!" error in the bootloader.
Click to expand...
Click to collapse
If you can get into recovery, then all's not lost.
Edit: sounds like you haven't super cided.
gotpriest said:
1. Downloaded Firmware and ROM from website.
2. Loaded both onto SDCard
3. Rebooted into recovery, PG58IMG did it's work.
4. Formatted / Wiped all Data
5. Installed Virtuous Inquisition
Tried reinstalling firmware again - Creates error "Wrong CID"
Click to expand...
Click to collapse
First and foremost, did you do a nandroid backup before you did any of this? If so just revert back.
Next, in step 3, you said you booted into recovery to flash the PG58IMG. You plain can't do that. All firmware updates are done through the bootloader not recovery.
And you also mentioned, wrong CID. Do you recall ever doing a superCID on your phone? If not, read through http://forum.xda-developers.com/showthread.php?t=1459767 to get the correct firmware. IF you go there for the firmware (I suggest 3.24), you do not need superCID on your phone.
GL
Sorry, wrong wording, I did originally do the PG58IMG through Bootloader.
Quite, *quite* stupidly, I only did a Titanium backup, not a nandroid backup.
I have not done SuperCID on my phone.
Working on multiple options you guys have posted at the moment, y'all type too fast for my SDCard switching speeds!
As a side question at the moment, the Virtuous website mentioned that it has only tested through CWM. I was under the impression that 4EXT, while a different interface, behaved and functioned no differently than CWM. I may be wrong on this, but either way, I cannot get CWM to take control. It won't flash in the bootloader (gets stuck at "Parsing") and installing a Zip of it through 4EXT opens it, but does not make it the primary Recovery method
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Update 2: The Virtuous Boot animation has gotten far enough for the V to begin pulsing. It has never gotten this far. I think it may actually be going through the "initial" boot up sequence. May take a few minutes.
gotpriest said:
Sorry, wrong wording, I did originally do the PG58IMG through Bootloader.
Quite, *quite* stupidly, I only did a Titanium backup, not a nandroid backup.
I have not done SuperCID on my phone.
Working on multiple options you guys have posted at the moment, y'all type too fast for my SDCard switching speeds!
As a side question at the moment, the Virtuous website mentioned that it has only tested through CWM. I was under the impression that 4EXT, while a different interface, behaved and functioned no differently than CWM. I may be wrong on this, but either way, I cannot get CWM to take control. It won't flash in the bootloader (gets stuck at "Parsing") and installing a Zip of it through 4EXT opens it, but does not make it the primary Recovery method
Click to expand...
Click to collapse
I use 4ext for my recovery and works just as well. Just use the firmware in that thread I mentioned. That thread is a great one to read up on. Especially for people who are new to CID terminologies.
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
gotpriest said:
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Click to expand...
Click to collapse
The only thing Nandroids do not back up are radios, SD stuff, kernels,firmware and RIL files. The RIL and Radio's are bundled in the rom itself. So essentially the nandroid backs up the ROM itself. Hope that makes sense.
Hope its working now? My thought was the problem was firmware you flashed originally not supported by your CID = boot loop.
SupwrCID def recommended!
Sent from my Pyramid-T
Jesus Joseph and Mary you guys saved my Bacon. Working Phone. Thanks to all, particularly kpjimmy for the right firmware link!
Lessons Learned:
1. Don't be an Idiot.
2. Murphy is an Asshole
3. Do nandroid backups
4. SuperCID my phone.
5. Stop trying to Flash ROMS on my phone when I haven't slept in 24 hours.
6. Don't be an Idiot.
stringer7 said:
Hope its working now? My thought was the problem was firmware you flashed originally not supported by your CID = boot loop.
SupwrCID def recommended!
Sent from my Pyramid-T
Click to expand...
Click to collapse
Correct, you were on the right track. I have not done SuperCID, so when I installed the Firmware straight from Virtuous, it wasn't T-Mo specific.
gotpriest said:
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Update 2: The Virtuous Boot animation has gotten far enough for the V to begin pulsing. It has never gotten this far. I think it may actually be going through the "initial" boot up sequence. May take a few minutes.
Click to expand...
Click to collapse
Happy for you. We've all been to hell and back before.
tropical cactus said:
Happy for you. We've all been to hell and back before.
Click to expand...
Click to collapse
It actually scared the crap out of me. I switched back and forth between about 5 AOSP ROMS on my MyTouch back in the day, and have done countless ones on my Senny. This was my first firmware update though, so clearly that was the issue - but I should really learn to stop doing these things on weekdays when I urgently need my phone...
Glad it worked. Enjoy VI 3.5. I know I am
gotpriest said:
It actually scared the crap out of me. I switched back and forth between about 5 AOSP ROMS on my MyTouch back in the day, and have done countless ones on my Senny. This was my first firmware update though, so clearly that was the issue - but I should really learn to stop doing these things on weekdays when I urgently need my phone...
Click to expand...
Click to collapse
Been there and done that. Leave the high for the weekend.
I tried to update my HTC Desire S with ICS update downloaded from HTC and although it appeared to install fine the phone won't boot. It just sits on a black screen, and if I try to enter recovery it shown the red triangle with the exclamation mark! I've tried Factory Reset but that does not work.
I have read that I should NOT have install an official ROM through the RUU while being on S-OFF and that I should have used PG88IMG.zip instead
There was nothing I need on the phone so I did not make a backup and I’m not sure how to access the SD card while in volume down and power mode.
What can I do to fix this issue?
If i press volume down and power:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3831.19.00.110
eMMC-boot
Mar 10 2011, 14:58:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Your hboot version is not ringing any bells?
Hint: you do not have a custom recovery anymore
Sent from my HTC Desire S
amidabuddha said:
Your hboot version is not ringing any bells?
Hint: you do not have a custom recovery anymore
Sent from my HTC Desire S
Click to expand...
Click to collapse
how do i fix it or is the phone completely dead.
Shabz81 said:
how do i fix it or is the phone completely dead.
Click to expand...
Click to collapse
Don't worry, you didn't brick your phone yet. But your HBOOT (v6.98.1002) doesn't support the /system/lib partition necessary for the ICS RUU. That's why the installation didn't succeed and why your phone can't boot. You should be able to flash a custom recovery again and from this recovery a custom ROM. You also upgraded your radio when you tried to flash the RUU.
yaonos said:
Don't worry, you didn't brick your phone yet. But your HBOOT (v6.98.1002) doesn't support the /system/lib partition necessary for the ICS RUU. That's why the installation didn't succeed and why your phone can't boot. You should be able to flash a custom recovery again and from this recovery a custom ROM. You also upgraded your radio when you tried to flash the RUU.
Click to expand...
Click to collapse
How do I do this? please explain in a simple step-by-step guide as I don’t want to do any more damage.
can anyone help with this issue?
The silence is a small hint for you. It's called "Google it".
People are tired of answering the same questions 3 times a day.
Look at the General section, there's another one like you.
Jack_R1 said:
The silence is a small hint for you. It's called "Google it".
People are tired of answering the same questions 3 times a day.
Look at the General section, there's another one like you.
Click to expand...
Click to collapse
Thanks for nothing Jack
I manage to fixed it by following this link: http://forum.xda-developers.com/showthread.php?t=1679338
I used a second sd card, I formatted it first and only put the file I need at that time on it. I
In step 5 Reboot into bootloade, select recovery wait till you see the screen with the red triangle exclamation mark and press the volume up and power button at the same time.
You will enter the Android system recovery <3e> and see the following options:
reboot system now
apply update from SD card
wipe data/factory reset
wipe cache partition
wipe the cache partition and wipe data/factory reset
Now following step B from this link: http://forum.xda-developers.com/showthread.php?t=1858508
When update is finished - reboot, then configure ICS and delete PG88IMG.zip from sd card.
Congratulations - you actually did what Jack suggested and SEARCHED. We do not exist here as free tech-support for people who are too lazy to bother searching or reading - especially when the same damn question is asked time after time after time.
On another note - insulting very knowledgeable and respected members of the forum is a very, very stupid thing to do. Firstly because it will get his back, and many other peoples' backs, right up. Secondly, because if he was so minded then you could easily find the next response you get to a question is either total silence or advice that would end up bricking your phone totally.
When you rely on people, do not pi$$ them off - that is one of the first things you learn as a soldier and is is equally applicable in everyday life.
SimonTS said:
When you rely on people, do not pi$$ them off - that is one of the first things you learn as a soldier and is is equally applicable in everyday life.
Click to expand...
Click to collapse
So true.
@Jack_R1 and SimonTS. I did not mean to piss anyone off, I was just seeking an answer
#3
please tell me step by step!
Little Sykes said:
please tell me step by step!
Click to expand...
Click to collapse
Search and read - First rule of XDA.
The link for recovery, the pg88img method.
http://forum.xda-developers.com/showthread.php?p=41343637
Sent from my HTC Desire S using XDA Free mobile app
Thats because yer using a stock recovery. If you want to enter it,just press v up and power on warning black screen. Easy.
Sent from my Desire S using XDA Free mobile app
Hi guys.
I have a strange problem.
when I'm trying to flash custom ROMS, mostly cyanogen ROMS,
I do a full wipe and try to flash the ROM, it finishes, but when I reboot my phone it gets stuck on the HTC logo until the battery runs out and then I have to return to a different ROM.
I managed to flash cyanogen 7 but then I tried to update to 10 and again it got stuck on the HTC logo and now I cant return to cyanogen 7 even with my nandroid backup.
what can I do to fix this?
I looked all over the forum but I didn't manage to find any post with a fix for my problem
my HBOOT is 6.98.1002 and RADIO 3831.17.00.310
and I'm S-Off using revolution
and I'm currently using fallout 5.0 which lags alot (thats mainly wht I want to try the cyanogen)
any help would be very appreciated.
thanks
o`ebii said:
Hi guys.
I have a strange problem.
when I'm trying to flash custom ROMS, mostly cyanogen ROMS,
I do a full wipe and try to flash the ROM, it finishes, but when I reboot my phone it gets stuck on the HTC logo until the battery runs out and then I have to return to a different ROM.
I managed to flash cyanogen 7 but then I tried to update to 10 and again it got stuck on the HTC logo and now I cant return to cyanogen 7 even with my nandroid backup.
what can I do to fix this?
I looked all over the forum but I didn't manage to find any post with a fix for my problem
my HBOOT is 6.98.1002 and RADIO 3831.17.00.310
and I'm S-Off using revolution
and I'm currently using fallout 5.0 which lags alot (thats mainly wht I want to try the cyanogen)
any help would be very appreciated.
thanks
Click to expand...
Click to collapse
Do you try to update recovery?
I didn't but I didn't think it would matter seeing as it finishes the ROM installation but just gets stuck when i reboot.
also I have CWM recovery 5.0.2.0 and I think thats a latest for Desire S
o`ebii said:
I didn't but I didn't think it would matter seeing as it finishes the ROM installation but just gets stuck when i reboot.
also I have CWM recovery 5.0.2.0 and I think thats a latest for Desire S
Click to expand...
Click to collapse
u have a hitaci display u only have 2 flash a different kernel man and all be ok
read THIS
o`ebii said:
I didn't but I didn't think it would matter seeing as it finishes the ROM installation but just gets stuck when i reboot.
also I have CWM recovery 5.0.2.0 and I think thats a latest for Desire S
Click to expand...
Click to collapse
As a suggestion change cwm for 4ext, there have been issues with cwm not formatting the partitions properly and some issues on flashing files. Also take a look at the none Sony panel users hangout lounge, click the link in my sig and you'll find a link on post 2
“So many books, so little time.”
― Frank Zappa
ok thanks alot I'll try flashing the new kernel, and also does it matters which HBOOT I have?
should I try to upgrade to 2.x.x? or it doesn't really matters?
o`ebii said:
ok thanks alot I'll try flashing the new kernel, and also does it matters which HBOOT I have?
should I try to upgrade to 2.x.x? or it doesn't really matters?
Click to expand...
Click to collapse
only matter if in the rom post there is written
anyway if u want upgrade hboot put the 7.00.1002 search it in the forum (this is an hboot 2.x.x rearranged )
Ok, thanks alot for help
o`ebii said:
Ok, thanks alot for help
Click to expand...
Click to collapse
Hboot 7.00.1002
ok I think I might have a big problem now,
I tried doing what's written in this guid http://forum.xda-developers.com/showthread.php?t=1943524 and it seemed like there was an improvement..
only than I realised it got stuck on the bootanimation this time..
I waited, and I guess the battery was draind or something becuase my phone was shutdown, but now I cant open it or even get into bootloader.
it just vibrated for 7 times in a row and thats it.
I'm not even sure if it's charging when I plug it in
please help..
Have a read of this post, it looks like the same issues you have worth your hboot version http://forum.xda-developers.com/showthread.php?p=38466304
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
well right now I think the main problem is that I can't open the device, even HBOOT or reccovery. nothing.
I'm not sure if it's even charging.
I don't know how to use adb when the phone is completly closed and the computer doesn't even reconize it.
I really don't know what to do from here...
bump
please help guys
o`ebii said:
bump
please help guys
Click to expand...
Click to collapse
In post 2 of the help thread in my sig is a link to how to set up and run adb, sounds like you dont have the drivers installed correctly, what os are you on?
“To live is the rarest thing in the world. Most people exist, that is all.”
― Oscar Wilde
did you update to the latest "boot.img"
For example in "[Flinny] Andromadus Test builds - CM10.1[16]" is Kernel version 3.0.66.
I did update the kernel
After that used 4Ext v1.0.0.5 RC8 to format the system and seperate system_lib
Installed Flinny and had no problems.
I am using
HBoot : 7.00.1002
Baseband : 20.48011.30.0822U_3822.10.50.24_M
Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)
first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium
exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.
I have the htc one x with Rogers, version 3.17.631.2... the RUU isn't available for this version.
***TAMPERED***
***UNLOCKED***
s-on
Currently I have no OS installed, I have been searching through forums on this website for about 6 hours last night with no solution. Can someone please help. Thanks
I also have the token ID saved on my computer.
What I tried was:
installing the stock rogers PJ83IMG.zip from here
but since my version is 3.17.631.2 it wouldn't let me downgrade to the 1.73.631.1 version
Any suggestions?
Why are you trying to ruu. In order to ruu downgrade you will need to be s-off.
Sent from my VENOMized HoxL
is there any way to be s-off with no OS installed?
1. How did you even delete the OS?
2. Do you have a custom recovery?
Sent from my HTC One XL using XDA Premium 4 mobile app
I was installing a custom rom, and erased the OS by accident in TRWP, and I can flash a custom recovery on my phone. What would i do after that though?
Also go to the cleanROM thread and use their boot.img to get things at least booting up
You don't need soff to flash img files via fastboot
Sent from my HTC One XL using XDA Premium 4 mobile app
alright im giving it a try atm!
Why not just flash a ROM? You already have a custom recovery on your phone, that's what TWRP is. Should you really be messing with your phone in the first place though? It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Sent from my Evita
I LOVE YOU GUYS!
its all fixed up
timmaaa said:
It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Click to expand...
Click to collapse
I tend to agree. There has also seems to be an increase of this occurrence in the last several months of "I wiped the OS accidentally and I don't know how to recover". Which is a bit troubling since the default wipe in TWRP is factory reset, Dalvik, and cache. The Wipe screen on TWRP explicitly states that this is all the is usually needed. If you wipe /system, you did so deliberately by going into the Advanced screen and picking it from there. Meaning the OP took extra steps to do something without knowing if it was necessary, and without knowing how to recover from it.
This also means the OP didn't create a nandroid backup in TWRP, which would have been a simple way to recover. This is basic, fundamental step that should be taken whenever modding a phone, but something n00bs seem to be "skipping" (or ignorant of) lately.
This type of behavior/mindset while modding does not bode well for the life of your phone.
actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
I've learned what i have done wrong, and thank you guys for it.
I currently have cleanROM flashed on my phone, but its really buggy.. it even turns off randomly and if i ever lose reception I will have to restart my phone to gain reception again. Not sure why this is happening? What do you guys suggest I do?
You need to search properly before posting. It's XDA rules. The reboots and signal loss problems have been discussed countless times in the Cleanrom thread. Read a few of the last pages and you're guaranteed to find the solution.
Sent from my Evita
ecakici said:
actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
Click to expand...
Click to collapse
That's a pretty lame excuse. My previous general notion still holds: You took deliberate steps to wipe the OS (/system) as that option is still not selected as default even on older versions of TWRP. And you were therefore wiping things willy-nilly without understanding what they were, whether they really needed to be wiped, or how to recover from them.
And you still should have made a nandroid (TWRP backup).
All in all, it implies a careless mindset while modding your phone (skipping steps and doing things without understanding).
I have searched the forum: [ROM][9/11] - CleanROM 7.0.P1 -★| Android 4.2.2! | Sense 5! | Lite! | Stable! |★-
and found that if i install hboot 2.15 on my phone it should stop rebooting and the reception would go back to normal right?
is there anything else I have to do.
please, if it isn't too much trouble link me to a guide that fixes these issue for the HTC One X (Rogers)
or just give me a few steps of how to fix these issue.
Thank you so much!
PS my battery life improved so much, i usually charged my phone twice a day, and I haven't charged my phone at since 7am today.
Yes. Flash the 2.15 firmware. It's in the first post of Turge's stock Sense 5 ROM thread in the development section.
Sent from my Evita
Step 1: SuperCID 11111111
Step 2: S-Off using beaups guide
Step 3: Flash the 2.15 firmware
Can someone link me to the best guide to follow for step 1?
You can do it two ways, here's the first:
Step 1: SuperCID with hex edit method.
Step 2: S-off with Facepalm S-off.
Step 3: Flash firmware.
Or the other way:
Step 1: S-off with Rumrunner S-off.
Step 2: SuperCID with fastboot command:
Code:
fastboot oem writecid 11111111
Step 3: Flash firmware.
I believe the second method is easier. The Rumrunner s-off process seems much easier, it doesn't require you to have SuperCID first to work. Once s-off is achieved you can easily change your CID by fastboot command as opposed to messing around with hex editing.
Sent from my Evita
thanks a lot guys!
i learned a lot through this forum!
HTC One X plus OS has been deleted accidentaly
ecakici said:
I LOVE YOU GUYS!
its all fixed up
Click to expand...
Click to collapse
Can u plz tell me how did u u fixed it
reachsoumendra said:
Can u plz tell me how did u u fixed it
Click to expand...
Click to collapse
What is your exact problem?
Sent from my Evita.