Hello all,
I've had my nexus 4 ever since it came out and never faced this problem. Apparently, flashing any Lollipop ROM other than CM12.1 causes me to lose root. I would install SuperSU and whenever root access is required, it would prompt me, but no access is gained.
Any idea how to fix this? I want to use AOSP roms too!
Thanks.
Anyone?
Sent from my Nexus 4 using XDA Free mobile app
MisT. said:
Hello all,
I've had my nexus 4 ever since it came out and never faced this problem. Apparently, flashing any Lollipop ROM other than CM12.1 causes me to lose root. I would install SuperSU and whenever root access is required, it would prompt me, but no access is gained.
Any idea how to fix this? I want to use AOSP roms too!
Thanks.
Click to expand...
Click to collapse
When you flash new Rom's, do you do a clean or dirty flash. Do you use a custom kernel?
Thanks for replying. Clean,, always clean flashing. And no I don't use any custom kernels; tho I've tried using them to see if I get root access and it didn't work.
Sent from my Nexus 4 using XDA Free mobile app
MisT. said:
Thanks for replying. Clean,, always clean flashing. And no I don't use any custom kernels; tho I've tried using them to see if I get root access and it didn't work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
What about if you flash a ROM based on CM? Does that work? If not you could try flashing a factory image and start from scratch. Rooting and stuff again.
CM based ROMs work most of the time. I'll try doing the factory image thing. Do u recommend I try anything else?
Sent from my Nexus 4 using XDA Free mobile app
MisT. said:
CM based ROMs work most of the time. I'll try doing the factory image thing. Do u recommend I try anything else?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I can't really think of anything but it is possible some of the more knowledgeable members here at xda have som other suggestions.
This seems like a really strange problem with a clean flash with SuperSU. The only thing I can think of is that root access is being granted too slowly. Have you tried any of the ROM's built-in root apps?
Related
Hello, I have the Nexus 4 I am running 4.2.2 and I'm rooted I was going to update the other day to 4.3 but it didn't work. Could this be due to a custom recovery? I am on stock android and i was unrooted at the time.
I was also wondering if there are any good root methods out there I have heard a lot of problems with rooting on 4.3?
Just would like some opinions?
Thanks guys
Sent from my Nexus 4 using xda premium
Freakyy6 said:
Hello, I have the Nexus 4 I am running 4.2.2 and I'm rooted I was going to update the other day to 4.3 but it didn't work. Cos this be due to a custom recovery? I am on stock android and i was unrooted at the time.
I was also wondering if there are any good root methods out there I have heard a lot of problems with rooting on 4.3?
Just would like some opinions?
Thanks guys
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
There's not really any problems just gotta make sure you're following instructions properly. All you need to do is obviously just unlock your device, then push recovery to it then flash root. Obviously the are more in the between steps.
Sent from my SPH-L900 using xda app-developers app
XxLostSoulxX said:
There's not really any problems just gotta make sure you're following instructions properly. All you need to do is obviously just unlock your device, then push recovery to it then flash root. Obviously the are more in the between steps.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
do you have any idea why it wouldn't update over air? I was unrooted but did have CWM recovery. would that be the reason?
and ok thats good to know thanks and thanks for the video reference.
Hey guys quick question my n4 is rooted and running cm10.1.3. I never bothered to upgrade to 4.3, so my radio, kernel and bootloader are stock 4.2.2. Is it better to get the ota update and be up on things or flash stock kernel, boot loader and radio for 4.4 when ever there available? Or maybe factory image?
Sent from my Nexus 4 using xda app-developers app
Just flash the stock images for kit Kat when they are available, right now back up all your data
Sent from my Nexus 4 using xda app-developers app
sacramento458 said:
Hey guys quick question my n4 is rooted and running cm10.1.3. I never bothered to upgrade to 4.3, so my radio, kernel and bootloader are stock 4.2.2. Is it better to get the ota update and be up on things or flash stock kernel, boot loader and radio for 4.4 when ever there available? Or maybe factory image?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
my friend as this will pop up all over the forum the best thing to do is just wait for a rooted version to show up. I did not upgrade my bootloader and I have not had any issues with 4.3 which mind you is a great running OS you should try it.
I dont understand having root then unrooting to flash stock which you obviously dont like since you run cm and then wait to root it all over again to back an upgraded rooted version of cm...
aanonymoushuman said:
Just flash the stock images for kit Kat when they are available, right now back up all your data
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Alright thanks will do
Sent from my Nexus 4 using xda app-developers app
Question on the way for the custom recovery+kernel guys on 4.3 what is the best to upgrade besides wiping your entire phone and flashing the stock images entirely?.
I think i know 2 ways just not sure they are recommended, 1st is flashing stock kernel + returning recovery to stock (should get OTA)
2nd is flashing only the system.img and the bootloader me thinks.
Feel free to verify this.
:good:
playya said:
my friend as this will pop up all over the forum the best thing to do is just wait for a rooted version to show up. I did not upgrade my bootloader and I have not had any issues with 4.3 which mind you is a great running OS you should try it.
I dont understand having root then unrooting to flash stock which you obviously dont like since you run cm and then wait to root it all over again to back an upgraded rooted version of cm...
Click to expand...
Click to collapse
You make a lot of sense ,its more of curiosity and so I won't brick my nexus. So I can get away with not upgrading my bootloader for 4.4?
What about kernel, do I need to update that for 4.4 or is that judgement call?
Sent from my Nexus 4 using xda app-developers app
sacramento458 said:
You make a lot of sense ,its more of curiosity and so I won't brick my nexus. So I can get away with not upgrading my bootloader for 4.4?
What about kernel, do I need to update that for 4.4 or is that judgement call?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
you are asking questions that trial and error are going to figure out for us. Kernels of course if you are on a 4.4 rom you would use a 4.4 kernel. Upgrading your bootloader may or may not be needed but we wont know until kitkat starts popping. everyone said you needed to upgrade bootloader for 4.3 but I have never had any issue at all.... Just wait it out and read read read
Tricepz said:
Question on the way for the custom recovery+kernel guys on 4.3 what is the best to upgrade besides wiping your entire phone and flashing the stock images entirely?.
I think i know 2 ways just not sure they are recommended, 1st is flashing stock kernel + returning recovery to stock (should get OTA)
2nd is flashing only the system.img and the bootloader me thinks.
Feel free to verify this.
:good:
Click to expand...
Click to collapse
Not to sure but as long as you're on stock ROM and stock kernel you should be fine although I don't know if custom recovery keeps you from getting update.
Sent from my Nexus 4 using xda app-developers app
playya said:
you are asking questions that trial and error are going to figure out for us. Kernels of course if you are on a 4.4 rom you would use a 4.4 kernel. Upgrading your bootloader may or may not be needed but we wont know until kitkat starts popping. everyone said you needed to upgrade bootloader for 4.3 but I have never had any issue at all.... Just wait it out and read read read
Click to expand...
Click to collapse
Thanks for the clarification, appreciate the support.
Sent from my Nexus 4 using xda app-developers app
sacramento458 said:
Thanks for the clarification, appreciate the support.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
no problem hopefully you can pass it on to others like you who may be unsure of what to do...
playya said:
no problem hopefully you can pass it on to others like you who may be unsure of what to do...
Click to expand...
Click to collapse
Absolutely bro
You do have to be on stock recovery, stock bootloader for the update to go thru properly otherwise it'll fail.
Tricepz said:
Question on the way for the custom recovery+kernel guys on 4.3 what is the best to upgrade besides wiping your entire phone and flashing the stock images entirely?.
I think i know 2 ways just not sure they are recommended, 1st is flashing stock kernel + returning recovery to stock (should get OTA)
2nd is flashing only the system.img and the bootloader me thinks.
Feel free to verify this.
:good:
Click to expand...
Click to collapse
If you are still on stock rom and you just have custom kernel+recovery, U could do the following for not using any current apps or files.
- Wait till your favorite Toolkit (e.g Wug) get updated for 4.4 and then download the official factory rom.
- Extract it and keep all separate zips, like radio, bootloader,system etc.
- Unroot and flash stock kernel
- Flash all previous zips, EXCEPT user.img which will delete everything
- Reroot and U r ready to flash again custom kernel
Maybe a noob question but my n4 is rooted. Will this cause any problems withe the update?
Sent from my Nexus 4 using xda app-developers app
RASTAVIPER said:
If you are still on stock rom and you just have custom kernel+recovery, U could do the following for not using any current apps or files.
- Wait till your favorite Toolkit (e.g Wug) get updated for 4.4 and then download the official factory rom.
- Extract it and keep all separate zips, like radio, bootloader,system etc.
- Unroot and flash stock kernel
- Flash all previous zips, EXCEPT user.img which will delete everything
- Reroot and U r ready to flash again custom kernel
Click to expand...
Click to collapse
The original stock kernel of 4.3 is on the bootloader.img on the google source code aye?
Thanks, now we just need to wait for the official 4.4 on google's developers.
Tricepz said:
The original stock kernel of 4.3 is on the bootloader.img on the google source code aye?
Thanks, now we just need to wait for the official 4.4 on google's developers.
Click to expand...
Click to collapse
Here a direct link for stock kernel 0.84 from JWR66V factory image
http://d-h.st/cIJ
Hello,
My phone has already had the radio upgraded to latest so it can run 4.3. I am rooted, have TWRP 2.6.3.0, will I be ok to flash the PA 4.4 and gapps? I keep posts about folks losing their sdcard data and their custom recovery being removed (not sure how!).
Thanks.
Schur1k said:
Maybe a noob question but my n4 is rooted. Will this cause any problems withe the update?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you have a custom recover?
Sent from my Nexus 4 using xda app-developers app
Schur1k said:
Maybe a noob question but my n4 is rooted. Will this cause any problems withe the update?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you have a custom recovery?
Sent from my Nexus 4 using xda app-developers app
maritimesbob said:
Hello,
My phone has already had the radio upgraded to latest so it can run 4.3. I am rooted, have TWRP 2.6.3.0, will I be ok to flash the PA 4.4 and gapps? I keep posts about folks losing their sdcard data and their custom recovery being removed (not sure how!).
Thanks.
Click to expand...
Click to collapse
I'm sure that radio doesn't affect your ability to flash certain ROMs so you shouldn't have a problem flashing 4.4. As far as losing SD data not sure how that's happening.
Sent from my Nexus 4 using xda app-developers app
Sorry I'm not too educated in the whole root thing, I really want knock Code on my g2, but I'm currently rooted. Is there any safe way to update to get it without losing root?
Sent from my LG-D800 using XDA Free mobile app
nikushx said:
Sorry I'm not too educated in the whole root thing, I really want knock Code on my g2, but I'm currently rooted. Is there any safe way to update to get it without losing root?
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Flash any KK ROM. I can recommend Pardus Rom
What if I'm already on kitkat but original rom
Sent from my LG-D800 using XDA Free mobile app
nikushx said:
What if I'm already on kitkat but original rom
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
People say d800 upgrade is here - with knock code support.
Today d80020u update started rolling out to d800 and it includes knock code, just wait until you get it
Sent from my Potato powered G2 D800
I am rooted without recovery, but when i tried to install it, I got an error. Is there a way to install it without any issues?
mertbba said:
I am rooted without recovery, but when i tried to install it, I got an error. Is there a way to install it without any issues?
Click to expand...
Click to collapse
if you have modified anything on the phone(mods/xposed/debloat) ota fails because it knows you rooted, returning everything back to complete stock usually fixes the error
Hello xda community.
i just purchased a galaxy s4 from a friend he he updated it to kitkat 4.4.2. i rooted itbut im having an issue installing a custom recovery. i tried the cmd method, the twrp apps on the market but although it says succesfull when i try to reboot into recovery it goes onto download mode. Someone please help me. i know samsung has a security system for the boatloader and i dont care tripping the securty system because im not with at&t nor on contract.
please help me i want to flash cm11 so bad.
androidfine16 said:
Hello xda community.
i just purchased a galaxy s4 from a friend he he updated it to kitkat 4.4.2. i rooted itbut im having an issue installing a custom recovery. i tried the cmd method, the twrp apps on the market but although it says succesfull when i try to reboot into recovery it goes onto download mode. Someone please help me. i know samsung has a security system for the boatloader and i dont care tripping the securty system because im not with at&t nor on contract.
please help me i want to flash cm11 so bad.
Click to expand...
Click to collapse
Try this one. It's what I use.
http://forum.xda-developers.com/showthread.php?t=2427125
Apoplectic1 said:
Try this one. It's what I use.
http://forum.xda-developers.com/showthread.php?t=2427125
Click to expand...
Click to collapse
I've seen that but I heard/read if you mess up that's it for your phone. Plus toy never truly have a Susie stable recovery. Seems like a lot of risk
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
androidfine16 said:
I've seen that but I heard/read if you mess up that's it for your phone. Plus toy never truly have a Susie stable recovery. Seems like a lot of risk
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
I can't say I have ever heard of anyone messing up the installation process before. It's load the apk to your SD card, install it to your phone and then tapping the install button once you open it. That's it.
As long as your root method installs busybox and your SU app disables Knox, you should be fine.
androidfine16 said:
Hello xda community.
i just purchased a galaxy s4 from a friend he he updated it to kitkat 4.4.2. i rooted itbut im having an issue installing a custom recovery. i tried the cmd method, the twrp apps on the market but although it says succesfull when i try to reboot into recovery it goes onto download mode. Someone please help me. i know samsung has a security system for the boatloader and i dont care tripping the securty system because im not with at&t nor on contract.
please help me i want to flash cm11 so bad.
Click to expand...
Click to collapse
Trying to load a custom recovery on a locked bootloader could mess up your phone. Safestrap was made for our phones. Read up a bit you'll see we can't do normal custom recoveries and we can't flash normal roms cause we're locked. Only thing we can do is root and safe strap. I'll suggest odin nb1 update to nc1 root. The reason I say odin to nb1 is because right now you don't have a recovery at all due to you trying to install cwm or twrp.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Apoplectic1 said:
I can't say I have ever heard of anyone messing up the installation process before. It's load the apk to your SD card, install it to your phone and then tapping the install button once you open it. That's it.
As long as your root method installs busybox and your SU app disables Knox, you should be fine.
Click to expand...
Click to collapse
So I'll be able to install cm 11. Without any complications?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I don't have a current recovery. Your right about that . How do I fix it
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
androidfine16 said:
So I'll be able to install cm 11. Without any complications?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Do you have an AT&T S4? If so then no. It will not load if you try. Until someone figures how to crack the locked bootloader, we are stuck with ROMs that use stock Samsung (you'll also hear them referred to as TouchWiz or TW) kernels. I believe CM uses their own custom one.
I am able to use the Google Edition one because a user modified it to work on aTouchWiz kernel, and even then things like USB file transfer does not work.
I do not believe anyone has done the same for CM.
androidfine16 said:
I don't have a current recovery. Your right about that . How do I fix it
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
You need to odin nb1 (flash back to stock) this will put your recovery back.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Apoplectic1 said:
Do you have an AT&T S4? If so then no. It will not load if you try. Until someone figures how to crack the locked bootloader, we are stuck with ROMs that use stock Samsung (you'll also hear them referred to as TouchWiz or TW) kernels. I believe CM uses their own custom one.
I am able to use the Google Edition one because a user modified it to work on aTouchWiz kernel, and even then things like USB file transfer does not work.
I do not believe anyone has done the same for CM.
Click to expand...
Click to collapse
Yes I have the at& t s4. And that sucks I was really looking forward to flashing cm 11s. I don't care for the knox being ticked off being that I'm on no contract. Do you think I can use Odin or something to revert back to 4.2 safely without bricking the device. I hate touch wiz. And the battery drains quickly plus the phone gets hot when used for a while
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
drock212 said:
You need to odin nb1 (flash back to stock) this will put your recovery back.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Won't this look the bootloader cause I read downgrades are practically unsafe on this device. If not than I'd much rather go back to 4.2 so I can load a custom recovery being that u don't mind tripping knox. So long that it doesn't Brick or render the phone use less
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
androidfine16 said:
Won't this lock the bootloader cause I read downgrades are practically unsafe on this device. If not than I'd much rather go back to 4.2 so I can load a custom recovery being that u don't mind tripping knox. So long that it doesn't Brick or render the phone use less
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
androidfine16 said:
Won't this look the bootloader cause I read downgrades are practically unsafe on this device. If not than I'd much rather go back to 4.2 so I can load a custom recovery being that u don't mind tripping knox. So long that it doesn't Brick or render the phone use less
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Odining back to NB1 will not trip Knox. Also, I believe downgrading to 4.2 will not touch your bootloader, if it were that easy we'd all be rocking CM.
You could run this ROM: http://forum.xda-developers.com/showthread.php?t=2767026
Its technically not a TW ROM, but it has its quirks. It was never intended to work on locked bootloader phones, but it has been retrofitted on to them.
Wrote this if you would like a guide on how I got 4.4.4 version up and running, it's kind of tricky.
androidfine16 said:
Won't this look the bootloader cause I read downgrades are practically unsafe on this device. If not than I'd much rather go back to 4.2 so I can load a custom recovery being that u don't mind tripping knox. So long that it doesn't Brick or render the phone use less
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Nb1 and nc1 are the same. Nb1 is just a small update over nb1, there isn't even a tar file for nc1 because it's such a small update. You won't be able to odin back to anything prior to nb1 unfortunately without bricking. Now I do understand the hatred of touchwiz but once you're rooted you're able to delete a lot of the garbage bloatware put on by Samsung and AT&T. This makes the phone so much better along with super long battery life. I've been able to get 4.5 hours of on screen time and about 16 - 17 hours of off the plug time like this.
When deleting bloat you can easily Google and find lists of what people have deleted off their phones using titanium backup (amazing app, let's your freeze or delete what you don't want). Also one thing I found out which is dumb. Deleting Samsung hub breaks auto rotation (what one has to do with the other I'll never know) but you can download the file needed to fix that here
http://forum.xda-developers.com/showthread.php?p=51260826
I've had my touchwized sgs4 for about 3 weeks now and can say I'm not as upset with it as I thought I would be. Let me know if you have any questions about certain things. I've found a lot of workarounds and little edits here and there to get my phone a lot closer to how I want it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Are there people working in unlocking our bootloader because this thing is really annoying .
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Ps: No one answered my question. If I don't care for tripping the bootloader being that I'm on no contract. Is their a way to trip the flash counter and get on a recovery? I don't care for Samsung security knox or their bootloader security.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
androidfine16 said:
Ps: No one answered my question. If I don't care for tripping the bootloader being that I'm on no contract. Is their a way to trip the flash counter and get on a recovery? I don't care for Samsung security knox or their bootloader security.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Nope. Bootloader and knox are completely different. Knox will just give annoying messages once tripped. Bootloader without unlock we're pretty much dead in the water. There has been some talk about ways to possibly unlock the bootloader so it's definitely being worked on. I've also read that the black hat even (hackers convention) might have something promising. Also anything that is done on the s5 could very well apply to the s4. It's all just a matter of time
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
Nope. Bootloader and knox are completely different. Knox will just give annoying messages once tripped. Bootloader without unlock we're pretty much dead in the water. There has been some talk about ways to possibly unlock the bootloader so it's definitely being worked on. I've also read that the black hat even (hackers convention) might have something promising. Also anything that is done on the s5 could very well apply to the s4. It's all just a matter of time
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds great that the s5 and s4 integrate . Also there's a bunch of stuff online which shows how to disable certain aspects of the bootloader using linux (Ubuntu) . Do you think that'll work. It's a huge risk.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
androidfine16 said:
Sounds great that the s5 and s4 integrate . Also there's a bunch of stuff online which shows how to disable certain aspects of the bootloader using linux (Ubuntu) . Do you think that'll work. It's a huge risk.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
If it hasn't been done to give us anything I wouldn't do it. Only thing we have right now is safestrap. Which is similar to a dual boot
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
If it hasn't been done to give us anything I wouldn't do it. Only thing we have right now is safestrap. Which is similar to a dual boot
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Similar to dual boot but can't load any rom you want on it
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Whenever I try to install a custom rom with Safestrap, it doesn't even get to the boot animation; it just goes to a black screen. The touch lights on the bottom of the phone are lit for like 5 seconds, then go out. What do I do?
48 views, no replies... anybody know a fix?
I don't know what the problem is. But what I'd do is flash the stock firmware in Odin again. Then root and reinstall safestrap and try again. But it would help to know what roms you tried to install. You can only install roms that specifically work with safestrap
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I don't know what the problem is. But what I'd do is flash the stock firmware in Odin again. Then root and reinstall safestrap and try again. But it would help to know what roms you tried to install. You can only install roms that specifically work with safestrap
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I still have the stock firmware. The roms I tried were two different Google Edition roms, Kangpop, and Hyperdrive.
OrbitGum22 said:
I still have the stock firmware. The roms I tried were two different Google Edition roms, Kangpop, and Hyperdrive.
Click to expand...
Click to collapse
I don't think either one of those work with safestrap
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I don't think either one of those work with safestrap
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Could you maybe redirect me to some that do? Or what other recovery can I use?
OrbitGum22 said:
Could you maybe redirect me to some that do? Or what other recovery can I use?
Click to expand...
Click to collapse
First you need to use safestrap as your recovery. http://forum.xda-developers.com/showthread.php?p=56453100
Then you can only flash touch wiz based roms. http://forum.xda-developers.com/showthread.php?p=53758227
All of this can be found in the general forum
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
First you need to use safestrap as your recovery. http://forum.xda-developers.com/showthread.php?p=56453100
Then you can only flash touch wiz based roms. http://forum.xda-developers.com/showthread.php?p=53758227
All of this can be found in the general forum
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Even TW based roms give me a black screen... guess I'll have to stick with stock...
Unless anybody else has any ideas?