I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4
LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi
Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.
It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...
LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.
Related
Hey, first time posting something on this forum but to all devs reading this thanks alot for everything you do!
And Thanks to anyone who can help me!
Now my problem is as following,
My stock rom is 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.exe
I followed this guide to unlock the bootloader and get root http://forum.xda-developers.com/showthread.php?t=1583427
I used this recovery "Official CWM of koush (HTC One S)" (both toutch and regular has been tested)
Then i downloaded MIUI at first and flashed that(full wipe), it installed fine so i rebooted.
Once i got passed the htc boot screen everything went black, no boot animation.
After that i tested some more Roms, ParanoidAndroid and AOKP Milestone 6.
The exact same thing happend with and exeption for AOKP where the toch keys turned on.
I also noticed it showed up as a removable device in windows from time to time when plugged in (dont if that helps).
After that i restored my one s to stock and then did all the steps again but that yeilded the same results.
I have no idea what the problem is and im hoping its something that has an easy fix and im just to dumb to see it.
If you need any more info just ask, and again thanks for any help!
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Daikar said:
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Click to expand...
Click to collapse
just use twrp and problem solved.
CWM IMO sucks in comparison. Not to mention the level of support with TWRP is so far and above ANYTHING you will get with CWM.
To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.
What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".
Its not bricked.If u can enter recovery
Sent from my HTC sensation
Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse
DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309
impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.
You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4
Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")
My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
AKAndrew41 said:
HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
Click to expand...
Click to collapse
install latest 4ext from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
then from 4ext format all partitions except sdcard
enable smartflash( because you are on S-ON)
flash the custom rom
note: enable smartflash exactly before flashing the rom
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
AKAndrew41 said:
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
Click to expand...
Click to collapse
see this guide
http://forum.xda-developers.com/showthread.php?t=2751187