I believe I may have Cyanogenmod 10.1 booting on my S4 Active via Safestrap. Granted, I am a total noob and have no idea what I'm doing, I can see the display light up after installing a 10.1 build for GT-I9525, however there is nothing actually displaying. I'm assuming this might have to do with the driver differences between the GT-i9525 and SGH-i537. Could someone point me in the direction of what I need to tweak to get this display working? Again, I am a noob and managed only to modify the contents of META-INF and a few other files to get this going. Any help is appreciated.
Related
Hello everyone! I just got a new (replacement) Galaxy Note from Expansys. The one I had before had a creaky back cover and the screen had problems with over-saturation, so I had to send it back to Amazon. Now, I pull this one out of the box and I notice it is in pristine condition. I boot it up and notice that the kernel version is a KKA and says "[email protected]" in the second line. It's already kinda funny because KKA came out in november. The Note I got from Amazon had KL7 on it. I forgot what was on the second line. Anyway, I just don't get why "root" is mentioned in a STOCK firmware? Has anyone else noticed this. And for what it was worth I tried gaining root permissions on different apps and it fails. Also I cannot seem to receive any OTA updates? You would think there would be a an update for KKA. It just keeps saying "Network not found", although I have setup my google account, WiFi and mobile data. Anyone else see this "root" on their stock, un-rooted Notes?
PS. I just realized it kinda sounds like the prompt on bash? has this got something to do with the (linux) computer the kernel was compiled on?
I suspect DELL87 is the (non fully qualified) hostname of the machine that was used for the kernel (or system) compilation, while root is, obviously, the UNIX user name of the then logged in user.
I had it on mine stock, new Note as well. Nothing to worry about - it doesn't mean that your Note is rooted and you have superuser access.
I admit that my initial phrasing wasn't quite up to par, so let me put it this way: Android is a flavour of GNU/Linux and, amongst other parts, it uses the Linux kernel (albeit a rather modified version). More so in the case of Android, this kernel has to be built/compiled from source code for each specific device and/or firmware combination out there. Now, the Linux kernel has a cute particularity that, each time you built it, it stores in the built image the user name and the host name (computer/network name) of the machine that were used for building it.
So, for example, if I were a Samsung engineer about to be build a new Linux kernel to use for a new firmware for the Note, I would probably be connected/logged on to the machine with the (network) name DELL87 as user root (the UNIX super user—well, most of the times).
I hope now things are a bit clearer.
inkanyamba said:
I admit that my initial phrasing wasn't quite up to par, so let me put it this way: Android is a flavour of GNU/Linux and, amongst other parts, it uses the Linux kernel (albeit a rather modified version). More so in the case of Android, this kernel has to be built/compiled from source code for each specific device and/or firmware combination out there. Now, the Linux kernel has a cute particularity that, each time you built it, it stores in the built image the user name and the host name (computer/network name) of the machine that were used for building it.
So, for example, if I were a Samsung engineer about to be build a new Linux kernel to use for a new firmware for the Note, I would probably be connected/logged on to the machine with the (network) name DELL87 as user root (the UNIX super user—well, most of the times).
I hope now things are a bit clearer.
Click to expand...
Click to collapse
Yes. I realized this a while back. Thanks for the information though.
I am back on CM9 ICS and everything is fine and dandy.
My apologies if I'm hijacking your thread you appear have found the answers you where looking for.
acidburn89 said:
Yes. I realized this a while back. Thanks for the information though.
I am back on CM9 ICS and everything is fine and dandy.
Click to expand...
Click to collapse
Can someone dumb this down for me?
I have the same Galaxy Note version.
I don't need to understand the answer fully, I'm not sure I'm capable of understanding
Has user: acidburn89 found a way to update to the latest official Samsung update CM9 without having to root and flash his mobile?
Or is waiting for Samsung to update this [email protected] version of Galaxy Note firmware a lost cause,
has Samsung forgotten about us?
I just know if there is a way to fudge up a rooting & flashing of a mobile I'll probably find a way, regardless of how simple it is to do.
Thought I'd add more info according to Samsung kiss:
Latest firmware version is: PDA:KKA / PHONE:KK5 / CSC:KK3 (XEU)
Besides being the wrong thread to ask this question, I'm rather positive that CM9 is not an official Samsung firmware...
inkanyamba said:
Besides being the wrong thread to ask this question, I'm rather positive that CM9 is not an official Samsung firmware...
Click to expand...
Click to collapse
My bad I think I'll start another thread, sorry for the mix up
I'm rooted and it shows my system version is 7.2.3_user_2330720. Superuser works, everything works, but I'm still trying to understand what the difference would be if I somehow used CM. I read about CM on rooted devices everywhere but I'm still not clear on what it would do. Is it basically like a launcher/theme that still lets me have root access?
I'm baffled by all the info available and how everything works together, like roms, kernels, etc. Are these all separate things you do for different reasons, or would you need to do them all at the same time for some reason?
I've still not rooted my phone because I'm just not clear on this and I can't do without my phone.
Cm is Cyanogenmod a ROM.ROM's replace the whole system with another one. You cannot get cyanogenmod yet unless you build from source.
I have a feeling that I should probably post a thread of this nature in the development subforums, however I have nothing to present. What I'm looking to do is either modify an existing or build a new script which will root the Bell version of the Atrix HD which is on Jelly Bean. As many of you may know, the methods using Ubuntu, Motofail2Go and the various other options do not work. However they work partially for us. For example, when using Ubuntu I can get the message that I have rooted the device but it cannot copy the certain files (busybox, etc) to the device. On the other hand, MotoFail2Go also works to a certain extent, installing the sudoku.apk and the like, but the root either doesnt work or stick. With this being said, my question is how can I go about modifying any of these scripts or methods to work with 4.1.2 or is there anything I can do to help a developer with this issue? Any direction would be appreciated, whether it is me working alone on this project or with the help of other developers and community members.
Those other apps stick around because they're pushed to a writeable temp folder. If the exploit isn't working, I'm not sure tweaking a script will do anything to help.
Have you tried any other root methods?
The GS4 just got rooted and it hasn't even been released yet
Markyzz said:
Those other apps stick around because they're pushed to a writeable temp folder. If the exploit isn't working, I'm not sure tweaking a script will do anything to help.
Have you tried any other root methods?
The GS4 just got rooted and it hasn't even been released yet
Click to expand...
Click to collapse
As of now I've tried all of the published ways here on XDA and nothing seems to work for 4.1.2 yet it works for 4.1.1 which is why I thought that it would be possible to tweak one of the exploits in whichever way needed to root this slightly different (as it would seem) firmware. I'm not sure where exactly where to start looking when it comes to rooting the device, any help would be appreciated. Which files do I need to have on my device and where do I need to have them in order to obtain root?
Is there literally nothing for this? I've got the method to downgrade to 4.1.1 but that only yields root apparently. No custom roms or anything.
Is there anything available for this tablet or remarkable about being on 4.1.1 I've searched both on all boards here on Tab S2 and it seems useless.
Aside from that, is there any way to unlock the simcard slot?
I apologize for the questions but it's looking like the tab may as well stay on 6.0.1.
Thanks for comments and advice, and yes, I've searched up and down (T817T all boards, etc.)
You have got to search and read through a bit more.
I only got this tablet (a used one of course) only 2 days back, so others may be able to help you more.
For me I just rooted the tablet and installed some xposed modules. For my need with the tablet, I don't need anything else.
Unlocking simcard slot has to be done from tmobile. I am not aware of any hacks available in xda.
You can install twrp and root the device if you want. T810/T815 they uses the same chipset. The information I have gathered so far indicate that you can install aosp roms for those models, but you shall not get cellular connectivity. Any chance of having official Nougat on this tablet is very very slim. There are some aosp 7.0 roms, but they are in early developmental stage; things like fingerprint sensor won't work.
Anyone feel free to correct me if I am wrong on any of the things I mentioned.
I no longer have tmobile.
Could I flash the t810 firmware onto the t817 tab s2? This way I could get the updates straight from Samsung.
I was only able to get one ROM to work on mine. Ultimately, I gave up and just kept it stock.
Sent from my SM-N920T using Tapatalk
I'm also frustrated with the T817T. I have been able to root it, flash TWRP, but I have never been able to flash a custom ROM. I have heard that the T815 ROMs should work, but I get an error in TWRP if I try to flash one.
I was reading something in the Note 10.1 2014 forum that you could flash the P605 (International) ROM to the P607T (T-Mobile) if you unzipped the ROM, removed the modem files, and rezipped it. I'm wondering if something like this would work for the T817T as well.
If anyone has any ideas how to do this, please respond here.
Ugh. I've done this before and should have made notes. For the life of me I cannot enable root on the acclaim AOSP 6.01--I know, wrong forum but this probably won't be seen in the "right" place and this is where the @amaces ROMs have their "home".
I've tried to follow the instructions in the beginning of the Marshmallow, Nougat, etc. thread. That did not work. I've tried various other ideas gleaned from later in the thread. I've tried the same approach I use for AOSP 7.0. None of it works
Can someone put me out of my misery, please? (I'll write it down this time!)
I recall vaguely on CM13 one needs to flash UPDATE-SuperSU-v2.46.zip to get root access option.
digixmax said:
I recall vaguely on CM13 one needs to flash UPDATE-SuperSU-v2.46.zip to get root access option.
Click to expand...
Click to collapse
You, sir, are a scholar and an gentleman--and you're right! CM13 for acclaim doesn't require anything beyond choosing a setting. It might be different for hummingbird or ovation. But the @amaces AOSP 6.01 for acclaim needs a helping hand and you just gave it