[Q] HTC Desire S Stuck on htc logo - HTC Desire S

Hi all,
I'm facing a strange behaviour after rom flashing.
I've unlocked my device through HTCDEV, then I've installed EXT4 Recovery from here RECOVERY then I've installed this ROM
After last step, flash boot image using this code: fastboot flash boot boot.img, the device stuck on logo during the first reboot even if all the steps (also the flash boot.img) finished well.
I'm able to access in fastboot , run recovery etc etc
The only way to recovery my device is "re-lock" using this code: fastboot oem lock , and flash again the original one (RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835 _3831.19.00.110_275068)
I did these steps many times using other devices (same model) withou errors.
Am I missing something ?
Any hint or suggestion how to debug it ?
Tns,
SBK

sbk01 said:
The only way to recovery my device is "re-lock" using this code: fastboot oem lock , and flash again the original one (RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835 _3831.19.00.110_275068)
Click to expand...
Click to collapse
Not quite understanding what you want to do with this.
You have access to recovery, why not simply flash the rom and boot.img again?

Its a JB rom, it's possible you have an mddi panel have a quick read of this thread and see if it applies to you http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge
"Happiness is good health and a bad memory."
- Ingrid Bergman (1917-1982)

oddoneout said:
Not quite understanding what you want to do with this.
You have access to recovery, why not simply flash the rom and boot.img again?
Click to expand...
Click to collapse
Because I did it many times ... and still stuck. Moreover, I try to flash another ROM with the same behaviour

jugg1es said:
Its a JB rom, it's possible you have an mddi panel have a quick read of this thread and see if it applies to you http://forum.xda-developers.com/showthread.php?t=1943524
[/I]
Click to expand...
Click to collapse
Uhmmmm ... interesting. I'll check about that.
Thanks
sbk

jugg1es said:
Its a JB rom, it's possible you have an mddi panel have a quick read of this thread and see if it applies to you http://forum.xda-developers.com/showthread.php?t=1943524
) [/I]
Click to expand...
Click to collapse
Got it! You've right.
In this device I've installed a Hitachi MDDI panel.
Unfortunately the procedure to change the kernel it seem that did not work with flinnny's ROM.
I have to find a new compatible rom.
Tnx
Sbk

I've installed this ROM CyanogenMod 10 Experimental Alpha for HTC Desire S by nk111 with 82n kernel
and all works fine :laugh:
sbk

Related

[Q] Help!! Strange problem with desire s

Hi all. I'm new in the forum and i found something really strange with my phone. my desire s is unlocked from htcdev and rooted using super one click.
The strange thing is that i'm not able to flash something like cwm or a boot.img from the phone itself. i can just flash them from pc using fastboot method everytime. i've installed several roms but i can't boot them up because of this problem. Also i tried to flash cwm from rom manager and it said that cwm is installed successfully; but i couldn't get in the cwm.
Now i need some help with this problem. How can i flash my phone without fastboot method? Thanks so much!!
Edmerf said:
Hi all. I'm new in the forum and i found something really strange with my phone. my desire s is unlocked from htcdev and rooted using super one click.
The strange thing is that i'm not able to flash something like cwm or a boot.img from the phone itself. i can just flash them from pc using fastboot method everytime. i've installed several roms but i can't boot them up because of this problem. Also i tried to flash cwm from rom manager and it said that cwm is installed successfully; but i couldn't get in the cwm.
Now i need some help with this problem. How can i flash my phone without fastboot method? Thanks so much!!
Click to expand...
Click to collapse
Do not unlock with HTCDev.com
Downgrade and S-OFF instead - there are 2 guides in the Index
thanks. but is it normal that i'm not being able to flash boot.img from the phone itself with using htcdev method? sorry for being a noob.
Edmerf said:
thanks. but is it normal that i'm not being able to flash boot.img from the phone itself with using htcdev method? sorry for being a noob.
Click to expand...
Click to collapse
The HTCDev unlocks the system, boot (kernel) and recovery partitions for custom modifications. S-ON means that your Radio and Bootloader (hboot) partitions remain locked/secured. But when in recovery (when flashing a ROM) or OS mode the kernel partition remain locked. Boot (kernel) is unlocked only when the phone is in bootloader. Then you can use the fastboot flash command to write on it.
This is wise IMO, because is preventing the people that are not familiar with the details to play. So only the ones that know what means partition, kernel, security flag, etc. to use this method. Or the ones that are reading this forum
ok. i want to ask one more question: Will something happen in the future if i flash boot.imgs and any other thing using the fastboot method?
HI
amidabuddha said:
The HTCDev unlocks the system, boot (kernel) and recovery partitions for custom modifications. S-ON means that your Radio and Bootloader (hboot) partitions remain locked/secured. But when in recovery (when flashing a ROM) or OS mode the kernel partition remain locked. Boot (kernel) is unlocked only when the phone is in bootloader. Then you can use the fastboot flash command to write on it.
This is wise IMO, because is preventing the people that are not familiar with the details to play. So only the ones that know what means partition, kernel, security flag, etc. to use this method. Or the ones that are reading this forum
Click to expand...
Click to collapse
Copy and paste is a good friend ;-)
Sent from my Desire S using XDA App
eyahl said:
HI
Copy and paste is a good friend ;-)
Sent from my Desire S using XDA App
Click to expand...
Click to collapse
If you search through my posts you will find out that I had repeated this hundreds of times to deferent users in different threads. Why typing the same over and over again...
amidabuddha said:
If you search through my posts you will find out that I had repeated this hundreds of times to deferent users in different threads. Why typing the same over and over again...
Click to expand...
Click to collapse
yea, thats exactly my point of view too.
didnt recognize you have used it that often already

