Database Info

[Q] Bootlooping and cannot open recovery

hi all,
Firstly apologies if this is covered somewhere but for the life of me I cannot get to the bottom of this. I have spent 2 weeks on and off trying to get a solution but my Sensation is still boot looping.
The problem occurred when I turned on the camera but was faced with a blank screen. I could return to home screen but the camera would not work each time I launched. So I rebooted the device but then I was stuck in this boot loop.
Device info
HTC Sensation S-OFF RL
HBOOT-1.27.0000
RADIO-11.21.3504.13_2
I was running Insert Coin 2.3.5 ROM for some time without issue
I was hoping I could just do a superwipe and flash a new ROM
FAIL - each time I boot into CWM and select Recovery, it just goes back to bootloop.
I selected Factory Rest from CWM menu
FAIL - it just goes into bootloop
Also cannot use ADB as the device will not connect to the PC. Im using a card reader to put files on the SD card but have not being successful resolving the issue.
Tried an SD card from a stock Sensation, no difference. Booting with no SIM, not working.
Most Bootloop fix's seem to involve super wipes / flashing new ROMs but because my Recovery goes into the bootloop I dont have this option. I wish it was so easy.
Can anybody offer an other ideas.
Thanks for you patience, I am not much of a modder or Android expert. I had just flashed a ROM many months ago to help improve battery life and I was happy with that.

Have you tried re-installing your recovery throught the bootloader?

try different recovery (4EXT) or reinstall recovery again

thanks guys.
I found these flashable recovery files. Both CWM and 4EXT. I have tried both zips and ran the update in HBOOT but am still booting in CWM and if I select RECOVERY is goes too bootloop again.
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
I think I might just give up and drop the phone into a phone repair shop and let them try it.

Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2

Try this pg58img (it helped me)http://www.wuala.com/LuckyThirteen/Elegancia/Official RUU Sensation/ it will update your sensation to ICS, (you will maintain s-off)

Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.

GROGG88 said:
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.

markmcie said:
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
Click to expand...
Click to collapse
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem

If you can boot normally into ICS and you are rooted, then get the 4Ext app or the ROM Manager app and flash the recovery through one of those.

dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
Ill do this a few times over the weekend and hopefully I can get up and running again. I will let you know how I get on.
Thanks

markmcie said:
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
Click to expand...
Click to collapse
Well I'd have to agree with dublinz then...
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse

so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now

markmcie said:
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
Click to expand...
Click to collapse
Flashing the ICS PG58IMG.zip doesn't replace the recovery.
Fix recovery first. Use stock recovery. When you get that working, change to "simple" cwm recovery.

thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.

markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
before flashing stock recovery...can you try this first
get this recovery image
and flash the recovery via fastboot
steps:
1.go to fastboot in your device and connect it to your pc (after this device should read fastboot usb)
2.get the adb/fastboot setup ready guide here
3.go to your adb folder and place the downloaded recovery.img there
4.type fastboot devices (it should show your device serial number)
5.now to flash type
fastboot flash recovery recovery.img
this should do...if it didnt work then let me know ASAP...then we'll think of other solutions

markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
EddyOS has them , search that. I'll try to locate them.
I remembered incorrectly, it was only CWM and 4EXt
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
But you can find stock recovery in this forum:
http://www.htcsensationforum.com/ht...ota-update-on-rooted-phone/msg76452/#msg76452
scroll down a little bit ...

markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
Here you go:
http://db.tt/kvTvDblW
It should include all MID's and most CID's that I know of...

GROGG88 said:
Here you go:
http://db.tt/3YSslZVg
It should include all MID's and most CID's that I know of...
Click to expand...
Click to collapse
Link is doing a 404 ...

SanityPreservation said:
Link is doing a 404 ...
Click to expand...
Click to collapse
Fixed...

[Q] Flashing Stock from CMB

I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I

xnosajx said:
I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I
Click to expand...
Click to collapse
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Edit: http://droidbasement.com/db-blog/?p=3210
Sent from my DROID4 using Tapatalk

berndblb said:
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.

xnosajx said:
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.
Click to expand...
Click to collapse
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason

berndblb said:
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason
Click to expand...
Click to collapse
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.

xnosajx said:
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.
Click to expand...
Click to collapse
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....

Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.

