Develop Bugs

Power button reboots phone with Skyraider 3.3

Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?

patsfan1130 said:
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
Click to expand...
Click to collapse
You sure its Skyraider? That happened to me... Phone wouldnt shut off, if your in dark you can see the screen doesnt even shut down. With me though, it would shut off if plugged in.. Turned out the phone was damaged, a power surge damaged it. Got it replaced. If you flash another rom and it still wont shut down, then your gonna need a replacement.

Thanks for the response Mike. No, It does not happen with any other ROM I flash. Been bouncing between CM, Virtuous and uncommon for a week now and the power button works as it should.
I dunno, I realize I am a n00b with all of this but it simply doesnt make sense to me
Again, Thank you for the response

What radio are you using? A lot of people using 2.05 were having that issue and it went away when they upgraded to a 2.15 radio baseband.

No problem. But what you have going on is very odd, i wasnt aware that a ruu could do that. Try upgrading to the latest radio.

That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28

patsfan1130 said:
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
Click to expand...
Click to collapse
Yes, that's the baseband version and you should be good to go with the one you are using. The only other things I can come up with is to ensure you are S-OFF and running HBOOT 0.79 or higher.

Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.

patsfan1130 said:
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
Click to expand...
Click to collapse
Not a problem. This is how we learn. To find your HBOOT version power down then reboot into recovery. When you get to the white recovery screen look in the top left corner. The first line should state S-OFF and the second line should state your HBOOT version.

I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions

I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.

patsfan1130 said:
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
Click to expand...
Click to collapse
Well that's unfortunate. I read a couple of posts in the Skyraider thread that sounded as though a couple of people had the "recommended" setup (like you) but also had the reboot problem. Those posts seemed to get no response so I guess there was no fix found. Most of the discussion on this problem starts around post #2432 in the Skyraider thread if you want to do some more digging but I couldn't really find anything more.
Some other factors to consider:
When you first flashed the ROM did you wipe all data? (factory reset, wipe data cache, wipe dalvik cache).
If you flashed a custom kernel, try going back to the stock kernel.
What version of ClockworkModRecovery are you running? They released a buggy update a couple of weeks ago and it was pulled shortly after release so if you have a version higher than 2.5.0.5 then you should revert to an older version of CWM.
You could flash the 2.15.00.09.01 radio baseband but I don't think it would make a difference with this problem. Also, if you screw up or accidentally flash the same radio over itself then you will have a brick so use extreme caution if you decide to go that route.
That pretty much exhausts my knowledge on the subject so if everything is as it should be then you could always try wiping everything and flashing the ROM again.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
I didn't think of that but definitely a possibility. Good call.
Best of luck.

RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
Well wouldn't you know it! Problem solved
I did not know the add ons were not compatible
Thanks everyone!

I'm glad I was able to help...
Really though, good to hear you got it working. Enjoy.

[Q] Help! My desire stopped booting!

I Have a Desire with S-Off alpharev, and MIUI ROM.
All was working well until today.
It started to become very very slow....and now, the boot is really slow...and hangs on splash screen.
I could not complete the boot procedure..
So I tried a nandroid restore.... and now the launcher is doing loops...
What can I do???
Thanks for your help!

Tried a full wipe?

yes, full wipe done... same thing
I tried nandroid restore of my original HTC ROM.... seems more stable.. but still buggy.... impossible to activate wifi....

moreje said:
yes, full wipe done... same thing
I tried nandroid restore of my original HTC ROM.... seems more stable.. but still buggy.... impossible to activate wifi....
Click to expand...
Click to collapse
Hmm if you have stock hboot and stock rom something might be messed in terms of hardware i guess. I have no clue, bring your desire back to stock, then send it for repair, that's what i'd do. Good luck!

You may have flashed a bad radio

reaper7881 said:
You may have flashed a bad radio
Click to expand...
Click to collapse
but I did not flash new radio since many weeks.... and my last ROM flash has 2 weeks old...
The problem came suddenly, without any new flash...
But I can try recent radio, to test...

moreje said:
but I did not flash new radio since many weeks.... and my last ROM flash has 2 weeks old...
The problem came suddenly, without any new flash...
But I can try recent radio, to test...
Click to expand...
Click to collapse
That's why i suggest you to return the phone for mantainance: assuming you haven't flashed a bad radio, if your radio is just wrong or not up to date for the rom you have you may have signal issues, camera not working and more, but even those problems should be encountered as soon as you flash it, not days later.
Another chance, now that i think about it, it might even be a broken sd-ext messing up. Did you use data2sd or some script of any sort when on MIUI?

