Related
Hi there,
it's my fist post here so please do not shoot on sight if I did post in the wrong section. Also, I searched before posting if someone had the exact same problem and didn't find anything conclusive so here goes :
I have a unbranded Desire S which I sucessfully S-OFFed (HBOOT 2) a while ago, then installed 4Ext Recovery and rooted with success.
Now I reckon I am a bit tired of waiting for the ICS update from HTC, so what the heck, I decided i'd try some custom ROMs.
I did a full backup of all partitions using 4ext recovery and then wiped the data, cache and dalvik cache as most ROMs require.
I then proceeded to flash 3 different ROMs with the same unfortunate result : The flashing is always successful, and upon reboot I am just stuck on the HTC boot screen forever.
Then I have to turn the phone off (vol up+vol down + power) then remove the battery and put it back, and have to boot into recovery to continue from there.
After the same thing happened with the 3 ROMs (Fallout 4.4, Vanilla ICE 2 and IceColdSandwich) I just restored my initial backup and then the phone booted back to the original ROM without problems.
What could have I done wrong please ? What can I try next to make a custom ROM work ?
Thanks for your expertise !
Are you HTC dev unloced? or S-Off after downgrade?
I had a similar problem with my Desire S. It was a while ago but I finished up formatting my SDcard to FAT32. Used gparted to delete all partitions, then make one FAT32.
You can use gparted from the live CD or as I did rebooted PC with the CD, download here
I use Reaper v3.0 ROM which is very stable.
Hope this helps
suku_patel_22 said:
Are you HTC dev unloced? or S-Off after downgrade?
Click to expand...
Click to collapse
HTC Dev unlocked.
Taysider said:
I had a similar problem with my Desire S. It was a while ago but I finished up formatting my SDcard to FAT32. Used gparted to delete all partitions, then make one FAT32.
You can use gparted from the live CD or as I did rebooted PC with the CD, download here
I use Reaper v3.0 ROM which is very stable.
Hope this helps
Click to expand...
Click to collapse
Delete all partitions from what, SD card ? I seem to only have one partition so far ... Could you be more specific please, sorry, I just don't want to do something wrong
flash boot.img manually.. use search to know why i said this..
Skanob said:
flash boot.img manually.. use search to know why i said this..
Click to expand...
Click to collapse
I now entered 4ext recovery, cleared cache and wiped data, flashed the ROM, then rebooted into hboot and switched to fastboot mode. then plugged the USB and ran the command
fastboot flash boot boot.img
with the boot.img file extracted from the ROM's zip.
Rebooting did work and I now saw a different logo (HTC One since the ROM was ported from there) and then the phone booted into Android.
Thanks Skanob !
Flash boot.img from fastboot
Check the forum or Google about how to do it
Tapatalked from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!!!
How to fix this problem once and for all
I have the exact same problem
Also did the htcdev unlock then superoneclick root.
Is there any way to fix it so that it flashes the boot.img on automatically when you flash a ROM?
slugger7 said:
Is there any way to fix it so that it flashes the boot.img on automatically when you flash a ROM?
Click to expand...
Click to collapse
Yes, S-OFF.
chninkel said:
Yes, S-OFF.
Click to expand...
Click to collapse
ok then how do you go about s-offing the device for good after the htcdev s-off and then superoneclick root that switched it back on again for some reason
slugger7 said:
ok then how do you go about s-offing the device for good after the htcdev s-off and then superoneclick root that switched it back on again for some reason
Click to expand...
Click to collapse
Htcdev doesn't s-off, it unlocks boot loader but you're still s-on
The forum contains all the information, read the index
So you need to relock
Downgrade
Soff
There are multiple guides
Sywepd form my DsereiS
Hi -
I have an HTC One S (unlocked and rooted - t-mobile) running cm-10.0.0-ville - This is the last stable CyanogenMod ROM.
I would greatly appreciate it if someone could walk me through the steps on how to upgrade this to another ROM (of your choice) that will give me Android 4.3 - There are some features in 4.3 OS that I would love to have (very practical)...
I have heard that I would have to flash boot.img manually using adb if I were to install another ROM. I am worried I will miss a step and soft or hard brick my phone during the process.... I am familiar with Samsungs but HTC from my experience is a hit or miss when it comes to upgrading ROMS or flashing new ones...
Please help so I dont end up with 'unable to mount sdcard' type errors
DroidLuvver said:
Hi -
I have an HTC One S (unlocked and rooted - t-mobile) running cm-10.0.0-ville - This is the last stable CyanogenMod ROM.
I would greatly appreciate it if someone could walk me through the steps on how to upgrade this to another ROM (of your choice) that will give me Android 4.3 - There are some features in 4.3 OS that I would love to have (very practical)...
I have heard that I would have to flash boot.img manually using adb if I were to install another ROM. I am worried I will miss a step and soft or hard brick my phone during the process.... I am familiar with Samsungs but HTC from my experience is a hit or miss when it comes to upgrading ROMS or flashing new ones...
Please help so I dont end up with 'unable to mount sdcard' type errors
Click to expand...
Click to collapse
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
khan.orak said:
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
Click to expand...
Click to collapse
Thanks - complete/informative/precise response. Exactly what I was looking for.
My phone isn't S-OFF (meaning, it is S-ON) so I will follow your directions to update to Android 4.3 - will try the ROMs you suggested. Before I do anything, I will make a backup of existing CM rom though of course.... My concern, and the reason why I posted here, was that last time when I made a backup of existing ROM, then tried to restore from it, I got "unable to mount sd/card' message that I was not able to fix myself (had to pay someone to get that one fixed) .. I dont want to get burned again so needed precise instructions to be able to go back and forth (to a new ROM as u suggested, then go back to my existing one using backup)
DroidLuvver said:
Thanks - complete/informative/precise response. Exactly what I was looking for.
My phone isn't S-OFF (meaning, it is S-ON) so I will follow your directions to update to Android 4.3 - will try the ROMs you suggested. Before I do anything, I will make a backup of existing CM rom though of course.... My concern, and the reason why I posted here, was that last time when I made a backup of existing ROM, then tried to restore from it, I got "unable to mount sd/card' message that I was not able to fix myself (had to pay someone to get that one fixed) .. I dont want to get burned again so needed precise instructions to be able to go back and forth (to a new ROM as u suggested, then go back to my existing one using backup)
Click to expand...
Click to collapse
SD not being able to mount is the result of formatting it using anything other than stock recovery.
If you happen to face that error again, flash a stock recovery, wipe SD from bootloader and it's good to go.
You can then reflash custom recoveries.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
SD not being able to mount is the result of formatting it using anything other than stock recovery.
If you happen to face that error again, flash a stock recovery, wipe SD from bootloader and it's good to go.
You can then reflash custom recoveries.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Ok - so three questions...
1) flash a stock recovery -- pointers on downloading stock recovery for Tmobile/unlocked HTC One S (s4) ?
2) flash a stock recovery - once I have the recovery files, I use adb to push the recovery to the phone or TWRP ? I couldnt use TWRP or clockwork because it didnt even see sd-card...
3) wipe SD from bootloader - do you mean, using adb, issue a command that formats SD card? If so, what is the command?
DroidLuvver said:
Ok - so three questions...
1) flash a stock recovery -- pointers on downloading stock recovery for Tmobile/unlocked HTC One S (s4) ?
2) flash a stock recovery - once I have the recovery files, I use adb to push the recovery to the phone or TWRP ? I couldnt use TWRP or clockwork because it didnt even see sd-card...
3) wipe SD from bootloader - do you mean, using adb, issue a command that formats SD card? If so, what is the command?
Click to expand...
Click to collapse
1. Stock recovery can be found in the forums. It can also be extracted from any Jellybean OTA.zip for any region but intended for S4 device and not an OTA.zip for One S S3. It can be found in Ota.zip\firmware.zip\recovery.img
2. You put the phone in FASTBOOT mode from bootloader and connect to PC, place recovery inside adb folder and issue this command.
Code:
fastboot flash recovery recovery.img
Pretty much similar to boot.img method.
Similarly you can flash custom recoveries
3. When you flash stock recovery, go to bootloader and select CLEAR STORAGE and then FACTORY RESET. That does the job.
Sent from my Nexus 7 using Tapatalk HD
Here is the info on my phone ... (below) - I have an older kernel and in order to upgrade to Android 4.3 (Odyssey or PAC), I will have to upgrade kernel right??
cw v6.0.3.1
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
OpenDSP-v31.1.0.45.0015
eMMC-boot
Apr 20 2012, 15:14:18
Can anyone please confirm this method?
This looks great, but I'm wary that no one has confirmed success.
My phone:
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
TWRP 2.4.1.0
Currently running CyanogenMod:10.1-20130304-Experimental-ville-M2
(On of the last of the 10.1 ROMs before the updated kernel requirement?)
So is this a good (confirmed) method for me? Other ideas? Thanks.
khan.orak said:
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
Click to expand...
Click to collapse
jeremybagai said:
This looks great, but I'm wary that no one has confirmed success.
My phone:
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
TWRP 2.4.1.0
Currently running CyanogenMod:10.1-20130304-Experimental-ville-M2
(On of the last of the 10.1 ROMs before the updated kernel requirement?)
So is this a good (confirmed) method for me? Other ideas? Thanks.
Click to expand...
Click to collapse
Unrelated to what you asked but can you tell me that if you are running "10.1-20130304-Experimental-ville-M2" do you have 4G/3G connection ?
DroidLuvver said:
Unrelated to what you asked but can you tell me that if you are running "10.1-20130304-Experimental-ville-M2" do you have 4G/3G connection ?
Click to expand...
Click to collapse
4g works, no problem. I have some issue with Widget Locker that makes me reboot every day or so, but other than that it's a nice build.
jeremybagai said:
4g works, no problem. I have some issue with Widget Locker that makes me reboot every day or so, but other than that it's a nice build.
Click to expand...
Click to collapse
Can you tell me what radio you have got?
Sent from my HTC One S using xda app-developers app
DroidLuvver said:
Can you tell me what radio you have got?
1.13.50.05.25
So it sounds like I'm helping you get to an Experimental Cyanogen 10.1 rom without updating your firmware. It should work. Enjoy.
But I wish someone would comment more on your original question -- how best to upgrade firmware and explore the newer 10.1 and 10.2 roms?
Can anyone confirm what method they used?
Jeremy
Click to expand...
Click to collapse
jeremybagai said:
DroidLuvver said:
Can you tell me what radio you have got?
1.13.50.05.25
So it sounds like I'm helping you get to an Experimental Cyanogen 10.1 rom without updating your firmware. It should work. Enjoy.
But I wish someone would comment more on your original question -- how best to upgrade firmware and explore the newer 10.1 and 10.2 roms?
Can anyone confirm what method they used?
Jeremy
Click to expand...
Click to collapse
So my radio is 1-13.50.05.31 - I wonder if I should find and flash 11.13.50.05.25 to get my 4G back ? You got 1.13 HBOOT ?
Click to expand...
Click to collapse
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!
Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo
ipk1 said:
Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo
Click to expand...
Click to collapse
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.
Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
You don't need to do anything with your hboot, it's fine
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
sudo adb flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
And ... I hope this is not the wrong forum. If so, really sorry ...
Click to expand...
Click to collapse
It is - questions should be posted in the Questions subforum :silly:
SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.
Click to expand...
Click to collapse
all right. thanks. i found that recovery and did
sudo fastboot flash recovery 4EXT_Recovery_Touch_v1.0.0.6_RC1.img
when i go into recovery then, again nothing ... phone is stuck in the white screen. sorry. with white screen i meant the splash screen, which is white on my phone, but has the telecom logo. so i think the screen is allright.
so i pulled the battery and back to cwm (flashed the cms recovery and voila).
Aquous said:
Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
Click to expand...
Click to collapse
absolutely. that's why i came here. the phone was fine under htc sense, so its not the phone. it got to be me.
Aquous said:
You don't need to do anything with your hboot, it's fine
Click to expand...
Click to collapse
Good.
Aquous said:
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
oh. typo. sorry.
Aquous said:
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This boots into recovery. But not exactly. It boots to the white Telekom screen, and then it reboots and goes into recovery. Since I found that strange I extracted the boot image once more from the flinny...zip and tried again. confirmed.
Aquous said:
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Click to expand...
Click to collapse
Downloading. This is "SVHD v2.1.0 by mygamers (MultiDevice)", right ? The thing is huge. That's gonna take a bit and I have to go to work. Get back to you later ...
Aquous said:
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
It is - questions should be posted in the Questions subforum :silly:
Click to expand...
Click to collapse
I extracted the boot.img
Can somebody move this ?
SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
GL.
Click to expand...
Click to collapse
4ext touch 1.0.0.6 RC1, same problem. stuck at the white telekom screen.
twrp-2.7.0.0-saga-recovery.img, same problem.
but openrecovery-twrp-2.6.3.0-saga.img did work
Ingo
Aquous said:
I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good.
Click to expand...
Click to collapse
tdDDAAA !!!
So I installed the SVHD .zip with TWRP 2.6 (see above) and that did go nowhere yet.
But I then extracted the saga boot image from that zip kernel/saga/boot.img, renamed that to avoid confusions, and then
<code>
fastboot boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
And my Telekom splash screen blinks up, then the HTC sense (quietly brilliant), and some 3 minutes later ... it worked.
Flashing
<code>
fastboot flash boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
MY guess is it was the reformatting to ext4 ... is that something I should have done all along ? Or any other idea ?
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Yeah,check panel now.Some phones has that problem.If you have hitachi then I'm sorry.From what I know no1 make MDDI kernel anymore.
teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Must be, since I tried to install blindnnumbs cm now, and same problem, again ... Good ... so back to SVHD and check that thread. Thanks.
Ingo
One more thing:
On the link you provided the instructions are given as follows, and i am not 100% clear on everything:
1) Wipe all data
2) Flash your custom ROM
3) Get your MDDI compatible kernel and flash it
--> IF (and only IF) you've this error when flashing kernel in recovery: assert failed:write_raw_image("/tmp/boot.img","boot"):
--> 3a) extract boot.img from custom rom ZIP and put it in the adb directory on your PC
--> 3b) reboot in fastboot mode
--> 3c) execute from PC: fastboot flash boot.img
--> 3d) reboot in recovery and retry to flash your new kernel
--> 3e) Now, flashing kernel is completed and you can continue to Step 4)
4) Get new boot.img: in recovery, attach USB cable and run from PC terminal --> adb pull /tmp/newboot.img (it will trasfer generated boot.img to your PC) <--
5) On your PC rename newboot.img file to boot.img
6) Reboot in fastboot mode
7) Install new boot.img (from PC terminal execute --> fastboot flash boot.img <--)
So I
- in twrp i installed cm-10.1-20130709-UNOFFICIAL-saga.zip (blindnnumb cm-10.1, penultimate version. the very last version does not unzip, no matter how many times i download it)
- then flashed fastboot flash boot cm-10.1-20130709-UNOFFICIAL-saga.img
- then flashed fastboot flash boot saga_mddi_291212.img (from your link)
- i pulled newboot.img and then flashed newboot.img
and i am stuck again ... but maybe i did not totally understand the instruction from above ? i.e. 2). do i need to install the zip and the img ?
also in line 7) the command seems to be wrong. right ?
ingo
If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img
teadrinker said:
If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img
Click to expand...
Click to collapse
Oh my ... that did not go either. Now I flashed
cm-10-20121116-EXPERIMENTAL-saga-NK111.zip
saga_kernel_82n_4.0_4.1.zip (which does not seem to produce a newboot.img, and does not have a boot.img either)
that, at least, brings up the spinning clockworkmod wheel ... but then that's that, too ...
oh well ... i guess SENSE it is gonna be then ...
ingo
Didn't you read the warning at the top of the hitachi panel thread? It said:
WARNING!
ALL THE LATEST 4.1.x AND 4.2.x ROMS DO NOT SUPPORT HITACHI SCREEN PANELS, EVEN AFTER APPLYING THE CORRECT MDDI KERNEL!
THIS APPLIES TO ROMS THAT ARE BASED ON AOSP, AOKP, CyanogenMod, ParanoidAndroid, PAC-Man, etc., AND ROMS THAT ARE BASED ON MIUI
THE LAST CUSTOM ROM THAT DOES SUPPORT MDDI PANELS IS CyanogenMod 10.1 Build 13 by Flinny, SO THE DATE WHEN BUILD 13 WAS RELEASED IS YOUR GUIDE TO CHOOSE THE CORRECT ROM THAT WILL BOOT UP AFTER FLASHING THE MDDI KERNEL
Click to expand...
Click to collapse
Aquous said:
Didn't you read the warning at the top of the hitachi panel thread? It said:
Click to expand...
Click to collapse
Read it ... and I think I did not understand it right ... I guess I got too tired over it. I thought I had one that should match those criteria. Tomorrow is another day ...
Ingo
Dear all,
i have htc desire s hboot 2.00.0002 s-on which already rooted and boot locker unlocked.i was try t0 install cm 11 but i cant install .although i manage to install cm10 once but after install i reboot the device then nothing come without black screen.
now, i install stable cm7 but which is too old version. some one told me because me phone is s -on that why i cant install latest version of cm.so i need help how can i s-off my phone . I found few methods like for 0.98 hboot example Revolutionary" method.
I really want to update my phone to kitkat or at-least ice cream .can any one help me how i can so that
thanks in advance ....
You don't need s-off to install latest custom ROMs
All you need to do is to flash boot.img extracted from zip after flashing the ROM, using this command
fastboot flash boot boot.img
If it's done correctly and your phone still doesn't boot, then you need to look into this
http://forum.xda-developers.com/showthread.php?t=1943524
Edit:
Also, make sure you are on lastet 4EXT recovery 1.0.0.6 or TWRP recovery 2.7
ContactFront said:
You don't need s-off to install latest custom ROMs
All you need to do is to flash boot.img extracted from zip after flashing the ROM, using this command
fastboot flash boot boot.img
If it's done correctly and your phone still doesn't boot, then you need to look into this
http://forum.xda-developers.com/showthread.php?t=1943524
Edit:
Also, make sure you are on lastet 4EXT recovery 1.0.0.6 or TWRP recovery 2.7
Click to expand...
Click to collapse
thanks for your reply i have CWM 4 wheni install cm11 it stuck my phone nothing boot.
ContactFront said:
You don't need s-off to install latest custom ROMs
All you need to do is to flash boot.img extracted from zip after flashing the ROM, using this command
fastboot flash boot boot.img
If it's done correctly and your phone still doesn't boot, then you need to look into this
http://forum.xda-developers.com/showthread.php?t=1943524
Edit:
Also, make sure you are on lastet 4EXT recovery 1.0.0.6 or TWRP recovery 2.7
Click to expand...
Click to collapse
your recomand tread it says su
dmesg | grep -i panel
If the app shows you any text with word "sony" in it - then your device has a screen panel made by Sony (obviously). If that's the case - you can just close this thread at once and don't worry that your device might freeze at "HTC Quietly Brilliant" screen after flashing a ROM. Otherwise, proceed forward.
any my phone is made by sony as well
akankha said:
thanks for your reply i have CWM 4 wheni install cm11 it stuck my phone nothing boot.
Click to expand...
Click to collapse
Like said above, flash latest 4ext recovery v1.0.0.6 via fastboot commands. Flash the rom then boot straight into fastboot and flash the boot.img then reboot.
Or if u want to s-off, follow this guide.
http://forum.xda-developers.com/showthread.php?t=1318919
akankha said:
thanks for your reply i have CWM 4 wheni install cm11 it stuck my phone nothing boot.
Click to expand...
Click to collapse
You need to use latest 4EXT or TWRP for these newer 4.4 roms. CWM is no good.
130
ContactFront said:
You need to use latest 4EXT or TWRP for these newer 4.4 roms. CWM is no good.
Click to expand...
Click to collapse
thanks for finally i managed to upgrade to kitkat .but one new problem is arise .no one can hear my voice while i or they call me they only can hear there voice repeated.