Related
I recently purchased a used droid 4 on ebay. Unfortunately it has been upgraded to the OTA release of ICS 4.04. Anyone working on lifting the simlock associated with the version of the bootlocker included with ICS (I'm assuming the bootloader is the origin of this simlock but technically I could be wrong)? Or is it a lost cause because it is signed? I know it's written to protected ram so any workaround would be nontrivial but does anyone have any possible exploit ideas? Motorola is unlocking a couple other models that they have out. Would petitioning them to include the droid 4 in their list of unlockable devices be a surefire path to getting the simlock lifted? Or should I consider this a lost cause and return my droid 4 to the ebay ether?
If anyone is considering working on this issue I would be more than glad to contribute. While I'm no Android expert I have a decent understanding of the OS and work in command line Linux for a living so I'd be glad to help. The selection of qwerty phones today is beyond attrocious.
One last thought. Is the idea of spoofing the carrier a possibility?
Sent from my SGH-T839 using Tapatalk
Hi blackstar,
So, I recently got a Droid 4 off of CraigsList that I wanted to use on StraightTalk, but found out that what I had perceived (that 2G/Edge was working on GSM North America) was incorrect.
They're not completely sure WHERE it's broken at the moment as far as SIM lock. Some have suggested it might be baked in the ROM -- but more than likely it is built into the modem.
Here have been some stabs at it -- and what to do in regards to getting the modem setup/altered.
http://forum.xda-developers.com/showthread.php?t=1916869
A thought, though -- since we have SafeStrap and Root, doesn't that let us essentially bypass the bootloader in some ways? My understanding is that the bootloader was required to boot the device to a "correct" image and lock the load to Motorola's firmware, but SafeStrap/root gave us access to actually overwrite the RAM/memory and replace the existing kernel with a new one for the chance at custom ROMs. So, I'm not entirely sure it has to do with the bootloader.
To me, it seems like something that's potentially baked into their ROM or in the modem firmware. If it's in the modem firmware, it's a matter of figuring out what keys/values need to be adjusted and then run it. There have been talks about AT&T getting the Photon Q (Asanti) -- rumors that were back around April of this year... but we have yet to see it there and no news about it showing up anytime soon. Not sure if they scrapped the keyboard and then shipped it as a different device.
I would imagine that if we can have the lowest level debug logging enabled and plug in an American SIM, you might be able to figure out what is breaking. Not sure how low logcat can go...
That's my understanding of the current situation, from a programmer's point of view (though I don't code for Android). Spoofing might be interesting -- but if it's locked at the radio firmware, I don't think spoofing can adjust the frequencies. But more power to you if you can figure it out (and force me to find ANOTHER Droid 4, haha).
Good luck! Definitely talk with the OP of the Topic I sent you, since s/he has a pretty deep interest in this as well.
OH, and one more thought -- there was a thought to grab an AT&T version of the Bionic and Verizon version, wherein they had the same radios, but different firmware, and do a diff on them to figure out if some settings had changed, and then potentially patch that into the D4. That might be a good strategy, but that would require us to get dumps from a few different people -- something you might be able to facilitate if you guys all work together.
One final thought -- is there any way we could have a sticky'd topic for people to post their findings, so we don't have to keep scanning and finding this?
Much thanks terinfire.
Let me start off by saying I don't have any definitive information with regards to any of the good questions you posed but if I find out anything I'll be sure to update the thread.
I spent a good chunk of the weekend trying to educate myself on the situation. From what I understand (anyone feel free to correct me or point me to the appropriate thread if I'm completely reinventing the wheel), it seems like it comes down to two most likely scenarios. Either Verizon added an MCC/MCN lock in the baseband when pushing out the OTA ICS release or they placed a restriction in the radio interface layer (RIL) of the ICS ROM. My research hasn't quite enabled me to determine which scenario is more likely. My unscientific intuition (and wishful thinking) is that the restriction is in the ROM somewhere in the RIL (if that makes any sense, still learning the Android OS architecture).
I will post what I've mentioned above in the the forum you mentioned; hopefully I can garner an audience. I will also look into getting a sticky topic created.
Not too sure how to implement any of my intuitions noted above with regards to this problem but I will try and learn as it goes.
One more note - so it is claimed that the Samsung Galaxy III for Verizon can be unlocked to use domestic GSM carriers. I've found no confirmation. (https://plus.google.com/103583939320326217147/posts/b7JbBKjJVSQ)
Pertinent links I came across in my research that may be useful:
MCC/MCN Codes: http://en.wikipedia.org/wiki/Mobile_Network_Code
Radio Interface Layer: http://en.wikipedia.org/wiki/Radio_Interface_Layer, http://www.kandroid.org/online-pdk/guide/telephony.html
RIL Header: https://code.google.com/p/linux-on-android/source/browse/radio/headers/ril.h
Qualcomm MDM660Device Specification: http://www.scribd.com/doc/54154049/...odem-Device-Specification-Advance-Information
This may sound like a noob question, so forgive me if it is. I'm currently on Verizon with a dev edition, and the possibility of an OTA in the near future seems pretty bleak. So I was wondering, would it be possible to take the camera update from another carrier and turn it into a flashable zip for us users here on Verizon?
From what I read and understand, it't not just a matter of the APK, so no unfortunately i dont think so. I am in the same boat you are, VZW DE Moto X.
I'm sure someone is trying... so I'm keeping my fingers crossed. But some of the changes are probably at the kernel level (I'm guessing), making it difficult I'm sure.
If anyone has something they want to test, send it my way, I'll gladly test it out on my dev edition
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?
David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.
Hello Fellow XDA Users!
Some of you might remember me from over the years or maybe just from SamPWND root on the S8/S8+. I have had a number of devices since SamPWND with a few being Sammy's. I have been real busy with life and work but of course every spare time I get has been breaking Samsung devices!
I've found some exploits I never released publicly due to the devices being "unpopular" but figured since I am close now as well as what I have found so far most likely works on most Samsung devices (I've only tested on Tab S4 and N9 from Big Red) that I wouldn't keep this one away from everyone.
With that being said, I do not have FULL root yet but am very close. I wanted to create this thread as I don't have let's of free time these days to hopefully bounce ideas around to achieve our end goal a lot faster.
I am going to spare all the specific details to the masses but will let you know what I got so far. I prefer to collaborate over other applications that are more "real time" if there are any developers that read this then PM me and we can share contact info. If you just want to toss ideas in here then that is ok. I just don't want to have someone potentially take my hard work and claim it as their own before I can achieve root. I have been almost non stop since the N9 was released so you can understand hopefully why I want to be the one to bring root to you all!
With that being said, I will begin telling my story and what I have so far.
Some time last year I was working on another Sammy device after SamPWND as I wanted root of course. I spent weeks and weeks trying to find exploits until I finally did! For this time I wanted to see what Sammy would offer for it as it was a tablet, the XDA forum was deserted etc. They did pay out a 2500$ reward so it was ok.
The reason I bring this up is because the exploit plays a factor here as well. The exploit was a mix of SamPWND and SamFAIL as I used the same rooting script as SamPWND but with a custom partition that wasn't checked for integrity when flashing in ODIN.
On this partition there were some init rc scripts. I noticed these scripts could be executed on combo firmware as root user. This means I could mount the partition in Linux, modify the scripts to my liking, sparse it back up and flash in ODIN. Then I could execute them. Believe it or not, they were executed by entering a simple setprop command in ADB. So from start to finish I simply extracted this partition, modified the scripts to install root as well as packaged the root package in with the image, flash it and then execute an adb command and viola! I felt like a loser it took me so long to find yet was so simple to exploit.
This ties in to where I am at now. I spent months looking through various attack vectors with no luck due to enhanced security not just with Sammy but Android also. So one day last week I decided to take a look at combo firmware again. In no time I found something interesting and then I slapped myself for spending months again when I should have looked at init scripts first.
I found it on my Tab s4 initially but wanted to see if the same file was on my N9 on combo and it was!
The first script runs as system user. For some reason the entire folder it is in is world readable/writable which means there is a script I can modify. This one is not an init script but is a script none the less that runs as system user that I can modify and execute with a simple adb command. Of course we want root, not system so I keep looking.
So I started writing all sorts of scripts/commands and executing it as system user since it's better than running as shell user right? One day I decide I am going to try and change permissions on the entire device. To my surprise it actually changed permissions to ALOT of partitions/files including EFS. I start messing with efs but don't want to break my phone so I settled with backing it up, enabling hidden menu, changing my sales code, enabling factory test mode etc. Etc.
One day I decided to see if I could access the same scripts I used previously. The partition was not readable (perms denied) so initially I thought it was a dead end. Then for some reason I tried to go into the sub-directory where I knew the scripts were and guess what!? The parent directory perms were not changed but its sub directories were! Now I am somewhere I have been before and now I have some scripts that I know are executed by init and as root and how to trigger them.
I spent over a week and all my spare time trying to gain full root but progress is slow moving due to new security. I can make a script that backs up every partition on the device, mounts "most" partitions as rw, dd magisk boot images (of course secure check fail due to locked bl but I had to try lol), create folders and push files to roots etc. Etc. Its basically like having full root but you have to run it in a script for everything you do.
Since we have locked bootloaders, we cannot boot modified boot.img. There's also more security causing me to have issues with system root. One of those issues is the fact that system, vendor and odm partitions cause the kernel to panic instantly as soon as they are mounted.
I managed to force some stuff quickly before the crash but they also have something called "secure write protect" which basically backs out anything you might have written before it reboots. I have tried installing chains systemless root and even tried to install magisk without modifying the boot but I am just getting frustrated and tired.
One thing I am currently trying is a safestrap recovery. The end goal is to try and get a GSI on that is pre rooted. Yes, I also tried to dd a gsi and tried with a file manager... it appears to write but it doesn't. I think there is some security going on as it along with odm and vendor are "protected" partitions.
I can modify rootfs and just about every other partition on the device with ease but haven't successfully gained root via su or magisk etc. Some stuff will cause device to boot with good old custom unlock splash screen and even say custom and custom binary in ODIN. That plus it being project treble certified indicates we shouldn't have any issues using GSI's and more soon as we can get ot nailed down!
So in a nutshell, I now have the ability to do almost anything as root user using init scripts on our locked bootloader devices but we only have a little bit left to go in figuring out how to get su binaries onto the device thanks to sammy and googs enhanced security updates.
Hopefully this gets the convo going and I wanted everyone to know that it's not "impossible" and now seems like a guarantee! Let's get some ideas going in here on this last hurdle! If you are a developer please also PM me as I tend to forget to check xda sometimes plus I like a more real time conversation when it comes to this stuff.
We are almost there!
Donation Link: https://forum.xda-developers.com/donatetome.php?u=3812611
Forgot as a reminder that I can confirm the scripts there on tab s4 and n9 combos.. it's very likely they are present on S9/S9+ also and potentially other devices but they will need to be confirmed once we get to that point.
Was just barely reading up on Samsung defex security.. hope that's not the problem since only fix I can find requires hex patching the boot.img
so i noticed you gave quite a lot of info without going too much into details. i understand that you don't want anyone to steal your ideas and take credit.
would be a shame to get root.
and not get the credit where it is due..
now, that being said, isn't making these statements public open up the door for samsung to notice these possible exploits and patch them up for good? thus rendering all your efforts in vain? As even if the details were kept at a minimum from kangers to use them, the samsung devs can probably read through the lines quite easily.
anyways, hope your effort will bare fruit for as long as it is possible.( samfail lasted what 3 or 4 months? before patches made it too difficult to keep up)
Regards
bober10113 said:
so i noticed you gave quite a lot of info without going too much into details. i understand that you don't want anyone to steal your ideas and take credit.
would be a shame to get root.
and not get the credit where it is due..
now, that being said, isn't making these statements public open up the door for samsung to notice these possible exploits and patch them up for good? thus rendering all your efforts in vain? As even if the details were kept at a minimum from kangers to use them, the samsung devs can probably read through the lines quite easily.
anyways, hope your effort will bare fruit for as long as it is possible.( samfail lasted what 3 or 4 months? before patches made it too difficult to keep up)
Regards
Click to expand...
Click to collapse
I can see where youre coming from but I dont think they can glean exactly what I have as theres are probably hundreds of scripts throughout the system.
Also, this approach is far from new. People have been using init scripts for rooting purposes for many years.
I also tried it with newer firmware and it actually didnt work. So it already requires an older frmware and I expect Sammy will increment bootloaders soon making it unavailable to those who have updated at that poimt in time. I figured best to put out the word on progress now and those can choose to wait or not.
Exploits never last very long. The only way to ensure longevity is to remain on old firmware. There was SamPWND before there was SamFAIL. This could be the perfect time. Unless I am the only one working on this device there will be other exploits to be found.
With that being said, only you have posted all day and no devs have reached out to join in the fun so at this rate by the time full root is achieved it most likely will already be patched.
Thats just my thoughts though.
elliwigy said:
I can see where youre coming from but I dont think they can glean exactly what I have as theres are probably hundreds of scripts throughout the system.
Also, this approach is far from new. People have been using init scripts for rooting purposes for many years.
I also tried it with newer firmware and it actually didnt work. So it already requires an older frmware and I expect Sammy will increment bootloaders soon making it unavailable to those who have updated at that poimt in time. I figured best to put out the word on progress now and those can choose to wait or not.
Exploits never last very long. The only way to ensure longevity is to remain on old firmware. There was SamPWND before there was SamFAIL. This could be the perfect time. Unless I am the only one working on this device there will be other exploits to be found.
With that being said, only you have posted all day and no devs have reached out to join in the fun so at this rate by the time full root is achieved it most likely will already be patched.
Thats just my thoughts though.
Click to expand...
Click to collapse
the note 9 kinda missed the party bus.
ive had almost all Sammy's devices and i have to unfortuanly say this is by far the most bleek state of development ive ever experienced.
but back in the day, there was far less android competition.
edit:
and i think that if not the competition, the fact that alot of people feel content with what stock samsung is offering. when the device came out, the forums were littered with Shakespearean: 'to root or not to' type of threads.
This is great news. Hopefully some devs contact you. Loved your work with the S8.
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here. ?
Wow, this is very interesting, and I loved reading your detailed post. I am super exited, and can't thank you enough for all your work elliwigy! :good:
Full on beast!
Sent from my SM-N960U using Tapatalk
PsiPhiDan said:
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here.
Click to expand...
Click to collapse
I wanna say s8/+ and the note 8.. both of which root solutions I used.
Word brotha ?? thank you for your diligence. I love that your hobby can help out so many who don't have the time, will, or discipline to learn it.
PsiPhiDan said:
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here. ?
Click to expand...
Click to collapse
you should be fine as long as you remain on rev1 firmware..
PsiPhiDan said:
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here. ?
Click to expand...
Click to collapse
lol ive had a lot of devices thats for sure but most my work is on samsung
teknowiz23 said:
I wanna say s8/+ and the note 8.. both of which root solutions I used.
Word brotha ?? thank you for your diligence. I love that your hobby can help out so many who don't have the time, will, or discipline to learn it.
Click to expand...
Click to collapse
Yeeeeeeeesssssss!
You are always the loveliest "Rev1 firmware baby"
elliwigy said:
you should be fine as long as you remain on rev1 firmware..
Click to expand...
Click to collapse
So.. I had to get a replacement via Asurion, and before setting it up I installed the earliest unlocked firmware. Sm-n960u on Verizon plan. I understand that this should work as long as I don't update, correct?
teknowiz23 said:
So.. I had to get a replacement via Asurion, and before setting it up I installed the earliest unlocked firmware. Sm-n960u on Verizon plan. I understand that this should work as long as I don't update, correct?
Click to expand...
Click to collapse
Yes, just make sure you stay away from anything that says N960UxxU2 or S2
Jammol said:
Yes, just make sure you stay away from anything that says N960UxxU2 or S2
Click to expand...
Click to collapse
Mine says Rev 1.1. Does that mean game over for me?
PsiPhiDan said:
Mine says Rev 1.1. Does that mean game over for me?
Click to expand...
Click to collapse
No that's for hardware revision. Is normally for when a device has had a hardware fix that changed something from the original design. So if they realized the fingerprint readers on rev1 were crappy and changed it out for future ones, they would show rev1.1 or whatever numbers they want to classify it as.
I'm not sure what they may have changed on the Note 9 though. Could have been camera or even something internal such as memory or radio chip.
What you want to stay away from is any changes to the attached image. Don't update to anything that says U2 or S2 at that section of the firmware.
Thank you for your hard work on this .
Hello first time poster here, but my question is about the issue with voice over LTE in the pie ROMs. I know its been answered before with it being the IMS issue if I am correct but looking at the thread that gave the answer I guess I didn't see a post that elaborated a bit more on it. My question is what about it in the coding , is causing the issue? I'm nowhere near a software expert but I know enough to understand the verbiage and with that I'm asking the devs here what has been hard to crack that IMS issue? I'm only asking cause I really enjoy the pie ROMs all you devs have done a fantastic job keeping this phone alive but with me being a Verizon user I know I'm doomed eventually once they cut CDMA and I hate the 18:9 phones so its hard to want to upgrade . has anyone been close to finding a solution on this ? Either way thank you all for your time in keeping this phone alive .
probles08 said:
Hello first time poster here, but my question is about the issue with voice over LTE in the pie ROMs. I know its been answered before with it being the IMS issue if I am correct but looking at the thread that gave the answer I guess I didn't see a post that elaborated a bit more on it. My question is what about it in the coding , is causing the issue? I'm nowhere near a software expert but I know enough to understand the verbiage and with that I'm asking the devs here what has been hard to crack that IMS issue? I'm only asking cause I really enjoy the pie ROMs all you devs have done a fantastic job keeping this phone alive but with me being a Verizon user I know I'm doomed eventually once they cut CDMA and I hate the 18:9 phones so its hard to want to upgrade . has anyone been close to finding a solution on this ? Either way thank you all for your time in keeping this phone alive .
Click to expand...
Click to collapse
IMS depends on proprietary apps and binaries. The last ones we have are from android 7 and don't work on Android 9 anymore as a lot of stuff has changed.
But somebody made some progress adapting the IMS.apk lately :https://github.com/eErenYeager/ims_apk
Thanks for your answer
Elektroschmock said:
IMS depends on proprietary apps and binaries. The last ones we have are from android 7 and don't work on Android 9 anymore as a lot of stuff has changed.
But somebody made some progress adapting the IMS.apk lately
Thank you for that answer. It makes a lot more sense to me and if it ended at 7 I can see how it survived to 8.1 with its similarities to nougat but I hope the progress is made with adapting that new IMS for legacy devices . I also own an lg v30 but I'm back on the shamu cause I really do hate the 18:9 how dare they say the v30 6 inch is a true 6 inch like a nexus lol, but their aosp ROMs had issues with volte as well so that's why I was curious cause at first I thought it was an issue of 32bit vs 64bit . again thank you for the response.
Click to expand...
Click to collapse