berndblb said:
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....
Click to expand...
Click to collapse
I should have been more specific. Before I attempt the install of the recovery, I get this when I do fast boot devices:
Code:
C:\>fastboot devices
###d2bbce61c### fastboot
The #'s are actual numbers.
After I try to install the recovery image here is the output:
Code:
C:\>fastboot flash recovey recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 3.588s]
writing 'recovery'...
OKAY [ 3.182s]
finished. total time: 6.770s
C:\>fastboot devices
???????????? fastboot
c:\>
And the green flashing (around the icons) stops and hangs.
I have to hold down power to reboot after that.

sbdags said:
Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.
Click to expand...
Click to collapse
I'm an idiot...thanks. I'll try the CROMi-X 5.3

HTC one XL evita deleted restore via factory reset

I was running a rom on my phone working fine until the new update came and I tried to install which sent me to my recovery page (TWRP v2.5) I then factory reset hoping this would work and managed to delete my recoveries and now whenever i restart my phone i either get the message of no os installed or when i install a rom and it actually works i get stuck in a boot loop. im not sure if it is the rom or not (KickDroidXL v5) any help would be appreciated, Thankyou

Your problem is your recovery version, TWRP 2.5 is very buggy and has major issues with wiping and with flashing. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash the ROM again and you should be fine.
Sent from my Evita

thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy

Guested said:
thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy
Click to expand...
Click to collapse
Yeah, you should get s-off either here or here. Then you won't have to worry about flashing the boot.img anymore. You're gonna need s-off to upgrade your firmware anyway, otherwise you're gonna suffer signal losses and random reboots.

so trying to use s-off at the moment and i am not able to boot into recovery (just goes to htc startup screen and phone turns on) i then tried usb debugging where i got the response, needs to be formatted, tried that and said it was impossible as i didnt have any permissions! any ideas?

Neither of the s-off processes need to boot into recovery, what do by mean by that?
Sent from my Evita

