Related
I recently have spent a decent amount of time trying to get my inc2 to boot JB without extreme lag(maxed out CPU). I've ran JB quite a few times until one day I overclocked to 1.5GHz and my phone boot looped and could never get JB or ICS to run properly. Its been reported that over clocking over 1.3GHz can break the partition on your phone and even lose root. If u have similar problems this is what I did -
Put the stock ruu GB 2.3.4 on the root SD card as pg32img.zip
Boot into boot loader and click vol up to accept update.
you are now on the latest stock gb without root but s-off will b preserved
download super one click and htc drivers to gain root.
reboot
I flashed twrp thru goo manager cuz that it's what I prefer. Wipe and flashed dkstunna's build 3 with 4.2 gapps and boom BACK TO FAST JB in under 30 min.
hope this helps someone! hit thanks if it did
next I hope to help on the main thread one day, Ive flashed almost every ics jb Rom and would luv to help
Sent from an incredibly running JB inc2
Can anyone verify this works? Not that I doubt you OP, just wondering if this has worked for anyone else?
Quick question.
I have been rooted for so long I've almost forgotten how it is done but I don't remember Super One Click supporting the DInc2. Does this mean it does root 2.3.4?
yes super one click works for inc2, and yes it will root 2.3.4. s off is the hard part on 2.3.4 if ur not already, so be s-off. I'm sure this will work differently for everyone cuz god knows why ics jb stopped working right in the first place. I bet kernel source would fix this too...
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
I'm running PA for months now and it hasn't locked up or lagged. I came from Venom before. I wiped everything except SD card, installed CM10 10/3, booted, flash PA, booted, flashed gapps and kernel. It booted up just fine for me.
I also flashed the firmware in the Venom thread. I don't use v6supercharger, 1024MHz smartassv2, and I undervolt -50.
TheAtheistReverend said:
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
Click to expand...
Click to collapse
I was in a bit of a panic cause i was using viper, went to aeroevans 11/13 jb, it worked for about 6 hours and then the massive lag and boot loops started. I couldn't flash any ics/jb aosp rom, I tried mimicry, dkstunna, and aeroevean's cm9/10. all non usable, crazy lag and boot loops. viper seemed to flash fine though.
I did try the solution in this thread and it didn't seem to work so I reflashed viper formatting using aroma. I let it boot and settle. then i formated all partitions in 4ext and reinstalled viper without formatting in aroma and i let it boot and settle, finally i reformatted all partitions in 4ext, installed aeroevan's 11/13 with latest jb gapps and all has been great for the past few days. fingers crossed.
I have tried just about everything. I can't think of anything else to try. I wish we knew why some phones were doing this.
The first thing I remember not going as usual on my phone was MIUI was not installing properly. It would hang on "updating boot" during install. I couldn't for the life of me get it any farther than that. The next thing was a JB NAND wouldn't boot properly, and then it was all down hill.
Back on the same bull**** of bootlooping on cm10. There should be a warning on the viper thread to not install it if you ever want to use another rom.
I don't know why but I'm not having any problems after viper...
I'm so fresh you can suck my nits...
None of us know the answer and that's the only common denominator. I'm just lucky that Miui works or i'd be sol
Uhh so yeah, tried this and it didn't work. Never had any problems with the phone before I got rid of ViperInc. I was on the latest firmware, every ROM flash was a totally clean one, followed the instructions in the OP and CM10 Global is just sitting here bootlooping. I know the dev isn't responsible for what happens to our phones, but multiple cases of the same seemingly unsolvable problem says there's something wrong with that ROM, imho. ****ing bogus.
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
chillybean said:
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
It's not the cm10 devs' problem
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
chillybean said:
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I don't think it is ViperROM dev's problem, nor is their responsibility to help. They make it very clear they hold no responsibility for what happens to your device when you flash their ROM. They are also not making any money from the free rom they put out for us to enjoy, so their is no driving force really behind their desire for "fans" if you will.
That being said, it would be nice if they could help and did. Has anyone directly, and nicely asked Nitsuj or any of the Viper team for help?
fen0m said:
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
Click to expand...
Click to collapse
Doubt it. I went all the way except for S-off and re-rooted but it still will not load any JB rom I try. But by all means, it might be worth trying if you're so motivated. Seems like some things work for some, but not for others at this point.
Just got back onto CM10. Was on Viper, did full wipe x2, formatted partitions to ext3 in 4ext Recovery, fix permissions, then formatted cache.
Then...here's the weird part....since Mimicry was the only non GB Rom I could get to at least boot, I tried a clean flash of it. Used only the baseline items in the Aroma installer (only things I installed were the jb animations, trebuchet, v6, and daemon). Booted into Mimicry and let it settle without signing in to Google. Profit!
Next phase was a full wipe x2, flash newest CM10, flash GApps, then format cache.....double profit! Hopefully this will hold up. Will report back once its had time to fully settle.
Sent from my Incredible 2 using xda premium
Sry didn't mean to say it like that but I know its not their responsibility..I just asked if they try to figure this out..I'm gonna try this mimicry method...I hope I profit like twice
Sent from my HTC Droid Incredible 2 using xda app-developers app
I wouldn't call it a method really....I think I may have just gotten lucky
Sent from my Incredible 2 using xda premium
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.
So I've come a long way to get to where I am now. I tried to install AOKP or PACman but was lost in a boot loop. I gave up and reflashed the Stock ROM and stayed with it for a while. A couple of days ago I decided to give it another go and reinstalled PACman. I found out about the OTA update and reflashing the previous radio. Did all of that and finally installed PACman and it works flawlessly.....well kinda. Here are the problems I've run into after a perfectly clean install:
Small problems:
* No lock screen
* Paranoid Android settings randomly don't apply after boot.
Bigger problems:
* Can not send more than 140 charcter texts without receiving network problems (any lower works fine)
* NO notifications. None. Zip. Nadda. I've tried changing the UI (Stock, Phablet, Tablet) to see if it would change in any of them. Didn't And notifications was ticked as on when I was in Tablet mode.
I'm not sure what to think about all of this. I have CM10 running on my Touchpad and it works flawlessly. Never had any sort of problem ever with it. But now with this ROM I'm getting screwed over.
Now needless to say, I have tried flashing AOKP the other day just see how it would do. The problem was that it was slow AND showed no notifications. So i should change having problems with the ROM to having problems with my phone.
So at this point I am open to any suggestions or input of any kind regarding this issues.
What carrier are you on? Sounds like your on someone else than vm. These ROMs are designed for VM but can be modified to work with cricket and all those other ones. What version of pacman u using? What kernel also?
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Tehwafflez said:
What carrier are you on? Sounds like your on someone else than vm. These ROMs are designed for VM but can be modified to work with cricket and all those other ones. What version of pacman u using? What kernel also?
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
I am using Virigin Mobile. I am also using this pacman: http://forum.xda-developers.com/showthread.php?t=1948034
Okay, there is something definitely wrong here. I just tried to call my phone from a LAN line and nothing. I checked the call history and it shows up but does not notify me when I am being called. Tried to stay in the app while I called and still nothing. Tripping out now.
Try reflashing the ROM full wipe aka factory reset + dalvik. Although I'm pretty sure u did that. I have an old version of 19.3 that doesn't have the goo.im support which did give a lot of bugs. Ask in your face in his thread if he still has the DL link for that old version.
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Tehwafflez said:
Try reflashing the ROM full wipe aka factory reset + dalvik. Although I'm pretty sure u did that. I have an old version of 19.3 that doesn't have the goo.im support which did give a lot of bugs. Ask in your face in his thread if he still has the DL link for that old version.
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
Yeah, I've flashed the same rom multiple times after a clean wipe (factory + caches) using TWRP. Also tried miltiple roms with multiple kernels. After backing up my SMS I'll give it another go and report back here. I hate it when people figure stuff out and don't post how they do it.
Do you think IYF will even respond? That thread is aging much no?
For those of you who will soon be cursed with the HTC One V like I have, here is my solution:
I used the Port ROM of Provisions: http://forum.xda-developers.com/showthread.php?t=2098618
Make sure to use the Gapps linked to in the thread or else the keyboard will screw up and you will have to flash everything all over again.
Notifications now work, along with calls, I havent gotten around to try texts yet but i'm sure it works.
I sounds like you may want to retry the install. My hov running pacman has no issues. And I mean none. Make sure you wipe everything. I wipe system, then factory reset, then cache and dalvik. Then flash ROM, then kernel, boot then flash gaps. I also use twrp. And I am all good
Sent from my HTC One V using xda premium
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?
Hi guys, i swear i searched! for like days! i still haven't found out how to solve this issue. problem started when i tried hellybean a few weeks back, and then i heard someone on the thread said to try and use the latest beta uber kernel at the time, and i did. What end up happening was that my hardware keys are dead, the lights still works but very dim, i think this is because of the swipe to wake thing where it leaves your hardware keys on 24/7 as long as the phone is on, which is not that bad because i'm now used to using the nav bar. but the real problem is that now every time I install a rom that is not JB 4.1 (haven't tried 4.2 though) i.e. 4.3, 4.3.1, it gets stuck at the app optimization screen, it would go about half way through optimizing the apps, and then just reboots itself, and it'll do that over and over, like boot loop but it can actually go into the rom. So i think this is not as bad as a situation as soft bricking or hard brick, but i just really don't know what the heck is going on to even try and fix it. I've tried odin, thinking that there may be something wrong in the boot file, nada, factory reset, nada, the only thing that worked was installing the 4.1 roms, i think it is because the 4.1 roms don't require app optimization.
If anything maybe anyone out there can help me find a way to disable app optimization? maybe that'll let me get into the rom.
btw, i dont really mind using 4.1, but i really want to try the jedi rom, but having my hardware buttons dead and jedi rom being TW and it doesn't seem to have a nav bar make it impossible for me to use the rom, so i've only been able to use cyanogen 4.1, which are great but they are pretty outdated, so if there are anyway to fix that, lmk too.
Anyways, any help would be appreciated thanks a ton guys! sry for essay!
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
krazierokz said:
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
Click to expand...
Click to collapse
Lol actually the problem started when I was on 4.3, and then upgraded to 4.3.1 helly bean, in which i tried to use the beta uber kernel, that was when the problem started. So the only roms that allows me to get pass the optimization screen were the 4.1.2 roms, which were TW, pananroid, like i tried a bunch, like super old ones, they all worked, just that when i try to get any rom higher than 4.1.2, it keep going back to that. And yeah when i tried to upgrade from jedi to aosp, to tried using infamous cache and it didnt work :/ because i've heard that's what would fix it... and lastly, Im using twrp 6.1 i think, not the latest one.
Thanks alot for the reply!
PS. I see you running slimbean 4.2.2, how is it? any probs? maybe i can try a 4.2.2 if this doesn't work out, i havn't been able to get any 4.2.2 roms cause the links are all dead, so idk if i'll have problems with 4.2.2. if there's anyway you can link it for me that'll be great! thanks!
PSS: also i've tried odin, but idk if that actually wipes everything, i'm having a feeling that it might be a script problem or something because it goes into the rom once, but it just refused to work and after like 10 seconds it reboots.
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
krazierokz said:
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
Click to expand...
Click to collapse
Ey thanks for the reply, ok so first, I did not try to restore any apps or system apps, I even odin so everything were wiped cleaned. So really dont know whats going on. After I updated to a newer hellybean, not newest by now, and a beta uber kernel, this happens. I see two other people having the same problem too. Also I tried to use 4.2.2 roms, did not work
Anyways any insight would be apreciated!
Thanks!
One more thing, I tried twrp 2.6.1.0 to flash as reccomended by all devs and still no results. :/
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
krazierokz said:
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
Click to expand...
Click to collapse
oh well, thanks for the reply then, im trying 4.4, hopefully it'll help... somehow... lmao idk haha