Is there any way to get the s4 camera app to work on a nexus 4? And how can I get it to work? I downloaded the stock s4 rom, found the camera app, tried to install it and it didn't work. I wasn't surprised though lol. So is there a way to get it to install?
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
chromium96 said:
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
Click to expand...
Click to collapse
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
NuckFuggets said:
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
Click to expand...
Click to collapse
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
I don't know about brick, but it would definitely not boot.
Sent from an N4 blessed with AOKP and sanctified by Faux123!
NuckFuggets said:
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
Click to expand...
Click to collapse
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
exb0 said:
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
Click to expand...
Click to collapse
Oh I see. Well I wasn't planning on doing it anyway but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
NuckFuggets said:
Oh I see. Well I wasn't planning on doing it anyway but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
Click to expand...
Click to collapse
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.
Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
exb0 said:
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.
Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
Click to expand...
Click to collapse
Oh I see. What if the two phones have the same hardware? Then would you be able to?
NuckFuggets said:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
Click to expand...
Click to collapse
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
chromium96 said:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
Click to expand...
Click to collapse
Oh ok. That sucks :/
NuckFuggets said:
Oh ok. That sucks :/
Click to expand...
Click to collapse
That's why each device on XDA has their own little section call home.
Sent from my Nexus 4 using Tapatalk 2
chromium96 said:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
Click to expand...
Click to collapse
Probably the way they chose to assign the partitions on the device. It would be nice if there was a standard that everyone followed, but oh well.
NuckFuggets said:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
Click to expand...
Click to collapse
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
Sent from my Nexus 7 using xda premium
rayiskon said:
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo
NuckFuggets said:
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo
Click to expand...
Click to collapse
in that case it shouldn't be called a Nexus anymore
Related
can anyone here give me the drivers for our adreno 320 gpu, i am hoping that reinstalling those drivers may fix my problem
thanks
Don't want to fresh install stock room and back up with titanium?
Sent from my Nexus 4 using xda app-developers app
Kick-Ass Joe said:
Don't want to fresh install stock room and back up with titanium?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What he said. If your issue is software related, that'll fix it.
You can't just install drivers like you can on windows. It doesn't work that way...flash the stock ROM/kernel images and that should fix the issue if its software related.
Sent from my Nexus 4 using Tapatalk 2
Kick-Ass Joe said:
Don't want to fresh install stock room and back up with titanium?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
already did that
estallings15 said:
What he said. If your issue is software related, that'll fix it.
Click to expand...
Click to collapse
i think it really is a hardware problem
Serious_Beans said:
You can't just install drivers like you can on windows. It doesn't work that way...flash the stock ROM/kernel images and that should fix the issue if its software related.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
already did that and the problem still persist
RMA it
estallings15 said:
RMA it
Click to expand...
Click to collapse
sadly i cant rma it, i only got the phone from my mother in UK and i'm in philippines
Serious_Beans said:
You can't just install drivers like you can on windows. It doesn't work that way...flash the stock ROM/kernel images and that should fix the issue if its software related.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sure it does.
Take the appropriate files, push then into their folders, load the module and it works.
if you reinstall a stock rom, does the gpu drivers is also reinstalled?
Are you using a stock rom without any mods? That issue looks exactly like what happened to mine when I modified the background images in navigation bar xml files of systemui.apk.
Either way try flashing the stock image and see if it still happens
whenever you have problems always revert to stockrom and see if issue persists.
kamp said:
Are you using a stock rom without any mods? That issue looks exactly like what happened to mine when I modified the background images in navigation bar xml files of systemui.apk.
Either way try flashing the stock image and see if it still happens
Click to expand...
Click to collapse
republicano said:
whenever you have problems always revert to stockrom and see if issue persists.
Click to expand...
Click to collapse
already did that and it still persist
If you can screenshot it, it is most likely a software issue. Reflash the stock rom. :good:
dannaoj said:
already did that and it still persist
Click to expand...
Click to collapse
Then it's a hardware fault. Rma is your only option
Do you have any edited thing on your nav bar? It seems only nav bar messed up. Either way it would be better to flash stock images
Some people seem to think a factory reset is the same thing as reverting to stock. It's not. Make sure you did it correctly.
estallings15 said:
Some people seem to think a factory reset is the same thing as reverting to stock. It's not. Make sure you did it correctly.
Click to expand...
Click to collapse
how?
dannaoj said:
how?
Click to expand...
Click to collapse
Factory resetting does not change or remove system files. Reflashing stock ROM will renew the system files and such. Your problem is with your system that's somehow corrupted. Search the forums on how to do it.
Sent from my Nexus 4 using Tapatalk 2
Saw that this might be helpful to you. In the general forums. Here.
I am not responsible for anything that happens though. Good luck. :good:
tried reflashing stock rom but it still happen
I noticed that looking at a blank white page on my Nexus 4 that it wasn't as white as I would love. So I searched and found out I could calibrate it.
I prefer not to use a different kernel, so I would like to use this app: https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
Question #1: Is that app good? Like would it fix my problem?
Question #2: I would like to get updates from Google as well, how does that work with a rooted phone? Will I lose my calibration once I update?
That's all the questions I have.
Thanks!
thenerdal said:
I noticed that looking at a blank white page on my Nexus 4 that it wasn't as white as I would love. So I searched and found out I could calibrate it.
I prefer not to use a different kernel, so I would like to use this app: https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
Question #1: Is that app good? Like would it fix my problem?
Question #2: I would like to get updates from Google as well, how does that work with a rooted phone? Will I lose my calibration once I update?
That's all the questions I have.
Thanks!
Click to expand...
Click to collapse
Yes, check his thread for the kernel a well. http://forum.xda-developers.com/showthread.php?t=2002782
A custom rom will probably give you the Google updates faster. But, you'll be able to get updates as well, yes.
Vangelis13 said:
Yes, check his thread for the kernel a well. http://forum.xda-developers.com/showthread.php?t=2002782
A custom rom will probably give you the Google updates faster. But, you'll be able to get updates as well, yes.
Click to expand...
Click to collapse
What's a kernel? Is it like a Linux Kernel? This seems complicated to me. :| Like if I mess up, I'll mess up my phone. What does this kernel do?
And yeah, I was looking at custom rom's. cyanogenmod specifically, but they're doing nightly updates, so I'm worried that if I do use that rom, it'll be buggy and mess up my phone.
thenerdal said:
What's a kernel? Is it like a Linux Kernel? This seems complicated to me. :| Like if I mess up, I'll mess up my phone. What does this kernel do?
And yeah, I was looking at custom rom's. cyanogenmod specifically, but they're doing nightly updates, so I'm worried that if I do use that rom, it'll be buggy and mess up my phone.
Click to expand...
Click to collapse
Oh boy, you have some catching up to do.. Start here http://forum.xda-developers.com/showthread.php?t=2010338
Roms aren't buggy nowadays, you'll be ok.
Vangelis13 said:
Oh boy, you have some catching up to do.. Start here http://forum.xda-developers.com/showthread.php?t=2010338
Roms aren't buggy nowadays, you'll be ok.
Click to expand...
Click to collapse
I've decided to root, but not use a custom rom. Is that okay? I just want to use it to calibrate my screen using the app I saw. And Maybe. Maybe use roms later.
Excited about this.
thenerdal said:
I've decided to root, but not use a custom rom. Is that okay? I just want to use it to calibrate my screen using the app I saw. And Maybe. Maybe use roms later.
Excited about this.
Click to expand...
Click to collapse
Ok, as in do you have our permission..?
He*l yeah mate, you decide what & how big steps forward you take!
Vangelis13 said:
Ok, as in do you have our permission..?
He*l yeah mate, you decide what & how big steps forward you take!
Click to expand...
Click to collapse
One more question. I have tmobile insurance, if I root it, will they replace it still if something happens?
thenerdal said:
One more question. I have tmobile insurance, if I root it, will they replace it still if something happens?
Click to expand...
Click to collapse
Can't answer that I'm not afraid.
You can always unroot though if phone works. Usually they care about the bootloader being unlocked..
Vangelis13 said:
Can't answer that I'm not afraid.
You can always unroot though if phone works. Usually they care about the bootloader being unlocked..
Click to expand...
Click to collapse
Damn, I know that. Just if the screen is unresponsive, is there a way they will be able to find out I rooted?
thenerdal said:
Damn, I know that. Just if the screen is unresponsive, is there a way they will be able to find out I rooted?
Click to expand...
Click to collapse
If the phone turns on they can see if it is bootloader unlocked or not. If it doesn't, they can't tell.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
If the phone turns on they can see if it is bootloader unlocked or not. If it doesn't, they can't tell.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Recommend me a way to root please. I tried this: http://www.youtube.com/watch?feature=player_embedded&v=g88PPZyvfDI
But the when i plugged in my device in fastboot with usb debugging on, Windows 7 said it couldn't install the drivers correctly. So I didn't continue.
thenerdal said:
I noticed that looking at a blank white page on my Nexus 4 that it wasn't as white as I would love. So I searched and found out I could calibrate it.
I prefer not to use a different kernel, so I would like to use this app: https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
Question #1: Is that app good? Like would it fix my problem?
Question #2: I would like to get updates from Google as well, how does that work with a rooted phone? Will I lose my calibration once I update?
That's all the questions I have.
Thanks!
Click to expand...
Click to collapse
you cant calibrate without a kernel. the google kernel does not expose the needed interfaces and rgb calibration will get you no where. so, no, it will most likely not fix your problem. if you install a custom kernel, then yes, it will solve your problems.
in case youre interested, i compiled a bunch of calibrated google stock kernels for 4.2.2:
http://forum.xda-developers.com/showthread.php?t=2136295
with these simple rgb calibration will be enough.
First of all if you are on the updated 4.2.2 stock kernel you wont be able to use display control apps to change your gamma settings. Google removed access to change the gamma settings on the stock kernel. So you will have to flash a custom kernel.
You can flash a custom kernel and remain on the stock rom. But will have to return back to the stock kernel in order to receive the OTA updates. There are many kernels so just look around in the development sections or even better search videos.
In terms of rooting many will advise you to manually do it yourself as this is the best way and it will increase your understanding of how everything is done. However, not everyone is confident even after learning how everything is donw and would rather use toolkits to prevent mishaps. I would recommend Wugfresh's toolkit.
So the app i used worked! WAY BETTER. What does gamma do?
Also, I rooted. Now what? How do I backup? I want CyanogenMod, but the monthly version, wondering how I can do that.
Thanks.
thenerdal said:
So the app i used worked! WAY BETTER. What does gamma do?
Also, I rooted. Now what? How do I backup? I want CyanogenMod, but the monthly version, wondering how I can do that.
Thanks.
Click to expand...
Click to collapse
I hate to have to say it like that, directly, but there's no other way around it; search & read up mate!
"Now what"..? :what:
No one is gonna hold your hand and walk you through it step by step, you have to do it yourself. There are guides everywhere, check the Stickies in General.
Vangelis13 said:
I hate to have to say it like that, directly, but there's no other way around it; search & read up mate!
"Now what"..? :what:
No one is gonna hold your hand and walk you through it step by step, you have to do it yourself. There are guides everywhere, check the Stickies in General.
Click to expand...
Click to collapse
True, but sometimes guides miss somethings.
thenerdal said:
True, but sometimes guides miss somethings.
Click to expand...
Click to collapse
No, they don't. The guides that you find in the Stickies are (for their purpose) complete.
It's a phone, won't bite you.. Play around a bit!
Does anyone know of a stock flashable ROM without Root and Busybox?
I'm aware of the thread guiding people on going back to factory but I don't want to do that. I want to be able to just flash a Rooted ROM if I want one and flash back to standard unrooted if I want using TWRP.
My reason behind this that I spend a lot of time on the train at the minute so decided to get Sky Go. Unfortunately it detects that the device is rooted and won't run.
There are a few threads around the net with scripts and suggestions but nothing seems to work for me.
I don't think there are any..... Hmmm.
Sent from my Nexus 4 using Tapatalk 2
You can flash the stock ROM with fastboot but not from within recovery. Get it here: https://developers.google.com/android/nexus/images
I could make one I suppose, wouldn't take long at all...
EddyOS said:
I could make one I suppose, wouldn't take long at all...
Click to expand...
Click to collapse
If you could do that it would be great.
I was just looking at the tutorial to bake it myself but having issues with Cygwin. Much quicker and easier if you did it.
Owe you one.
I use Linux so it won't take long. You literally want a flashable stock ROM, no changes whatsoever?
EddyOS said:
I use Linux so it won't take long. You literally want a flashable stock ROM, no changes whatsoever?
Click to expand...
Click to collapse
Exactly. I use a standard stock rooted ROM usually.
Just realised I don't actually use root for anything at the minute but likely will do in the future.
Thanks again.
I'll try and do it this afternoon but if not this evening once back at home
Uploading at the mo, it's literally the stock ROM dumped into the kitchen and cooked out with no change whatsoever
EddyOS said:
Uploading at the mo, it's literally the stock ROM dumped into the kitchen and cooked out with no change whatsoever
Click to expand...
Click to collapse
Excellent. Thanks buddy.
I think I'll play with it too and keep the zip stored just so I have it.
Thanks
Sent from my Nexus 4 using Tapatalk 2
Here you go. I've not tested but it should be fine (let me know if it's not)
https://www.yousendit.com/download/UVJnSU5IQVNiV3dPd3NUQw
Working perfectly so far mate! Sky Go is working and no wipe was required.
Owe you one mate. Top work. Thank you.
Good to hear! You're welcome
EddyOS said:
I could make one I suppose, wouldn't take long at all...
Click to expand...
Click to collapse
Very cool that you've done this, but I should give a word of caution: there are some problems that wiping via fastboot will fix, but installing a flashable stock .zip won't fix. For example, when a 16GB phone thinks it's only 8GB. (I have reason to believe that there are other problems that can only be fixed in this way, but I can't prove it. :silly
That's not something the OP cared about, he just needed to 'unroot' to use a TV app that checks for root access
He should give this app a try
http://forum.xda-developers.com/showthread.php?t=1241517.
Sent from my Nexus 4 using XDA Premium HD app
trapdogg said:
He should give this app a try
http://forum.xda-developers.com/showthread.php?t=1241517.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
It doesn't work - none of the 'root hiding' apps work with Sky Go
trapdogg said:
He should give this app a try
http://forum.xda-developers.com/showthread.php?t=1241517.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that.
I tried a script that was published on the net to remove root and busybox.
I tried removing root and busybox manually.
I tried flashing stock kernal
I tried several other apps.
A flashable stock rom was my last resort as I was under the impression that I'd need to wipe and I didn't want to do that. I just tried it without wiping on the off chance that it worked and it did, so problem solved.
None of my Apps were using Root so I thought I'd get rid of it completely but wanted the option to flash CM10.1 once Bluetooth MAP profile is fixed and working without having to go through putting TWRP on again.
It's all in the OP and posts following that.
EddyOS saw what I was after and offered to help. He's a great dude.
Just for learning purposes, how come no one has made a flashable stock zip until now? Wouldn't it just be like any custom rom but instead its just stock?
Any word a Nightly or M Snapshot for the ATT G2?
Symbian_Black said:
Any word a Nightly or M Snapshot for the ATT G2?
Click to expand...
Click to collapse
ROMs take time to port. It isn't as simple as just changing a few config files and recompiling. There are proprietary drivers, etc. that have to be figured out first.
Be patient. It'll come.
Well no offense but until they create the port and include the features from stock your losing functionality not gaining speed.
Sent from my VS980 4G using XDA Premium 4 mobile app
Methinks that we all need to show a little patience. Feel free to correct me if I am wrong, but it is my belief that until we can unlock our bootloaders, we cannot flash third-party ROMs, no?
MarkAtHome said:
Methinks that we all need to show a little patience. Feel free to correct me if I am wrong, but it is my belief that until we can unlock our bootloaders, we cannot flash third-party ROMs, no?
Click to expand...
Click to collapse
We already have Loki, we can flash roms. IM currently running CleanRom on my G2.
tdevaughn said:
We already have Loki, we can flash roms. IM currently running CleanRom on my G2.
Click to expand...
Click to collapse
We do? I will search for it, as I did not find it during my regular reading. Thanks.
MarkAtHome said:
We do? I will search for it, as I did not find it during my regular reading. Thanks.
Click to expand...
Click to collapse
Look here, http://forum.xda-developers.com/showthread.php?t=2449670
part of the TWRP thread. The recovery is loki'd, but I kept the loki-master zip as well.. just to be safe
MarkAtHome said:
Methinks that we all need to show a little patience. Feel free to correct me if I am wrong, but it is my belief that until we can unlock our bootloaders, we cannot flash third-party ROMs, no?
Click to expand...
Click to collapse
No.
Also there is already a CM10.1 alpha build available. It doesnt do anything though and you dont even have data on it. As others said we need to get proprietary drivers and such sorted out to have anything usable. It will happen, just takes time. Hopefully Nexus 5 rumors are true because if so we will have a ton of great AOSP support really easily on this phone then too since drivers would be nearly (completely?) identical.
Bout how long do you guys think? The S4 was pretty fast to get a stable Cyanogen mod up
screw cm Omnirom is coming lol
I found a *****en ROM named Nameless in the f/g variants of the Note 4. Was all psyched to flash it and play with it only to realize there's data issues. Is there any body who knows how to fix the data issue or maybe properly port this to our device?
http://forum.xda-developers.com/showthread.php?t=3220738 there ya be sir
Sent from my SM-N910W8 using Tapatalk
kkeith said:
http://forum.xda-developers.com/showthread.php?t=3220738 there ya be sir
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
I tried that and was unable to get it to get data. It really stumped me
Edit: Oh damn. I realized I flashed the wrong kernel and tried again. after flashing the data fix I got data for a second before the phone rebooted. I wiped everything but data when I flashed from my stock rom
Naturesretard said:
I tried that and was unable to get it to get data. It really stumped me
Edit: Oh damn. I realized I flashed the wrong kernel and tried again. after flashing the data fix I got data for a second before the phone rebooted. I wiped everything but data when I flashed from my stock rom
Click to expand...
Click to collapse
I have managed to get the rom up and running.....for the most part. Only downside so far is I can't get Netflix to work. It just loads forever
Naturesretard said:
I have managed to get the rom up and running.....for the most part. Only downside so far is I can't get Netflix to work. It just loads forever
Click to expand...
Click to collapse
Google will be your friend on that one, i cant remember off the top of my head but there is a file you need to delete
Sent from my SM-N910W8 using Tapatalk
kkeith said:
Google will be your friend on that one, i cant remember off the top of my head but there is a file you need to delete
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
T_T I'm not sure of what to search for. For branded roms it's relatively easy, but as an INT'L ROM I'm not sure if my process would work. So it's just some obscure file? I was thinking it may be because I flashed something wrong. No chance you can remember where you think you may have seen it? Like xda or another site?
Naturesretard said:
T_T I'm not sure of what to search for. For branded roms it's relatively easy, but as an INT'L ROM I'm not sure if my process would work. So it's just some obscure file? I was thinking it may be because I flashed something wrong. No chance you can remember where you think you may have seen it? Like xda or another site?
Click to expand...
Click to collapse
I went back to the beanstalk forum and just so happened across the fix just now haha
Go to system/vendor/lib and delete liboemcrypto.so and reboot
Sent from my SM-N910W8 using Tapatalk
kkeith said:
I went back to the beanstalk forum and just so happened across the fix just now haha
Go to system/vendor/lib and delete liboemcrypto.so and reboot
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
OMG You're a lifesaver. It worked! Thanks!
Now to create some more threads or posts in the Nameless ROM section; Upon reflashing my backup to perform this fix, I now have random system information on my lockscreen and notification bar. Oh well.
Thanks again!
Naturesretard said:
OMG You're a lifesaver. It worked! Thanks!
Now to create some more threads or posts in the Nameless ROM section; Upon reflashing my backup to perform this fix, I now have random system information on my lockscreen and notification bar. Oh well.
Thanks again!
Click to expand...
Click to collapse
I have been trying my hardest, asking on every forum i can find, to find out how to get the beta release of emotion kernel R24 for N910T. Not one single response.....but anyway. It is my understanding that the latest release of Emotion Revolution rom has r24 kernel as an option in aroma. My question is this; would it be possible to unzip the R23 kernel zip for N910T and replace only the R24 boot image from the emotion rom and leave all the other system files. Or would that be a really bad idea? Ha. I just want the kernel on Tekhds URv7. I know this is possible a really stupid question but I'm just now beginning to learn all the technical details of these things. And I will say ahead of time that any answer will be beneficial because I don't know much about how a N910T kernel differs from international as far as data is concerned or what the fix actually fixes when you flash it. But if it has any relwvance my phone is carrier unlocked and i dont even use tmobile. My goal is to learn something new everyday without hard bricking my baby like I did my N900A. I'm not by any means new to rooting but am very new to having a device that I can actually play with. Thanks in advance and us noobies appreciate everybodys patience.