so i tried the rum runner method which got stuck when on test 2 it tells me it must ferment longer, i wait in this process for awhile and it attempts to start my phone however it doesnt start up only a black screen with no led (i assume the phone is off) the only way to start is by holding down the power and waiting for the 15 flashes from the buttons then putting it into bootloader, from there i chose recovery and it starts normally without entering the twrp screen.
Test 2: Booting device
Waiting for ADB (19/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit

Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita

timmaaa said:
Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita
Click to expand...
Click to collapse
no CID, i tried using http://androidforums.com/sensation-4g-all-things-root/636482-guide-how-supercid.html
didnt work came up with an error of too many links after getting to this stage -change CID
fastboot oem writecid 11111111 (eight ones)

okay so i assume it has something to do with the rom, i flashed twrp 2.6 back and recovery works fine! any suggestions on a battery low and stable rom?

Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita

timmaaa said:
Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
Click to expand...
Click to collapse
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected

Guested said:
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected
Click to expand...
Click to collapse
You need to get adb/fastboot and your drivers sorted out. Try using an app called pdanet+ from the Play Store, you download it to your phone and then another component on your PC. When you open the PC component it'll install drivers, it's what got everything working for me.
Sent from my Evita

[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

HTC ONE SV STUCK AT BLACKSCREEN. help please!

Hi,
I'm having problems with my HTC one SV. it powers on then it will show "htc quietly brilliance logo" and after that it shows black screen then stuck on it. i had this problem before so I remove the battery then power it on solves the problem but lately it does not work anymore lets say it's like 1/100 before it goes thourgh. i really dont know what to do tried searching for solutions just cant get it. I'm kinda newbie on terms so if anyone can help me I'm very thankful.
Thank you in Advance!

Seems like a common problem for many HTC One SV's.
Take a look in the Q&A section, there should be many threads, where i described what to do. As long as it's no US carrier phone, then things are different.
Basically:
- unlock your phone with htcdev.com (all data is lost)
- flash TWRP recovery with fastboot
- flash a rom for your model

old.splatterhand said:
Seems like a common problem for many HTC One SV's.
Take a look in the Q&A section, there should be many threads, where i described what to do. As long as it's no US carrier phone, then things are different.
Basically:
- unlock your phone with htcdev.com (all data is lost)
- flash TWRP recovery with fastboot
- flash a rom for your model
Click to expand...
Click to collapse
my phone is from middle east. i assume that its all in htcdev.com? like step by step on what to do? honestly i really don't know how to flash TWRP, flash a rom and etc. I'm just having a hard time learning maybe because it's 1st time for to do it plus I'm not yet familiar with it.

You needto learn, how to use fastboot cmd, otherwise i guess your phone is lost.
But its not so hard, if you can use a computer
At htcdev you can get the basic fastboot files you need.
Try to read and follow the unlock guide, then we see how far we come.

old.splatterhand said:
You needto learn, how to use fastboot cmd, otherwise i guess your phone is lost.
But its not so hard, if you can use a computer
At htcdev you can get the basic fastboot files you need.
Try to read and follow the unlock guide, then we see how far we come.
Click to expand...
Click to collapse
Hi,
im having hard time. tried to follow the steps on htcdev but im having error. here is the message.
"the program can't start because adbwinapi.dll is missing from your computer. Try reinstalling the program to fix the problem.
any idea on how fix this?

phuge17 said:
adbwinapi.dll is missing
any idea on how fix this?
Click to expand...
Click to collapse
This dll should be in the package that you have downloaded from htcdev.

old.splatterhand said:
This dll should be in the package that you have downloaded from htcdev.
Click to expand...
Click to collapse
Hi,
I managed to unlock my phone , TWRP and all that. i also downloaded your "[ROM]Stock odexed Android 4.2.2 Sense 5 " for k2_ul. i followed your instruction on how to install by the way mine is S-on so flash with fastboot (fastboot flash boot boot.img) am I correct? i see some okay it was kinda fast so i feel weird i thought the installing will take a minute or so because its almost 1gig file download. anyway the only thing i did not do is this part "Don't forget to flash Superuser file (look into my index thread) if you want root!" actually i really dont know what you mean by that sorry. my phone still not yet booting still stuck at blackscreen.
UPDATE** phone is just restarting over over again from htc quietly brilliant >> power off >> htc quietly brilliant >> power off.

phuge17 said:
Hi,
I managed to unlock my phone , TWRP and all that. i also downloaded your "[ROM]Stock odexed Android 4.2.2 Sense 5 " for k2_ul. i followed your instruction on how to install by the way mine is S-on so flash with fastboot (fastboot flash boot boot.img) am I correct? i see some okay it was kinda fast so i feel weird i thought the installing will take a minute or so because its almost 1gig file download. anyway the only thing i did not do is this part "Don't forget to flash Superuser file (look into my index thread) if you want root!" actually i really dont know what you mean by that sorry. my phone still not yet booting still stuck at blackscreen.
UPDATE** phone is just restarting over over again from htc quietly brilliant >> power off >> htc quietly brilliant >> power off.
Click to expand...
Click to collapse
Why install an odex 4.2.2 Rom when your 4.2.2 Rom is odex by stock?

phuge17 said:
Hi,
I managed to unlock my phone , TWRP and all that. i also downloaded your "[ROM]Stock odexed Android 4.2.2 Sense 5 " for k2_ul. i followed your instruction on how to install by the way mine is S-on so flash with fastboot (fastboot flash boot boot.img) am I correct? i see some okay it was kinda fast so i feel weird i thought the installing will take a minute or so because its almost 1gig file download. anyway the only thing i did not do is this part "Don't forget to flash Superuser file (look into my index thread) if you want root!" actually i really dont know what you mean by that sorry. my phone still not yet booting still stuck at blackscreen.
UPDATE** phone is just restarting over over again from htc quietly brilliant >> power off >> htc quietly brilliant >> power off.
Click to expand...
Click to collapse
Have you done a wipe in recovery before flashing the new rom?
SHM said:
Why install an odex 4.2.2 Rom when your 4.2.2 Rom is odex by stock?
Click to expand...
Click to collapse
Usually it it is.

old.splatterhand said:
Have you done a wipe in recovery before flashing the new rom?
Usually it it is.
Click to expand...
Click to collapse
sorry it took me weeks before i reply. anyway i did wipe the phone. are there any like reset command while on fast boot or something so that i can start from the beginning? actually im a bit lost.

Boot to recovery -> Wipe menu -> Advanced Wipe and wipe System, data, cache, dalvik cache.
Then go to Install and flash the rom for your model.
Then boot to fastboot and flash the boot.img of the rom with fastboot cmd fastboot flash boot boot.img
If that does not bring your phone back to life, something else is wrong.