Just don't forget to restore your phone using the RUU ...

<SOLVED> Help!!!! data connection kills my wildfire!!!

Hello all guys!
Thank you a lot for the work that are you doing, sharing to all of us how we can make our phones free...
Recently i found xda-forums and because i own a wildfire, i wanted to make it better.
I started reading and i learned how to make things better... S-off my phone, rooted, completly wipe internal memory and flash a new rom. All good.... i had GPS problems first time, but i managed to fix it... anyway... Now i have a REAL PROBLEM...
A few days ago i flashed CyanogenMod7 nightly #232, after a full wipe. All good, but now i can't use it because data connection kills it... it doesn't matter what i do, but when i try to use browser/e-mail/market or any app that uses internet the same thing happens: reboot or power down.
I restored my stock froyo nandroid wich i had, same thing... Anybody knows a way to fix it??? please help me out, tethering phone's data connection was my getaway, but now it reboots my phone...
Here are my phone specs:
Phone: HTC Buzz Wildfire
S.OFF:Revolutionary
Hboot:[6.01.1002]
Recovery: [v.5.0.2.0] ClockworkMod Recovery
ROM: [2.3.7] CyanogenMod7-NIGHTLY-buzz #232
Kernel:[2.6.35.14]-nFinity [email protected] #1
Radio: [13.55.55.24H_3.35.20.10]
OC: SmartAssV2 min:[264]Mhz max:[691]Mhz
Jit=yes
VM Heap size: 32m
Help!
Edit: flashed the previous CM7 kernel (2.6.32) -> nothing happens
reflashed radio, still nothing... flashed 3.35.19.25 radio... still nothing...
Edit 2: now i see that if i connect phone to power socket, stays awake... i can use internet only with the phone. tethering still reboots my phone...
Final edit: Problem solved, i sent the phone to the sellers and after a failed attempt (where they thought that a sw update and a screen protector can make me happy), they figured out that all the phone needed is a new battery... they sent me the new one, and now all works just fine... i'm happy again, now i'm searching new tweaks for the BuzzFire... thx all who tried to help me out , special thx to 3xeno

Anyone can help? Desperate user here, guys!!! I'll pray for you... i just search for an answer but i cannot find a thread with the same issue or something close to it... Pleaseee!!!

HappyWILDFIRE said:
Anyone can help? Desperate user here, guys!!! I'll pray for you... i just search for an answer but i cannot find a thread with the same issue or something close to it... Pleaseee!!!
Click to expand...
Click to collapse
Does it reboot when you just turn the dataconnection on? and are you using v6turbocharger or the 3gturbocharger scripts?

Some options:
1. Reflash radio file to your phone
2. Get a official release of cyanogenmod
3. Make sure you wipe data/cache/dalvik before you flash the rom
Hope this helped, if it did please press the thanks button!
---------- Post added at 03:08 PM ---------- Previous post was at 02:56 PM ----------
Also partition your sd card! A lot of the time this helps!

dud3me said:
Does it reboot when you just turn the dataconnection on? and are you using v6turbocharger or the 3gturbocharger scripts?
Click to expand...
Click to collapse
no, i don't use v6turbocharger or 3g turbocharger... i don't need them, phone acts verry well without those scripts...
The phone dies few seconds after i enable data connection...
i also tried to read from the "Adb logcat" but i don't understand a s##t

mrweqa said:
Some options:
1. Reflash radio file to your phone
2. Get a official release of cyanogenmod
3. Make sure you wipe data/cache/dalvik before you flash the rom
Hope this helped, if it did please press the thanks button!
---------- Post added at 03:08 PM ---------- Previous post was at 02:56 PM ----------
Also partition your sd card! A lot of the time this helps!
Click to expand...
Click to collapse
I have 3 zips of CyanogenMod7 nightly (#202 #220 #232)... i allways perform a full wipe before i flash the rom... i reflashed all 3 radios from http://forum.xda-developers.com/showthread.php?t=1029318 ... same result...phone get killed or rebooted...
Now after a full wipe i have restored only Boot.img and System.img from my original Froyo nandroid backup, so basically i belive that could be a fresh install of the original Sense Froyo... the kernel is the original Htc kernel... but i still have the same problem... phone get killed after enabling data connection... i don't know why phone acts like this... All this "phone dies" story started suddenly... one day i woke up and the phone started acting like this... i think it hates me
Partitioning card helps?? i'l give it a shot... i'll tell you if it works... thx in advance...

wiped dalvik cache and cache... patition - 128 mb ext - 32 swap... nothing... same prob...(((((

Partitioning an SDCard can prevent freeze ups / network issues? That is a new one!
On topic, try flashing an RUU and check for the issue when on the stock ROM. I can't find the post, but it worked for someone else who was facing similar issues,

3xeno said:
Partitioning an SDCard can prevent freeze ups / network issues? That is a new one!
On topic, try flashing an RUU and check for the issue when on the stock ROM. I can't find the post, but it worked for someone else who was facing similar issues,
Click to expand...
Click to collapse
since i am a noob... i try all the suggestions... even for me sounded strange... anyway... i choose the RUU_Buzz_HTC_WWE_1.14.405.2_R_Radio_13.45.55.24_3. 35.15.31_release_130814_signed.exe, since i don't know what i had in my phone when i bought it, and i don't want to use a Froyo RUU because i'm afraid i won't be able to S-OFF and root my phone again... but another question... If i have HBoot:6.01.1002, the RUU is able to downgrade the HBoot, or i have to make it myself?... thx @3xeno... in advance... i hope this will solve my phone disease...
Edit: When i bought it, the phone had Sense 2.1 Eclair, but i made the 2.2.1 in-phone software update (dhaaaa)... i'm happy i managed to s-off it after that... and i didn't used AlpharevX (i had no idea at that time), i used "revolutionary-0.4pre4"...

You can use a Froyo RUU (WWE 2.22.405.1). The HBoot will not be touched. (You will lose Clockworkmod Recovery though, but, since you know how to use Fastboot, it shouldn't be an issue at all I am assuming). Also, your device, except the SDCard, will be formatted, so make sure you have your important stuff backed up.

3xeno said:
You can use a Froyo RUU (WWE 2.22.405.1). The HBoot will not be touched. (You will lose Clockworkmod Recovery though, but, since you know how to use Fastboot, it shouldn't be an issue at all I am assuming). Also, your device, except the SDCard, will be formatted, so make sure you have your important stuff backed up.
Click to expand...
Click to collapse
I learned this things thx 2 u... i have backups... fastboot... now i have to download the RUU... i'll tell you if it works in a couple of days... i have a poor bandwidth ( +>- 5KBps)... i'll pray to all the Gods i know (i'm christian but doesn't matter, maybe my God doesn't now a shee about ANDROID) ... i'll make you know if it worked, if not, i'll apply the RUU, downgrade Hboot, and i will go in the shop where i bought the phone and ... i'll make it pieces in front of the sellers... or request for warranty... am i correct?

Yes, do that, definitely if the RUU method doesn't work as well.

Anyway, it doesn't matter my data... if the phone doesn't work as it should, i don't think data is so important... data is a thing that can be refound... a phone with unknown issue.. is a really phookin' problem... the incredible thing is the fact that the phone works quite well without data connection... rarely app FC's, smooth UI... i'm amazed... did'n tried wifi... i will... maybe will work...

3xeno said:
Yes, do that, definitely if the RUU method doesn't work as well.
Click to expand...
Click to collapse
sorry for stressing you with questions... assuming that i may have some little knowledge (i think) about android and wildfire... let's say that RUU does his job... but what really does an RUU?? Rom update utility... removes clockworkmod+ performs a fresh install of an original HTC rom+ sometimes upgrades or downgrades HBOOT+S-on's the phone...
this stuff we can do it via Fastboot and adb... I have my original rom... i backed it up when i thought that AOSP ROM is something that definetly phone needs ( well i can say that: yes... it needs... <3 CM7NB)
so... if i "advanced" restore my Sense nandroid (only boot+system) after a full and complete wipe( i performed the wipe via clockworkmod-->mounts and storage--> all "format" options+ yes + wipe Dalvik cache + reboot in HBOOT -clear storage= phone boots and reboots in HBOOT... cuz there's no boot or operating system)... it means i have the original stock froyo... without configurations and stuff like that... am i correct?

Yes you can do that, but with an RUU, you are practically guaranteed a clean install. It's a good way to point out where exactly an issue potentially lies.

3xeno said:
Yes you can do that, but with an RUU, you are practically guaranteed a clean install. It's a good way to point out where exactly an issue potentially lies.
Click to expand...
Click to collapse
That's the point... ( linked to my phone issue)... if it's not the kernel or the radio or the custom recovery... remains the hboot... in your opinion can this be the problem?? sorry if i'm stressing you again...let's make this thread useful and discuss all the aspects... for the future, in case that this can be useful for all the community of XDA... maybe is pointless... but i wanna learn, and this is a verry good subject to discuss(i think)
While i wait that RUU to download (14% of 130+MB)
I think that since my nandroid is clean...(btw... i made a factory reset before making the Stock Froyo nandroid) and i know that data connection worked before and after... it just doesn't make sense for me why the RUU can fix things...

Sorry, but I am not so technically proficient as to go in depth and explain stuff, because, I myself don't know about it. I suggested something that has been known to work for others, and, it stays just that - a suggestion. It's totally upto you what you wish to do, what you wish to experiment etc. Its your device and your wish.
Hopefully, someone with in-depth knowledge of how stuff works can explain these to you.

3xeno said:
Sorry, but I am not so technically proficient as to go in depth and explain stuff, because, I myself don't know about it. I suggested something that has been known to work for others, and, it stays just that - a suggestion. It's totally upto you what you wish to do, what you wish to experiment etc. Its your device and your wish.
Hopefully, someone with in-depth knowledge of how stuff works can explain these to you.
Click to expand...
Click to collapse
yeah... if someone can explain, or i'll keep search for it till i find the explanation myself... man, thx for your advices (not suggestions) as i know that you understand more than i do this things, at the end i am a beginner in Android, also in XDA, i don't try to be rude or disrespect anyone, and most of all, i don't want my questions to be seen as stupid questions... i am a user that wants to know more...
Thx for your time and advices man!!! God Bless you!!

RUU installed, but issue not resolved
Bad news... looks that the RUU (2.22.405.1) did remove the custom recovery, flashed new radio and flashed the stock Froyo rom... didn't touch the hboot... but my phone is not cured... still dies few seconds after i enable data... i'll try to downgrade the Hboot to 1.01.0001 S-ON to see if the problem is resolved, if not, i think it may be a hardware problem and i hope i can send it for a warranty intervention... God!!! Why are you doing this to me?!!

I had it wrong doesn't matter.

Any idea why no rom will work? (CDMA)

I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.

Did you do a full wipe ???

ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...

donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.

You mean the Rom booted normally right ?? If yes then the problem is with the Rom

donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).

Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.

[Q]What kernel is most stable for OC?

Hello there guys. As the title says, Which kernel for the HTC ONE X is the most stable one to install that you also can overclock it to lets say 1.55-1.65GHz & to OC the GPU? My HTC ONE X is modded ARHD 21.0(S-Off & Rooted) and ive ONLY tried to do this once and i did it with Bricked Kernel(sweep2wake one) with no success. At first it kept getting stuck at HTC logo and next time it didnt even want to go to bootloader and the sence stopped working(fixed with reflashing the kernel for ARHD 21.0) Reason why i even bother asking is because ive done research time to time, reading carefully each topic ive managed to find for the HTC ONE X that you can do this and i still am not sure which one is the best one to use without getting any big issues, like f'up the phone completely.
Anyone who know and can take his time to post a link to a topic with a good kernel that is easy to flash and do the things mentioned here would be greatly appriciated!

Bricked kernel was only developed for ICS roms. Not jellybean. That's why it probably didn't work.
This one is nice
http://forum.xda-developers.com/showthread.php?t=2134086
http://forum.xda-developers.com/showthread.php?t=2136731
http://forum.xda-developers.com/showthread.php?t=2276590
And as additional info : there is no best kernel to use, try some yourself and find out which one suits you the best.

Mr Hofs said:
Bricked kernel was only developed for ICS roms. Not jellybean. That's why it probably didn't work.
This one is nice
http://forum.xda-developers.com/showthread.php?t=2134086
http://forum.xda-developers.com/showthread.php?t=2136731
http://forum.xda-developers.com/showthread.php?t=2276590
And as additional info : there is no best kernel to use, try some yourself and find out which one suits you the best.
Click to expand...
Click to collapse
Yeah thanks alot for those. Appearently i was wrong about S-OFF, its actually S-ON. Should i download the Sense ones from any of those links you provided now that it actually is S-ON or does that have nothing to do with what i chose?(Sense or AOSP)

Depends on your running rom. The kernel needs to match the rom.
Sense rom = sense kernel
Aosp rom = aosp kernel

Mr Hofs said:
Depends on your running rom. The kernel needs to match the rom.
Sense rom = sense kernel
Aosp rom = aosp kernel
Click to expand...
Click to collapse
I havent figured out what is what but i went ahead and chosed the AOSP kernel and flashed it. Everything was working fine and i think i did it right with the packing and all that stuff. Managed to get to the HTC One screen with the Beats Audio then it just was stuck there. MAYBE i was unpatient as usual so what i did is restarted the phone, flashed the kernel for ARHD 21.0 and reinstalled it. Phone works perfectly fine untill i saw that Rosie isnt working no more and the modpack 6.6 started to reboot my phone the second it got to the locked screen for some reason. Before that it worked perfectly fine and i had my setup so fine it went so damn fine you know ;/ But what caused this issue? Did i f' it up when i flashed the kernel(2nd post you linked one) or is it just me whos installing it all wrong? The way i did was:
1: Get the one One X click running.
2: took out the boot img of that zip file(AOSP kernel)
3: repacked that(that is what i thought i had to)
4: flashed it
5: phone rebooting constantly, even went in to safe mode for some reason but got fixed upon reinstalling ARHD 3 times.
EDIT: funny thing btw is that the first time i installed ARHD the rosie worked. I remember doing something wrong that i had to reinstall it and Rosie did not work. Got rosie back by installing the modpack 6.6 but now its not working either way... And appearently im a retard. I shouldnt have installed AOSP... I just tried the Sense one and it works perfectly! Going to try to reinstall rosie from modpack 6.6 and see if it works.

sp3tan said:
I havent figured out what is what but i went ahead and chosed the AOSP kernel and flashed it. Everything was working fine and i think i did it right with the packing and all that stuff. Managed to get to the HTC One screen with the Beats Audio then it just was stuck there. MAYBE i was unpatient as usual so what i did is restarted the phone, flashed the kernel for ARHD 21.0 and reinstalled it. Phone works perfectly fine untill i saw that Rosie isnt working no more and the modpack 6.6 started to reboot my phone the second it got to the locked screen for some reason. Before that it worked perfectly fine and i had my setup so fine it went so damn fine you know ;/ But what caused this issue? Did i f' it up when i flashed the kernel(2nd post you linked one) or is it just me whos installing it all wrong? The way i did was:
1: Get the one One X click running.
2: took out the boot img of that zip file(AOSP kernel)
3: repacked that(that is what i thought i had to)
4: flashed it
5: phone rebooting constantly, even went in to safe mode for some reason but got fixed upon reinstalling ARHD 3 times.
EDIT: funny thing btw is that the first time i installed ARHD the rosie worked. I remember doing something wrong that i had to reinstall it and Rosie did not work. Got rosie back by installing the modpack 6.6 but now its not working either way... And appearently im a retard. I shouldnt have installed AOSP... I just tried the Sense one and it works perfectly! Going to try to reinstall rosie from modpack 6.6 and see if it works.
Click to expand...
Click to collapse
AOSP kernel will not work on Sense ROM's correctly. ARHD is a Sense based rom (AOSP kernels have a lot of Sense stuff missing).

parkentosh said:
AOSP kernel will not work on Sense ROM's correctly. ARHD is a Sense based rom (AOSP kernels have a lot of Sense stuff missing).
Click to expand...
Click to collapse
So when i flashed my HTC ONE X that was modded with ARHD with the AOSP kernel it somehow "removed/lost" the rosie app in it or something? Because everything else is working PERFECTLY fine except for rosie. Like i said, i got the Xmister sense kernel to work right now and its running smoothly.

I just don't understand why you flash a aosp kernel on a sense rom while i even said that a kernel must match the rom. learn the differences before flashing......

Mr Hofs said:
I just don't understand why you flash a aosp kernel on a sense rom while i even said that a kernel must match the rom. learn the differences before flashing......
Click to expand...
Click to collapse
That was me being unpatient and not reading thats all mate. Im just asking now if that is what caused it or not. What is done is done, just wanna know if that was the reason or not, simple. And if theres a fix for it i would highly appriciate to know how to fix it!

Reflashing a sense kernel and modules should do the trick, thats all
Or install the rom from point 0

Mr Hofs said:
Reflashing a sense kernel and modules should do the trick, thats all
Or install the rom from point 0
Click to expand...
Click to collapse
Already installed the rom plenty of times now like ive mentioned. IF from point 0 means that you just goto recovery mode and install it again. Did that like 5-6 times already and it still isnt working for some reason. Do i have to wipe my SD card completely and then put back the zips n stuff and then reinstall it that way like you usually do? should i factory reset it first and wipe something else or is that even necessary?