Hangs at bootloader or reboots to recovery

I rooted my phone yesterday and installed a rom.
I followed all steps clearly but once i flashed the rom and i restart, it hangs at htc logo screen for 1 minute and then reboots and shows htc logo screen again and goes directly to recovery. I am unable to see any rom interface. I tried two different roms and same result. Now tried to restore back to my sense ui and still it does not work. Help please
A wild guess: you used HTCDev unlock method and didn't flash kernel manually, even though it's written in zillion places to do so.
Jack_R1 said:
A wild guess: you used HTCDev unlock method and didn't flash kernel manually, even though it's written in zillion places to do so.
Click to expand...
Click to collapse
yes what do i do now
Read the guides that say how to flash kernel manually.
Jack_R1 said:
Read the guides that say how to flash kernel manually.
Click to expand...
Click to collapse
Thank you i fixed it with guides to flash manually
Fastboot flash boot boot.img
Edit: too late
Swyped from my DesireS
mrbadguy5 said:
Thank you i fixed it with guides to flash manually
Click to expand...
Click to collapse
Good that you learned how do do it yourself..
Sent from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!
I got that problem here, and it doesn't help flashing the boot.img manually.
Restore stock ROM using RUU (and use misc_version script to downgrade the main version first). If you unlocked using HTCDev, you'll need to relock first. Read the guides, they're aplenty.
If it won't help or will write Fail-PU during restore - your phone is done.

Help needed!!

I have hitachi screen panel n I flashed xperia jellybean then gaps and then 82n kernel..the phone gets past htc logo but stucks in a black screen n only capacitive buttons light up and nothing occurs...plz help mee!!
pknagi said:
I have hitachi screen panel n I flashed xperia jellybean then gaps and then 82n kernel..the phone gets past htc logo but stucks in a black screen n only capacitive buttons light up and nothing occurs...plz help mee!!
Click to expand...
Click to collapse
1.reboot to recovery again,
easiest via ADB on pc
2.restore the backup of your previous rom
you've surely made before flashing
3.or any sense rom
4.tell me why-knowing about your panel-
you have flashed the rom without obtaining
some information about possible complications
asgardr said:
1.reboot to recovery again,
easiest via ADB on pc
2.restore the backup of your previous rom
you've surely made before flashing
3.or any sense rom
4.tell me why-knowing about your panel-
you have flashed the rom without obtaining
some information about possible complications
Click to expand...
Click to collapse
What complications...just have to flash the kernel n rest everything is same?
pknagi said:
What complications...just have to flash the kernel n rest everything is same?
Click to expand...
Click to collapse
Well, not every aosp based rom,cooperates nicely
with the panel your device is having...
Check general section for non sony panel thread,
of course, there might be another reason your device does not start,
and that would be:
when it is s- on, boot.img from that rom
needs to be flashed separately, because it has not been flashed from recovery-with the rest,
as some partitions on an s-on device are only reachable via fastboot- in bootloader...
but i suppose you know that,..
There is one or two, or sometimes even more such threads a day,
info about flashing boot img on an s-on device, is dominating
Q&A section for a long time
asgardr said:
Well, not every aosp based rom,cooperates nicely
with the panel your device is having...
Check general section for non sony panel thread,
of course, there might be another reason your device does not start,
and that would be:
when it is s- on, boot.img from that rom
needs to be flashed separately, because it has not been flashed from recovery-with the rest,
as some partitions on an s-on device are only reachable via fastboot- in bootloader...
but i suppose you know that,..
There is one or two, or sometimes even more such threads a day,
info about flashing boot img on an s-on device, is dominating
Q&A section for a long time
Click to expand...
Click to collapse
No I have s-off with revolutionary hboot

[Q] Kernel and rom problem

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!

[Q] Help with ROM needed (maybe trivial ...)

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

Categories

Resources