I rooted and unlocked my One S[S4] by this guide http://forum.xda-developers.com/showthread.php?t=1583427 and it went fine.
Wifi was working fine on stock Rom but when I flashed LeeDroid's Rom and booted the wifi didn't turn on. I just said error.
Then I tried Flashing Viper One S rom and no luck it gave the same error. I tried flashing the kernel and still didn't work.
Anyway I kept on trying different things and got the wifi to turn on but now it shows the connection but doesn't connect to it. It tries two three times and automatically turns off or the phone hangs and restarts.
Please help I need wifi and I can't get it to connect.
Baseband version: 1.08ts.50.02.16_10.08e.50.04L
Build Number: 2.31.401.5 CL81535
HELP!!
Anyone here can help me please. I'm stuck with this problem as I cannot find a direct solution and I have tried eveything I can but cannot get it to connect.
When you flashed it, did you flash the boot.img before, too? Do this!
And, also important: After each change of ROM, always also wipe "System" in Recovery! Maybe some ROMs don't do so automatically. And if you change from ROM A to ROM B, also factory reset your phone.
// you find the boot.img in the zip-file you flash
I would recommend to:
- choose a ROM (Viper?), transfer it to your sd-card
- get into bootloader, flash boot.img which comes in the zip-file
- from bootloader select recovery to boot (best use TWRP)
- go to wipe, choose to wipe system, androidsecure, dalvik- and cache and do a factory reset
- select install in recovery, install new ROM
I am pretty sure, everything will work after this
andryyyy said:
When you flashed it, did you flash the boot.img before, too? Do this!
And, also important: After each change of ROM, always also wipe "System" in Recovery! Maybe some ROMs don't do so automatically. And if you change from ROM A to ROM B, also factory reset your phone.
// you find the boot.img in the zip-file you flash
I would recommend to:
- choose a ROM (Viper?), transfer it to your sd-card
- get into bootloader, flash boot.img which comes in the zip-file
- from bootloader select recovery to boot (best use TWRP)
- go to wipe, choose to wipe system, androidsecure, dalvik- and cache and do a factory reset
- select install in recovery, install new ROM
I am pretty sure, everything will work after this
Click to expand...
Click to collapse
Yes, I flashed the boot.img before then flashed the ROM from recovery.
I just did a factory reset, did not specifically do the system wipe.
Let me try wiping the system and then flash the ROM. I'll get to you after trying.
akhrot91 said:
Yes, I flashed the boot.img before then flashed the ROM from recovery.
I just did a factory reset, did not specifically do the system wipe.
Let me try wiping the system and then flash the ROM. I'll get to you after trying.
Click to expand...
Click to collapse
Okay
you could flash the official RUU ，the problem will be solved…remember.，when you flash a ROM using recovery，you'd better format SYSTEM，that's important…
Sent from my HTC One S using xda app-developers app
andryyyy said:
Okay
Click to expand...
Click to collapse
I did exactly as you said but wifi doesn't connect. When I enter my wifi password it goes to connecting and quits stating the network out of range even when I'm standing besides the router and then it hangs and reboots.
All other things work fine, i.e bluetooth, mobile network etc.
I flashed the boot.img prior to flashing the ROM in TWRP. Wiped system, android.secure, cache and wiped data/factory reset. No luck.
I've no idea why is this happening. :S
harveychina said:
you could flash the official RUU ，the problem will be solved…remember.，when you flash a ROM using recovery，you'd better format SYSTEM，that's important…
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
The RUU is a .exe file and I'm on Ubuntu 12.10. I can't run RUU.
I borrowed a friend's laptop which was running on windows 7 but could'nt get the sync manager to sync my phone.
I'm stuck!!!
Strange .. you have neighbours you can ask to connect to their wifi for test?
Is your wifi "b/g" or "n" only?
Will write when I got another idea .. sorry.
andryyyy said:
Strange .. you have neighbours you can ask to connect to their wifi for test?
Is your wifi "b/g" or "n" only?
Will write when I got another idea .. sorry.
Click to expand...
Click to collapse
Yes, They can let me do that. I'll try that too.
Its b/g/n.
Its so frustrating, can't connect to wifi.
It's a T-Mobile phone with Hboot 1.14.0004 maybe this can help you think of something.
Thanks for your help.
akhrot91 said:
Yes, They can let me do that. I'll try that too.
Its b/g/n.
Its so frustrating, can't connect to wifi.
It's a T-Mobile phone with Hboot 1.14.0004 maybe this can help you think of something.
Thanks for your help.
Click to expand...
Click to collapse
Hey,
searched the Viper thread:
"Hello,
Did you do the 2.35 OTA from T-Mobile? If so then you can't get Wi-Fi working on any other rom then Trickdroid 7.0.0 or Stock 2.35. It all has to do with the way Wi-Fi is handled in 2.35 and hboot 1.14 not letting you downgrade those partitions.
You Could always SuperCID your phone and in stall the 2.31 RUU then install Viper. That has the same hboot so you shouldn't have any problems. I haven't tried this because I dont need to. Hope that helps.
Rsotbiemrptson"
To be sure, best wipe everything as before, then flash trickdroid 7.0.0
//edit: just editing CID is not enough, I guess .. I would modify mmcblk0p23 to 1.00.000.0 (see thread "downgrade/unbrick"), too. If that does not work, downgrade hboot, works fine. I think you are good with linux.
andryyyy said:
Hey,
searched the Viper thread:
"Hello,
Did you do the 2.35 OTA from T-Mobile? If so then you can't get Wi-Fi working on any other rom then Trickdroid 7.0.0 or Stock 2.35. It all has to do with the way Wi-Fi is handled in 2.35 and hboot 1.14 not letting you downgrade those partitions.
You Could always SuperCID your phone and in stall the 2.31 RUU then install Viper. That has the same hboot so you shouldn't have any problems. I haven't tried this because I dont need to. Hope that helps.
Rsotbiemrptson"
Click to expand...
Click to collapse
hi. I don't know this because I just got the phone from my cousin last night and he has no idea too. Where could check this if the OTA is done or not?
Okaaay. I tried Trickdroid v8.1.0 and it didn't work. I'm downloadiing the v7.0.0 right now to test it.
He must have dont the 2.30 OTA that's why wifi is not working on any other ROM.
Can you tell me a way other than virtual machine for me to apply the 2.31 RUU on Ubuntu/linux?
Shrink your ext3/4 partition using gparted and install win7
Virtualising and using "pass-through" will not work anyway. The phone switches its mode too often, you would need to "pass-through" it again and again.
You best use a laptop of a friend .. :/
But yes, try 7.0.0
So it worked?
andryyyy said:
Shrink your ext3/4 partition using gparted and install win7
Virtualising and using "pass-through" will not work anyway. The phone switches its mode too often, you would need to "pass-through" it again and again.
You best use a laptop of a friend .. :/
But yes, try 7.0.0
Click to expand...
Click to collapse
IT WORKED!! :laugh:
Thank you SO much andryyyy. I would've died without wifi on my phone.
Thanks again. :laugh::good:
Hi,
Try the following link
http://forum.xda-developers.com/showthread.php?t=2151142
I use Viper 2.1 and hboot 1.14.004. But, remember to use stock kernel when you flash your Viper rom.
Thank you
Related
Hello,
I found on the XDA site, a patch to solve the problem of wireless reception, but I do not know if I can use it on my HTC Desire S, S-off with the official rom 1.36.415.6 Arabic, then I use this patch, is there a tutorial to install it? thank you
from gtg465x the link: http://forum.xda-developers.com/showthread.php?t=1051674
HTC DESIRE S
S-OFF
ROOTED
OFFICIAL ROM 1.36.415.6 ARABIC
It's written there: Flash through Clockwork Recovery
It will work with EXT4Recovery too.
Download ROM Manager from Market and install it. Then from menu go to boot to recovery. Phone will reboot and will enter in to the recovery menu. From there choose install zip file from sd card - that post http://forum.xda-developers.com/showthread.php?t=1051674 (you must put it before that on the root of your sd card) Choose install yes and voila.
teddy_irish said:
It's written there: Flash through Clockwork Recovery
It will work with EXT4Recovery too.
Download ROM Manager from Market and install it. Then from menu go to boot to recovery. Phone will reboot and will enter in to the recovery menu. From there choose install zip file from sd card - that post http://forum.xda-developers.com/showthread.php?t=1051674 (you must put it before that on the root of your sd card) Choose install yes and voila.
Click to expand...
Click to collapse
Think you very, teddy irish, I juste install it, but lost my wifi signal now lol,
Hi,
Finally I reinstall my Rom, everything it's ok
If you read the thread it says only use this on custom deodexed roms since you are using a stock Rom which you have rooted it will not work however if you want to use this fix i suggest you download the Arabic pre rooted Rom from the pre rooted Rom thread then you can apply the patch as the Rom is deodexed
http://forum.xda-developers.com/showthread.php?t=1183684
I hope this helps
Sent from my HTC Desire S using XDA App
Hi all!
I'm having some problems with Wifi on my DS.
I have installed a wifi fix zip which I shouldn't have (unfortunately I didn't read the whole post...) Here's the post: http://forum.xda-developers.com/showthread.php?t=1051674
After installing I have stucked at the HTC logo, after a few retries and backups it has succesfully booted. But now I couldn't see my wifi at home but it still works at other places (like at work). I tried to add the home network manually by typing the SSID and password but nothing...
Any suggestions? Can i uninstall the zip or overwrite it somehow? As it works at other places I think it has just screwed up some settings.
Thank you in advance...
(BTW I have Reaper v3.0)
Have you tried simply rebooting into recovery, flashing your original ROM zip file, wiping cache and dalvik cache
If you're unlocked via htcdev you may need to seriously flash kernel via fastboot
Swyped from my DesireS
ben_pyett said:
Have you tried simply rebooting into recovery, flashing your original ROM zip file, wiping cache and dalvik cache
If you're unlocked via htcdev you may need to seriously flash kernel via fastboot
Swyped from my DesireS
Click to expand...
Click to collapse
I'm have already reflashed the ROM but haven't wiped cache and dalvik.
Should I wipe before/after or both?
I'm making a nandroid now and give it a try.
I didn't know how was it unlocked cuz i bought it second-hand and it was already rooted.
Flash then wipe cache and dalvik
what does you boot loader screen say? Are you s-off? Or unlocked?
Swyped from my DesireS
Doesn't seem to work, any other ideas?
I don't know much about kernels...
***LOCKED***
SAGA PVT SHIP S-OFF RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
I don't really understand much from it...
Kokufuu said:
Doesn't seem to work, any other ideas?
I don't know much about kernels...
***LOCKED***
SAGA PVT SHIP S-OFF RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
I don't really understand much from it...
Click to expand...
Click to collapse
This looks like you have a phone S-OFFed with XTC clip, which means you can flash what ever you want... In that case I would do a nandroid backup and try to flash the latest RUU just to see if the problem with WIFI dissapears.
Sent from my HTC Desire S using xda premium
How can it be that wifi is working at some places and can't see it at other places?
Is there any config file which I can check with rootexplorer?
If there is I could copy it here, maybbe it would help...
---------- Post added at 10:11 AM ---------- Previous post was at 09:56 AM ----------
dmatik said:
This looks like you have a phone S-OFFed with XTC clip, which means you can flash what ever you want... In that case I would do a nandroid backup and try to flash the latest RUU just to see if the problem with WIFI dissapears.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Nandroid has been made last night.
Where can I find the latest RUU? If I flash it would I lose root access? Sorry if its a noob Q but I have only flashed custom ROMs till now.
My biggest problem is that I do not really understand "what is the problem"...
How come that it can see open networks and I can use WiFi properly at work but at home it doesn't see network and can't even add it manually with SSID.
What did that fix.zip actually did?
Kokufuu said:
How can it be that wifi is working at some places and can't see it at other places?
How come that it can see open networks and I can use WiFi properly at work but at home it doesn't see network and can't even add it manually with SSID.
What did that fix.zip actually did?
Click to expand...
Click to collapse
could you previously connect at work? are you sure that they're not hiding the SID (ie not broadcasting?)
ben_pyett said:
could you previously connect at work? are you sure that they're not hiding the SID (ie not broadcasting?)
Click to expand...
Click to collapse
Here's a short brief what happened:
- used WiFi properly everywhere
- automatically found network (both at work and home, open and secured)
- typed in password and used it day by day
- installed wrong wifi fix.zip, freezed at HTC logo at boot, somehow managed to make it work after a few tries of wipes and backups
- at home it could not see the network (out of range)
- deleted it from known networks, tried to find it again, couldn't, tried to add manually, couldn't
- next day at work the network at there worked properly henceforward (didn't touched anything)
PROBLEM SOLVED!
Don't really know what was the problem...
After reflashing and rebooting a few times and reseting the router at home, it's working somehow...
Thanks for everyone who tried to help!
Glad its sorted!
sounds like it may have been a bleeding router issue!
keeping the phone horizontally with two hands you can easily experience the antenna issue.
anyone found a *hardware* fix? opening the phone, isolating something that is in touch with the metal chassis?
thank you
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Checked MD5?
torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.
Of course you need to use fastboot!!
Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.
herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?
you didn't mention wiping System as part of the full wipe--needs done
Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.
To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.
What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".
Its not bricked.If u can enter recovery
Sent from my HTC sensation
Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse
DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309
impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.
You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4
Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")
My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date
I have downloaded CleanRom 5.1 from a long time ago, now the link is not up for that rom. The size is 598 mb.I have flashed this rom before but now I can't get it to flash. In recovery I have wiped, dalvic,cache, system, and factory. After I choose what to flash from Aroma it goes to flash a couple of seconds then goes to the other screen to finalize, but when going to reboot, I get "no OS , do you really want to reboot".
S-OFF
unlocked
on 2.20
Tried this with HBOOT 1.09 and now on HBOOT 1.14, I would redownload but the link is gone now , and I can't figure out how to get it to flash, luckily I do have a back up that works
Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2
jerrycoffman45 said:
Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3
Sorry maybe someone else will know what to do I am out of ideas
Sent from my HTC One X using Tapatalk 2
leesumm said:
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3
Click to expand...
Click to collapse
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.
exad said:
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.
Click to expand...
Click to collapse
NO. I don't have the md5 for that rom. I downloaded it some time ago and sitting idle in the folder on the PC. I was messing around in places that I shouldn't have been and somehow things got deleted. My backup of that rom I had flashed works fine. Its when I go to flash the rom from zip that I have a problem.
I am really scratching my head now!!!
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...
leesumm said:
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...
Click to expand...
Click to collapse
Makes sense to me, sounds like you didn't do fastboot erase cache after switching recoveries. When you flash a new recovery you need to do fastboot erase cache.