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
Related
Okay so my sisters sensation would freeze up every time she got calls from certain people so I told her to let me root it. Since this is something I have done many times before I didn't think I would have any problems, but I do.
I can only boot into bootloader and then recovery. I can flash ROMs, restore, and do anything else you do in recovery, except afterwords when I choose reboot the phone just turns off and nothing happens and I can't boot into recovery for several minutes (during these minutes the phone has to be charging). I've been up for literally 5 hours, 1-6 am, trying to figure this out. Someone PLEASE help me. Seriously WILLING TO PAY for an answer that works.
Thank you.
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
Yea I've taken it off the sd and tried that didn't work either man
tr1p7s said:
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
Click to expand...
Click to collapse
See my problem with super CID is the guide that I see for it http://forum.xda-developers.com/showthread.php?t=1459767 requires me to be able to actually use my phone and I screwed that up lol. I tried that fastboot method too and it didn't work. I fear I've really messed this up.
EddyOS said:
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Click to expand...
Click to collapse
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Should be able to find your phones RUU in the development part of the forums.
Also most of the major Western carriers have the firmware posted on this forum. Did you download the correct one?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Download an RUU from here http://forum.xda-developers.com/showthread.php?t=1074559 to your pc making sure it is the appropriate one for your device (give me more details if you are unsure), boot your phone into fastboot (volume down and power), plug the usb cable into your phone and pc. Your device should now say fastboot usb then double click the RUU.exe that you have downloaded to your pc. This will restore your device to stock.
So problem is the rom refuses to boot, but recovery, bootloader does?
Check whatever fw you flashed is compatible with the rom you are trying to boot. If not change one.
If this does not help then use Eddy's suggestion and run correct ruu. Make sure your CID supports the one you use, or forget this if you have superCID.
Sent from my Pyramid-T
Do what is said here: http://forum.xda-developers.com/showthread.php?t=1192300 (the superCID part) and skip steps 5,6 and 7 just boot into bootloader manually. Then, flash the firmware you need, you won't have to worry about the CID. Get it from here: http://forum.xda-developers.com/showthread.php?t=1459767
Having almost the exact same problem after flashing the firmware..
Def. Gonna try this.
ok i have open root with htcdev went smooth second used superboot also flashed first time
after flashing namleless v1.1 starting going wrong
problem im having now is the phone loads normaly when i try clockwork recovery it hangs on logo screen same for factory reset
software is as follows
android version 4.0.3
htc sense version 4.0
software number Nameless v1.1
htc sdk api level 4.21
htc extension version _403_1_ga_9
kernal version 3.0.16-g8149866 [email protected]#1
baseband version 10.08.98.09h_1.05.98.11m3
build number 1.45.401.4 cl65553
browser version webkit/534.30
***unlocked***
golfu pvt ship s-on rl
hboot-1.28.0000
radio-1.05.98.11m3
emmc-boot
is there away to get clock work bk working have tryed reflashing it says complete but still will not load recovery or factory reset
is there a compatable ruu i can use or maybe some other flash
regards
I had this problem too with my Droid 3. I had to re-install SafeStrap like 3 times to get the recovery menu to work again. Then I had access to clockworkmod.
theGekkoST said:
I had this problem too with my Droid 3. I had to re-install SafeStrap like 3 times to get the recovery menu to work again. Then I had access to clockworkmod.
Click to expand...
Click to collapse
Is SafeStrap an app if so im even more stuck as the wirless is coming up error on my phone still must be the namless v1.1 still ??
Have you tried reflashing CWM via fastboot? Could just be your recovery got borked and you need to reflash recovery.
You can also try reflashing CWM via ROM Manager.
edit: Your img file might be corrupt, did you compare the MD5 sum? How are you flashing recovery?
orangekid said:
Have you tried reflashing CWM via fastboot? Could just be your recovery got borked and you need to reflash recovery.
You can also try reflashing CWM via ROM Manager.
edit: Your img file might be corrupt, did yo the MD5 sumu compare ? How are you flashing recovery?
Click to expand...
Click to collapse
im useing flasboot cmd fastboot flash recovery clockworkrecovery.img from android folder c
and as for apps when i try to use htc sync to load my apps comes up installation failiure pls chk the file and ensure sufficient space
did yot he MD5 sumu compare i have just downloaded this but have never used it before
after i flash namless v1.1 the broblems start as i used cwm to flash from sd card
sorry for my bad grammer btw
regards
just used md5 and it dosnt match
maybe i can find a ruu to load to start afresh maybe ?? any reply welcome pls
spiderx1972 said:
im useing flasboot cmd fastboot flash recovery clockworkrecovery.img from android folder c
and as for apps when i try to use htc sync to load my apps comes up installation failiure pls chk the file and ensure sufficient space
did yot he MD5 sumu compare i have just downloaded this but have never used it before
after i flash namless v1.1 the broblems start as i used cwm to flash from sd card
sorry for my bad grammer btw
regards
just used md5 and it dosnt match
maybe i can find a ruu to load to start afresh maybe ?? any reply welcome pls
Click to expand...
Click to collapse
No you don't have to do all of that,
Just download the correct CWM recovery.img file, CHECK the MD5, then flash via fastboot, you don't have to start fresh or anything.
edit:
what phone is this for?
I got that it's an HTC device running Sense 4 but we might help you find a better CWM recovery link if we know which device you're using on what carrier.
orangekid said:
No you don't have to do all of that,
Just download the correct CWM recovery.img file, CHECK the MD5, then flash via fastboot, you don't have to start fresh or anything.
edit:
what phone is this for?
I got that it's an HTC device running Sense 4 but we might help you find a better CWM recovery link if we know which device you're using on what carrier.
Click to expand...
Click to collapse
may i say first a big tks for rplying very greatfull tbh
my phone dare i say the name is htc desire c /gulp do i here bad news incoming lol
spiderx1972 said:
may i say first a big tks for rplying very greatfull tbh
my phone dare i say the name is htc desire c /gulp do i here bad news incoming lol
Click to expand...
Click to collapse
No you're fine, that should not be an issue.
Let's just find you a good recovery file you can flash.
edit:
Here, http://forum.xda-developers.com/showthread.php?t=1785010
download that beta2 file and flash from fastboot
orangekid said:
No you're fine, that should not be an issue.
Let's just find you a good recovery file you can flash.
edit:
Here, http://forum.xda-developers.com/showthread.php?t=1785010
download that beta2 file and flash from fastboot
Click to expand...
Click to collapse
WORKS LIKE A DREAM
doing a full bk up now gona try the rom from that page aswell
tks to orangekid rly happy now
btw was gona ask with my back i could upload it it if it would help any 1 else or by request duno the rules on uploading stuff if its ok or not
will update after loading rom
cheers all /respect for the help
spiderx1972 said:
WORKS LIKE A DREAM
doing a full bk up now gona try the rom from that page aswell
tks to orangekid rly happy now
btw was gona ask with my back i could upload it it if it would help any 1 else or by request duno the rules on uploading stuff if its ok or not
will update after loading rom
cheers all /respect for the help
Click to expand...
Click to collapse
Awesome!
Glad we got you back up and running, it can be a real pain when the issue is a bad img file and you can't seem to figure out what is going on, but people need to remember to check MD5 sums for recoveries, radios and bootloaders lest they brick.
I don't think you need to upload since that link seems to work, they can just find the CWM for that phone from the link I provided and flash via fastboot from there.
Cheers bro, let us know how it's going after you flash the ROM
orangekid said:
Awesome!
Glad we got you back up and running, it can be a real pain when the issue is a bad img file and you can't seem to figure out what is going on, but people need to remember to check MD5 sums for recoveries, radios and bootloaders lest they brick.
I don't think you need to upload since that link seems to work, they can just find the CWM for that phone from the link I provided and flash via fastboot from there.
Cheers bro, let us know how it's going after you flash the ROM
Click to expand...
Click to collapse
flashed Slim Sense 1.0 for HTC Desire C works fine got my wireless working aswell lol
But i have another question maybe me but when i used other roms in the past i couldnt use htc sync strange i no but i tested the roms to see if it was them causing the problem even formated pc but still no joy stuck at loading Apps from my pc ??
connection from phone is there when i pick drive my sd card pops up on pc when i sync phone is saying unable to open htc sync manager on your computermake sure the application is installed and open witch it is ??
Are all of the drivers installed?
Also try a different USB port.
Sent from my Galaxy Nexus using xda app-developers app
orangekid said:
Are all of the drivers installed?
Also try a different USB port.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
still trying been hours now running at like a bull but no joy yes ive used the same drivers as when it worked before think ive tryed every version of htc sync must be some think saft knowing me
spiderx1972 said:
Is SafeStrap an app if so im even more stuck as the wirless is coming up error on my phone still must be the namless v1.1 still ??
Click to expand...
Click to collapse
Yea it is, but I think it's more for Motorola devices. I don't know what HTC uses if anything different. But my phone would boot to the OS so I could still install apps via the SD card. Once I got that properly reinstalled I could access the boot menu again.
Seems like you got that issue solved by I still wanted to follow up.
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi,
It's not possible to use 4ext, because the phone doesn't boot. he's stop at the boot loader.
I've try with adb for mac but I think I don't do the good command to flash by adb the kernel
ADB does not work, you have to use fastboot! Just follow the instructions by astar26. Connect your phone to your PC/mac and type "fastboot reboot-bootloader" and then "fastboot flash boot boot.img"
Regards
Gesendet von meinem HTC Sensation mit Tapatalk 4
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is an Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
seamo123 said:
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is am Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
Click to expand...
Click to collapse
Usually the ROM is flashed before the kernel, this is what I did
Babyhustle said:
Usually the ROM is flashed before the kernel, this is what I did
Click to expand...
Click to collapse
I have no idea how to flash a kernel on the HTC - that's my main problem
seamo123 said:
I have no idea how to flash a kernel on the HTC - that's my main problem
Click to expand...
Click to collapse
astar26 explained how it works. If the sensation of your friend has 4ext recovery use smartflash, if twrp use htc dumlock then you don't need to flash the kernel seperately.
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Far_SighT said:
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Click to expand...
Click to collapse
seamo123 said:
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Click to expand...
Click to collapse
Ah, I see:
Power off and pull out the battery. Press Power + Vol down. Once the bootloader screen comes up it'll either say S-ON or S-OFF.
For flashing ROMs S-ON use this (also includes 4ext recovery). Read about S-ON here.
Just use smartflash (see link in 1). For the special cases I mentioned in previous post (no smartflash), just see the ROM's thread for S-ON flashing.
Note that if you want just want to flash ROMs the above method is good. For S-OFF, either use this, in case you followed above steps, or use this, in case you want to S-OFF first. S-OFF is not needed for flashing ROMs.
htc sensation z710e wifi problem
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
VS23BG said:
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
Click to expand...
Click to collapse
flash the boot.img of your current rom and see if wifi works
rzr86 said:
flash the boot.img of your current rom and see if wifi works
Click to expand...
Click to collapse
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
VS23BG said:
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
Click to expand...
Click to collapse
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Far_SighT said:
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Click to expand...
Click to collapse
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
VS23BG said:
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
Click to expand...
Click to collapse
lift up gently the antenna which is responsible for wifi in the back cover
I think I finally found the solution to the wifi problem!
The solution is in this post:
http://forum.xda-developers.com/showpost.php?p=23554125&postcount=1804
Now I use Android Revolution HD 7.3,sometimes the problem occurs again, but now I have a solution!
Just repeat the procedure described in the post and wifi working again.
When you delete a file "wpa_supplicant.conf", I have to re-enter all the router's password which I linked, but this is not such a big problem!
Hello,
I'm new here but today I tried to root my phone and put CM10 on it. Rooting was not that hard but with flashing the rom I had some problems. I used a tutorial from youtube "Htc One s jellybean 4.2.2 Nightly Cm10.1 Rom" and did everything as he said but when I tried to boot CM it came in a boot loop so I restored my backup and everything was back normal again. But I thought i'll give it another try so I did that and it still didn't work so I restored (via recovery) and at the end it said: It appears your phone isn't rooted do you wanna do it now...(or something like that)? I found that a bit strange but I clicked yes but now if I boot up my phone first you just see "HTC - quietly brilliant" and then the red letters come beneath it saying its a developers version. I Couldn't do anything so I jumped into my bootloader and did factory reset but now everything is gone and I still have that booting problem,
I can acces bootloader and recovery mode but that's it
I really need my phone soon and don't have much time to look on the internet for solutions so could you please help me?
Thanks in advance!!
Lennard
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
808phone said:
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
Click to expand...
Click to collapse
I don't even know what that it >.< (sorry for being noob )
Did you flash boot.img with cm10
Sent from my One S
ka_55 said:
Did you flash boot.img with cm10
Sent from my One S
Click to expand...
Click to collapse
Jep, as instructed in the youtube video
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
ka_55 said:
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
Click to expand...
Click to collapse
Hboot : 2.15.000
Radio : 1.15.50.05.29
Then it can be a bad download. If not I I'm out of ideas
Sent from my One S
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
808phone said:
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
Click to expand...
Click to collapse
I did the factory reset, dalvik cache and cache wipe. When I tried to install CM it indeed said unable to find md5 or something like that.
I think I have a europe version and looked for fitting RUU but the numbers are completely different maybe you could find a good RUU? (See attachement) Btw I have S4/Ville/Z520e
CID
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
LS.xD said:
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
I don't know if this is it but it says CID: HTC__E11
Lennardude said:
I don't know if this is it but it says CID: HTC__E11
Click to expand...
Click to collapse
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
LS.xD said:
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
Click to expand...
Click to collapse
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Lennardude said:
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Click to expand...
Click to collapse
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you. May be your storage got corrupted and thats why your phone crashed and you can't install the rom.zip stored on the sd-card. You could connect the phone to your pc as mass storage via recovery, format it and put a new customrom.zip on it. By the way, why you installed such an old rom? You can use CM11 for sure
LS.xD said:
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you.
Click to expand...
Click to collapse
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Lennardude said:
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Click to expand...
Click to collapse
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it.
Click to expand...
Click to collapse
v2.6.0.0
Lennardude said:
v2.6.0.0
Click to expand...
Click to collapse
that is TWRP. My suggestion ist installing the latest Recovery and try install CM11. I just get the links for you.
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
Click to expand...
Click to collapse
The problem is, we're talking about an HTC One S which DOESN"T have a SD Card slot...
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying: