Hi! Yesterday, after installation of new room my htc don't take signal phone. I can't make calls except emergency number. I try with other two roms but i have the same problem. Now, when i boot the phone, on the white screen of htc i see "this build is ford evelopment purposes only ecc."
Its not dead. The red writing upon boot is normal if you have custom ROM...
Did you flash the correct boot.img for your ROM ? Do you have the correct APN settings ?
Have you done a full wipe in recovery ? have you gone back to a ROM when signal did work ?
Hi, where i can find the correct boot.img for my rom?
I try some rom but i can't resolve problem.
Sounds like your efs or imei has gotten deleted. This happened a lot with the Vibrant when I had mine (not to me, but others complained about it constantly), so I always backed them up with ROM Manager, or SGS Kernel Flasher just in case. Not sure if it applies with the One S, but the symptoms are identical.
Sent from my HTC One S using XDA Premium
In phone identity there are Telephone name: htc one s but in Model number: Htc One X. Is this the problem????
No, that's not the problem. You'll find the right recovery where you got your rom.
Did you flash a One X rom?
Sent from my HTC One S using xda premium
Okin910 said:
In phone identity there are Telephone name: htc one s but in Model number: Htc One X. Is this the problem????
Click to expand...
Click to collapse
Simple. You flashed a ROM for the one X on your One S..
do a full wipe and flash the correct ROM
Friends, he didn't flash a wrong rom. He simply flashed a one s rom with a wrong text string. I'm pretty shure it's/was Pauls Ir1 1.78.401.2 DUO...
Here is a screenshot, as i kept a nandroidbackup.
And ey, would the device have been booting if it's a wrong rom?
Dualcore <-> Quadcore and so on?
rootrider said:
Friends, he didn't flash a wrong rom. He simply flashed a one s rom with a wrong text string. I'm pretty shure it's/was Pauls Ir1 1.78.401.2 DUO...
Here is a screenshot, as i kept a nandroidbackup.
And ey, would the device have been booting if it's a wrong rom?
Dualcore <-> Quadcore and so on?
Click to expand...
Click to collapse
yes you have a point there !! however i dont think anyone is brave enough to try it out lol.
So have you restored a nandroid ? How is it now ? if its still not right, Have you tried reflashing a ROM that signal did work on ??
1.78 ROMs require a boot.img update, So extract it from the ROM and flash in in fastboot.
azzledazzle said:
yes you have a point there !! however i dont think anyone is brave enough to try it out lol.
Click to expand...
Click to collapse
At least not by choice
azzledazzle said:
So have you restored a nandroid ? How is it now ? if its still not right, Have you tried reflashing a ROM that signal did work on ??
Click to expand...
Click to collapse
Everything works fine and dandy. Recovery of boot- and recovery-image works flawless. You can change between roms easily so far (as I did for the screenshot).
oops, nearly forgot: changed from LeeDroid to MoDaCo and back.
so your problem is now solved ??
excellent
Related
I installed ROM manager on my phone and when I tried to back up my ROM, it said I need to flash clockworkrecovery. I thought I already did that, when i rooted my phone and flashed revolutionaryHD 3.0 ... Will I screw things up if I click "ok" when manager prompts me to?
nextonline said:
I installed ROM manager on my phone and when I tried to back up my ROM, it said I need to flash clockworkrecovery. I thought I already did that, when i rooted my phone and flashed revolutionaryHD 3.0 ... Will I screw things up if I click "ok" when manager prompts me to?
Click to expand...
Click to collapse
I would just flash CWM again through ROM Manager. That samething happened to me on my NS.
Sent from my HTC Sensation using Tapatalk
It says that because alpharev recovery it's a different version of recovery. If you want to use rom manager you need to flash the one that it wants. And don't worry, I'm using it and it works
thats what i had to do
The version rom manager will flash has the charging bug. Just boot into recovery and back up from there. Not that hard
Sent from my HTC Sensation 4G using XDA App
Omg I flashed it before I read your comment about the bug... Guess I need to reflash the working one back.
nextonline said:
Omg I flashed it before I read your comment about the bug... Guess I need to reflash the working one back.
Click to expand...
Click to collapse
I wouldn't worry about the bug... I'm using that version and I have no problems, I also know people who flashed the "bugless" cwm, and they experienced the charging issue.... Its a case by case scenario, see what works for you... Just make sure you keep your battery from completely dying and monitor charging....
Sent from my Virtuous Sensation
I've got a perplexing problem. For some reason, after flashing certain ROMS I get stuck at the HTC boot screen (have waited 30mins so definitely stuck). Some ROMS work and others don't. For example, Android Revolution 3.03 and 3.04 worked, but 3.10 does not. All LeeDroid ROMS never work. I have asked in the actual ROM threads but nobody knows. Why would some ROMS work on my device, while others just hang at the boot screen?
Likely to be something low-level related. I'd use the Super Wipe script if you've not already before flashing the new ROM
Thanks for the reply. I have experienced this problem even after a super wipe. What is the simplest way to restore to factory (keeping the s-off of course) so I can start from scratch again?
Follow the guide in the Dev forum. You need to use your RUU to go back to stock
Have you been checking the ms5 checksum before flashing to be certain you don't have a bad download?
Sent from my HTC Sensation 4G using Tapatalk
i see more and more ppl getting this problem.. well you the second one P. yesterday i have experienced it aswell after using a wipe that i have used many times in the past.. the wipe refused to work so i ended up just flashing the rom instead... was wierd tho,
edit: btw what recovery were u using? I just tried out twerp at the time, altho i did successfully flash a rom with a wipe that same morning
Rhiannon224 said:
Have you been checking the ms5 checksum before flashing to be certain you don't have a bad download?
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
Silly me. No I haven't. I'll try this. Thx..
Hey Guys
Can someone please point me in right direction to download
RUU for UK network O2, build 1.50.206x ?
Just got my sensation back from repair and have rooted again. Ive also backed up the orginal ROM on my phone but would really like the RUU to go with it should I wish to go S-ON incase of any future problems.
Thanks guys
Aj =)
No such thing at present
EddyOS said:
No such thing at present
Click to expand...
Click to collapse
Thanks for getting back to me bud.
Isn't there really?.... even tho I've backed up that particular version of my phone?
I got it back today and that was the build number.
Can I still restore the backup in that case and go S-ON normally?
If you backed it up before adding root then yes you will be able to restore it, flash the stock recovery and S-ON to go back to stock
The only o2 RUU to leak was the original one that was out when the Sensation was first released. Good to know o2 have updated to 1.50 though
EddyOS said:
If you backed it up before adding root then yes you will be able to restore it, flash the stock recovery and S-ON to go back to stock
The only o2 RUU to leak was the original one that was out when the Sensation was first released. Good to know o2 have updated to 1.50 though
Click to expand...
Click to collapse
Hey, yep, I got s-off then installed clockwork then backed it up right away. I didn't root, I just flashed your Stock rooted XE ROM and all is good. the 1.73.401.4
So let me get this right.
I fullwipe, restore backup then flash the stock 1.18.000 recovery it had and thats it? I guess I must extract recovery img from the a 1.50xx ruu?
Radio?
@ ajay
I am getting shabby signal on my sensation ( ~45%MAX) on o2 uk.
I have tried a few radios with no luck so im hoping you can tell me, when your sensation came back with the o2 uk stock rom on it, which radio version was loaded onto it?
Was it the version in your signature?
Cheers
beady_uk said:
@ ajay
I am getting shabby signal on my sensation ( ~45%MAX) on o2 uk.
I have tried a few radios with no luck so im hoping you can tell me, when your sensation came back with the o2 uk stock rom on it, which radio version was loaded onto it?
Was it the version in your signature?
Cheers
Click to expand...
Click to collapse
Hello mate.
The radio in my signature is what I'm using now, although my phone returned to me with the radio from 1.45.xxx build.
Look in android development section for radios & you should see it. Hope this helps =)
ajay83 said:
Hello mate.
The radio in my signature is what I'm using now, although my phone returned to me with the radio from 1.45.xxx build.
Look in android development section for radios & you should see it. Hope this helps =)
Click to expand...
Click to collapse
ok thanks for that. I know about the radio thread and have tried 10.14, 10.15 & 11.16 and always have ****ty signal so just thought id see which radio o2 use for their roms.
How do you find the signal with the radio your using?
I never get full signal now in places where my desire would give me full signal.
Im starting to wonder if maybe the back cover with the antenna's in is a bit ****ty cos i get the wifi death grip quite severe.
Thanks again
ajay83 said:
Hey, yep, I got s-off then installed clockwork then backed it up right away. I didn't root, I just flashed your Stock rooted XE ROM and all is good. the 1.73.401.4
So let me get this right.
I fullwipe, restore backup then flash the stock 1.18.000 recovery it had and thats it? I guess I must extract recovery img from the a 1.50xx ruu?
Click to expand...
Click to collapse
You can get the HBOOT from any 1.45 RUU, but yes what you said pretty much sums it up. I would:
1. Restore backup
2. Flash stock recovery
3. Hard reset
4. Reset CID (if changed)
5. S-ON
6. Boot phone to make sure it works then hard reset again
Thanks EddyOS =)
Appreciate the advice bud.... Always handy to know how to cover your arse incase of the worst.
@beady_uk. Are you flashing the appropriate 'rils' to match the radios?
Can't really think of anything else bud. My radio & ril match & since I've done it this way I've always had good reception.
ajay83 said:
@beady_uk. Are you flashing the appropriate 'rils' to match the radios?
Can't really think of anything else bud. My radio & ril match & since I've done it this way I've always had good reception.
Click to expand...
Click to collapse
yeah mate ive matched radio's and ril's for 10.14 & 10.15 but i only get max of 45% reception when checking through the app "opensignal". Right now ive got no signal and on my desire i would normally have full.
Going to try a 2.3.4 rom as i have tried a few 2.3.5 roms with the same result.
hi guys,
my misses sensation is on O2 as well and after flashing ARHD 4.1.13 the reception went down noticeably. right, so ive donwoladed recomemnded radio from ARHD post ( 10.15.9035.02_2 ) I pressume i only have to pack the radio.img in a zip and run the bootmenu ?
do I have to be eng off ??
and finally battery life is barelly 14 h without using it can it be that radio or its becasue i let the phone to restore the apps after flasshing ??
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Is there a way to make the Desire S completely unlocked so that I can flash using cwm without the need of fastboot?
lowrider82 said:
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Is there a way to make the Desire S completely unlocked so that I can flash using cwm without the need of fastboot?
Click to expand...
Click to collapse
Yes. You need to downgrade your hboot, there are guides for this in the general section, you'll need to find a compatible ruu, get back to stock rom and then use revolutionary to S-Off
Sent from Purgatory - Still stuck between the One X and the SGS3.
How do i do the boot.img
Did it all on the exact same way you did
got the exact same problem at the moment.
Were do i find the boot.img and how do i go about getting it onto the phone
Im new to flashing
slugger7 said:
Did it all on the exact same way you did
got the exact same problem at the moment.
Were do i find the boot.img and how do i go about getting it onto the phone
Im new to flashing
Click to expand...
Click to collapse
I got a solution, but its a bit tricky: use the forum search
Sent from my HTC Desire S using xda app-developers app
Feel like an idiot lol
c.m.b said:
I got a solution, but its a bit tricky: use the forum search
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Yep found out like now and it is working now. Thanx for teaching me the ways of the force
slugger7 said:
Yep found out like now and it is working now. Thanx for teaching me the ways of the force
Click to expand...
Click to collapse
No problem, but use it with caution
Sent from my HTC Desire S using xda app-developers app
help needed.
c.m.b said:
No problem, but use it with caution
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
hey.
please help me..
i flashed the pacman rom using clockmod recovery..
i downloaded it ,copied into my sd and then installed it..
i am still stuck on htc screen..
please help..
i dont know what to do!
jigi1993 said:
hey.
please help me..
i flashed the pacman rom using clockmod recovery..
i downloaded it ,copied into my sd and then installed it..
i am still stuck on htc screen..
please help..
i dont know what to do!
Click to expand...
Click to collapse
Are you htcdev unlocked?
lowrider82 said:
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Click to expand...
Click to collapse
I have flashed many devices(Desire, Desire S, HD2, HD and One X) a hundred of times because I am a beta tester. So I know the ins and outs of flashing. But this time I need your help guys.
I have unlocked my Desire S (Hboot is 2.00.0002, S-ON, Radio 3822.10.50.24_M)
flashed TWRP recovery
flashed Viper Saga 2.1.3 JB
flashed boot.img
And the Rom booted and installed. All fine so far.
Now I want to install a different ROM.
Flashed the new PACman JB_2.2_v22 ROM, and boot.img. But this time I got stuck at white screen. So I tried CWM recovery and even 4EXT. Flashed Rom and its boot.img again. No luck. Stuck at white screen every time.
But now the weirdest. At the end I flashed TWRP recovery, Viper Rom and its boot.img again. And damn, I'm stuck at the white screen again.
Also weird is that I am not able to flash an official RUU after unlocking the bootloader again. When plugging in the device I can start the RUU installation proces. But during the sending firmware proces, the phone screen remains black with HTC on it for hours. So I had to remove the cable and boot the phone into bootloader again.
It looks like something is blocking these two processes.
Any ideas? I searched through XDA and on the internet. The only thing I can find to solve the white screen with green HTC is flashing boot.img. But that is not the issue.
The problem and sollution with the RUU installation, I haven't seen at all yet.
Hope somebody could point me in the right direction.
wanahave said:
I have flashed many devices(Desire, Desire S, HD2, HD and One X) a hundred of times because I am a beta tester. So I know the ins and outs of flashing. But this time I need your help guys.
I have unlocked my Desire S (Hboot is 2.00.0002, S-ON, Radio 3822.10.50.24_M)
flashed TWRP recovery
flashed Viper Saga 2.1.3 JB
flashed boot.img
And the Rom booted and installed. All fine so far.
Now I want to install a different ROM.
Flashed the new PACman JB_2.2_v22 ROM, and boot.img. But this time I got stuck at white screen. So I tried CWM recovery and even 4EXT. Flashed Rom and its boot.img again. No luck. Stuck at white screen every time.
But now the weirdest. At the end I flashed TWRP recovery, Viper Rom and its boot.img again. And damn, I'm stuck at the white screen again.
Also weird is that I am not able to flash an official RUU after unlocking the bootloader again. When plugging in the device I can start the RUU installation proces. But during the sending firmware proces, the phone screen remains black with HTC on it for hours. So I had to remove the cable and boot the phone into bootloader again.
It looks like something is blocking these two processes.
Any ideas? I searched through XDA and on the internet. The only thing I can find to solve the white screen with green HTC is flashing boot.img. But that is not the issue.
The problem and sollution with the RUU installation, I haven't seen at all yet.
Hope somebody could point me in the right direction.
Click to expand...
Click to collapse
To flash an ruu you need to lock your bootloader. As for the other issue do you know what panel your phone has, it's not an issue on sense roms and only becomes apparent in jb roms. Check http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge I'd your not sure
The person who reads too much and uses his brain too little will fall into lazy habits of thinking.
—Albert Einstein
AW: HTC DESIRE S stuck at HTC White screen after flash Plese help!
And the problem with flashing ViperSAGA from TWRP is a different issue, TWRP is known to be problematic, I would recommend 4ext.
jugg1es said:
To flash an ruu you need to lock your bootloader. As for the other issue do you know what panel your phone has, it's not an issue on sense roms and only becomes apparent in jb roms. Check http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge I'd your not sure
The person who reads too much and uses his brain too little will fall into lazy habits of thinking.
—Albert Einstein
Click to expand...
Click to collapse
Thanks for your reply.
Yes I've locked my phone again before installing the RUU. Made no sense. I've tried 2 WWE RUUs both with the same issue.
What panel I have I really don't know. Viper is sense. Worked om first flash. But after flashing PACman, the boot issues started. Now even Viper is not booting anymore.
I check the thread you posted. Will try the kernels. See what is happening.
EDIT: flashing these kernels do not work, because I'm S-ON. Need boot.image.
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
teadrinker said:
And the problem with flashing ViperSAGA from TWRP is a different issue, TWRP is known to be problematic, I would recommend 4ext.
Click to expand...
Click to collapse
As I wrote. I've tried all of them. Am now on 4EXT. But still facing same issues. White screen with green logo.
I'd start fresh, make sure your unlocked, check the drivers are installed correctly (are you on win 8, if so check post two of link in my sig) format all but sd in 4ext, flash rom (sense rom to start) flash kernel. Your obviously no noob but sometimes we miss the obvious. I'm around for a bit so report back
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
Hi tried to flash AOKP_saga_unofficial using goomanager twrp recovery downloaded then flashed Rom in goomanager but on reboot got white screen HTC logo stuck scenario any ideas what went wrong
Desire s
Unlocked and rooted using all in one tool
S-on still
Hboot 2xxxx not downgraded
Sent from my HTC Desire S using xda app-developers app
gazzy21uk said:
Hi tried to flash AOKP_saga_unofficial using goomanager twrp recovery downloaded then flashed Rom in goomanager but on reboot got white screen HTC logo stuck scenario any ideas what went wrong
Desire s
Unlocked and rooted using all in one tool
S-on still
Hboot 2xxxx not downgraded
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Did you flash boot.img?
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
Hi first time have done it thru goomanager I don't remember ticking or seeing option to flash boot image would it be safe to do so and be necessary thanks
have to research a bit more I was a bit lax flashing rom
Sent from my HTC Desire S using xda app-developers app
Sorry my bad
Should have read up a bit more didn't flash bootloader sorry for wasting your time also wondering if I should flash ext4 recovery instead of using twrp seems every body using ext4 now
Sent from my HTC Desire S using xda app-developers app
gazzy21uk said:
Sorry my bad
Should have read up a bit more didn't flash bootloader sorry for wasting your time also wondering if I should flash ext4 recovery instead of using twrp seems every body using ext4 now
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Don't worry about it, 4ext is the best recovery for our device. There seems to be a few issues with the other two.
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
having a look round revolutionary Rom looks better prospect see you using it atlas this stock gb is running near perfect only trying to improve battery drain 18-20MA in sleep at mo revolutionary has under clock facility which is only way I can see but at what cost
This may I say is a really excellent thread filled by people like me not reading up enough before we tinker to our cost and thanks to you xda this is a casualty department for noobs
Sent from my HTC Desire S using xda app-developers app
gazzy21uk said:
having a look round revolutionary Rom looks better prospect see you using it atlas this stock gb is running near perfect only trying to improve battery drain 18-20MA in sleep at mo revolutionary has under clock facility which is only way I can see but at what cost
This may I say is a really excellent thread filled by people like me not reading up enough before we tinker to our cost and thanks to you xda this is a casualty department for noobs
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
The casualty department is located in the help Thread (follow link in my sig)
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app
Zombie thread alert!
Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app
_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita