Related
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...
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium
subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.
wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...
Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium
I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?
Unlocked
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
eMMc-boot
I installed the new viper 1.41 rom and then tried to flash one of the kernals. It said it was all done but then now I'm stuck in a continuous bootloop.
I can boot into recovery and have tried to flash another rom already but it stays in bootloop, also tried flashing different kernal and still doesn't work.
Tried to start from the beginning using cmd etc (adb etc) but cmd can't find a device when using the command adb devices.
What should I do? Please help !!1
mattyon9 said:
Unlocked
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
eMMc-boot
I installed the new viper 1.41 rom and then tried to flash one of the kernals. It said it was all done but then now I'm stuck in a continuous bootloop.
I can boot into recovery and have tried to flash another rom already but it stays in bootloop, also tried flashing different kernal and still doesn't work.
Tried to start from the beginning using cmd etc (adb etc) but cmd can't find a device when using the command adb devices.
What should I do? Please help !!1
Click to expand...
Click to collapse
Hi,
Do you have 4EXT recovery installed?
If so ,enable smartflash.
malybru said:
Hi,
Do you have 4EXT recovery installed?
If so ,enable smartflash.
Click to expand...
Click to collapse
"Download 4EXT recovery (1.0.0.5!)" I have this on installed and smartflash is already enabled via recovery.
mattyon9 said:
"Download 4EXT recovery (1.0.0.5!)" I have this on installed and smartflash is already enabled via recovery.
Click to expand...
Click to collapse
Hi,
Unless you have it permanently enabled,you must enable it just before you flash anything.
malybru said:
Hi,
Unless you have it permanently enabled,you must enable it just before you flash anything.
Click to expand...
Click to collapse
Again I've already set smartflash before every flashing of roms. Just this time I'm stuck in a bootloop and can't do nothing about it?
mattyon9 said:
Again I've already set smartflash before every flashing of roms. Just this time I'm stuck in a bootloop and can't do nothing about it?
Click to expand...
Click to collapse
Hi,
Have you got a nandroid you can restore?
malybru said:
Hi,
Have you got a nandroid you can restore?
Click to expand...
Click to collapse
Unfortunately not
Also stuck in the same boat
Hi!
I too am stuck in a bootloop trying to flash CM10.
The problem is I thought I needed CWM to flash the firmware and am now stuck with the CM10 logo when I try and reboot the phone.
Doing more reading 4ext seems to be required to fully wipe the phone rather than CWM
I've found PG58IMG.zip which is recognised when I boot into recovery, but not apparently installed. Perhaps not surprisingly CWM won't install the zip.
Does anyone have any ideas what I can do to the installation?
Thanks
Kevin
mattyon9 said:
Unfortunately not
Click to expand...
Click to collapse
Hi,
You might therefore consider a RUU
Look HERE
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
StockportGerbil said:
Hi!
I too am stuck in a bootloop trying to flash CM10.
The problem is I thought I needed CWM to flash the firmware and am now stuck with the CM10 logo when I try and reboot the phone.
Doing more reading 4ext seems to be required to fully wipe the phone rather than CWM
I've found PG58IMG.zip which is recognised when I boot into recovery, but not apparently installed. Perhaps not surprisingly CWM won't install the zip.
Does anyone have any ideas what I can do to the installation?
Thanks
Kevin
Click to expand...
Click to collapse
Hi,
Firmware is not dependent on a particular recovery.
4 EXT is a better choice ,because it gives you more options.
What PG58IMG.zip were you trying to flash?
S-on/off?
hboot?
radio?
ROM?
Kernel?
etc
etc
etc
More information is required...
Getting past the bootloop
After my plea for help yesterday regarding the bootloop after I had tried to update my HTC Sensation, I eventually found the answer to my problem. Also the response I had yesterday raised some questions which I note at the end
.
Firstly I was trying to update my stock firmware HTC Sensation to CM10; the build I was using was the AOKP / Kang build by bruce2728 dated 16th November as that seemed to be being actively maintained and the functionality I required was reportedly working fine. I read the rather cursory instructions and given I’ve updated several Android tablets before I thought this will be easy. FAIL!
I’ll document elsewhere the process I followed, however the problem I had was when I tried to apply the CM10 image using CWM. It seemed to write successfully but when I came to reboot the phone it was stuck in a boot loop with the cyanogenmod logo stuck on the screen until I pulled the battery out. I couldn’t install 4ext using the play store app as I’d trashed the android installation.
I eventually replace CWM with 4ext by downloading the correct recovery image to my PC (from the third post of http://forum.xda-developers.com/showthread.php?t=1666401, note that the recovery image is different for different phones and possibly operator.)
I then started the phone in bootloader (noting the phone was S-ON), plugged in the USB connection and pressed the power button, so fastboot was selected and then Fastboot usb was displayed on the phone.
From a command prompt on the PC after changing to the directory where I had placed fastboot and adb I typed “fastboot recovery recovery.img” and this replaced CWM with 4ext.
After rebooting the phone and getting back into the bootloader, I selected recovery. This time 4ext started. Before writing the new Android image I wiped user data and (I think it was in tools once you scrolled to the bottom) selected “enable 4ext superflash” before flashing the ROM and Google Apps and then successfully rebooting the phone. For reference the phone took less than 5 minutes to start up.
I now think my problem was trying to flash the ROM with S-ON and not using 4-ext superflash. Oh well
Following on from the response from malybru (Thanks)
Does writing a new rom change the radio? I’d understood it remained the same unless you made special efforts to change it and you were likely to wipe out the phone?
Thanks again
Kevin
maybe i am wrong but radio can be changed only when you are flashing different firmware and to do that you have to be S-OFF
StockportGerbil said:
After my plea for help yesterday regarding the bootloop after I had tried to update my HTC Sensation, I eventually found the answer to my problem. Also the response I had yesterday raised some questions which I note at the end
.
Firstly I was trying to update my stock firmware HTC Sensation to CM10; the build I was using was the AOKP / Kang build by bruce2728 dated 16th November as that seemed to be being actively maintained and the functionality I required was reportedly working fine. I read the rather cursory instructions and given I’ve updated several Android tablets before I thought this will be easy. FAIL!
I’ll document elsewhere the process I followed, however the problem I had was when I tried to apply the CM10 image using CWM. It seemed to write successfully but when I came to reboot the phone it was stuck in a boot loop with the cyanogenmod logo stuck on the screen until I pulled the battery out. I couldn’t install 4ext using the play store app as I’d trashed the android installation.
I eventually replace CWM with 4ext by downloading the correct recovery image to my PC (from the third post of http://forum.xda-developers.com/showthread.php?t=1666401, note that the recovery image is different for different phones and possibly operator.)
I then started the phone in bootloader (noting the phone was S-ON), plugged in the USB connection and pressed the power button, so fastboot was selected and then Fastboot usb was displayed on the phone.
From a command prompt on the PC after changing to the directory where I had placed fastboot and adb I typed “fastboot recovery recovery.img” and this replaced CWM with 4ext.
After rebooting the phone and getting back into the bootloader, I selected recovery. This time 4ext started. Before writing the new Android image I wiped user data and (I think it was in tools once you scrolled to the bottom) selected “enable 4ext superflash” before flashing the ROM and Google Apps and then successfully rebooting the phone. For reference the phone took less than 5 minutes to start up.
I now think my problem was trying to flash the ROM with S-ON and not using 4-ext superflash. Oh well
Following on from the response from malybru (Thanks)
Does writing a new rom change the radio? I’d understood it remained the same unless you made special efforts to change it and you were likely to wipe out the phone?
Thanks again
Kevin
Click to expand...
Click to collapse
Hi,
Flashing a ROM does NOT change the radio.
In fact,you cannot change the radio or firmware if you are s-on.
"Smartflash" is what I would have suggested if you had 4 EXT recovery and s-on.
It is all well documented HERE
malybru said:
Hi,
Flashing a ROM does NOT change the radio.
In fact,you cannot change the radio or firmware if you are s-on.
"Smartflash" is what I would have suggested if you had 4 EXT recovery and s-on.
It is all well documented HERE
Click to expand...
Click to collapse
Hi!
I think I read everything except that guide yesterday - thanks it is interesting.
Regards
Kevin
Hi, everything messed up from using the stupid TWRP 2.6.0.0 .... I was going to flash a custom rom , but it didn't let me, so I did a little research that I need 2.3.3.0 in order to instal any custom rom.So I tried to switch to 2.3.3.0 but it didn't let me... after that I tried to push stock recovery and now i'm stuck at the white HTC Entering Recovery ( pink letters) screen, ( The recovery just doesn't load) ... I just want to finish with this , and go back to my stock htc rom with not roots or anything.. im tired of this seriously.....
When I try to run RUU I get stuck at the Black HTC Letters screen , the the setup stops and says that it will try to repair my phone, sadly with no result every time.. I think that I don't have any OS on my phone right now, because when RUU starts it shows :
Change image version from : ( blank space)
To: ..... bla bla bla , ( the version of the ruu) ...
I have no problems with entering fastboot and unlocking/relocking my Hboot.
Any help about restoringmy phone will be appreciated . Thanks , I'm online all the time so if I get any responses I'll answer quick.
P.S. I can't mount my usb storage from anywhere, and it doesn't show up on my PC when i connect the usb
looperman said:
Hi, everything messed up from using the stupid TWRP 2.6.0.0 .... I was going to flash a custom rom , but it didn........................
P.S. I can't mount my usb storage from anywhere, and it doesn't show up on my PC when i connect the usb
Click to expand...
Click to collapse
Don't lose hope, don't panic.
Tell me which RUU did you use?
Also, what is your CID?
How did you flash your recovery ?
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Don't lose hope, don't panic.
Tell me which RUU did you use?
Also, what is your CID?
How did you flash your recovery ?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
looperman said:
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Rad io_16.21.20.02U_16.09.20.11_M2_release_286571_sign ed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_ 1.06s.50.02.27_2_10.08.50.04L__release_271119_sign ed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
Click to expand...
Click to collapse
If you downloaded RUUs from androidruu, then it's a case of bad RUU.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
If you downloaded RUUs from androidruu, then it's a case of bad RUU.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well what am I supposed to do ?
looperman said:
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
Click to expand...
Click to collapse
Okay, just now I noticed. You used two Different RUUs for two different versions.
The 1st one is for S3/C2 version, the 2nd one is for S4 version.
Use This Thread to download RUU's only for your version (S4 or S3 whichever you have got). In your case, it does matter which RUU you use.
If you need any help further just ask away.
the thing is that the RUU doesn't get to the process of installing , and I have used those RUU's before....
I need some solution the get to a working recovery and instal some kind of OS because the last time I could get in my recovery it said that I don't have any OS installed...
looperman said:
the thing is that the RUU doesn't get to the process of installing , and I have used those RUU's before....
I need some solution the get to a working recovery and instal some kind of OS because the last time I could get in my recovery it said that I don't have any OS installed...
Click to expand...
Click to collapse
okay you gonna need fastboot for this. What I have been successful with is:
1. Download an RUU (VERSION SPECIFIC!).
2. Go into Bootloader -> Then select FASTBOOT
3. Connect your Phone to PC. It should say Fastboot - USB mode.
4. Run the RUU, it will get you through all the steps.
khan.orak said:
okay you gonna need fastboot for this. What I have been successful with is:
1. Download an RUU (VERSION SPECIFIC!).
2. Go into Bootloader -> Then select FASTBOOT
3. Connect your Phone to PC. It should say Fastboot - USB mode.
4. Run the RUU, it will get you through all the steps.
Click to expand...
Click to collapse
doesn't work as I've told you , it happens with every RUU ... I get the Black screen with white HTC letters...
I think that what RUU does is : it updates the version my software I think it just doesn't place a new software right away( just an update), but as TWRP said I don't have OS installed...
can anyone help me ?
looperman said:
doesn't work as I've told you , it happens with every RUU ... I get the Black screen with white HTC letters...
I think that what RUU does is : it updates the version my software I think it just doesn't place a new software right away( just an update), but as TWRP said I don't have OS installed...
Click to expand...
Click to collapse
Man you're making this difficult. The more I want to help you, the more you become hasty.
RUU doesn't do what you think. It puts New software, updates firmware (hboot, radio, RECOVERY), so yes it is basically a one-stop solution.
Please calm down as panicking won't help.
Tell me your One S version (S3/S4) at least? so that we can move forward in right direction. and also your CID
Tell me what recoveries and RUU you tried. and what errors do you get while you run them.
EDIT: Thanks to @tivofool I forgot to mention that you have to RELOCK your bootloader before running RUU
I'm with S3
I wrote the 2 RUU's I tried to use,
before that i tried TWRP 2.5.0.0,2.3.0.0.,2.6 and finally I flashed factory stock recovery that's it and both my carrier and bl are unlocked
P.S. : Yeah i knew about the relocking but still stuck on black screen with white HTC Letters
looperman said:
I'm with S3
I wrote the 2 RUU's I tried to use,
before that i tried TWRP 2.5.0.0,2.3.0.0.,2.6 and finally I flashed factory stock recovery that's it and both my carrier and bl are unlocked
P.S. : Yeah i knew about the relocking but still stuck on black screen with white HTC Letters
Click to expand...
Click to collapse
Black Screen with HTC is the oem update screen.
Okay do this please and we'll try to see if there's a problem with the HBOOT. Give me this info and We'll reflash HBOOT.
Go to fastboot and connect your phone to PC.
Enter this command from your PC:
Code:
fastboot getvar all
post results here (MINUS IMEI AND SERIAL #)
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
looperman said:
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
Click to expand...
Click to collapse
That was fast.
I am using Viper ROM and it's very good. Customization and speed.
For a better battery life, BULLETPROOF KERNEL.
Edit: how did you get it to work by the way.
Viper rom is for s4 only isn't it ?
looperman said:
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
Click to expand...
Click to collapse
Make sure you flash a S3 Rom (you mentioned having a s3 right?)
Sent from my HTC VLE_U using Tapatalk 2
looperman said:
Viper rom is for s4 only isn't it ?
Click to expand...
Click to collapse
Oh yes sorry.
okay, so ... I'm going to explane everything I did, I hope I'll help some other people too.
I flashed TWRP from One_S_All-In-One_Kit_v4.0 but without luck, then i flash the factory stock recovery, still the phone was letting me into any of these two recoveries, then i decided reflash the same TWRP again and it worked,
First I couldn't mount the storage from the recovery , but it was still showing in "My Computer" , I had only one option and it was to Format the Storage. So I did.. then copied this rom with gapps on it ---> http://forum.xda-developers.com/showthread.php?t=2164406
Fully wiped --> Flash Rom , then Flash Gapps, ---> then I booted in fastboot to boot from CMD the "boot.img" with "fastboot flash boot boot.img" from the Pacman Rom and then I Rebooted the HTC and Done
Huge thanks to @khan.orak
I hope I helped someone with the same ****tyass problem.
looperman said:
okay, so ... I'm going to explane everything I did, I hope I'll help some other people too.
I flashed TWRP from One_S_All-In-One_Kit_v4.0 but without luck, then i flash the factory stock recovery, still the phone was letting me into any of these two recoveries, then i decided reflash the same TWRP again and it worked,
First I couldn't mount the storage from the recovery , but it was still showing in "My Computer" , I had only one option and it was to Format the Storage. So I did.. then copied this rom with gapps on it ---> http://forum.xda-developers.com/showthread.php?t=2164406
Fully wiped --> Flash Rom , then Flash Gapps, ---> then I booted in fastboot to boot from CMD the "boot.img" with "fastboot flash boot boot.img" from the Pacman Rom and then I Rebooted the HTC and Done
Huge thanks to @khan.orak
I hope I helped someone with the same ****tyass problem.
Click to expand...
Click to collapse
Glad it worked for you buddy.
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