Replaced digitizer & screen - Fixed then broken again? - Galaxy S 4 Q&A, Help & Troubleshooting

Hello,
I have a UK unlocked, GT-I9505 that had a broken screen, I bought a new black edition screen (dark black not black mist) and replaced it. Previously there was an AOSP 4.4.2 ROM on it that worked fine and everything was happy and good. I then upgraded to a AOSP 4.4.4 ROM which stopped the touch screen functioning (it displays, but no touch), and also tried a 4.4.3, same story.
The touch screen works in TeamWin but anytime it gets on the OS it just stops taking input.
Any help/advice would be massively appreciated

It almost sounds like you placed a different type of touchscreen in your phone and you got lucky it worked in the 4.4.2. It sounds to me like some drivers were changed after the 4.4.2. versions.
If your touch screen works in the recovery, then it's definitely software related.
Do a full wipe in the recovery and flash the rom again. If it still doesn't work, try a different rom (preferably TW based, because you are already on an aosp rom).

Lennyz1988 said:
It almost sounds like you placed a different type of touchscreen in your phone and you got lucky it worked in the 4.4.2. It sounds to me like some drivers were changed after the 4.4.2. versions.
If your touch screen works in the recovery, then it's definitely software related.
Do a full wipe in the recovery and flash the rom again. If it still doesn't work, try a different rom (preferably TW based, because you are already on an aosp rom).
Click to expand...
Click to collapse
Thanks, I've tried full wiping, I'll flash a TW (TouchWiz?) rom and see if that works

jamie_ap said:
Thanks, I've tried full wiping, I'll flash a TW (TouchWiz?) rom and see if that works
Click to expand...
Click to collapse
Hi,
Yes TW stands for TouchWiz, and I agree with the person above there. As it works on recovery, it should work on system. Just try flashing another ROM, and the best would be go back to the ROM you were IMHO. At least it worked right .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10

XxLordxX said:
Hi,
Yes TW stands for TouchWiz, and I agree with the person above there. As it works on recovery, it should work on system. Just try flashing another ROM, and the best would be go back to the ROM you were IMHO. At least it worked right .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
Don't seem to be getting anything working , I'ved tried what I believe to be the 4.2.2 ROM I had working but as soon as I swip install on TeamWin it insta-power offs and then reboot into TeamWin :/

Related

Cyanogenmod Samsung Logo Hang

Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP
What twrp version?
xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM
How long has it been doing this/at what point did it start?
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.
Sorry, didn't read your whole post and missed the rc2.
jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.
It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.
cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers
Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!
emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.

[Q] freezes on 4.4.2 custom roms / kernels

on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.
push! no one else with same problems? maybe i got a hardware defect?
paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.
added a poll as a matter of interest.
omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases
i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.
using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed

Screen discoloration and weird zoom after trying to flash CM-11

Hi all,
Today has been a disastrous day for me. My Nexus 4 decided to update itself and got stuck at "Android is updating.... Starting apps.." screen. It is rooted and the bootloader is unlocked. Fastboot recognized my phone but not adb and I couldn't figure my way out of that so I basically reset my phone, flashing the stock version of Android 4.4.2.
It worked fine for a few minutes, so I tried flashing the latest snapshot version of CM-11, but that failed. I believe it was after I restarted my phone that everything became discoloured and the screen was zoomed in and repeated.
I tried flashing the stock ROM again in hopes of fixing the discolouration and zooming, but it didn't help. I've attached a picture of what my phone's display looks like. The colours of the bootloader are normal and unaffected.
Can anybody help me with this? I've been using Android Toolkit 1.2.8 and Nexus Root Toolkit on my Windows 8.1 x64 laptop. My Nexus 4 currently has the stock version of Android 4.4.2.
I'm inexperienced at this, so please let me know if more information is required.
you are using a kernel that support AOSP rom with a CM11, you should use a compatible kernel
Svarion said:
you are using a kernel that support AOSP rom with a CM11, you should use a compatible kernel
Click to expand...
Click to collapse
Thanks for the fast response,
Sorry, could you be more specific? I not QUITE sure what that means, but could it not be an issue if I've flashed the stock 4.4.2 onto my phone?
Thank YOU!
I guess I kind of remember flashing the stock 4.4.2 failed (I think it said too many connections), but I retried it just now after restarting my computer and the display is back to normal.
In terms of kernels, how will I know which kernel(s) is/are compatible?
n4helpneeded said:
I guess I kind of remember flashing the stock 4.4.2 failed (I think it said too many connections), but I retried it just now after restarting my computer and the display is back to normal.
In terms of kernels, how will I know which kernel(s) is/are compatible?
Click to expand...
Click to collapse
if you are using cm11 or any rom based on cm11 you should use a compatible kernel, if you are using stock/aosp rom you can use almost all kernels like franco.kernel, ak, hellscore

[Q] last fast (really) android version?

ok, we have a nexus, so we deserve updates and we have them....that's why we bought a nexus no?....
yes....but every update is a hit for our device's performance...I thought that last one would fix performance issues, but is not .
so...I bought one of these to my gf, sure that it would work well, I owned one a year ago and it was very good! nope....is slow, lags, remembers me a 100$ cheap tablet.
I considered to downgrade....is frustrating...what version do you remember as stunning fast, like a nexus should be?
4.1? damn, is too 2012-ish....
4.2? old but at least we have tiles on notification drawer...
4.3? good, some performance goodies, hw vsync...
4.4? I thought this would be the best choice because in theory is optimised for 512mb ram devices too....but was not performing well
5.0? don't say nothing...pff
I also read about f2fs as a revolution, but is not my tablet and my gf uses it for study and I can't take it to test...
thanks for reading and answering
My 2012 Nexus 7 (wifi) I had been on Android 4.4.4 when I updated to Android 5.0 using Wugs nexus root tool kit.
It had been sluggish on Kit Kat, but got more so when I went to Lollipop, even with a full wipe.
After about a week on 5.0 I rolled back to Android 4.3, and have been happy since.
Everyone is having different experiences and mine personally is that 5.0 is running greater for me then 4.4.4. That was with a complete full wipe (including data) when I flashed the image through wugs toolkit. There were initially bouts of lag (waking up screen, lock screen, etc) but the lags pretty much gone bar a few occasions. 5.0.1 will hopefully make the system more stable and not repeat what happened with 4.4.4 because my n7 ran like a pig after that update.
tabuser said:
My 2012 Nexus 7 (wifi) I had been on Android 4.4.4 when I updated to Android 5.0 using Wugs nexus root tool kit.
It had been sluggish on Kit Kat, but got more so when I went to Lollipop, even with a full wipe.
After about a week on 5.0 I rolled back to Android 4.3, and have been happy since.
Click to expand...
Click to collapse
And how are you with 4.3? Perfect? I'm really considerino a downgrade....
I will try forma the last time a full wipe and factory image, and then downgrade until I'm satisfied.
No words about f2fs?
I have just updated my n7 to Slim rom 5.0.1.
I have been frustrated by not being able to read a simple email using gmail application. Lags, lags, and "gmail is not responding do you want to close it"
I need to have two accounts for me and my wife, so the performance was even more slow.
Now with f2fs it is a rocket. I have installed every toolvI wanted and now also the Godfire game, and I must admit that it was a hit.
So thank you google to slow our machines to force buying the new ones, but my nexus7 from 2012 acts lighning fast now.
remmyhi said:
I have just updated my n7 to Slim rom 5.0.1.
I have been frustrated by not being able to read a simple email using gmail application. Lags, lags, and "gmail is not responding do you want to close it"
I need to have two accounts for me and my wife, so the performance was even more slow.
Now with f2fs it is a rocket. I have installed every toolvI wanted and now also the Godfire game, and I must admit that it was a hit.
So thank you google to slow our machines to force buying the new ones, but my nexus7 from 2012 acts lighning fast now.
Click to expand...
Click to collapse
ok....I have to format on f2fs....that's the only way....
than...con you tell me how to do that? and also, I want to flash stock lollipop, no custom roms...
I read some but guides were outdated...and, FYI I am very experienced on flashing, so I will not take you much time
Not sure if stock can be ran on f2fs.
I installed slim rom and itis close to aosp.
Instruction is provided in the rom thread.
I am no very experienced and I handled without problems.
remmyhi said:
Not sure if stock can be ran on f2fs.
I installed slim rom and itis close to aosp.
Instruction is provided in the rom thread.
I am no very experienced and I handled without problems.
Click to expand...
Click to collapse
wait. are you running kk?
Nope. Lollipop.
Slim f2fs on lollipop?
ConstantineTheGreat said:
Slim f2fs on lollipop?
Click to expand...
Click to collapse
Have you got it? I'm not sure I want to keep lp on that tablet....how is it?
Even on my m8 lp performs bad, considering that is stock and my phone was on the top of benchmarks before nex 6 and 9 came out..
throcker said:
Have you got it? I'm not sure I want to keep lp on that tablet....how is it?
Even on my m8 lp performs bad, considering that is stock and my phone was on the top of benchmarks before nex 6 and 9 came out..
Click to expand...
Click to collapse
No, I don't have it. I just asked is there slim lollipop on f2fs, because I tried rastapop and SleamFreak which are on 5.0 and have f2fs support, but I had problems like rebooting, problem with installing new apps, etc.
So for now, till I get answer from user emmyhi, I back to slimkat KK which run fantastic on our Nexus 7.
SlimPop (f2fs) by Freak is great. very fast.
cosmickamal said:
SlimPop (f2fs) by Freak is great. very fast.
Click to expand...
Click to collapse
Yes, I can agree with you that is really fast, but I had a problem with gapps (downloaded one's give in thread) and I couldn't install Google play store (it wasn't installed with gapps???)
I couldn't resolve my problem with that, and also, even I did clean install I haven't got screen like I first time use this rom. I haven't got possibility to chose language, and everything else. Rom just moved me to homescreen. Maybe this is not for this thread, but, I'll wait some other version of slim on 5.0.
ConstantineTheGreat said:
Yes, I can agree with you that is really fast, but I had a problem with gapps (downloaded one's give in thread) and I couldn't install Google play store (it wasn't installed with gapps???)
I couldn't resolve my problem with that, and also, even I did clean install I haven't got screen like I first time use this rom. I haven't got possibility to chose language, and everything else. Rom just moved me to homescreen. Maybe this is not for this thread, but, I'll wait some other version of slim on 5.0.
Click to expand...
Click to collapse
Did you try SlimGapps Normal one from the op link. That worked fine for me. You first flash the Rom. Boot. Go to recovery again. than flash Gapps. Boot. You will get the initialisation screen.
too much beta, I can't take my gf's tablet everytime she has a problem ahahah
I will try an evening every factory image and a kk f2fs rom to see which one performs better...then I'll let you know!
I'm running stock rooted 4.4.4 kitkat on mine with Lean Kernel 4.1. No lag, no issues with apps not working like on 5.0. Good battery life ,watched over 5 hours of movies last night and still had 49% left from a full charge. Standby time is excellent, I've only lost 2% over the last 9 hours.
ConstantineTheGreat said:
Yes, I can agree with you that is really fast, but I had a problem with gapps (downloaded one's give in thread) and I couldn't install Google play store (it wasn't installed with gapps???)
I couldn't resolve my problem with that, and also, even I did clean install I haven't got screen like I first time use this rom. I haven't got possibility to chose language, and everything else. Rom just moved me to homescreen. Maybe this is not for this thread, but, I'll wait some other version of slim on 5.0.
Click to expand...
Click to collapse
cosmickamal said:
Did you try SlimGapps Normal one from the op link. That worked fine for me. You first flash the Rom. Boot. Go to recovery again. than flash Gapps. Boot. You will get the initialisation screen.
Click to expand...
Click to collapse
riggerman0421 said:
I'm running stock rooted 4.4.4 kitkat on mine with Lean Kernel 4.1. No lag, no issues with apps not working like on 5.0. Good battery life ,watched over 5 hours of movies last night and still had 49% left from a full charge. Standby time is excellent, I've only lost 2% over the last 9 hours.
Click to expand...
Click to collapse
that stock one with f2fs?
No, not here. Pure stock, rooted 4.4.4 KitKat. Removed a few Google apps I don't use, but still ext4. Lean Kennel really make a difference.
and....after a flashing afternoon....
4.2.2 stock was damn fast....
4.3 stock was even faster and smoother than 4.2.2
4.4 was worse......got better with lean kernel, but wasn't just fast and responsive enough.
the winner is....4.3......that's what I left on my gf's tablet....
everything runs good, apps opening instantly, look much 2013 but google launcher and google keyboard help...
this is my suggestion after my tests. good luck and hope next LP ota will fix some performance issues, not only on this one but for every phone which got slower with this update

[Q] Phone refuses to boot with a rom

Hi, I've been trying to install a custom rom (at this point ANY custom rom) on my friend's phone. I have worked on several phones before, including my own sprint GS3, but this is my first time trying to work around a locked bootloader, and BOY is it a pain, haha. I'm no dev, but I would like to think that I'm pretty competent.
First a few things to note, are that the phone is currently on NI1 (Been too much of a sissy to go to NJ4 in case it screws something up, I don't even know why), it is the 16Gb version, I am using an external sd card to flash everything, and yes I am flashing loki-doki after everything.
So what I've done so far is:
- Try to install TWRP
- Find out that won't work and finally figure out I need safestrap
- Successfully install safestrap after using towelroot by ODIN-ing the NC1 kernel then going back to the NI1 kernel
- Try to flash Resurrection Remix and KToonsez kernel using a new rom-slot, and wind up soft-bricking (stuck on bootloader screen, can get to download mode)
- ODIN NB1 tar then ODIN NI1 update
- Repeat the last few steps several times because I'm too idiotic to realize that it JUST ISN'T GOING TO WORK!
- Finally find a reference to flashing the ATT kernel modules after the rom. That got me past the soft brick and safestrap screen, but I don't even see a boot animation
As of right now my sequence to successfully not soft-bricking (what an accomplishment) is to flash the rom>gapps>ATT kernel module>supersu>loki-doki>wipe dalvik/cache
Now, is it worth it having already spend a good 7 hours, just to get a custom rom? Of course not, it's not my phone and my friend isn't picky. He'd be just fine with rooted TW. However, It kills me that I don't know what's going on, so here I am lol.
TL;DR: Phone has safestrap, is rooted, but any time I flash a rom it gets past the boot loader/safestrap screen and never shows a boot animation, or anything past that. Can anyone help figure out what's going on please?
Thanks in advance.
You can only flash touch wiz based roms with safestrap and you can't flash kernels with safestrap. That's been your problem with soft bricking.
Edit, see this for roms you can flash http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2616221
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Masterjuggler said:
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Click to expand...
Click to collapse
It wouldn't hurt to update to nj4. But it's not going to help you either. Only phones on mdb or mdl bootloader can flash non touch wiz based roms using loki. And you can't go back to those bootloaders
Sent from my Nexus 9 using XDA Free mobile app
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Masterjuggler said:
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Click to expand...
Click to collapse
Again, you can't flash a kernel in safestrap
Sent from my Nexus 9 using XDA Free mobile app
Oh, I get it now. That didn't quite register before. So just to confirm, after I flash the rom (which already has its own custom kernel included), I still need to flash the stock ATT kernel, correct?
Flash the rom, super su, and the att module for your base. Hyperdrive is a very good rom, good luck. Also the rom doesn't include a kernel, your original kernel stays put. That's why only tw roms work, because your new rom has to be compatible with the kernel already on your phone.
Just reporting in, I now have the phone up and running using Hyperdrive Rom. Thanks for the help!
I actually had a problem where it would not shut down correctly, but found out it was because I was installing the rom in a rom-slot in safestrap. As soon as I tried the stock rom slot, it worked flawlessly.

Categories

Resources