Related
There is a guide on how to flash a new radio on the One S, but its outdated and obsolete.
While we still dont have S-OFF yet, there is a trick that lets you flash radio images.
Requirements.
The latest TWRP recovery image. Available here.
Grab the latest US or EU radio here and copy it to your SD Card. (adb push filename.zip /sdcard/radio.zip) Click the changelog-button to see which radio's are US and EU.
Lets get flashing
Reboot your device into the bootloader.
Code:
adb reboot bootloader
Use fastboot to boot up into recovery.
Code:
fastboot boot openrecovery-twrp-2.3.1.0-ville.img
You will boot directly into recovery from the recovery image, and no restrictions apply. Now simply flash the radio.zip file that you pushed over earlier, and you're all set!
Enjoy!
Credits to xkonni for the tip!
Is it really bad if I flash a EU radio on my TMOBUS device? I have done so 24hrs ago and notice very fast speeds and good signal strength. I don't get why there is a difference.
Closed Source Project said:
Is it really bad if I flash a EU radio on my TMOBUS device? I have done so 24hrs ago and notice very fast speeds and good signal strength. I don't get why there is a difference.
Click to expand...
Click to collapse
i would like to know the answer to this also
No it works great on my tmobile one s no problems here
sent from a guy living in a van down by the river
Untouchab1e said:
There is a guide on how to flash a new radio on the One S, but its outdated and obsolete.
While we still dont have S-OFF yet, there is a trick that lets you flash radio images.
Requirements.
The latest clockwork recovery image. Available here. Make sure you get the latest version for the Ville. (released on or after 29-apr-2012).
Grab the latest US or EU radio here and copy it to your SD Card. (adb push filename.zip /sdcard/radio.zip) Click the changelog-button to see which radio's are US and EU.
Lets get flashing
Reboot your device into the bootloader.
Code:
adb reboot bootloader
Use fastboot to boot up into recovery.
Code:
fastboot boot recovery-clockwork-5.5.0.4-ville.img
You will boot directly into recovery from the recovery image, and no restrictions apply. Now simply flash the radio.zip file that you pushed over earlier, and you're all set!
Enjoy!
Credits to xkonni for the tip!
Click to expand...
Click to collapse
got the same result by just rebooting into bootloader, then choosing fastboot>recovery.....then chose radio.zip i placed on "sdcard"...never having to plug phone into PC
On leedroid without the radio it gets about 12mb but with this radio i get 10mb, when i load the same site, this radio loads about 2seconds faster..tmobUS thanx btw
I too just flashed the .zip from Clockwork Recovery from my T-Mobile US phone for the EU radio. Working just fine.
I'm getting an error when I enter stock recovery that it can't find /sdcard cause the file doesn't exist... a little help please
ralph96gt said:
I'm getting an error when I enter stock recovery that it can't find /sdcard cause the file doesn't exist... a little help please
Click to expand...
Click to collapse
Had the exact same problem as you.
I just flashed the recovery with CWM recovery image. The one in this topic didn't work for me cause it wouldn't mount the /sdcard either. I used a different version.
Then I just installed the radio.zip from this topic.
So if I have the last CWM, just I have to put the zip to the SD, and flash it from recovery?
Edit: The radio I have now is the 0.15.31501S.19_2_10.13.31501S.06L
cualla84 said:
So if I have the last CWM, just I have to put the zip to the SD, and flash it from recovery?
Edit: The radio I have now is the 0.15.31501S.19_2_10.13.31501S.06L
Click to expand...
Click to collapse
From what Ive been told, and what I did, was to boot directly into the latest recovery image. Meaning, you dont flash the recovery image first, you simply fastboot boot into it, then you flash the radio.zip from there.
Again, make sure you pick the newest version of the recovery image.
Untouchab1e said:
From what Ive been told, and what I did, was to boot directly into the latest recovery image. Meaning, you dont flash the recovery image first, you simply fastboot boot into it, then you flash the radio.zip from there.
Again, make sure you pick the newest version of the recovery image.
Click to expand...
Click to collapse
Thank you! I have the CWM 5.8.3.1. I have to wipe before flashing?
cualla84 said:
Thank you! I have the CWM 5.8.3.1. I have to wipe before flashing?
Click to expand...
Click to collapse
No, you dont have to wipe data before flashing a new radio.
Untouchab1e said:
No, you dont have to wipe data before flashing a new radio.
Click to expand...
Click to collapse
Thank you very much! I'll make a nandroid my rom, and flash radio and alpha8 of CM9
cualla84 said:
Thank you very much! I'll make a nandroid my rom, and flash radio and alpha8 of CM9
Click to expand...
Click to collapse
Sounds like a good plan! Enjoy Alpha8. Nightly builds are available too (check signature)
Untouchab1e said:
Sounds like a good plan! Enjoy Alpha8. Nightly builds are available too (check signature)
Click to expand...
Click to collapse
Better then flash the nightly? What improvements have regarding alpha8? I can´t see the features!
cualla84 said:
Better then flash the nightly? What improvements have regarding alpha8? I can´t see the features!
Click to expand...
Click to collapse
No Ville-specific improvements, just the latest CM9 commits. Its basically the exact same ROM, just with the latest CM9 improvements.
Thanks Untouchab1e!
Untouchab1e said:
No Ville-specific improvements, just the latest CM9 commits. Its basically the exact same ROM, just with the latest CM9 improvements.
Click to expand...
Click to collapse
OK! I will charge the battery and I get to it!
Flashed 1.78 EU radio to stock tmous and I'm getting zero issues and excellent battery life so far. Thx
Sent from my HTC VLE_U using xda premium
flash directly from cwm?
having already unlocked, root and flashed the latest cwm, can't i just move the radio.zip file to the phone and flash directly in cwm instead of all commands?
I was unable to flash any custom kernel on stock rom need help. firmware 3.33
maybe because 3.33 is still new and the kernels we have are only 3.32 based?
arabology said:
maybe because 3.33 is still new and the kernels we have are only 3.32 based?
Click to expand...
Click to collapse
No, it has nothing to do with this. OP is probably running a stock ROM and stock kernel. This has a locked ramdisk. Custom kernels need an unlocked ramdisk.
However OP, a bit more information would help. S-ON/S-OFF? Which firmware are you running? What ROM are you running?
V1k70r said:
No, it has nothing to do with this. OP is probably running a stock ROM and stock kernel. This has a locked ramdisk. Custom kernels need an unlocked ramdisk.
However OP, a bit more information would help. S-ON/S-OFF? Which firmware are you running? What ROM are you running?
Click to expand...
Click to collapse
um...ehm...he's stock man...why asking what ROM he's running
also, i have an EVO 3D and i flash custom kernels on the stock ROM for ever now.
Kernels and ramdisk are included in boot.img, so if he's S-OFF (in which i'm positive he is) it should work just fine.
i still back my point about the firmware difference.
V1k70r said:
No, it has nothing to do with this. OP is probably running a stock ROM and stock kernel. This has a locked ramdisk. Custom kernels need an unlocked ramdisk.
However OP, a bit more information would help. S-ON/S-OFF? Which firmware are you running? What ROM are you running?
Click to expand...
Click to collapse
Yes i am s-off with latest stock firmware 3.33.415.106
arabology said:
um...ehm...he's stock man...why asking what ROM he's running
also, i have an EVO 3D and i flash custom kernels on the stock ROM for ever now.
Kernels and ramdisk are included in boot.img, so if he's S-OFF (in which i'm positive he is) it should work just fine.
i still back my point about the firmware difference.
Click to expand...
Click to collapse
By the way even when i was on earlier 3.32 version i was unable to flash nor faux kernel nor bricked kernel, i think it has nothing to do with firmware version.
naelmnael said:
By the way even when i was on earlier 3.32 version i was unable to flash nor faux kernel nor bricked kernel, i think it has nothing to do with firmware version.
Click to expand...
Click to collapse
what sort of error did you get? bootloops? did you do wipes?
he will get status 7 error
and here is the proper explanation and possible fix
http://forum.xda-developers.com/showthread.php?t=1556620
assert failed: write_raw_image ("tmp/newboot.img". "boot")
E:Error in /sdcard/overclocked_kernel_v1.20_1728_Mhz_by_SebastianFM.z ip (status 7) installation aborted.
I wiped Dalvik cache and chache partition but none of this seems to work.
i tried different kernels and tried re-downloading and flashing but nothing seems to work
naelmnael said:
assert failed: write_raw_image ("tmp/newboot.img". "boot")
E:Error in /sdcard/overclocked_kernel_v1.20_1728_Mhz_by_SebastianFM.z ip (status 7) installation aborted.
I wiped Dalvik cache and chache partition but none of this seems to work.
i tried different kernels and tried re-downloading and flashing but nothing seems to work
Click to expand...
Click to collapse
try this boot.img
https://www.dropbox.com/s/fxo11b48qc3xuiw/boot.img
you need to flash that via fastboot though
copy the file to adb/fastboot folder
connect phone to pc in fastboot mode (phone reads "fastboot usb")
then this command
fastboot flash boot boot.img
after this try to flash the custom kernel's via recovery ..they will work
ganeshp said:
try this boot.img
https://www.dropbox.com/s/fxo11b48qc3xuiw/boot.img
you need to flash that via fastboot though
copy the file to adb/fastboot folder
connect phone to pc in fastboot mode (phone reads "fastboot usb")
then this command
fastboot flash boot boot.img
after this try to flash the custom kernel's via recovery ..they will work
Click to expand...
Click to collapse
Is this boot image for Sensation XE
After flashing the boot i get wifi error can't turn my wifi on.
naelmnael said:
After flashing the boot i get wifi error can't turn my wifi on.
Click to expand...
Click to collapse
the boot.img i have given you is only temporaray ..its to support other kernel's you are trying to flash until now
so just flash the kernel you want now from CWM
if you are S-ON and HTC-dev unlcoked then
stop and flash 4EXT recovery and flash the kernel with smartflash ON
this guide step #2 and step #3
ganeshp said:
he will get status 7 error
and here is the proper explanation and possible fix
http://forum.xda-developers.com/showthread.php?t=1556620
Click to expand...
Click to collapse
naelmnael said:
After flashing the boot i get wifi error can't turn my wifi on.
Click to expand...
Click to collapse
Like I said, locked ramdisk .
You flashed a boot image with an unlocked ramdisk, so now you should be able to flash a custom kernel OP. Wifi will probably work after that.
ganeshp said:
the boot.img i have given you is only temporaray ..its to support other kernel's you are trying to flash until now
so just flash the kernel you want now from CWM
if you are S-ON and HTC-dev unlcoked then
stop and flash 4EXT recovery and flash the kernel with smartflash ON
this guide step #2 and step #3
Click to expand...
Click to collapse
the problem was with bricked kernel wifi worked ok with Sebastian kernel thanks mate
V1k70r said:
Like I said, locked ramdisk .
You flashed a boot image with an unlocked ramdisk, so now you should be able to flash a custom kernel OP. Wifi will probably work after that.
Click to expand...
Click to collapse
I flashed MIUI 2.17 and then got error "status 7", then I flash bricked kernel and it worked. But I got a wifi problem: it only works with bricked kernel, I've flashed Sebastian and faux kernel but wifi keep on "turning wifi on" . What should I do now?
Hi i'm new to the att htc one x, just rooted, and installed twrp... then flash cleanrom5. I also noticed clean has a kernel, i did not see an install guide, but i've installed kernels before on my captivate. So what i'm wondering if it's as easy as....
1. place kernel on phone storage
2. reboot into recovery
3. install kernel from recovery
4. reboot
If there anything i am missing or if i am completely off could someone please help me out with this?
Thank you :good:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
redpoint73 said:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
Click to expand...
Click to collapse
Would you mind walking me through that process?
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
cannon19932006 said:
Would you mind walking me through that process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
absolutelygrim said:
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
Click to expand...
Click to collapse
I don't see anything about flashing kernels in that thread.
cannon19932006 said:
I don't see anything about flashing kernels in that thread.
Click to expand...
Click to collapse
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery. fastboot flash method http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
edit: btw, what exploit did you use to achieve root? Was it the x-factor exploit?
cannon19932006 said:
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
Click to expand...
Click to collapse
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
redpoint73 said:
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
Click to expand...
Click to collapse
i used x-factor yes, and yes it's 1.14, thank you both for the help.
cannon19932006 said:
i used x-factor yes, and yes it's 1.14, thank you both for the help.
Click to expand...
Click to collapse
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
absolutelygrim said:
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
Click to expand...
Click to collapse
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
cannon19932006 said:
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
Click to expand...
Click to collapse
Well, If cleanROM is using the same Kernel as stock, then you got lucky. If they use the same kernel, no need to flash boot.img.
If they are different kernels and you dont flash boot.img, you are now in a bootloop
lol Universal City
not bad
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
cannon19932006 said:
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
Click to expand...
Click to collapse
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
absolutelygrim said:
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
Click to expand...
Click to collapse
Success, THANKS!
absolutelygrim said:
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery.
Click to expand...
Click to collapse
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
cimenta said:
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
Click to expand...
Click to collapse
Because the new hboot makes it to where you cant flash kernels through recovery. only fasboot
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
cimenta said:
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
Click to expand...
Click to collapse
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
absolutelygrim said:
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
So although ROM zip file contains boot.img when flashing boot.img won't be flashed? That's why we need to flash is separately? Is it important to flash it before flashing ROM?
Thank you.R
I'm also, learning as I go. From reading and multiple failed attempts at flashing ROMs and kernels, I have found the correct way with 1.14 Hboot.
-dl the rom/kernel
-extract only the boot.img file
- save both .zip and boot to your desired folder.
-go into recovery and mount sd card to pc
-transfer .zip file to your phones sd card
-get back into fastboot on your phone
-transfer boot.img to fastboot folder
-from fastboot cmd prompt(if you have win7, open your folder with fastboot in it hold shift+right click and open cmd)
-type "fastboot boot boot.img" without quotes
-go back into recovery and clean cache/delvik
-then install .zip that you copied to the sd card
You should be good to go from there.
If I have left anything out, please feel free to correct.
Sent from my HTC One X using xda app-developers app
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
1aladdin1 said:
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
Click to expand...
Click to collapse
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Darknites said:
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Click to expand...
Click to collapse
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
1aladdin1 said:
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
Click to expand...
Click to collapse
I use to fastboot first then rom but now I just use Flash Image GUI. TWRP wont say its failed for some reason but it can if you remove the boot.img but thats nothing to worry about.
there is a method how to downgrade hboot:
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade+unbrick
it's a little bit tricky and requires some linux knowledge, but it takes you down to hboot 1.06
I recently s-offed my sensation using JuopunutBear and then managed to downgrade to HBOOT 1.18 because I was trying to downgrade the radio. I was facing the WiFi "error" and figured it might just be the radio so i downgraded it
That did not solve my problem and i decided to revert back to ICS rom to try something else and i flashed the rom and it wont boot
I tried other roms but nothing i selected booted. I did try flashing boot.img using adb but that didnt help either
all i need is to be able to go back to 1.27 HBOOT, remain S-off and somehow figure out how to get the WiFi working
stratoll said:
I recently s-offed my sensation using JuopunutBear and then managed to downgrade to HBOOT 1.18 because I was trying to downgrade the radio. I was facing the WiFi "error" and figured it might just be the radio so i downgraded it
That did not solve my problem and i decided to revert back to ICS rom to try something else and i flashed the rom and it wont boot
I tried other roms but nothing i selected booted. I did try flashing boot.img using adb but that didnt help either
all i need is to be able to go back to 1.27 HBOOT, remain S-off and somehow figure out how to get the WiFi working
Click to expand...
Click to collapse
Since you're s-off, then flash 3.33 universal firmware from this thread: http://forum.xda-developers.com/showthread.php?p=21711154
Also, make sure you format all partitions before flashing any ROM.
Sent from my Ouya
AndroidSupporter318 said:
Since you're s-off, then flash 3.33 universal firmware from this thread: http://forum.xda-developers.com/showthread.php?p=21711154
Also, make sure you format all partitions before flashing any ROM.
Sent from my Ouya
Click to expand...
Click to collapse
It says it supports all T-mobile versions
Does it matter that my sensation is international not T-mobile?
stratoll said:
It says it supports all T-mobile versions
Does it matter that my sensation is international not T-mobile?
Click to expand...
Click to collapse
that's why 3.33 is calling universal
also before flashing check md5 sums(important)
thanks you guys
I could only manage to get the stock rom to boot but it's something
now if only I could figure out how to get the WiFi to work...
stratoll said:
thanks you guys
I could only manage to get the stock rom to boot but it's something
now if only I could figure out how to get the WiFi to work...
Click to expand...
Click to collapse
flash the boot.img of the rom via fastboot command
try also with wifix manager
rzr86 said:
flash the boot.img of the rom via fastboot command
try also with wifix manager
Click to expand...
Click to collapse
Don't forget to change WiFi region code also
Sent from my Ouya
rzr86 said:
flash the boot.img of the rom via fastboot command
try also with wifix manager
Click to expand...
Click to collapse
tired flashing boot image using smartflash 4ext and manually
both failed
tried wifix told me it couldnt fix the problem and asked me to send an error report which I couldn't coz i had no wifi
and I believe you need to enable WiFi in order to change region code
since I can't enable it I can't change it
needless to say I've tried several different roms and also changed the radio to 10.something and it still would't work
stratoll said:
tired flashing boot image using smartflash 4ext and manually
both failed
tried wifix told me it couldnt fix the problem and asked me to send an error report which I couldn't coz i had no wifi
and I believe you need to enable WiFi in order to change region code
since I can't enable it I can't change it
needless to say I've tried several different roms and also changed the radio to 10.something and it still would't work
Click to expand...
Click to collapse
go to system->etc->wifi and delete the wpa_supplicant.conf file
back it up first just in case
after that check again wifi
edit:try it also on data->misc->wifi and delete the wpa_supplicant.conf file
rzr86 said:
go to system->etc->wifi and delete the wpa_supplicant.conf file
back it up first just in case
after that check again wifi
edit:try it also on data->misc->wifi and delete the wpa_supplicant.conf file
Click to expand...
Click to collapse
so I'm supposed to do that in the flashable zip and then flash the rom or am i supposed to do it in the alredy installed rom somehow?
stratoll said:
so I'm supposed to do that in the flashable zip and then flash the rom or am i supposed to do it in the alredy installed rom somehow?
Click to expand...
Click to collapse
in the already installed rom
use any file manager you have with root rights and delete it
don't forget to copy it to the sdcard first
rzr86 said:
in the already installed rom
use any file manager you have with root rights and delete it
don't forget to copy it to the sdcard first
Click to expand...
Click to collapse
well that was definitely something I hadn't seen before but unfortunately it failed
I deleted both files one by one
WiFi was stuck on turning on so i had to restart phone both times
rom still works fine, WiFi still doesn't work at all
gets stuck at turning on and eventually says error
stratoll said:
well that was definitely something I hadn't seen before but unfortunately it failed
I deleted both files one by one
WiFi was stuck on turning on so i had to restart phone both times
rom still works fine, WiFi still doesn't work at all
gets stuck at turning on and eventually says error
Click to expand...
Click to collapse
try to install a ruu.exe
see how it goes
rzr86 said:
try to install a ruu.exe
see how it goes
Click to expand...
Click to collapse
the RUU update utility fails to reboot my phone into bootloader and gives error 155:unknown error
stratoll said:
the RUU update utility fails to reboot my phone into bootloader and gives error 155:unknown error
Click to expand...
Click to collapse
as far as i know error 155 is a connection issue
switch off the device and remove the battery
reinsert it
press and hold together power button + volume down until it gets you to the bootloader
connect it to pc via usb and select fastboot
then run the ruu.exe
rzr86 said:
as far as i know error 155 is a connection issue
switch off the device and remove the battery
reinsert it
press and hold together power button + volume down until it gets you to the bootloader
connect it to pc via usb and select fastboot
then run the ruu.exe
Click to expand...
Click to collapse
thats brilliant actually but still no joy
now i have a locked bootloader and official recovery but the wifi still says error
should i flash recovery, after unlocking obviously, flash superuser and try to delete those files in this rom that i got through ruu
its GB, i thought maybe ICS was giving me problems so i wanted to revert to stock GB just to check if it worked... but it didnt
stratoll said:
thats brilliant actually but still no joy
now i have a locked bootloader and official recovery but the wifi still says error
should i flash recovery, after unlocking obviously, flash superuser and try to delete those files in this rom that i got through ruu
its GB, i thought maybe ICS was giving me problems so i wanted to revert to stock GB just to check if it worked... but it didnt
Click to expand...
Click to collapse
try it
also try to flash different roms from recovery too
if those fail too then maybe we have to do with a hardware problem
rzr86 said:
try it
also try to flash different roms from recovery too
if those fail too then maybe we have to do with a hardware problem
Click to expand...
Click to collapse
after having tried everything I could find here on xda I concluded it had to be a hardware issue and went back to my Desire for now
thanks for all the help mate
appreciate it