hi guys can someone help me out please im so scared this isnt even my phone was trying something for a friend.
so i did a system wipe and wipe internal in recovery twrp....
I then tried to install venom rom 2.1.0 it extracts everything then finishes after 7% I am rooted and s off
I have the phone on jelly bean S4 and hboot 2.15 can someone direct me to an ruu for the jellybean
TheDrone said:
it extracts everything then finishes after 7%
Click to expand...
Click to collapse
I believe this is a common issue either with certain versions of TWRP recovery, or when choosing to perform a fill wipe in the aroma installer.
Make sure you have a good recovery. (Read around for which TWRPs are affected.) Also do your wipe in recovery before starting the installer for the ROM, and dont choose to wipe in the installer.
touch of jobo said:
I believe this is a common issue either with certain versions of TWRP recovery, or when choosing to perform a fill wipe in the aroma installer.
Make sure you have a good recovery. (Read around for which TWRPs are affected.) Also do your wipe in recovery before starting the installer for the ROM, and dont choose to wipe in the installer.
Click to expand...
Click to collapse
I did do a wipe in recovery , and didn't choose wipe in aroma either.I have my own one s so I know what to do I think it was just the dodgy recovery anyway I'm back to stock now 're locked and used ruu, will try whole rooting process tomorrow . I knew there was problems with twrp but didn't take notice because it works on my device properly
Can anyone tell me which is the best twrp thanks
Sent from my HTC One S using xda app-developers app
TheDrone said:
I did do a wipe in recovery , and didn't choose wipe in aroma either.I have my own one s so I know what to do I think it was just the dodgy recovery anyway I'm back to stock now 're locked and used ruu, will try whole rooting process tomorrow . I knew there was problems with twrp but didn't take notice because it works on my device properly
Can anyone tell me which is the best twrp thanks
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
twrp 2.3.3.0 for sure; absolutely no problem up now
Can someone please link Me to 2.3.3 or another stable twrp please ? I can only find 2.4...
Sent from my HTC One S using xda app-developers app
TheDrone said:
Can someone please link Me to 2.3.3 or another stable twrp please ? I can only find 2.4...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Go on the TWRP website, search for ville
Sent from my One S using Tapatalk 2
I. Can't find it on the website someone please help
Sent from my HTC One S using xda app-developers app
TheDrone said:
I. Can't find it on the website someone please help
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/ville
Finally rooted the phone again flsshed venom 2.1.0 which works properly dlwnlaoded ota 2.2.0 flashed everything boots but statusbar does not show any help?
I didn't flash the boot.img because I am soff hboot 2.15 and venom 2.1 boots properly just not 2.20
Sent from my HTC One S using xda app-developers app
TheDrone said:
Finally rooted the phone again flsshed venom 2.1.0 which works properly dlwnlaoded ota 2.2.0 flashed everything boots but statusbar does not show any help?
I didn't flash the boot.img because I am soff hboot 2.15 and venom 2.1 boots properly just not 2.20
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I had that same problem with the OTA. I just decided to keep 2.1
Sent from my One S using xda app-developers app
I fixed it but I don't know what fixed it, flashed boot. Img then flashed 2.2. 0 and cleared cache and dalvik cache hope it helps try it
Sent from my HTC One S using xda app-developers app
Related
hi
ive screwed up now hope someone can help i was running on an old hd revolution rom which i flashed a while back now but thought i would have a look at the elegancia rom i was already s-off and all rooted so i downloaded the 4ext software then the rom and try to install the rom i am now left with the white htc screen i can still access the boot screen and the ext4 recovery touch but i tried everything i know formatted wiped tried restoring the original backup and the hd rev backup i just made it says your 4ext theme was corrupted it was uninstalled to prevent damage my sd card is still ok i believe can someone help this cretin
If u can get into fastboot then flash the RUU based on the last successful Rom u were running
Sent from my HTC Sensation 4G using XDA
I bet he's not on 3.32 firm
Sent from my HTC Sensation 4G using xda premium
Which firmware are u on? i believe u must be on 3.32 to flash any of the newer roms
all correct i thought which is the trouble that i already had it unfortunately now when i try to flash it it tells me
finding update package
opening----"--------
E: cant open /sdcard/pg581img
saranam said:
all correct i thought which is the trouble that i already had it unfortunately now when i try to flash it it tells me
finding update package
opening----"--------
E: cant open /sdcard/pg581img
Click to expand...
Click to collapse
Have you tried another version of the pg581img zip?
hey. sorry for bumping old thread. i have the same problem. no idea when that happened but the error is quite annoying to me. any helps on this? :/ thanks.
Hi
Greetings
Give us your bootloader details
And what problem you have?
And what you did that you are stuck in problem?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
shrex said:
Hi
Greetings
Give us your bootloader details
And what problem you have?
And what you did that you are stuck in problem?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
i encountered the problem of corrupted theme of 4ext. im not sure how it happened. maybe because i flashed CM10.1 then returned back to ViperS ICS? not sure bout that. its not really a problem but its quite annoying to press okay every time i boot into recovery. hehe
shaun3010 said:
i encountered the problem of corrupted theme of 4ext. im not sure how it happened. maybe because i flashed CM10.1 then returned back to ViperS ICS? not sure bout that. its not really a problem but its quite annoying to press okay every time i boot into recovery. hehe
Click to expand...
Click to collapse
Does the rom boot? If so just use the 4ext app to flash a new theme. That should overwrite whatever is corrupted. If that doesn't work reflash the recovery entirely. You can do that from the app too.
If that doesnt work comeback with a more detailed description of exactly what you get.
Sent from my HTC Sensation using xda app-developers app
Skipjacks said:
Does the rom boot? If so just use the 4ext app to flash a new theme. That should overwrite whatever is corrupted. If that doesn't work reflash the recovery entirely. You can do that from the app too.
If that doesnt work comeback with a more detailed description of exactly what you get.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
yeap. the rom did boot up. hmm. how doo i do that from the app? which app? or there's an app for 4ext?
There is an app for 4ext. Its available for download on the play store. Its an absolute must have app if you use 4ext recovery. It makes life so much easier.
Sent from my GT-P5110 using xda app-developers app
Until today I was using HyperSensation 3.0, decided to try a new ROM and choose BADOSP V 1.1 to test. After back-up/wipe cache-dalvik/format all partitions/installing ROM/reboot. The phone booted normally until the lockscreen showed up, then, immediately shutted down. Powering on again was met with the same results.
I did the process of wiping, formating and installing again in case I forgot something, and again the same thing happened. I tried with another ROM, this time with ViperS 1.0.1, and I got the same thing, power off after the lockscreen shows for the first time. Before restoring the back up, I tried installing again HyperSensation 3.0 and it works... As a last resort I installed a gingerbread RUU to start totally stock, and again... power off in the same place...
I reinstalled 4ext, updated the firmware again to 3.33 and restored my back up to have a functional phone again, but I cannot understand why is this happening.
Can someone out there chime in and help me with this?
Thanks in advance.
Daeox said:
Until today I was using HyperSensation 3.0, decided to try a new ROM and choose BADOSP V 1.1 to test. After back-up/wipe cache-dalvik/format all partitions/installing ROM/reboot. The phone booted normally until the lockscreen showed up, then, immediately shutted down. Powering on again was met with the same results.
I did the process of wiping, formating and installing again in case I forgot something, and again the same thing happened. I tried with another ROM, this time with ViperS 1.0.1, and I got the same thing, power off after the lockscreen shows for the first time. Before restoring the back up, I tried installing again HyperSensation 3.0 and it works... As a last resort I installed a gingerbread RUU to start totally stock, and again... power off in the same place...
I reinstalled 4ext, updated the firmware again to 3.33 and restored my back up to have a functional phone again, but I cannot understand why is this happening.
Can someone out there chime in and help me with this?
Thanks in advance.
Click to expand...
Click to collapse
Try to flash super wipe from android revolution install the Rom flash a custom kernel first then boot I had this problem but I couldnt flash any Rom w/o a bootloop or getting stuck at the HTC screen try flashing the sense o maniac Rom and overclocked kernel by Sebastian by the way that's what I did
Sent from my Sensation Z710e using xda app-developers app
Also do you have 4ext recovery
Sent from my Sensation Z710e using xda app-developers app
imxsteezin said:
Also do you have 4ext recovery
Sent from my Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Yes I have 4ext and I tried super wipe too, but didn't try with another kernel. I'll try your sugestion with the Sense o Maniac ROM. Thanks!
No problem let me know what happens
Sent from my Sensation Z710e using xda app-developers app
Daeox said:
Yes I have 4ext and I tried super wipe too, but didn't try with another kernel. I'll try your sugestion with the Sense o Maniac ROM. Thanks!
Click to expand...
Click to collapse
Are you S-ON?
Jonny said:
Are you S-ON?
Click to expand...
Click to collapse
No, i'm S-Off.
imxsteezin said:
No problem let me know what happens
Sent from my Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
I tried both Sense o Maniac latest versions, Sense 3.6 and 4.0, but neither of them worked... Any other ideas?
You flashed the kernel right ? I just helped someone fix thiet phone with this method
Sent from my Sensation Z710e using xda app-developers app
And did you flash the android revolution super wipe?
Sent from my Sensation Z710e using xda app-developers app
imxsteezin said:
And did you flash the android revolution super wipe?
Sent from my Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Yes, I flashed super wipe but forgot about the kernel part. I'll try that now. With what Sense o Maniac your solution worked, Sense 3.6 or 4.0?
I tried with both Sense ROMs. Super Wipe/Install ROM with everything stock/Flash Kernel/Reboot but that didn't work either.
Anyone have more ideas to know why this is happening? I'm lost...
Daeox said:
Anyone have more ideas to know why this is happening? I'm lost...
Click to expand...
Click to collapse
Did you check the md5sum of the roms you are trying to flash?
Sent from my HTC Sensation using xda premium
irrelephant said:
Did you check the md5sum of the roms you are trying to flash?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Yes, I check them and they are correct.
flash the rom again ..with wipe from 4EXT this time
4EXT -> wipe|format -> format all partitions except sdcard
then flash the new rom and see
ganeshp said:
flash the rom again ..with wipe from 4EXT this time
4EXT -> wipe|format -> format all partitions except sdcard
then flash the new rom and see
Click to expand...
Click to collapse
I have tried that too... That's why it is weird... I have installed a few ROM's before and everything went fine... But this time it is like my phone doesn't want to get out of HyperSensation... :laugh:
Daeox said:
I have tried that too... That's why it is weird... I have installed a few ROM's before and everything went fine... But this time it is like my phone doesn't want to get out of HyperSensation... :laugh:
Click to expand...
Click to collapse
reflash the firmware then if you are using 3.32 reflash it or update it to 3.33
ganeshp said:
reflash the firmware then if you are using 3.32 reflash it or update it to 3.33
Click to expand...
Click to collapse
I'm in 3.33 already... I even installed a gingerbread RUU to start from stock and the same thing happened.
Daeox said:
I'm in 3.33 already... I even installed a gingerbread RUU to start from stock and the same thing happened.
Click to expand...
Click to collapse
then the only culprit left is recovery ..
try reflashing it or ..update it to 1.0.0.5 RC (also can you check if you enabled smartflash (in 4EXT -> tools) ..coz that some times messes up for SOFF devices and make sure smartflash is disabled )
Hello friends,
Today I installed ROM from http://forum.xda-developers.com/showthread.php?t=1782009 .
Before I made backup etc etc.
After ROM installation I installed gapps for JB.
All installation processes went succefully.
The problem is:
- phone is starting but handling on loading screen CMX CyanogenMod 10 and this "cosmic guy"
Did I do something wrong?
HW Specification:
HTC Sensation
Before ROM change: Android 4.0.3 (ICS) 3.33.401.106
Thanks in advance for all replies. (If I place this post in bad place, dear admin im sorry but I don't know enough forum structure. Please move it )
Best regards,
Mat
So its stuck on the CM10 boot screen?
Are you sure you did a factory reset/wipe after backing up, and before flashing the new ROM?
Sent from my CM9 Stable Sensation using XDA Premium
Do you use 4ext recovery or cwm recovery ?
Sent from my HTC Sensation using xda premium
MrSoulSOng said:
So its stuck on the CM10 boot screen?
Are you sure you did a factory reset/wipe after backing up, and before flashing the new ROM?
Sent from my CM9 Stable Sensation using XDA Premium
Click to expand...
Click to collapse
Yes, I made factory reset/wipe and dalvik wipe.
rico727 said:
Do you use 4ext recovery or cwm recovery ?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I'm using CWM.
rico727 said:
Do you use 4ext recovery or cwm recovery ?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Currently I'm using 4EXT Recovery Touch v1.0.0.5 RC5
Sent from my CM9 Stable Sensation using XDA Premium
Did you flash the gapps right after the rom flashing?
Try to install them separately.
First install the rom then let it boot, set some things up and let it idle for some couple of minutes.
Then reboot and install the gapps.
That's how I usually do.
MrSoulSOng said:
Currently I'm using 4EXT Recovery Touch v1.0.0.5 RC5
Sent from my CM9 Stable Sensation using XDA Premium
Click to expand...
Click to collapse
What's the difference between 4ext and cwm?
syntax_gosong said:
Did you flash the gapps right after the rom flashing?
Try to install them separately.
First install the rom then let it boot, set some things up and let it idle for some couple of minutes.
Then reboot and install the gapps.
That's how I usually do.
Click to expand...
Click to collapse
I installed rom and after that (without reboot) gapps. I was waiting 2 hours with boot screen but it's not working.
rydzykje said:
What's the difference between 4ext and cwm?...
... I installed rom and after that (without reboot) gapps. I was waiting 2 hours with boot screen but it's not working.
Click to expand...
Click to collapse
Well I think the 4EXT Recovery Touch is just a much nicer experience. It's slick, simple, but does so much.
I flashed gapps directly after CM9 ROM with no problems at all. After a factory reset/wipe in 4EXT Recovery Touch. Haven't had a problem there. Don't know about CM10.
Sent from my CM9 Stable Sensation using XDA Premium
MrSoulSOng said:
Well I think the 4EXT Recovery Touch is just a much nicer experience. It's slick, simple, but does so much.
I flashed gapps directly after CM9 ROM with no problems at all. After a factory reset/wipe in 4EXT Recovery Touch. Haven't had a problem there. Don't know about CM10.
Sent from my CM9 Stable Sensation using XDA Premium
Click to expand...
Click to collapse
Do I need S-Off ?
With the 4ext you have to tick smartflash, then you don't need s-off
Sent from my HTC Sensation XE with Beats Audio using xda app-developers app
impact_ftw said:
With the 4ext you have to tick smartflash, then you don't need s-off
Sent from my HTC Sensation XE with Beats Audio using xda app-developers app
Click to expand...
Click to collapse
I made S-Off and CMX10 start to work
Thanks for your replies
Have a good night
Do you use Superwipe ?
AOSP rom does not support Superwipe tool.
You shold go Wipe factory data / Wipe Cache menu to do dual wipe.
Hope that helps you
hkhs10811 said:
Do you use Superwipe ?
AOSP rom does not support Superwipe tool.
You shold go Wipe factory data / Wipe Cache menu to do dual wipe.
Hope that helps you
Click to expand...
Click to collapse
I wipe Data/cache and dalvik : )
It's working now. I just needed S-off I'm a "noob" in that things so I just need more tutorials And everything is working now : )
Post can be closed.
Maybe you should try 4ext
Sent from my HTC Sensation using xda premium
if the issue is only with the boot loop stuck image then....
Just extract the boot image from the ROM zip file and place it in the adb folder on the OS partition then use fast boot commands to push the boot image to the device. it should work, worked for me.:good:
rydzykje said:
I wipe Data/cache and dalvik : )
It's working now. I just needed S-off I'm a "noob" in that things so I just need more tutorials And everything is working now : )
Post can be closed.
Click to expand...
Click to collapse
Im in the same boat, stuck on the CMX CyanogenMod10 boot screen, i just checked hboot and it says "Unlocked" but S-on. How can i get S-Off please?
willis1981 said:
Im in the same boat, stuck on the CMX CyanogenMod10 boot screen, i just checked hboot and it says "Unlocked" but S-on. How can i get S-Off please?
Click to expand...
Click to collapse
what recovery do you have ?
you can flash roms with S-ON
flash 4ext recovery
enable smartflash from it
flash the rom
rzr86 said:
what recovery do you have ?
Click to expand...
Click to collapse
CWM
willis1981 said:
CWM
Click to expand...
Click to collapse
i have edited my above post
rzr86 said:
i have edited my above post
Click to expand...
Click to collapse
Can you link me please, it would be much appreciated also thanks for the swift reply
Hi, i entered to boot menu and its say S-OFF thats means im Permroot or what, becasue i already have superSU app and i want to install another ROM to my Cellphone the Stock rom its giving me error lots of it because today it close the sense application and some how it erase every short cut i have and when i tried to take a picture my cellphone suddenly restart i decide to chose CMW problem is if im not in permroot i have Hboot 1.29
what can i do?
thank you
Pretty much, I suggest you use 4ext to flash your ROM.
Sent from my Sensation using Tapatalk 2
Amenofhis said:
Hi, i entered to boot menu and its say S-OFF thats means im Permroot or what, becasue i already have superSU app and i want to install another ROM to my Cellphone the Stock rom its giving me error lots of it because today it close the sense application and some how it erase every short cut i have and when i tried to take a picture my cellphone suddenly restart i decide to chose CMW problem is if im not in permroot i have Hboot 1.29
what can i do?
thank you
Click to expand...
Click to collapse
Well, once you're s-off you should install a custom recovery so you could install custom roms. I suggest 4Ext recovery (see my signature for the link) . After that you should Nandroid (e.g complete backup) you phone through the recovery. It will create a large file in your SD card which contains a full backup of your phone. Later you can install whatever rom you wish. I suggest you begin with Android Revolution HD - it looks like stock but it contains latest kernels, mods and tweaks.
Sent from my HTC Sensation Z710e using xda premium
Raven2k said:
Well, once you're s-off you should install a custom recovery so you could install custom roms. I suggest 4Ext recovery (see my signature for the link) . After that you should Nandroid (e.g complete backup) you phone through the recovery. It will create a large file in your SD card which contains a full backup of your phone. Later you can install whatever rom you wish. I suggest you begin with Android Revolution HD - it looks like stock but it contains latest kernels, mods and tweaks.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Thanks for the reply! The free version of the 4Ext works fine or I have to use the paid version?
Amenofhis said:
Thanks for the reply! The free version of the 4Ext works fine or I have to use the paid version?
Click to expand...
Click to collapse
Free version is enough . . .
Sent from my Sensation using xda app-developers app
Itsakash said:
Free version is enough . . .
Sent from my Sensation using xda app-developers app
Click to expand...
Click to collapse
Great than you btw recently install the new rom but it came with a super user I don't like how I uninstall this one and install another one?
Sent from my HTC Sensation using xda app-developers app
I've run multiple versions of CleanROM and also CM10, but anytime I install a Sense based JB ROM (I've tried Newt's, JellyBlam, and a few others), my phone gets stuck on the HTC boot splash, reboots, and enters recovery. I am on HBOOT 1.09 and Ive tried to fastboot flash the boot.img just to be sure, but it still doesn't work? I'm sure I'm doing something wrong, any clue what it is? Thanks in advance.
Are you doing full wipes before flashing?
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Are you doing full wipes before flashing?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I do a factory reset in TWRP. Does that count, or is there more to it?
Grazzert said:
I do a factory reset in TWRP. Does that count, or is there more to it?
Click to expand...
Click to collapse
Tell us what ROM you're trying to install. Also, you're right about the reset. Do all of that in twrp.
Sent from my One X using xda premium
ToxicWaste said:
Tell us what ROM you're trying to install. Also, you're right about the reset. Do all of that in twrp.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Newt's
Grazzert said:
Newt's
Click to expand...
Click to collapse
Are you sure it successfully installed?
omario8484 said:
Are you sure it successfully installed?
Click to expand...
Click to collapse
The log says it successfully installed and when i press reboot system, the sequence of events i described in OP happens
Factory reset and wipe system and both caches
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Factory reset and wipe system and both caches
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
same thing happens :/
bump for answers....
Sounds like the correct procedure to me.
Sent from my HTC One XL
ECEXCURSION said:
Sounds like the correct procedure to me.
Sent from my HTC One XL
Click to expand...
Click to collapse
And yet it won't work. lol
Maybe you have an init.d folder that is telling the JB ROM to overclock? Could check and delete that first. Otherwise you can double check the md5 of the ROM you're flashing to make sure its not corrupt. Aside from that it might be worthwhile to try a ROM like urdroid which allows you to flash the kernel during the installer.
Dunno man, your problem is a strange one.
Sent from my HTC One XL
ECEXCURSION said:
Maybe you have an init.d folder that is telling the JB ROM to overclock? Could check and delete that first. Otherwise you can double check the md5 of the ROM you're flashing to make sure its not corrupt. Aside from that it might be worthwhile to try a ROM like urdroid which allows you to flash the kernel during the installer.
Dunno man, your problem is a strange one.
Sent from my HTC One XL
Click to expand...
Click to collapse
Urdroid was another that i tried. It would get to the ROMs boot splash and lock there, but its the only one i recall that even got that far out of the 3 or so that i tried. where would that init.d folder be?
Either the directory of the /sdcard or /. I forget which as I have deleted it. But it should be a folder. Don't delete it if it's by itself.
Sent from my HTC One XL
Really sounds like you are not flashing the boot.img correctly.
Extract the boot.img from the ROM you want to use and install it with:
fastboot flash boot boot.img
You're not alone....
Grazzert said:
Urdroid was another that i tried. It would get to the rom's boot splash and lock there, but its the only one i recall that even got that far out of the 3 or so that i tried. where would that init.d folder be?
Click to expand...
Click to collapse
I've been experiencing the same problem on my HTC Sensation 4G for the past couple years since I've had it. I have 3 HTC Sensations in my family and I've been playing around with all 3 phones during the last year. On my sister and my mom's phones, I'm able to install any rom (Sense-based...ARHD, Elegencia; and AOSP/AOKP-based...CM10, Paranoid Android, etc); however, on my own phone, after dozens of installs, trying all types of different kernels and roms, I was only able to install AOSP/AOKP-based ones. I've been running Touchcream ICS rom for awhile, then Paranoid Android, and currently JB Samsation V5 on my HTC and I love it. I'm really not missing out on anything, but it's just weird Sense-based roms just wouldn't boot. After some researching on the forum and experimenting with others, I've deducted that the reason could be very well my own hardware. :victory: