Okay not sure what I going on! Maybe someone can help.
I am in no way bashing or blaming the venom ROM or aroma installer in any way, this is the series of events leading to my issue
I was running the sinless gpe ROM...was wanting to try the new venom ROM, went into twrp ( was running 2.7) wiped everything went to the venom ROM and it loaded the aroma installer...I went through the options ( the only thing I didn't keep stock was adding small apps).
Okay I loaded venom got set up and WiFi wouldn't work....couldn't get it to work so I was going to restore a cleanrom backup I had. No matter what I do the only restore that will work is my sinless backup.
When I try to install another ROM from scratch...nothing it will install, and there are no errors in twrp but will not get past the HTC red text screen.
Okay so I found the new op6bimg on my card but it is the 1.55.605?? 4.4.2 I ran that back to stock. Then installed my twrp again, and the same deal. Any suggestions?
I found the thread by (ugh name is misplaced at the moment) with the 4.4.3 RUU thread...I tried to flash that and got an error....wrong img. It went through the checking and all took a few mins then where it would usually say press up to update it just says power to reboot.
I'm not really sure where to go...partitions messed up? I thought while in hboot flashing 0P6Bimg.zip takes everything back....
Anyway. I think this is all the info, hopefully someone could point me in the right direction.
Thanks
TK
Flash the ruu and then factory reset from the stock recovery.
I got him all squared away
timmy_k said:
Okay not sure what I going on! Maybe someone can help.
I am in no way bashing or blaming the venom ROM or aroma installer in any way, this is the series of events leading to my issue
I was running the sinless gpe ROM...was wanting to try the new venom ROM, went into twrp ( was running 2.7) wiped everything went to the venom ROM and it loaded the aroma installer...I went through the options ( the only thing I didn't keep stock was adding small apps).
Okay I loaded venom got set up and WiFi wouldn't work....couldn't get it to work so I was going to restore a cleanrom backup I had. No matter what I do the only restore that will work is my sinless backup.
When I try to install another ROM from scratch...nothing it will install, and there are no errors in twrp but will not get past the HTC red text screen.
Okay so I found the new op6bimg on my card but it is the 1.55.605?? 4.4.2 I ran that back to stock. Then installed my twrp again, and the same deal. Any suggestions?
I found the thread by (ugh name is misplaced at the moment) with the 4.4.3 RUU thread...I tried to flash that and got an error....wrong img. It went through the checking and all took a few mins then where it would usually say press up to update it just says power to reboot.
I'm not really sure where to go...partitions messed up? I thought while in hboot flashing 0P6Bimg.zip takes everything back....
Anyway. I think this is all the info, hopefully someone could point me in the right direction.
Thanks
TK
Click to expand...
Click to collapse
..
Thank you. @Tigerstown.
I flashed the stock Thu (1.55...) Upgraded to the 4.4.3 firmware then loaded then flashed dottat's 4.4.3 ruu then Bucks tarp. All up and running.
Figured I'd post this in case someone else had the issue.
Thanks again tigerstown and dottat and buck for the d/l's
Related
Newbie flashing here. Followed everything and flashed my first rom yesterday.
Flashed: RUU_Kaiser_HyperDragon_IV_Mega_6.5_WWE_20091006_11-54PM
After trying that one, I then i flashed to another rom.
Flashed: KAISER_WM6.5__3_34_721_V31__B23041_09032009 (not sure which thread i got it from)
But when the phone started up it showed the stupid splash screen from the hyperdragon rom but booted into the new rom (slight problem)
Then i wanted to try another rom this morning and read to flash back to htc rom first. So i just did and i am stil looking at the last rom i flashed. I have hard reset a couple times here and there, and after installing the htc official rom (WTF problem)
Im gonna try loading this next rom now, but i have a feeling i wont see it when it boots, ugh
Not all roms come with splash screens. When you flash a rom that does not come with it's own splash, the splash from the previous rom is retained.
Hard reset, flash the stock ( oem ) rom, the when it says tap here to set up , hard reset again. If you fallowed the right flashing steps ( which you have previously, obviously ) the stock rom should boot up.
Ah, indeed. Thank you for the response. Flashed back to stock rom and all is well. Not so sure i like this flashing stuff.
carhigh said:
Ah, indeed. Thank you for the response. Flashed back to stock rom and all is well. Not so sure i like this flashing stuff.
Click to expand...
Click to collapse
Once you hardspl your phone, it is kind of hard to brick it. A stock flash usually solves everything. Flashing is addictive, it brings out the " gotta have the latest and greatest " in you.
But even after flashing over a hundred times, I still hold my breath everytime I flash. I already bricked one phone way back in the early days of Kaiser flashing when the phones first came out.
Hey guys, I been away from the sensation for a few months now and I think I bricked it on my first flash back! I was flashing ARHD & I followed the noob guide, I downloaded firmware & updated, deleted the firmware file, performed super wipe, flashed the rom, and I checked my md5 sums. Now I'm bootlooping the white HTC splash screen, and sometimes I see the beats audio symbol but right back to the slash screen! Ahhh.... I use this line for work. I used the 3.30 firmware as it said to & I'm on boot 1.27? I know one of you guys can help, so please ANYONE,I've got a get this fixed tonight.....
well if its booting then fortunately you're not bricked lol
have you tried re flashing the new firmware?
I flashed the 3.30 that the installation guide I was following told me to. I have ext 2.2, so is that an issue or is it the correct recovery.
Anyone who can walk me through this I'd really appreciate it guys. Just like most, I rely on my phone for work. I'm a little worried here, I've flashed quite a few times and I've never had an issue like this that I couldn't restore out of.....
Try this??
what I did was everything you did.. except I used this firmware update...
Firmware from 3.30.401.1 & 3.30.401.101 RUU
--- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
--- Only for 3.30.401.1 & 3.30.401.101 based ROMs
Then I installed the ICS Energy rom, and everything works great.. I've also flashed a few other roms without issues.. I haven't tried the arhd yet.. I'm currently running the virtuous AOSP rom.. and still, everything works great.. I hope this helps
Just a side note.. have you tried formatting the sdcard then trying that setup? I did have issues with my sdcard in the beginning, but after formatting, I've had no issues..Also make sure the ROM you're using is made for the correct firmware, otherwise you'll have bootloops! hope this helped!
That's the same firmware I used, and I've ran the firmware upgrade twice now. Now right after I updated the firmware the first time I did it, I rebooted on accident & it wouldn't boot even before I flashed arhd.... is this normal?
It wouldn't boot into hboot? What I did was put all the needed files on my sdcard, flashed the firmware, removed the sdcard(while the phone is powered on).. booted into the rom, then put the scdard back in and removed the firmware update..then rebooted the phone, then wiped and loaded an ICS rom..that was really about all I did.. and so far all works well.. I'm really at a loss as to what the problem on your end is.. it sounds like you've done everything you're suppose to do..
You could try to run the relevant ruu (assume you have s-off?) and start again?
http://forum.xda-developers.com/showthread.php?t=1074559
Update::II flashed Virtuous and had no issues and everything is running perfect. Looks just like my transformer prime now. I doing know why at this point that my system would not play nice with ARHD, I followed the guide to the letter and I flashed the firmware 3.30 several timed just as directed. None the less, I am satisfied with this from, and my device is much smoother and more productive than the ****ty GS2 by T-Mobile that I had been using the last few months! I just can't retire my Sensation. Thank you to all who chimed in, you're a great community!
Bricked
That happened to me too when I tried to install ICS without updating the firmware
first.
I just re-booted to recovery and did a restore. I'm assuming you backed up your
ROM right?
Then at least your phone will go back to normal and you can start over...and use it for work haha
I'm good now on virtuous, but I just couldn't get ARHD to work for me. Yes I had upgraded to the proper firmware first, and I always compare md5 sums. I'm by no means an expert, but I always research, read and ask all the nessecary questions before I flash anything I'm not familiar with. I think there may just be rare occasions when some of the devices just won't play nice with certain software. Virtuous took on the first flash & I'm actually very pleased with it, so all's well that ends well. ICS is just so much more intuitive & functional for me
.
Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
tom0779 said:
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
Click to expand...
Click to collapse
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
mittortz said:
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
Click to expand...
Click to collapse
Cm10 stable works for me. But I installed it in recovery
Sent from my HTC One X-
I figured out the issue. I forgot that with the 2.20 firmware you have to flash the boot.img separately from the ROM. So after the update all I had to do was flash the boot.img and it was all ready to go again
Hi people,
here is stock kernel extracted from One SV k2_u/k2_ul/k2_plc_cl version but with modded ramdisk.
I put this thread into general section but as soon as sources are out this will be moved into Original Development section and it will be replaced by my new kernel.
Features:
- Unsecured kernel
- init.d support
- Persistent ADB enabled
Instructions:
- Run "fastboot flash boot boot.img" command.
- Reboot & Enjoy!
DOWNLOAD for k2_u
DOWNLOAD for k2_ul
DOWNLOAD for k2_plc_cl
Make a nandroid backup first!
Credits:
- old.splatterhand
- eduardog131 for stock k2_plc_cl kernel
Enjoy!
xpirt
Will this help for a 4.2.2 rom?
GtrCraft said:
Will this help for a 4.2.2 rom?
Click to expand...
Click to collapse
Sorry this should be on One SV general section and I reported but anyone moved yet. @Ghost
It's stock kernel for One SV btw.
xpirt
Hi,
Can you mod k2ul version kernel?
@xpirt
Would you be willing to make a tutorial on here as to how you did this, the requirements needed to accomplish it, and what to check for, as well as the changes which must be made for such a modification? I am asking this so many will learn and as well take the idea and possibly grow from it by coming up with even better ideas in the future. Without the knowledge or know how then this will only keep people in the dark and nobody wins from this. You don't have to make a tutorial, but if you were to do so it would be very much appreciated friend.
Sent from my C525c using XDA Premium 4 mobile app
If someone gives me stock k2_ul kernel I can mod it as well.
@Modding.MyMind I modded it with cygwin kitchen, you can unpack any kernel and edit its ramdisk. The file modded is default.prop.
xpirt
Added k2_ul version! @bataya
xpirt
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Modding.MyMind said:
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
xpirt said:
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
Click to expand...
Click to collapse
No worries man. Handle your priorities .
Sent from my C525c using Tapatalk
Added modded k2_plc_cl kernel, thx to @eduardog131 for stock kernel.
xpirt
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
SnakeFist2005 said:
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
Click to expand...
Click to collapse
Not this, this is the kernel. To use toolbox a deodexed system + root/busybox should be enough.
xpirt
Experiment went awry!!!! Ended with a nice surprise!!!
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
Unlocked
K2_PLC_CL PVT SHIP S-OFF RL
CID 11111111
HBOOT 1.01.0000< oldest one i've seen lol.
Radio 1.12.00.0208
OpenDSP- v 10.2.0268.0401
eMMC-boot
Feb 8 2013, 16: 29: 40:-1
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Fant0m3 said:
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Click to expand...
Click to collapse
so are you saying that you flashed this kernel?
what exactly do you want a dev to do? i think, by reading what you said, that what you did was, try to compile a kernel with bits and pieces, and when you flashed it, it didnt work? so you tried to restore a backup that you also 'compiled'(?), which failed as well. you then flashed an older hboot which allowed your update to take.... the downgrade to update has stumped lots, including me. its basically the process of manual updating. these phones are all different because the partitions are in different locations in the device. and certain varients have no sim card slot. the radios are running "different channels" etc...
sorry for continuing off topic..
Thanks for the kernel and all your work