Forgive me if this is not the correct 'area' to post to. I can't seem to find anything at all in regards to what I need/want. Basically, I've got BackTrack5 running on my Sidekick 4g, but the current wireless driver that's installed on the phone does not support monitor mode / packet injection. I was under the impression that most new devices would have an updated driver for the wireless device that would in fact support this. I can't seem to dig up any information on the web or my phone itself to tell me what hardware device it's using. Does anyone know what driver it's using or perhaps know where to get an updated driver package so I can try to get this working? Has anyone out there put BT5 ARM on their Sidekick?
This is the wrong section.
Sent from my Senseless Doubleshot using xda premium
Where would this type of inquiry go? I've scoured the forums for similar threads, but have found nothing related.
General section. Plus backtrack is very experimental on phone. With my experience is doesnt work well.
Sent from my Senseless Doubleshot using xda premium
It's a broadcom 4329, the easiest way to find that out was to look at the kernel config from samsung's source, otherwise you could have looked at /system/etc/wifi/
Broadcom cards are notoriously difficult to get working, especially with packet injection. The chances that you are going to get packet injection working are worse than your chances of getting official GB on this phone.
This topic has been beaten to death. Broadcom basically neuters wireless chips that go into phones so although the driver may allow the functionality for this particular brand of chip it lacks the physical capability.
I'm currently working to add support for the DM9620 USB network adapter to the Android 4 kernel, specifically for the Samsung GT-I9100 (Galaxy S2) running CyanogenMod 9.
The driver can be found here: code.google.com/p/dm962x/source/browse/dm9620.c
I have added and compiled the driver into the kernel, along with enabling USB host mode. However, plugging the adapter into the phone does not cause a new device to appear (both `lsusb` and `ip link` show nothing new, and dmesg has no relevant messages).
I'm guessing that I didn't actually enable USB host mode correctly. Or maybe it's something else. But I don't really know enough to debug this on my own. Any insight provided would be very helpful.
Hey, go into the General section of Samsung Galaxy Nexus, there is a thread for "aircrack-ng", the original post show a couple of links + on page 2 there is another post from the same guy explaining on how to compile for Android.
Hope it could help.
Sent from my Galaxy Nexus using xda premium
This turned out to be a pretty stupid hardware issue, unrelated to the kernel or the driver. I was lead to believe that the adapter was a 5 pin USB OTG cable, when it was actually a standard 4 pin. A quick hardware hack later and the device is recognized just fine.
Mind making a tutorial of this? Im interested in testing it out myself. Also, can you tell me how to add support for the Galaxy S III? Id be happy to, myself, but I dont know how right now. Thanks
CJJohnson said:
Mind making a tutorial of this? Im interested in testing it out myself. Also, can you tell me how to add support for the Galaxy S III? Id be happy to, myself, but I dont know how right now. Thanks
Click to expand...
Click to collapse
I second the request for a tutorial of how to do this. Thanks!
I was wondering if anyone had any info on the status of roms for the Behold II. I just got one, used but in very good shape, and I am trying to get it to work better. I am fairly sure these phones were pretty popular, and I can't believe they were (almost) completely ignored. I found a pretty nice clean android 1.6 rom that I threw on it, but it has no vibrate.
Does anyone know of any stable gingerbread roms for this phone? If not, anyone know how to get vibration to work? Is there anyone out there willing to work on this phone at all?
Or can anyone point me in the direction of some information on taking the rom apart and figuring out how to get the vibration working? Basically I need to find out how to take apart a rom, then figure out how to get vibration working properly. It's driving me nuts that the phone doesn't vibrate when I get calls/texts.
Isn't that Donut? *throws up*
Couldn't find any ROMs above 1.6 with some googling. Its also likely that you would not be able to fix the vibrate issue, if the Dev couldn't. If you want to "take the ROM apart," just take the .zip file and unzip it.
But I recommend getting a new phone.
Sent from my Nexus 4 using xda premium
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
nookle said:
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
Click to expand...
Click to collapse
No prob. Always interested in the legacy devices.
I wouldn't try to fix the vibrate, the developer himself states it will likely never be fixed (http://androidforums.com/behold-2-all-things-root/54769-port-galaxy-1-6-behold-2-final.html). I didn't read into the thread, but usually some user asks why vibrate doesn't work, dev explains, etc. You don't know if the problem with the ROM is the same as the issues found in the threads you searched.
If you want Gingerbread, it looks like the device is pretty much dead, however you can port CM7 from a similar device. It would be quite a chunk of work though.
Sent from my DROID2 using xda premium
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
nookle said:
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
Click to expand...
Click to collapse
I wouldn't try to make a ROM from scratch. A better thing to do would be to port. Basically find a ROM made for a phone with similar internals (type of CPU and RAM) and port the ROM. Much easier than making a ROM from scratch which requires knowledge of a few computer languages (mainly java). There are a few porting guides available on the forum.. Lemme find a link
Sent from my Nexus 4 using xda premium
Hey, thanks for your help! It's much appreciated! And believe me, if I could get a new phone I would. This phone is on my parent's plan, and only used for calling and texting family. I can't use data or anything. At this point it's more for the sake of learning about how to build an android operating system than anything else. I just want a nice, stable, useful phone that is better than the old school flip phones (of which I have had quite a few over the years).
Once again no prob. I used a legacy device just last year but it had quite some development so all I had to do was flash Roms lol.
Anyways this is how you compile GB
http://forum.xda-developers.com/showthread.php?t=1183832
And this is how you port. I would port from a similar device like the My touch 3g
http://forum.xda-developers.com/showthread.php?t=1598713
Sent from my Nexus 4 using xda premium
Haha yeah I am in the same boat with my nook. I have been following the devs over in the nook sub-forum for a couple years now. I have had several iterations of gingerbread, a couple of ics, and now a few of jelly bean. I am used to just slamming the rom zip on the sd card and booting into recovery and flashing it over.
For this phone I had to do odin, which was a new experience for me. Went pretty painless, and I figured it out. I prefer the recovery method over odin.
I have one question about the second link, about porting. It says in the first post that if you don't have gb already compiled for your (my)device that guide is useless for you (me). Is that what the first link is for? Compiling specifically for my device? What if my device is not supported at all? Do I just pick a somewhat similar phone, compile, port, make a flashable rom, and put it on the phone and hope it doesn't brick it?
Yep thats what the first link is for. Don't compile and port for a different device, that is a sure way to brick your phone.
Is your device not supported at all? Usually legacy devices are since back then (lol) there weren't a whole ton of Android phones
Sent from my Nexus 4 using xda premium
I don't know if my device is supported or not. I have not got to that part in the guide yet. I will report back if it is or isn't.
Sorry for not getting back earlier, I've been real busy the past week or two.
I finally got ubuntu set up on a computer, and was following the first guide and ran into a few problems.
First, I wasn't able to install all the required packages. If you want to know what ones they are I wrote them down. Not sure how essential they are in the grand scheme, but they weren't available.
Second, I tried to install java and ran into a problem adding the repos for it. The second one, for src, would not work at all. So I went on sun's or oracle's website and downloaded the linux package and installed it. But apparently it didn't work because all I get after trying to lunch are lots of these:
Code:
/bin/bash: java: command not found
Basically anywhere it tries to use java I get those messages. Eventually it gives up and says I have
Code:
version: /bin/bash: java: command not found
and I should have
Code:
version 1.6
Third, after I issue
Code:
source build/envsetup.sh
I see it includes some devices, like htc passion and samsung crespo4g and samsung crespo. Is this normal?
Fourth, When I do lunch I get five options
Code:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
Should I just pick generic-eng?
I will be out of town all week for work, and won't have access to the computer I am doing all this on. For the life of me I cannot get unbuntu to install on my laptop. Never did like ubuntu, always favored fedora.
Anywho, thanks for any suggestions.
I am basing this thread on "[Q] How To Root the Straight Talk SCH-S968C Samsung Galaxy S III" (the latter portion of it)
Hey all, creating a new thread on this as it has blew up in the past couple of days and got the original thread all sorts of off topic. I am sharing my findings here in hopes that it will help others get Lollipop running on their StraightTalk S3 (or KK roms based off of CM after the 9/7 updates).
First a little history. Before the unified roms I was running d2vzw LiquidSmooth without any issue, then in late Feburary (2/26) the S3Unified rom was built, putting the correct rilblobs in /system/lib upon boot (if I am reading the code right that is). This was when I noticed that the Unified rom broke the S3 ST phone (no data), so I spent a couple of days researching and learning how to build roms and came up with this commit to LiquidSmooth, I noticed a few days later that it was pulled into the CM source, so all roms were back to working with our phone. I also vaguely remember something with rilblobs needing reverted around this time. So at this time, everything was working, up until the 9/7 CM updates where the rilblobs were once again changed. I worked with one of the CM devs (invisablek) on this issue and we were never really able to figure out what the issue was, the radio was throwing all sorts of odd error messages and would never connect. During that time there was enough of a change that even the old rilblobs wouldn't work (spent about a week worth of evenings trying to no avail). So I ended up giving up until 5.0 hit.
Yesterday I came across a d2lte CM12 build! Flashed it and was quite impressed to see everything working except mobile (both calling and data). In that thread I ran across the first linked thread here and seen that inserting a sim card seemed to work, so I hit up a coworker (on AT&T) and asked him if I could borrow his sim. He agreed, so I pulled the battery, popped in the sim and was AMAZED to see mobile working again, did a test call, browsed on 3g, and everything was working quite well. Got home last night and found an old (deactivated) sim card in my basement, popped it and have ran CM12 all day. Hooked it up to the bluetooth head unit in the car, setup a second account for my son, taken a few pictures, everything seems to be working fine.
One thing that has bugged me for a while (which I rarely use) was that MMS stopped working (not sure exactly when, but I'd guess back on 2/26), so I spent some time today pulling apart files, modifying things, and really haven't gained much (at least for the stock MMS). I did get hangouts working as MMS by adding an apn (Hangouts -> Settings -> SMS -> SMS Enabled, then scroll to the bottom and click on Access Point Names, Add one with the following settings Name Verizon Internet, MMSC http://mms.vtext.com/servlets/mms MMS proxy and port are blank, MCC 311 and MNC 480 ). I haven't completely given up on the stock messenger app, but I am done with it tonight.
Here are the things I have done so far:
Modified build prop to include TracFone Settings
added apns-conf.xml to /system/etc (and modified it a few times)
a few different apps to change APN settings (seems like all of them fail)
If anyone wants, my wifes S3 hasn't been touched, so I can get any of the 4.1.2 rom files from it if its helpful to anyone. I did run across this but I haven't had time to try it yet, and I ran across another page where they modified the messenger.apk and changed some of the apn settings in there (definitely interested in looking into this).
Also to clarify, what I believe is happening here with the sim card is this, Verizon updated their RIL's to require a SIM (make sense since they use 4G), and if it doesn't find one it shuts down the radio in the phone, so until ST updates their RIL's, we will probably be stuck. It might be interesting to see if some could 'emulate' having a sim card in using a 3rd party app (its well beyond my programming capabilities I am afraid).
Sorry for my rambling, but I hope this has been helpful to someone, and I am hopeful that this will take off and let the ROOTING thread go back to helping people root . Please post any other SCH-968C findings you have here, maybe we can get a good collection of information in one place.
RiXtEr
@rixter13 so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones normally would? or how do we mod the stock MMS apk so it plays nice with our 3g
also I consulted with motorhead at AA51 and explained what was happening with the roms on our device and he mentioned that the rils were gonna be a b****h, we've all been digging at this trying to get it surrounded, we've approached from every angle we can think of, its to the point that its gonna take some dev to fix
or call straight talk and get them to enter the APNs because they can't be entered manually on straight talk so we need a volunteer to call them and see if them doing the APNs will fix our issue, I have a feeling it won't because if the sim is required for the rom to work then even if the APNs are done by straight talk the SIM might mess that up because with the SIM in the system pulls the APNs from the SIM, so what is on the SIM might wipe out the APNs that straight talk enters from their end. I've stopped trying to think like the phone and started trying to think like the ROM, its gonna follow its programming unless we change the ROM, I no longer think the data tricks and edits are gonna work unless the ROM is cracked open and things for our phone spliced in and the verizon stuff taken out. Can this be done?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
@rixter13 so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones nornally would? or how do we mod the stock MMS apk so it plays nice with our 3g
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.
As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.
I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
how about we have everybody pull logs, would that help?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
how about we have everybody pull logs, would that help?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
So the radio logs often have the IMEI number in them, so we need to be careful there posting them, I can pull logs from a VM I have on my work computer and compare them to my wifes 'virgin' ST S3.
rixter13 said:
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.
As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.
I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
Click to expand...
Click to collapse
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?
wait! let me guess, those devices have an internal SIM?
so you're saying that even if we strip all the verizon stuff we'll still need the SIM for anything 4.4.4 and up?
there's even a 5.0 for the S2E4GT
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?
wait! let me guess, those devices have an internal SIM?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
rixter13 said:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
Click to expand...
Click to collapse
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
rixter13 said:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
Click to expand...
Click to collapse
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
The good news (if there is such a thing) is we get a fresh start with Lollipop. It looks like the first efforts for the SIII was to DE-Unify the rom . The flipside of this coin is that the Lollipop builds are still buggy. Once I get my main machine back up and running, I may try to roll my own rom for the SCH968. I have compiled CM and Liquid roms, but never ventured out on my own yet.
N_psycho_PD_uh? said:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
rixter13 said:
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
Click to expand...
Click to collapse
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guys on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one
Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guts on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one
Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Chainfire could root the H2's. It'd be best to ask him.
heXacode said:
Chainfire could root the H2's. It'd be best to ask him.
Click to expand...
Click to collapse
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
Sent from my SCH-S968C using Tapatalk
Speaking of the H2, what android version is on it?
N_psycho_PD_uh? said:
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
rixter13 said:
Speaking of the H2, what android version is on it?
Click to expand...
Click to collapse
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
heXacode said:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
Click to expand...
Click to collapse
yeah its 4.1.2 why?
the H1 and H2 are identical except for the patched kernel and the fact that H2 has two different versions itself, a qcom and a exynos
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
yeah its 4.1.2 why?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
No explanation as to why. They just don't handle that kind of thing which sucks.
heXacode said:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
Click to expand...
Click to collapse
yeah I know, I'd rather try myself than bother him, he has bigger fish to fry than a prepaid ST, even if it is one of the better S3's (H2/qcom anyways)
Sent from my SCH-S968C using Tapatalk
---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------
Im gonna like seeing what I can do with CM on 2Gb RAM with no bloat!
Sent from my SCH-S968C using Tapatalk
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):
-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so
-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so
and here are the new ones (VZW):
-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so
-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so
(the same files as the later ones are found on Lollipop as well)
I am looking into how to decompile a .so file at the moment.
rixter13 said:
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):
-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so
-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so
and here are the new ones (VZW):
-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so
-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so
(the same files as the later ones are found on Lollipop as well)
I am looking into how to decompile a .so file at the moment.
Click to expand...
Click to collapse
so do you intend to swap or decompile both and paste parts of the ST into the other? Just trying to reason out what you are doing for myself so I understand it better, I am pretty new at this depth, been rooting and romming a short time but only been into modding system for about two months or so so don't get too far over my head, I can follow you but don't take it for granted that I understand what you are saying, I'm learning, you won't have to wait on me ill catch up quick just give ne the time and resources.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 11:18 PM ---------- Previous post was at 11:05 PM ----------
to give you an idea when, CM11 4.4 was the first ROM I ever flashed lol
Sent from my SCH-S968C using Tapatalk