Hi to all, I'm having an issue with my sensation xe.
I'm using vipers 1.6.3 with bricked kernel and today I would like to try Pyd-x kernel. After install it, the phone rebooted and gone into boot loop.
Without trouble I tryed to restore my nandroid backup, already tryed another two times with full success, but now nothing change.
I'm still in boot loop.
The only things I'm able to do is enter in hboot and into 4ext recovery.
I already tryed to flash another kernel, another rom, but nothing change....
could somebody help me please?
Many thanks
Wooler
Wooler said:
Hi to all, I'm having an issue with my sensation xe.
I'm using vipers 1.6.3 with bricked kernel and today I would like to try Pyd-x kernel. After install it, the phone rebooted and gone into boot loop.
Without trouble I tryed to restore my nandroid backup, already tryed another two times with full success, but now nothing change.
I'm still in boot loop.
The only things I'm able to do is enter in hboot and into 4ext recovery.
I already tryed to flash another kernel, another rom, but nothing change....
could somebody help me please?
Many thanks
Wooler
Click to expand...
Click to collapse
Hi,
If you run a RUU,it will reset your partitions,and may help you out of this situation.
Look HERE
malybru said:
Hi,
If you run a RUU,it will reset your partitions,and may help you out of this situation.
Look HERE
Click to expand...
Click to collapse
That's seems a bit too hassling...
Wooler, the problem you're having is because of 4ext and smartflash/S-ON. In order to fix this, you need to flash the boot.img from ViperS using fastboot. 4ext requires a working boot partition in order to flash kernels with S-ON, so it's impossible to fix the problem by using 4ext (i.e. as you've already realized, no amount of flashing kernels/ROMs will fix this). I've attached the boot.img file from ViperS 1.6.3 to the bottom of this post; download it and follow the instructions here on how to flash a boot.img file with fastboot: http://forum.xda-developers.com/showthread.php?t=1752270
After you flash the boot.img and your phone turns on, reboot to recovery, flash PYD-X again, and it should work this time. If you have any questions on flashing a boot.img using fastboot then feel free to ask.
if you can`t run ruu, entern in bootloader ( adb reboot-bootloader ) and run ruu again
ripkid666 said:
if you can`t run ruu, entern in bootloader ( adb reboot-bootloader ) and run ruu again
Click to expand...
Click to collapse
ADB won't be of any use in this case because ADB is a userspace utility and Wooler's phone isn't booting at all. All the magic will be done with fastboot since all Wooler can access is the bootloader
A big thanks to all
Dear friends, first of all a BIG THANKS TO ALL.
I followed the suggestion of android1234567 and my sensation booted, but it stay into the welcome screen with the white background and the sensation xe logo.
Probably because I tryed many things before asking to you.
So I recovered my nandroid backup and all gone well. My sensation work again.
A big thanks to all.
Best regards
Wooler
Related
Guys, I rooted and unlocked bootloader via HTCDev on my friends HTC sensation... and installed ViperS 1.1.0 with S-ON..
I needed to flash boot.img taken from viperS.zip via fastboot so it would boot correctly.
The problem my friend is experiencing now is Wifi keeps connecting... so this means there is a problem with wifi.
On searching XDA forum replacing the kernel would probably fix the issue like using Bricked Kernel.... but isn't ViperS already using Bricked kernel?
What's a good fix for the wifi? so I can apply it to my friends HTC Sensation ViperS 1.1.0....
wogz143 said:
Guys, I rooted and unlocked bootloader via HTCDev on my friends HTC sensation... and installed ViperS 1.1.0 with S-ON..
I needed to flash boot.img taken from viperS.zip via fastboot so it would boot correctly.
The problem my friend is experiencing now is Wifi keeps connecting... so this means there is a problem with wifi.
On searching XDA forum replacing the kernel would probably fix the issue like using Bricked Kernel.... but isn't ViperS already using Bricked kernel?
What's a good fix for the wifi? so I can apply it to my friends HTC Sensation ViperS 1.1.0....
Click to expand...
Click to collapse
With S-ON T-Macgnolia have explained that
When you use HTC Dev to unlock your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read those partitions. But there is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the .zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed the New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
Click to expand...
Click to collapse
So, if you're having an issue of Wifi not working or keep 'Turning On...' you should enable the Smartflash in the 4EXT recovery menu and in the App itself after you flash any ROM. Asskicker explained it better than me in this thread in topic number 5.
Hope this will fix your issue
Aivard said:
With S-ON T-Macgnolia have explained that
So, if you're having an issue of Wifi not working or keep 'Turning On...' you should enable the Smartflash in the 4EXT recovery menu and in the App itself after you flash any ROM. Asskicker explained it better than me in this thread in topic number 5.
Hope this will fix your issue
Click to expand...
Click to collapse
Thanks pal, I'll try this on my friend's HTC sensation or maybe have him do it... I'm guessing though that things will start to work even without re-installing or flashing the entire rom....
EDIT:
We tried this... still wifi doesn't work... maybe re-flashing Bricked Kernel will help... I'm just guessing...
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
Heyy peeps,
Couple of weeks ago I unlocked my HTC Desire S. Thanks to this thread (http://forum.xda-developers.com/showthread.php?t=1525100) i succeeded and had the Reaper V4.0 rom installed.
I tried to experiment with other roms like PACman. Unfortunatly, every rom I try ends up with the same old HTC boot screen loop.
That's kinda the problem, so any help would be appreciated!
Read step 4 again.
??'boot.img'??
You're right, didn't change the boot image. So I did that now with the Fallout V5 and PACman roms. It worked this time and the rom booted spotless. But after a while I tried to reboot, now again I'm stuck a boot screen with HTC logo.
That's because instead of flashing boot.img to boot partition, you've actually booted the phone with it, but without flashing.
The correct form is:
fastboot flash boot boot.img
You did:
fastboot boot boot.img
Now tell me something: how does it happen that people can't read guides properly? EVERYTHING is documented, why do people still manage to mess things up?
Thanks mate.
hitmoky said:
Thanks mate.
Click to expand...
Click to collapse
You're welcome. Next time, please try to follow the guides exactly - copy-pasting pays off in this case.
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.
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