Related
Hi,
Just got my Nexus. Can't update it as Nexus says it's up to date. And my Android version is 4.0.1 at the moment.
But I see in your signatures most of you have 4.0.3.
Do I need to be a developer (must have SDK or smth) to upgrade? Or is there a simple way to do that?
Thanks!
4.0.3 OTA is not available. It's in AOSP.
Only way to get 4.0.3 is to use a custom ROM .
zephiK said:
4.0.3 OTA is not available. It's in AOSP.
Only way to get 4.0.3 is to use a custom ROM .
Click to expand...
Click to collapse
Thanks!!!
That was quick
I think I will wait for official. Have no balls messing with custom ROMs at the moment Tired already of messing with Windows Mobile and searching for a perfect ROM (didn't find that in 3 years).
bullka said:
Thanks!!!
That was quick
I think I will wait for official. Have no balls messing with custom ROMs at the moment Tired already of messing with Windows Mobile and searching for a perfect ROM (didn't find that in 3 years).
Click to expand...
Click to collapse
well luckily for you if you ever decide to go the custom rom route, the people at samsung, google, and the wonderful developers online have made it almost idiot proof, and safe to do. you will probably be surprised how easy it is. in fact, most people seem to have the most issues installing the windows(or mac) drivers properly.
peter alfonso - peteralfonso.com has the Bugless Beast rom, which is nearly stock aosp, and very stable
i have to say I tried rooting, unlock and custom rom... and the hardest bit was finding the right drivers.. but used the universal ones (in the forums) and it worked like a charm.. Just follow a guide and it's simple... but I've stuck with stock as the camera functionality isn't as good in AOSP... will flash cm9 when its ready though
go with the one touch app for rooting and the touch clockwork app they work great
Sent from my Galaxy Nexus using xda premium
JCP SR said:
go with the one touch app for rooting and the touch clockwork app they work great
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What is the name of the app? Its something in the market?
cancerouspete said:
well luckily for you if you ever decide to go the custom rom route, the people at samsung, google, and the wonderful developers online have made it almost idiot proof, and safe to do. you will probably be surprised how easy it is. in fact, most people seem to have the most issues installing the windows(or mac) drivers properly.
Click to expand...
Click to collapse
You don't need to install any drivers on Mac to make fastboot working. Just download a fastboot binary (like on Linux).
Btw
When we should expect 4.0.3 to be released officially?
How long it usually takes to release a new version?
bullka said:
Btw
When we should expect 4.0.3 to be released officially?
How long it usually takes to release a new version?
Click to expand...
Click to collapse
no ETA. it is ready when it is ready.
flash to custom 4.0.3 if you want it now
I am also still at 4.0.1 and when I check for update, still no 4.0.2
When were will be an update to 4,0,3 will we be able to update without losing all the settings?
I have Backup checkbox marked in my settings.
So, if I'm on 4.0.2 and download a 4.0.3 ROM it will be compatible? Same with flashing a 4.0.3 kernel on a 4.0.2?
Thanks
Hi guys,
I have recently added support for the Galaxy S3 for my Android ROM kitchen, and have confirmed that ROMs can successfully be built and flashed for the GS3 variants for AT&T, T-Mobile and International.
Since I don't have the Sprint device, I was wondering if some of you can confirm it works for the SPH-L710 (and also the C Spire SCH-L710).
Please follow the instructions below to use the kitchen for your GS3. These are T-Mobile instructions but should also work for the Sprint model:
http://forum.xda-developers.com/showthread.php?t=1939420
Would be greatly appreciated!
No one wants to give this a shot? It should definitely work, since the file format of the Sprint S3 custom ROMs are similar to that of the other S3 variants.
dsixda said:
No one wants to give this a shot? It should definitely work, since the file format of the Sprint S3 custom ROMs are similar to that of the other S3 variants.
Click to expand...
Click to collapse
I will give it a try this weekend. Sorry I can't do any sooner than that. I figured people would be all over this. Thanks for everything that you do.
What experience level is required to effectively use this?
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
DrgnRebrn said:
What experience level is required to effectively use this?
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
No ROM customizing experience required, maybe some basic Linux/UNIX command knowledge... but the FAQ should help you out.
Excellent! I've been studying up on Android development. I can't wait to get familiar with this! Thank you for this opportunity!
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Running this right now on a Linux box(Mint 13 Cin.). Will report back. Attempting to do the latest jelly bean leak.
How'd it go? Make sure you have latest version of kitchen.
Ran it and it wouldn't flash on my phone. Attempting to use my windows box just to see if it wasn't something that I did that made it not work.
Same thing happened on my other box. Keeps failing when it says updating cache. Says it expects an arguement of four but is only getting three.
lostcausenjtown said:
Ran it and it wouldn't flash on my phone. Attempting to use my windows box just to see if it wasn't something that I did that made it not work.
Same thing happened on my other box. Keeps failing when it says updating cache. Says it expects an arguement of four but is only getting three.
Click to expand...
Click to collapse
Updating cache? What did you try to do to your rom? Did you start with a stock, unmodified rom? The error about the arguments has to do with the update-binary, but first I need to know what you are doing. Simplest thing to do is to just root it and then flash that.
I am definitely interested in this. I'll try to get it prepped if the gf relinquishes my pc to me =(. Wb dsixda. Saw your kitchen was on hiatus before. Now to cook up some custom roms for myself and friends.
Sent from my SPH-L710 using Tapatalk 2
dsixda said:
Updating cache? What did you try to do to your rom? Did you start with a stock, unmodified rom? The error about the arguments has to do with the update-binary, but first I need to know what you are doing. Simplest thing to do is to just root it and then flash that.
Click to expand...
Click to collapse
I had the stock deodexed LIH update. It was in zip format. All I did was run it through the kitchen. (Make a working folder and the option 99 to build from working folder). I made no edits whatsoever. I used the interactive mode to build the rom. Both times, it failed on me with the same code. I can upload the update-binary from the one I built if that will help.
lostcausenjtown said:
It was in zip format. All I did was run it through the kitchen.
.
Click to expand...
Click to collapse
No no... that's not the way I intended it. I linked a guide on the first post, please do not ignore the instructions. The kitchen will not work with someone else's zipped ROM - everyone uses their own methods. Start with an untouched stock ROM image and root it, then flash it.
dsixda said:
No no... that's not the way I intended it. I linked a guide on the first post, please do not ignore the instructions. The kitchen will not work with someone else's zipped ROM - everyone uses their own methods. Start with an untouched stock ROM image and root it, then flash it.
Click to expand...
Click to collapse
Ok got it. Read the instructions wrong. Only have the LG8 in tar format that I will try. I flash this via odin when I have problems. Will report back.
Ran the odin files through the kitchen and the rom booted up just fine.
lostcausenjtown said:
Ran the odin files through the kitchen and the rom booted up just fine.
Click to expand...
Click to collapse
Awesome, you made the flashable zip? Root working?
If he doesnt confirm back with you, i'll take a shot at it... i'm really familiar with the kitchen because of my old evo view rom
Sent from my SPH-L710 using Tapatalk 2
contradude said:
If he doesnt confirm back with you, i'll take a shot at it... i'm really familiar with the kitchen because of my old evo view rom
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
That would be great..
dsixda said:
Awesome, you made the flashable zip? Root working?
Click to expand...
Click to collapse
Yes the zip did flash and root is working. I even deodexed now and it works as well(not that I expected anything different). Thank you for your awesome work.
lostcausenjtown said:
Yes the zip did flash and root is working. I even deodexed now and it works as well(not that I expected anything different). Thank you for your awesome work.
Click to expand...
Click to collapse
Thank you for your awesome work as well!
This should be relatively simple, I just can't find a solid, straightforward answer.
Is "Firmware" the same thing as what is commonly reffered to as the "Radio?"
It is separate from kernel, no?
TheAtheistReverend said:
This should be relatively simple, I just can't find a solid, straightforward answer.
Is "Firmware" the same thing as what is commonly reffered to as the "Radio?"
It is separate from kernel, no?
Click to expand...
Click to collapse
The firmware contains the radio. It is separate from the kernel. Not sure what all exactly comes comes in the firmware.
Sent from my Venomized ViperINC
tylerlawhon said:
The firmware contains the radio. It is separate from the kernel. Not sure what all exactly comes comes in the firmware.
Sent from my Venomized ViperINC
Click to expand...
Click to collapse
So, when we flash a "Radio", we're flashing "Firmware" but just calling it "Radio?" Is it possible to separate the two, or have you ever seen that?
Thanks for the re-ply :good:
TheAtheistReverend said:
So, when we flash a "Radio", we're flashing "Firmware" but just calling it "Radio?" Is it possible to separate the two, or have you ever seen that?
Thanks for the re-ply :good:
Click to expand...
Click to collapse
Yes you can seperate, the radio is considered a firmware update but also there are things such as the touch part of the hardware that is changed with firmware updates, to put into car terms firmware is like chevrolet and the radio is like corvette, it's a type of firmware. Hope my over simplified and non technical explanation helps you get the gist of it though I'm sure someone can and will come on here and correct it with the exact terminology and much longer explanation.
Sent from my Incredible 2 using xda app-developers app
From my understanding, and someone please correct me if in wrong, but a radio is related to signal strength and other means, and firmware is the android build
This message was sent via my Paranoid Android
jeremytn86 said:
Yes you can seperate, the radio is considered a firmware update but also there are things such as the touch part of the hardware that is changed with firmware updates, to put into car terms firmware is like chevrolet and the radio is like corvette, it's a type of firmware. Hope my over simplified and non technical explanation helps you get the gist of it though I'm sure someone can and will come on here and correct it with the exact terminology and much longer explanation.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the explination. I think I undcerstand it a bit better now. I guess I'm just a little confused because when I (briefly) had a Rezound, it was always "firmware this" and "firmware that" where as with the DInc2 there is almost never a reference to "firmware" but often to "radio."
It makes sense though. I'm just wary of (a post I saw recently in the DInc2 forums) when people say you need to "flash the latest firmware" to flash a specific rom when, where you find this "firmware" is in the "radio" everyone is familiar with as a "radio".
BTW, if anyone wants to go into more detail, I (and maybe others) would surely appreciate it!
JehC said:
From my understanding, and someone please correct me if in wrong, but a radio is related to signal strength and other means, and firmware is the android build
This message was sent via my Paranoid Android
Click to expand...
Click to collapse
This doesn't sound quite accurate considering the previous posts. Symantics may be at issue here...
TheAtheistReverend said:
This doesn't sound quite accurate considering the previous posts. Symantics may be at issue here...
Click to expand...
Click to collapse
I can't really add any technical knowledge, but it seems in Samsung land they call the radio the modem...At least that's what I saw when I was perusing the GSII forums.
gtdtm said:
I can't really add any technical knowledge, but it seems in Samsung land they call the radio the modem...At least that's what I saw when I was perusing the GSII forums.
Click to expand...
Click to collapse
Yep, was that way on the fascinate
Sent from my Incredible 2 using xda app-developers app
Now keep in mind that I am no expert, and I think TAR is referring to is the leaked ICS that was given to Nitsuj that had some firmware updates, correct me if I am wrong. I think there may have been some other firmware aside from the radio in that leak. I believe someone may have unpacked that rom and separated the firmware and/or radio and made it available to us to use, giving us the .320 radio. Now, here is where it gets a bit shady for me, if you installed that leaked rom (which I did not do) and updated the firmware you were using the .320 radio. I am running the .320 radio, but I installed from the .zip in the radio forum so I don't know if I may have missed some other type of firmware that was only provided if you installed the leaked ICS rom. I know that jameshmiller provided the .320 radio .zip and he may be the one to ask if there was any other firmware that was not provided in the radio he pulled out of the leak for us. Does this provide a better question, or am I just completely rambling? If some one were to ask me, I would say that the radios are firmware but again I don't know much about the Android Development, I just benefit from it.
The firmware pack contains the .320 radio and a few other updates (I can't tell what they are from looking at the filenames). The radio controls data, WiFi, GPS and all that, which is why people generally like upgrades. I think the radio in the radio thread is just the radio, without all the other firmware.
Sent from my Incredible 2 using Tapatalk 2
So what exactly is a kernel
sent from my paranoid android
JehC said:
So what exactly is a kernel
sent from my paranoid android
Click to expand...
Click to collapse
Basically a set of drivers for the rom.
Sent from viperINC2DIX
JehC said:
So what exactly is a kernel
sent from my paranoid android
Click to expand...
Click to collapse
Google it, you'll probably get a much more in depth explanation than we care to type out
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Google it, you'll probably get a much more in depth explanation than we care to type out
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
http://goo.gl/p9ftT
Sent from viperINC2DIX
I was only asking because it was also in the OP
sent from my paranoid android
JehC said:
So what exactly is a kernel
sent from my paranoid android
Click to expand...
Click to collapse
The way I understand a "kernel" is the programming that acts as the bridge, or interface between the hardware (the phone) and the software (the rom).
This is why we need HTC to release the source for it to make custom kernels for roms on different Android versions (2.3, 4.0, 4.1 etc.)
A kernel is something that, once heated, will make popcorn.
Ice Cream Sandwich flavored popcorn.
sent from my banned ViperDIX
Let's see if I can give a more comprehensive answer to this.
The term "firmware" is used to describe a piece of software that is stored in read-only memory which sticks around even if the device is powered off. The firmware is there when you power on the device so it can get it kick-started: reading the operating system from internal storage, etc.
One key component to your device is the hardware that talks to the networks, be they WiFi, CDMA, 4G, whatever. That hardware has associated firmware that controls how the hardware talks to the various networks. That specific firmware is often called the "Radio" or the "Modem". That firmware is stored on a dedicated partition of your phone's internal storage, allowing you to update just the "Radio" bits.
The kernel is the base operating system. Think of it like DOS on a PC: the kernel controls the system and includes drivers that talk to the display, touchscreen, radio, and other components. Like DOS, the kernel doesn't really provide much of a user interface, so you run Windows on top of that.
On Android devices, the kernel is Linux. You then run the Android User Interface (UI) bits on top of that, using the kernel to control access to the phone. The kernel is also firmware that's stored on a different dedicated partition of your phone's storage.
The kernel contains the drivers that allow access to the device-specific hardware in your phone. It also provides hooks for the Android system to control that hardware. You've got to have a kernel that's compatible with whatever version of Android you're trying to run; that's why devs need access to kernel source since that gives them the drivers that Android expects.
Note 4 owners over in the Verizon section are putting together a fair effort to investigate rooting themselves. We AT&T users should have a similar thread.
The Verizon thread, for reference:
http://forum.xda-developers.com/note-4-verizon/general/talk-root-t2908919
T-Mobile and Sprint have CF-Autoroot but not yet for AT&T and Verizon. So (I think) a new root should work for either, all the more reason to work together.
In the Verizon thread the general process was posted:
Surge1223 said:
I have no vested interest in this (other than seeing vzw get screwed over) but someone needs to get the ball rolling here:
1. Grab the Odin tar then boot.img to get kallsyms
2. Post partition info
3. Grab kernel source and confirm latest Linux kernel cves are patched/not patched
4. Find PoC for Linux exploits for 2014 Linux kernel cves and port them to android and test
If you have to ask what any of the above are/do Google is your friend.
Click to expand...
Click to collapse
Feel free to read through the other thread for info on CVEs and stuff.
The Verizon owners have to wait for kernel source but I guess our's is already posted (N910A):
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910
SHA1 and SHA256 for the kernel source zip that I downloaded, for reference:
99e00529ce613548664f3c986cd7df886b54caa0 SM-N910A_NA_KK_Opensource.zip
9a5dfcbcd1b77367507b9374afd4f1e1afd505255ff48b4d3779b235974650c0 SM-N910A_NA_KK_Opensource.zip
This might not be necessary as someone like Chainfire may already be working on a rooting method, but we might make it slightly easier.
Any contributions by more knowledgeable people are greatly appreciated.
Anyone want to post their kallsyms, boot, or full image of an AT&T phone?
I'll try to post myself if I can figure out of I'm supposed to use Odin or if the way the Verizon owners got their's was with some Verizon-only tool.
We have firmware here:
http://forum.xda-developers.com/note-4-att/general/stock-to-stock-odin-flashable-tested-t2915915
The kernel source is here:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910a
That should get us started.
Tikerz said:
We have firmware here:
http://forum.xda-developers.com/note-4-att/general/stock-to-stock-odin-flashable-tested-t2915915
The kernel source is here:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910a
That should get us started.
Click to expand...
Click to collapse
Nice! Yeah the kallsyms should definitely be in there.
Here are the kallsyms from the ATT image.
I've been googling but I can't figure it out
How do you get partition info from kallysyms?
v3ngence said:
I've been googling but I can't figure it out
How do you get partition info from kallysyms?
Click to expand...
Click to collapse
You don't. The kallsyms are information about the internal kernel functions, useful for writing code which gets you root access.
Partition information sits in a .PIT file inside the factory image (if it's available), or you can dump it from a running phone.
SirAthos said:
Here are the kallsyms from the ATT image.
They match the Verizon kallsyms. Good sign for finding a root method that works on both. :good:
Click to expand...
Click to collapse
They shouldn't match the Verizon n4 kallsyms... They should be different, if not then someone odd is happening..
Surge1223 said:
They shouldn't match the Verizon n4 kallsyms... They should be different, if not then someone odd is happening..
Click to expand...
Click to collapse
I'll extract them again, maybe I missed something...
Edit: Gah, still had kernel.Image extacted from the Verizon image, and didn't notice the message saying "kernel.Image: already exists; not overwritten". The attachment above has been updated. My apologies, and thanks for catching it.
This may be interesting though. The nexus devices have a check box in the developer settings to OEM unlock the phone. Basically you just check a box and it's boot loader is unlocked.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Maybe this can be used to find a loop hole on lollipop for this device. I think there could b be a small chance this device could get unlocked after the update. It might actually be easier.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
ShrekOpher said:
This may be interesting though. The nexus devices have a check box in the developer settings to OEM unlock the phone. Basically you just check a box and it's boot loader is unlocked.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Maybe this can be used to find a loop hole on lollipop for this device. I think there could b be a small chance this device could get unlocked after the update. It might actually be easier.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
While I appreciate the speculation, that's all this is, and at the moment we don't have Lollipop. I believe the OP specified good steps that should be looked into. I have downloaded the source code but am not exactly sure how to be looking for other then doing the steps as outlined: Finding the build date of the kernel then looking up know vulnerabilities in it. Obviously this is going to take a while and makes sense on where to look. Why focus on something we don't have when we could focus on what we do.
tl;dr We need to stay focused on the current task at hand. Also it'd be nice if this thread didn't get derailed with speculations.
ShrekOpher said:
This may be interesting though. The nexus devices have a check box in the developer settings to OEM unlock the phone. Basically you just check a box and it's boot loader is unlocked.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Maybe this can be used to find a loop hole on lollipop for this device. I think there could b be a small chance this device could get unlocked after the update. It might actually be easier.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
Didn't you get rid of your AT&T Note 4 for T-Mobile Note 4?
Tikerz said:
Didn't you get rid of your AT&T Note 4 for T-Mobile Note 4?
Click to expand...
Click to collapse
I write custom enterprise software for phones. I own many including 2 different Note 4s. Most provided to me by my company. So no I still have the AT&T Note 4, I also have a T-Mobile variant for the time being. My team also has a sprint model as well.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Srsroot
Has anyone heard if this actually works? I've been searching forums and the Internet in general looking for a possible root for the AT&T note 4
#SRSRoot: samsung SAMSUNG-SM-N910A (Build: KTU84P.N910AUCU1ANIE) #Android 4.4.4 Now Supported for #Root at SRSRoot.com (copied this from their twitter)
Drewsdad said:
Has anyone heard if this actually works? I've been searching forums and the Internet in general looking for a possible root for the AT&T note 4
#SRSRoot: samsung SAMSUNG-SM-N910A (Build: KTU84P.N910AUCU1ANIE) #Android 4.4.4 Now Supported for #Root at SRSRoot.com (copied this from their twitter)
Click to expand...
Click to collapse
wonder if we can get a dev to dl and take a look???
i looked through there list and i dont see our phone listed
Drewsdad said:
Has anyone heard if this actually works? I've been searching forums and the Internet in general looking for a possible root for the AT&T note 4
#SRSRoot: samsung SAMSUNG-SM-N910A (Build: KTU84P.N910AUCU1ANIE) #Android 4.4.4 Now Supported for #Root at SRSRoot.com (copied this from their twitter)
Click to expand...
Click to collapse
Just verified the tweet from October 26. I'm not sure, maybe this will be a pleasant surprise?
Mmm looking at the supported devices in their page I found the 910v and 910t... But no 910a
Monsi said:
Mmm looking at the supported devices in their page I found the 910v and 910t... But no 910a
Click to expand...
Click to collapse
I don't see it either. Their tweet says our phone specifically has been added. Not sure of the supported devices hasn't been updated or what. I'm kinda sketchy about trying stuff that I haven't seen discussed on here. Does anyone know if the stock firmware is available yet.? At least that way if someone ends up with a brick we can at least Flash it back to normal
Monsi said:
Mmm looking at the supported devices in their page I found the 910v and 910t... But no 910a
Click to expand...
Click to collapse
Pretty sure the Verizon crowd already dismissed this method. Likely a hoax.
Tried to find something in their forum but nothing... Something tell me that this is fake
Tried it and didn't get root.
hi guys i was digging around lg's source code distribution site and i have found source code for the t-mobile variant here is the link:
[url]http://opensource.lge.com/osSch/list?types=ALL&search=h932sv[/URL]
Useful for devs? probably
edit:
I have pulled /system [which without root only gave me most if not all LG Apps =1.54gb]
i also pulled /system/vendor and /system/framework [vendor gave me most libs. framework gave me the jar files and the framework.apk]
comment if that will be any use to anyone so i could upload to mega or google drive
R800x_user said:
hi guys i was digging around lg's source code distribution site and i have found source code for the t-mobile variant here is the link:
http://opensource.lge.com/osSch/list?types=ALL&search=h932sv
Useful for devs? probably
edit: They also have source code for the vs996 and ls998. The LS988 also has a LS988U version as well.
Click to expand...
Click to collapse
Can this actually help anything though? If they removed the commands, how will they get them back?
20degrees said:
Can this actually help anything though? If they removed the commands, how will they get them back?
Click to expand...
Click to collapse
Good point but if we get some development going that is, maybe someone can go over the source to inspect it for exploits. I'll finally have my hands on my phone tomorrow and I'll try to do a dump on the H932SV not sure if it'll help out though.
R800x_user said:
Good point but if we get some development going that is, maybe someone can go over the source to inspect it for exploits. I'll finally have my hands on my phone tomorrow and I'll try to do a dump on the H932SV not sure if it'll help out though.
Click to expand...
Click to collapse
It will help me a mile if you do bro. As im trying to port this to G4. Already have a working korean port in g4 thanks to @Astrako but no wifi calling and volte as the only thing missing..