Hey all,
Running CM 10.1 Wild For The Night and I noticed my WiFi had disconnected. When I went to the WiFi settings, the toggle was greyed out and the screen was stuck on 'turning Wifi on'. I rebooted and the screen was still stuck. I wiped Dalvik and cache, and when I rebooted, WiFi was off. I tried turning it back on and the same situation happened. Completely wiped and reflashed, same problem. Today I flashed a new ROM (MiUi 3.2.8), same problems persist. Im on HBOOT 1.5 S-ON (I know, I know). WiFi did work before with the ROM for at least a week. Is it possible the WiFi chip is borked?
a7nachmb said:
Hey all,
Running CM 10.1 Wild For The Night and I noticed my WiFi had disconnected. When I went to the WiFi settings, the toggle was greyed out and the screen was stuck on 'turning Wifi on'. I rebooted and the screen was still stuck. I wiped Dalvik and cache, and when I rebooted, WiFi was off. I tried turning it back on and the same situation happened. Completely wiped and reflashed, same problem. Today I flashed a new ROM (MiUi 3.2.8), same problems persist. Im on HBOOT 1.5 S-ON (I know, I know). WiFi did work before with the ROM for at least a week. Is it possible the WiFi chip is borked?
Click to expand...
Click to collapse
Your kernel isn't flashing properly so the WiFi driver doesn't match.
To get things back in sync start your recovery with the following fastboot command:
fastboot boot recovery.img
Click to expand...
Click to collapse
Once booted into recovery wipe all partitions except SD card and make sure SmartFlash (S-ON) is disabled in the tools menu if using 4EXT. Then flash the entire ROM as you normally would, except this time the boot partition (kernel) will be flashed from recovery because of the way it was started.
ramjet73
ramjet73 said:
Your kernel isn't flashing properly so the WiFi driver doesn't match.
To get things back in sync start your recovery with the following fastboot command:
Once booted into recovery wipe all partitions except SD card and make sure SmartFlash (S-ON) is disabled in the tools menu if using 4EXT. Then flash the entire ROM as you normally would, except this time the boot partition (kernel) will be flashed from recovery because of the way it was started.
ramjet73
Click to expand...
Click to collapse
Thanks for the reply! Just tried it. It's been a long time since I've messed with ADB and fastboot. I booted the device into whatever the white screen thing that isn't recovery is called (ha ha), performed the fastboot command from the folder I saved it in on my computer, ran the command, and it booted into the 4ext. I disabled Smartflash, wiped everything, and flashed, and now its hanging on the boot screen.
a7nachmb said:
Thanks for the reply! Just tried it. It's been a long time since I've messed with ADB and fastboot. I booted the device into whatever the white screen thing that isn't recovery is called (ha ha), performed the fastboot command from the folder I saved it in on my computer, ran the command, and it booted into the 4ext. I disabled Smartflash, wiped everything, and flashed, and now its hanging on the boot screen.
Click to expand...
Click to collapse
What ROM are you flashing? Some people had problems booting ICS Sense ROM's with hboot 1.5 and S-ON. I never had that problem myself, but if you want to stay on hboot 1.5 and not go for S-OFF it might be worth it to relock your bootloader and flash the 2.17.651.5 RUU to make sure everything is in sync. Flashing the stock ROM will also let you confirm whether your Wi-Fi is working or not.
You'd really be better off going for S-OFF and I have a guide that can help here.
ramjet73
Ah, okay I got MIUI 3.2.8 to bot using the fastboot recovery method. Still having the WiFi issue. I've never messed with logcats before, how would I go about posting the relevant bit of text from this enormous jumble that happened when I ran adb logcat?
a7nachmb said:
Ah, okay I got MIUI 3.2.8 to bot using the fastboot recovery method. Still having the WiFi issue. I've never messed with logcats before, how would I go about posting the relevant bit of text from this enormous jumble that happened when I ran adb logcat?
Click to expand...
Click to collapse
I think that ROM might be having WiFi issues per this post by DH.
You could try flashing the Sense version of the Mac kernel after the ROM is flashed and that might fix it.
ramjet73
ramjet73 said:
I think that ROM might be having WiFi issues per this post by DH.
You could try flashing the Sense version of the Mac kernel after the ROM is flashed and that might fix it.
ramjet73
Click to expand...
Click to collapse
Hm. I had terrible data connectivity on MIUI so I'm back on CM10.1. The things that lead me to believe the problems are deeper than kernel/ROM are
1. The issue happened abruptly. After using CM10.1 for a week or so with no wifi issues, suddenly this happened. Not even after a reboot, it just happened.
2. Its happening on multiple ROMs with full wipes and stuff in between.
Would a logcat not be helpful in diagnosing the issue? I just don't know much about them. Do I need to connect my phone via USB and then attempt to recreate the problem in order for the correct info to be in the log? As I said before, I can't get my wifi to turn off without wiping cache and dalvik, even after a reboot its still giving me the 'turning wifi on' message.
a7nachmb said:
Hm. I had terrible data connectivity on MIUI so I'm back on CM10.1. The things that lead me to believe the problems are deeper than kernel/ROM are
1. The issue happened abruptly. After using CM10.1 for a week or so with no wifi issues, suddenly this happened. Not even after a reboot, it just happened.
2. Its happening on multiple ROMs with full wipes and stuff in between.
Would a logcat not be helpful in diagnosing the issue? I just don't know much about them. Do I need to connect my phone via USB and then attempt to recreate the problem in order for the correct info to be in the log? As I said before, I can't get my wifi to turn off without wiping cache and dalvik, even after a reboot its still giving me the 'turning wifi on' message.
Click to expand...
Click to collapse
You're best bet is probably to flash the 2.17.651.5 GB RUU at this point and check your WiFi in a stock configuration since not everyone is having these problems. You will need to relock your bootloader before flashing the RUU, then unlock and re-flash your recovery afterwards, but you can use the unlock .bin file you have already.
ramjet73
ramjet73 said:
You're best bet is probably to flash the 2.17.651.5 GB RUU at this point and check your WiFi in a stock configuration since not everyone is having these problems. You will need to relock your bootloader before flashing the RUU, then unlock and re-flash your recovery afterwards, but you can use the unlock .bin file you have already.
ramjet73
Click to expand...
Click to collapse
Willing to give this a go. Is there info on how to relock and unlock with the unlock .bin? Thanks again for the quick replies
a7nachmb said:
Willing to give this a go. Is there info on how to relock and unlock with the unlock .bin? Thanks again for the quick replies
Click to expand...
Click to collapse
Everything you need should be in mpgrimm2's guide.
Once you relock and flash the RUU you can boot into the stock ROM and test WiFi. If everything checks out you can root your phone the way you did the first time, or take it to Sprint for a replacement if it doesn't work.
ramjet73
ramjet73 said:
Everything you need should be in mpgrimm2's guide.
Once you relock and flash the RUU you can boot into the stock ROM and test WiFi. If everything checks out you can root your phone the way you did the first time, or take it to Sprint for a replacement if it doesn't work.
ramjet73
Click to expand...
Click to collapse
Awesome, thanks!
dude, just make it easy on you ...
flash any ics sense 3.6 rom from fastboot and it is going to get your wifi going.
you'd be stuck here until you are s-off ... so no fancy roms for you, sorry~
I can confirm
I'm using the same rom, miui walking dead ICS... Tried to flash it a couple of times.
Seems when turning the wifi toggle off, the whole networking in android locks up. It'll do this on it's own if you have wifi set to disable on sleep. I am running S-OFF Hboot 1.58, and what's really interesting is dropping to terminal and running, netcfg, you get nothing. It locks up as well, and trying to run ifconfig wlan0 down/up gives you nothing. Ctrl-C to cancel doesn't respond either. I don't see anything in logcat, so I think it's a kernel issue.
Normally, you can drop to terminal and su, then 'shutdown -h now' and have the phone shut off within a second or two, but once the wifi locks, it won't shut down, restart, anything. You have to pull the battery. Once the battery is pulled, and you boot back up, wifi will be toggled off, and you can toggle it back on fine, at least in my experience so far.
I'd really be interested in what digitalhigh says, but I can't post on the developer forum yet. :|
Related
Ok, this is my first post so be gentle. I tried to root my sons phone and now it's useless. I went thru HTC's website to unlock bootloader due to having HBOOT 1.5. I'm unlocked and thinking life is good but, I loaded several different ROM's and get the same result. It starts to load the ROM and reboots, sometimes it goes into a safemode with the Viper Rom. I've been jacking with this for 2 days and need some help. I can't find a good link for the RUU or PG86...bla bla bla, I would take it back to stock and surrender but, can't even do that. I've installed TWRP and CWM, just to try different stuff, but get all the same reults.
I think you need to flash the boot.img separately. I'm not sure though. There's a thread for flashing with 1.50 somewhere in the development section
We're comin from a pure power source.
I am having the same issue here, I installed several ROMS, it works for a day, but then the reboot attack starts. Constant lockups and random restarts, sometimes 3 reboots in a row.
ROMs I tried to flash:
1. Xperia XE
2. Titan Trinity 3 HD
3. Nocturnal Adrenaline 1.0.2
Maybe it's the kernel, is there a list of kernels that I can flash?
This worked for me
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
armydude13090 said:
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
Click to expand...
Click to collapse
Unroot my phone?
Is it possible to re-root it?
Thanks all for the posts. I will give some of this a shot and see what happens. I can get to fastboot, and have loaded a couple of things thru the cmd prompt to try and help, but nothing so far. I'm not really sure if the kernel thing is what's stopping the roms for loading. I can't get the S-OFF, I'm unlocked. I can send anything I want thru the cmd prompt, and also flash zips thru twrp or cwm. Would like to start over but ca't even find a way to do that. Thanks again for the posts.
Cardmastr, we're on the same boat, pg86 takes forever to download, so as I'm waiting patiently, keep me in on the loop with what you're doing.
RUU didn't cut it, kept failing. have not found an image file to flash thru the cmd prompt. Still no luck. What can I throw into fast boot that might help me?????!!!!!!
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Which recovery did you install? Twrp 1.1.1 is your best bet.
The 2.x version twrp or cwm do not okay nice with some phones.
S3nt from my 3D wond3rland
I used the TWRP 1.1.1. Might of messed up with some of the cmd prompt stuff I'm going back thru.
thefsfempire said:
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Click to expand...
Click to collapse
Everyday is Halloween for u dude!! UR a Monster! This little tidbit hooked me up. Thanks to you we are back in game.
When installing a ROM, doesn't it wipe /data, /system, etc for us?
OK, so I got a little "cocky" and flashed to another ROM. Apparently it wasn't capability with Rezound as it didn't boot. When I tried to boot into recovery, only could select Hboot. That lead to a loop. Took out the memory card, the SIM chip, battery, cover all to no avail. I finally got Scott's rom that was working back on the phone. But still having issues, the phone constantly reboots. I get to the home screen and/or lock screen it works but then freezes and resets. I no longer have the ability to boot into recovery. When I connect to the MAC (or PC) it says charging only.
When able tried a factory reset but that didn't do anything, I can no longer get to that screen. Did a nandroid backup before playing around with the new ROM but can't figure out how to get to it.
HELP... need your help pretty please
Did you just do a factory reset before you flashed Scott's rom or did you wipe /system as well? Also make sure debugging is enabled as well. Have you tried to boot to recovery with adb?
Sent from my ADR6425LVW using Tapatalk 2
DOOD YOUR PHONE IS TOTALLY BORKED. PANIC!
Kidding
in all seriousness. What firmware are you on. ICS or GB firmware?
I.E. have you run an RUU, are you s-off or s-on
if you are unsure, just type out like the first 5 lines in HBOOT.
Did you just do a factory reset before you flashed Scott's rom or did you wipe /system as well? Also make sure debugging is enabled as well. Have you tried to boot to recovery with adb?
Click to expand...
Click to collapse
When I was able to select something other than HBOOT I did a factory restore but didn't notice anything different. Also manually deleted. However now when I try to go into recovery mode, only HBOOT is selected and the up/down button doesn't work.
Not sure how to boot to recovery with adp.
Appreciate your wisdom
What firmware are you on. ICS or GB firmware?
I.E. have you run an RUU, are you s-off or s-on
if you are unsure, just type out like the first 5 lines in HBOOT.
Click to expand...
Click to collapse
The last time the phone worked, was running Scott's Clean Rom 4.5, Android 4.0.3
Kernel ver: 3.0.16-g8fa42b5
I believe it's s-off but it's fighting me to get back to the recovery screen
Sadly I'm not sure about RUU
What ROM was it if you don't mind me asking? I mean was it at least for the Rezound if so then it shouldn't be that bad..
I didn't do anything different this morning than last nite, but the phone came back to life. I restored the nadroid backup and it appears to be working. Though getting an error about the SIM card after a reboot.
Don't know what I did wrong when trying to flash or if the ROM just wasn't compatible.
Last night with the assistance of a friend I was able to load Newt's ROM onto my phone 'successfully,' at least, that's what we thought. Initially it wouldn't allow the use of Wifi and we were able to discern that was because we flashed the wrong link for the patch, so it was an older boot.img. After we corrected that mistake, I was able to leave the MikMik bootup screen and the WiFi was working perfectly. After waking up from that, I restarted the phone twice throughout the day with no problem, it booted up fine, as if the phone wasn't rooted at all. Since it was working 'properly' I made a nandroid of the file, and that's when it all went downhill. After making the nandorid (I only used the default four boxes), the phone wouldn't reboot; it stayed stagnant on the Mik-Mik boot-up screen. We tried clearing the cache and Dal-vik Cache; re-flashing his ROM completely (flashed it twice to make sure the WiFi would stick) with the 3.2.1 patch and then rebooting the phone. It still won't leave the Mik-Mik boot-up screen. It puzzles me because it was working fine until I made the nandroid. :l Recap: Tried clearing Cache and Dal-Vik Cache, resetting permissions to ensure it wasn't trying to pull ID from stock, re-flashed ROM with 3.2.1 patch. Any ideas? Much appreciated.
Edit: Forgot to mention I'm S-On
Edit two: Just cleared off the SD card and started fresh with no luck. I flashed the ROM twice, then the 3.2.1.v2 patch, and then did "fastboot boot boot.img" in my commands prompt to start the phone, but it still gets stuck on the Mik-Mik loading screen (Before flashing the ROM I cleared the cache and Dilvik Cache). :l
Kelton Rivas said:
Last night with the assistance of a friend I was able to load Newt's ROM onto my phone 'successfully,' at least, that's what we thought. Initially it wouldn't allow the use of Wifi and we were able to discern that was because we flashed the wrong link for the patch, so it was an older boot.img. After we corrected that mistake, I was able to leave the MikMik bootup screen and the WiFi was working perfectly. After waking up from that, I restarted the phone twice throughout the day with no problem, it booted up fine, as if the phone wasn't rooted at all. Since it was working 'properly' I made a nandroid of the file, and that's when it all went downhill. After making the nandorid (I only used the default four boxes), the phone wouldn't reboot; it stayed stagnant on the Mik-Mik boot-up screen. We tried clearing the cache and Dal-vik Cache; re-flashing his ROM completely (flashed it twice to make sure the WiFi would stick) with the 3.2.1 patch and then rebooting the phone. It still won't leave the Mik-Mik boot-up screen. It puzzles me because it was working fine until I made the nandroid. :l Recap: Tried clearing Cache and Dal-Vik Cache, resetting permissions to ensure it wasn't trying to pull ID from stock, re-flashed ROM with 3.2.1 patch. Any ideas? Much appreciated.
Edit: Forgot to mention I'm S-On
Edit two: Just cleared off the SD card and started fresh with no luck. I flashed the ROM twice, then the 3.2.1.v2 patch, and then did "fastboot boot boot.img" in my commands prompt to start the phone, but it still gets stuck on the Mik-Mik loading screen (Before flashing the ROM I cleared the cache and Dilvik Cache). :l
Click to expand...
Click to collapse
First...are you on GB Firmware or ICS firmware???
Look at the hboot screen and tell me what you have for hboot and radios, please.
topgun1953 said:
First...are you on GB Firmware or ICS firmware???
Look at the hboot screen and tell me what you have for hboot and radios, please.
Click to expand...
Click to collapse
Hboot: 2.21.0000
Radio: 1.22.10.0310r/1.22.10.0308r
Kelton Rivas said:
Edit two: Just cleared off the SD card and started fresh with no luck. I flashed the ROM twice, then the 3.2.1.v2 patch, and then did "fastboot boot boot.img" in my commands prompt to start the phone, but it still gets stuck on the Mik-Mik loading screen (Before flashing the ROM I cleared the cache and Dilvik Cache). :l
Click to expand...
Click to collapse
its supposed to be
Code:
fastboot [I][B]flash[/B][/I] boot boot.img
AshtonTS said:
its supposed to be
Code:
fastboot [I][B]flash[/B][/I] boot boot.img
Click to expand...
Click to collapse
I've tried doing "fastboot flash boot boot.img," but it still perpetuates on the mik-mik screen.
Kelton Rivas said:
Hboot: 2.21.0000
Radio: 1.22.10.0310r/1.22.10.0308r
Click to expand...
Click to collapse
All right...that is ICS firmware. Not the 'latest', but still ICS firmware. That may be the source of the problem as I believe the flashable boot.img is based on later firmware.
JUst to make sure..you flashed the 3.2.1 Rom, THEN the RLS 2+ boot.img, and then finally the 3.2.1 patch ? The order might make a difference.
If this is what you've done, then I'd recommend flashing the latest leaked RUU so you'd have the latest firmware and then it should work. If you do that, be sure to do a FACTORY RESET in hboot immediately after running the RUU. Failure to do so, might result in data probs.:crying:
topgun1953 said:
All right...that is ICS firmware. Not the 'latest', but still ICS firmware. That may be the source of the problem as I believe the flashable boot.img is based on later firmware.
JUst to make sure..you flashed the 3.2.1 Rom, THEN the RLS 2+ boot.img, and then finally the 3.2.1 patch ? The order might make a difference.
If this is what you've done, then I'd recommend flashing the latest leaked RUU so you'd have the latest firmware and then it should work. If you do that, be sure to do a FACTORY RESET in hboot immediately after running the RUU. Failure to do so, might result in data probs.:crying:
Click to expand...
Click to collapse
I didn't realize I was on expired firmware, can you send me the instructions and link(s) for flashing it? I'm still somewhat new to this flashing business, I only started last night. Uhm, no, for order I went: Newt's ROM(x2), 3.2.1.v2 patch, then RLS2+ Boot.img. I have to do the boot.img last because I'm forced to shut down the phone and then go to that setting where "fastboot USB" is in red.
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
ronin_rone said:
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot.img?
gleggie said:
Have you tried fastboot flashing the boot.img?
Click to expand...
Click to collapse
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
ronin_rone said:
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
Click to expand...
Click to collapse
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
dragonstalker said:
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
Click to expand...
Click to collapse
I kinda understand what you are saying, but the other problem I have is.... When running adb my phone is not listed in the adb devices, although it is listed in the usb devices. Not sure what to do about that.
Are you in charge only mode on the phone?
Is usb debugging enabled?
USB debugging was selected prior to this incident and it was on charge only as well. It was not connected as a usb drive. I cannot get into the settings of the phone to find out what it is now or if its changed.
I would suggest going S-Off, it will make flashing a whole lot easier. As for getting back to a usable state, you should be able to flash a PH98IMG in bootloader. If anything, flash an RUU and go from there.
Correction2:
Flashed back to stom rom, and will install root again today, this was really frustrating. I guess it just isn't going to happen.
Correction, after many tries, it did react to the button combo. I formatted everything from CWM and reflashed the first rom. Now there's only a wifi problem. It simply does NOT turn on wifi, ever. From the notification bar it turns off right away, from the settings-wifi screen it turns on and keeps saying turning on wifi.
What now? Since this rom now works, I don't really want to go to another rom to fix wifi.
Also we just noticed the sim is not detected! It doesn't ask for pincode, can't call or anything.
I have a GSM One X+ and I wanted to flash a new rom.
What I did was unlock the bootloader via HTC dev, flashed CWM, flashed the SU zip, and it booted into the stock rom fine. However, wifi stopped working.
To fix the wifi problem, I first tried this rom:
http://forum.xda-developers.com/showthread.php?t=2044584
That booted, but still wifi problem.
Then flashed this:
http://forum.xda-developers.com/showthread.php?t=2068901
From CWM, I could not find the way to go to bootloader (to flash boot.img) so I used voldown+lock to restart and go into bootloader to flash the boot.img
That didn't work, got a error every single time (cannot load boot.img unknown error)
I'm 100% sure I did it the correct way, however at that point I could not enable USB debugging yet because android hasn't started in the new rom at that point.
So I went to bootloader and tried flashing the boot.img many times, but it just kept giving errors. The rom wouldn't boot either.
Then I tried re-flashing the first rom, because that booted at first.
That first rom is now stock at the bootscreen, and it doesn't do anything, it doesn't react to voldown+lock either.
What to do now? Can't pull battery and button combos don't work either.
When you are in bootloader, can you write what is written right under *** UNLOCKED *** ?
Lucky Thirteen said:
When you are in bootloader, can you write what is written right under *** UNLOCKED *** ?
Click to expand...
Click to collapse
It is a phone of a friend, he was here 4 hours while I tried everything.I rooted at least 5 phones and installed roms on them so I expected it to work. However there were so many problems we gave up.
We reinstalled the stock rom, and re-rooted.
First rom didn't have any wifi,
Second rom didn't boot because I couldn't flash the boot.img even manually.
At random times, the phone didn't react to ANY input, not even hard restart.
So we gave up. He is now back to stock+root. Might try again some time, when there are better stable roms with included boot.img files.
Delano.888 said:
Might try again some time, when there are better stable roms with included boot.img files.
Click to expand...
Click to collapse
There is plenty of stable ROMs available. Probably you didn't pick the right phone version. Can you confirm how the phone is identified by EVITARE_UL or ENRC2B?
Lucky Thirteen said:
There is plenty of stable ROMs available. Probably you didn't pick the right phone version. Can you confirm how the phone is identified by EVITARE_UL or ENRC2B?
Click to expand...
Click to collapse
Actually I cannot, the friend & phone is not here anymore. Thus this thread is now pointless, sorry.