Related
I would assume this ROM (EF 3.5.1) includes permanent root, since there are directions for coming from stock ED01- would this be a correct assumption? I flashed this when i already had root, so I just wanted to make sure before doing the same on my wife's non-rooted phone. Thanks in advance.
artvandelay440 said:
I would assume this ROM (EF 3.5.1) includes permanent root, since there are directions for coming from stock ED01- would this be a correct assumption? I flashed this when i already had root, so I just wanted to make sure before doing the same on my wife's non-rooted phone. Thanks in advance.
Click to expand...
Click to collapse
Yes it is already rooted.
artvandelay440 said:
I would assume this ROM (EF 3.5.1) includes permanent root, since there are directions for coming from stock ED01- would this be a correct assumption? I flashed this when i already had root, so I just wanted to make sure before doing the same on my wife's non-rooted phone. Thanks in advance.
Click to expand...
Click to collapse
You are correct in assuming it comes rooted. As in it comes with the SuperUser permissions and application already in the ROM/System.
You are incorrect in calling it "permanent". Rooting is never permanent. You could flash another non rooted ROM and lose your root rights. How do I know? I have done it and it confused the hell out of me!
cheers!
gkirby11 said:
You are correct in assuming it comes rooted. As in it comes with the SuperUser permissions and application already in the ROM/System.
You are incorrect in calling it "permanent". Rooting is never permanent. You could flash another non rooted ROM and lose your root rights. How do I know? I have done it and it confused the hell out of me!
cheers!
Click to expand...
Click to collapse
lol, true. I guess i wasn't clear by saying permanent root. I knew you could remove root, as i have done quite often for OTA update testing, and so forth. by permanent, i just meant that root would stick if you rebooted it. Thanks for the helpful information though
__________________________________________________
This version is now deprecated.
Please use the updated version available at
[ROOT] Galaxy Mega 6.3 - GT-I9205 and GT-I9200
__________________________________________________
This is a rootable Galaxy Mega 6.3 kernel compiled from the official Samsung sources with
su and busybox binaries added to the initramfs.
The boot.img.tar file can be flashed with Odin as PDA.
Keep Auto Reboot and F.Reset Time selected.
To complete the setup Superuser.apk from SuperSU 1.34 must be installed separately.
While this kernel is compiled from the GT-I9205 sources it is confirmed to work on the GT-I9200 device too (see posts below).
Use at your own risk, I'm not responsible for bricking your device.
Please click Thanks if you found this helpful.
VCore said:
As nobody has published a custom rooted ROM for the Galaxy Mega 6.3 (GT-I9205) so far,
I compiled a rootable kernel from the official Samsung sources and added the su and
busybox binaries to the initramfs.
The boot.img.tar file can be flashed with Odin as PDA.
Keep Auto Reboot and F.Reset Time selected.
To complete the setup Superuser.apk from SuperSU 1.34 must be installed separately.
This is for the Galaxy Mega 6.3 (GT-I9205) only.
Use at your own risk, I'm not responsible for bricking your device.
Download: hera.net/boot.img.tar
Please click Thanks if you found this helpful.
Click to expand...
Click to collapse
It worked for me... i am rooted:good:
Thank you !!!!
Does this phone even work in the us on T-Mobile
ss beanz T989
Ok, confirming that i got root on my Mega 6.3 I9200 using this kernel.
1 i flashed this kernel
2 installed SuperSU 1.3.4
3 flashed the official kernel from Samsung
4 still have root access!
baladev said:
some people flashed this kernel on the i9200 model and it worked, you can flash the original kernel after that and you will still have root
Click to expand...
Click to collapse
I have the i9200 and confirm that this worked. I am now rooted. I have to admit it was scary taking the plunge. I just bought the device yesterday and was contemplating returning it. Did not want to brick my phone and have no recourse but it worked. I am now installing application on my device that require root and they are working.
curgervending said:
I have the i9200 and confirm that this worked. I am now rooted. I have to admit it was scary taking the plunge. I just bought the device yesterday and was contemplating returning it. Did not want to brick my phone and have no recourse but it worked. I am now installing application on my device that require root and they are working.
Click to expand...
Click to collapse
Good to hear that it also works on the GT-I9200.
Do you use my kernel or did you go back to the stock kernel after rooting?
VCore said:
Good to hear that it also works on the GT-I9200.
Do you use my kernel or did you go back to the stock kernel after rooting?
Click to expand...
Click to collapse
after rooting i just flashed the stock kernel
VCore said:
Good to hear that it also works on the GT-I9200.
Do you use my kernel or did you go back to the stock kernel after rooting?
Click to expand...
Click to collapse
I kept your kernel. Is there any benefit in going back to the original kernel versus just keeping your kernel on the device?
curgervending said:
I kept your kernel. Is there any benefit in going back to the original kernel versus just keeping your kernel on the device?
Click to expand...
Click to collapse
I don't think so. As far as I know, the GT-I9205 kernel just has the additional LTE driver which is not used on the GT-I9200 device and should not cause any problems.
Where can I find the stock kernel?
kiwi45 said:
Where can I find the stock kernel?
Click to expand...
Click to collapse
+1...thank you!..
hatememarkz said:
Does this phone even work in the us on T-Mobile
ss beanz T989
Click to expand...
Click to collapse
According to Phone Arena, the phone supports the following bands:
GSM:850, 900, 1800, 1900 MHz
UMTS:900, 2100 MHz
Note, the 1900 band is not under the UTMS, so I'm not sure if you will be able to get HSPA+ if you are in a t-mobile area that has been refarmed.
VCore said:
As nobody has published a custom rooted firmware for the Galaxy Mega 6.3 so far,
I compiled a rootable kernel from the official Samsung sources and added the su and
busybox binaries to the initramfs.
The boot.img.tar file can be flashed with Odin as PDA.
Keep Auto Reboot and F.Reset Time selected.
To complete the setup Superuser.apk from SuperSU 1.34 must be installed separately.
While this kernel is compiled from the GT-I9205 sources it is confirmed to work on the GT-I9200 device too (see posts below).
Use at your own risk, I'm not responsible for bricking your device.
Download: hera.net/boot.img.tar
Please click Thanks if you found this helpful.
Click to expand...
Click to collapse
where is the download link?
kamfat said:
where is the download link?
Click to expand...
Click to collapse
OP only has 3 posts, and cannot post links. It's in the OP.
http://hera.net/boot.img.tar
tokuzumi said:
OP only has 3 posts, and cannot post links. It's in the OP.
http://hera.net/boot.img.tar
Click to expand...
Click to collapse
thks.....
kamfat said:
where is the download link?
Click to expand...
Click to collapse
Just copy and paste hera.net/boot.img.tar to your address bar
tokuzumi said:
According to Phone Arena, the phone supports the following bands:
GSM:850, 900, 1800, 1900 MHz
UMTS:900, 2100 MHz
Note, the 1900 band is not under the UTMS, so I'm not sure if you will be able to get HSPA+ if you are in a t-mobile area that has been refarmed.
Click to expand...
Click to collapse
This is from Samsung's website under specs for the galaxy mega 6.3:
HSPA+ 21/5.76 850/900/1900/2100
EDGE/GPRS 850/900/1800/1900
I have the i9200 version of the phone and am using it on T-Mobile in NYC. I can confirm that I have gotten HSPA+ speeds as high as 12mbps download and 3.5mbps upload (although it's inconsistent - I think it has to do with the towers and the refarming of band 1900 - I also think we need someone to port an HSPA+ supported modem from a T-Mobile device over to this phone so we can have consistent speeds with signal stability).
Here is an example of the inconsistency: within a 15 mile drive my signal will fluctuate between HSPA+, Edge, G and, in certain spots, no cell or data signal at all. I'll get that full gamut of fluctuation all right within the 5 boroughs of NYC.
Just flash with PC Odin in download mode(VolDown+Home+Power).
Root working fine.
But, below 2 red lines showing on boot screen(while showing samsung boot logo).
wp_status_check sector:0 ; wp_status_buffer:0x0000000aaaaa
wp_status_check sector:0 ; wp_status_buffer:0x0000000aaaaa
Anyone face like this?
Johnnynho said:
Just flash with PC Odin in download mode(VolDown+Home+Power).
Root working fine.
But, below 2 red lines showing on boot screen(while showing samsung boot logo).
wp_status_check sector:0 ; wp_status_buffer:0x0000000aaaaa
wp_status_check sector:0 ; wp_status_buffer:0x0000000aaaaa
Anyone face like this?
Click to expand...
Click to collapse
This is shown on all devices using this kernel. I have not noticed any adverse effect so far.
VCore said:
This is shown on all devices using this kernel. I have not noticed any adverse effect so far.
Click to expand...
Click to collapse
Can someone please post a stock kernel TAR for the 6.3 MAE firwware? I would like to try and flash back just the stock kernel and see if i can get screen mirroring to work again.
Samsung has this annoying habit to block screen mirroring from working when running a custom Kernel or a custom recovery.
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
1. Rooting: I understand this wonderful rooting exercise is successful: http://forum.xda-developers.com/showthread.php?t=2290798. I would think since the Dev Edition is unlocked, an owner would only utilize Step 3, and NOT the kernel exchange section. Correct?
2. ROMing: Since the ROMS were created using the Loki enabled system, does this affect ROMing the Dev Edition since it is already unlocked? What does a user need to do? Or, does it not matter? Do the Loki enabled ROMS work on a Dev Edition?
3. Recovery: Again, it appears TWRP and CWM are Loki adjusted, so does this affect recovery on the Dev Edition and restoring? Also, is there a Stock Factory Image which will NOT turn the phone back to a locked bootloader? Or, does the one which exists OK to use?
I only ask these questions since a few of us are somewhat confused.
Thanking you in advance!
markwebb said:
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
Click to expand...
Click to collapse
I've been thinking about buying the Verizon S4 Dev Edition phone, but have been hesitant due to not knowing how simple it would be to root. Is it as simple as just running MotoChopper? Or is there a better way?
Being that the bootloader on this phone is truly unlocked, can you install the current versions of CWM or TWRP that are LOKI enabled, and will it work on this phone? I haven't seen any compiled versions that were non-loki (standard).
Same question goes for kernels too.
The first batch of Dev phones sold out in less than 24 hours, so I'd expect some of the people that have them would start posting their experience with it here soon. At least, I hope so!
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
markwebb said:
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
Click to expand...
Click to collapse
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
guyd said:
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
Click to expand...
Click to collapse
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
markwebb said:
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
Click to expand...
Click to collapse
From what I've been able to gather, Samsung has put in place a SetUID restriction on the stock release kernel via CONFIG_SEC_RESTRICT_SETUID. Apparently the D2 prerelease kernel doesn't have this restriction in place. That seems to be why flashing that is required prior to using MotoChopper to gain root. What I can't figure out is why you can flash the release DK afterwards and still keep root?
On the T-Mobile and Sprint S4 they've been able to remove the SetUID restriction on their latest DL release kernel by recompiling the kernel source with the SetUID restriction commented out
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Click to expand...
Click to collapse
I think I may have found a solution. With the Developer Edition we have an unlocked bootloader, so there is no need to use loki. I was looking for a non-loki patched (normal) recovery that could be flashed in Odin. I think I found one here http://forum.xda-developers.com/showthread.php?t=2322675. Look for the "Latest version can be found here" link, not the "loki patched" link. The filename is : Philz_touch_5.06.6-jfltevzw.tar.md5
If this works like it did in previous unlocked Samsung devices, then we should be able to flash the custom recovery in Odin, and then boot into recovery afterwards to flash SuperUser. From there, we're rooted.
If I had my dev edition S4, I'd test it out myself. But I'm still waiting for them to get back in stock!
Great..am somewhat game to try. Well report back. Thanks!!
Sent from my SCH-I545 using xda app-developers app
IT WORKED...somewhat!!! When it boots, I now get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Not really rooted though. Can't update binary and when in Root Explorer I can explore most folders but Root checker says I am not rooted.
Now what do I do? LOL
markwebb said:
IT WORKED...somewhat!!! When it boots, I nLet me know how it goes ow get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Click to expand...
Click to collapse
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
guyd said:
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
Click to expand...
Click to collapse
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
markwebb said:
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
Click to expand...
Click to collapse
Do you now have root with the stock DK kernel, or did you flash a custom kernel?
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
guyd said:
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
Click to expand...
Click to collapse
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
markwebb said:
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
Click to expand...
Click to collapse
Good question. From what I have seen thus far, the recovery is the piece that has to be Loki adjusted to allow it to be flashed on a locked bootloader. I don't think the ROM cares one way or the other. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
guyd said:
Good question. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
Click to expand...
Click to collapse
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
markwebb said:
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
Click to expand...
Click to collapse
If we could get an MD5 of the Developer DK kernel (boot.img), and compare it to the MD5 of a completely stock DK kernel (boot.img). Or maybe compare the kernel build numbers? I dunno, just throwing some ideas out.
My att note 3 is giving me too much trouble with gps. I'm giving up on it. Thinking about getting the tmobile s5 instead of att for the unlocked bootloader. I'm just trying to find myself root and recovery guides but I don't see them .. Please point me in the right direction
Bump
Here you go.
http://lmgtfy.com/?q=how+to+root+the+T-Mobile+galaxy+s5
Sent from my toaster
blackknightavalon said:
Here you go.
http://lmgtfy.com/?q=how+to+root+the+T-Mobile+galaxy+s5
Sent from my toaster
Click to expand...
Click to collapse
The reason I asked on here is because I was hoping for something better, more "official" on xda than just some Googled sites... people brick phones over things they get from the Internet
optimusv45 said:
people brick phones over things they get from the Internet
Click to expand...
Click to collapse
Well...XDA isn't a telegraph service.
blackknightavalon said:
Well...XDA isn't a telegraph service.
Click to expand...
Click to collapse
What do you mean ? I looked up what telegraph means, and can relate it to what we are talking about ..
http://forum.xda-developers.com/showthread.php?t=2723994
I think I found what I was looking for
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2723994
I think I found what I was looking for
Click to expand...
Click to collapse
not sure about other methods of rooting, but I'm pretty specific in avoiding the breakage of KNOX... if you're the same, here's an up-to-date guide to root and keep KNOX at 0x0 http://forum.xda-developers.com/tmobile-galaxy-s5/general/how-to-root-s5-firmware-knox-0x0-t2909352
dimm0k said:
not sure about other methods of rooting, but I'm pretty specific in avoiding the breakage of KNOX... if you're the same, here's an up-to-date guide to root and keep KNOX at 0x0 http://forum.xda-developers.com/tmobile-galaxy-s5/general/how-to-root-s5-firmware-knox-0x0-t2909352
Click to expand...
Click to collapse
With this you'll still need to odin the recovery. So exactly trigger knox ? I think I'll just odin the recovery, not bother with rooting the stock rom, and just flash a rom
optimusv45 said:
With this you'll still need to odin the recovery. So exactly trigger knox ? I think I'll just odin the recovery, not bother with rooting the stock rom, and just flash a rom
Click to expand...
Click to collapse
Odin the recovery? no... if you're on the latest ROM already, all you do is Odin the NE6 kernel given in the post, run towelroot, verify root, Odin NK2 kernel back and bam! rooted the latest NK2 ROM with KNOX intact.
dimm0k said:
Odin the recovery? no... if you're on the latest ROM already, all you do is Odin the NE6 kernel given in the post, run towelroot, verify root, Odin NK2 kernel back and bam! rooted the latest NK2 ROM with KNOX intact.
Click to expand...
Click to collapse
I understand how the method works. It's like they can't root the latest kernel or something so revert back for root and come back. My point is if your final goal isn't just a rooted stock phone, there is almost no point in this ? Because since the phone doesn't have a looked bootloader you can just odin a recovery and flash a rom without rooting first
optimusv45 said:
I understand how the method works. It's like they can't root the latest kernel or something so revert back for root and come back. My point is if your final goal isn't just a rooted stock phone, there is almost no point in this ? Because since the phone doesn't have a looked bootloader you can just odin a recovery and flash a rom without rooting first
Click to expand...
Click to collapse
well yeah, no point in this if you're looking for more than a rooted stock phone...
Nice, this is my first time getting a tmobile device. So tired of att lock down. Can't wait for a real recovery on a good phone
Bump so I can find this easy in a few days.m
Since the update on Saturday I can't get more than 2 hours SOT,before the update (lollipop) I used to get 3-3.5 sometimes 4. Same exact apps, settings (Wi-Fi on when home off when not,mobile data on when not on Wi-Fi auto switch enabled,GPS on all the time with little GPS usage mainly google location services being used ,everything "optimized". I'm really lost here. If anyone can tell me their experiences before and after the update that would be great with setting changes if available. NOTE: I'M NOT ROOTED (PURE STOCK).
Anyone?
Sent from my 0PJA2 using Tapatalk
My suggestion would be to try this.
1. Root your device and S off.
2. Flash a custom Rom
3.profit.
mammothjojo88 said:
My suggestion would be to try this.
1. Root your device and S off.
2. Flash a custom Rom
3.profit.
Click to expand...
Click to collapse
Don't you have to pay to get s-off? Does anyone have any other suggestions?
mammothjojo88 said:
My suggestion would be to try this.
1. Root your device and S off.
2. Flash a custom Rom
3.profit.
Click to expand...
Click to collapse
I'm rooted and battery life is no better
@racingmatt1 yes you do. 25.00 for s off via sunshine. @Deathmeter let's look more into it. Have you s off?
mammothjojo88 said:
My suggestion would be to try this.
1. Root your device and S off.
2. Flash a custom Rom
3.profit.
Click to expand...
Click to collapse
You don't need s-off to flash custom rom or root.
Unlock bootloader, flash twrp recovery, flash custom rom, root (No need for s-off in all that)
And as @Deathmeter said, no improvement in battery life with custom rom or root
mammothjojo88 said:
@racingmatt1 yes you do. 25.00 for s off via sunshine. @Deathmeter let's look more into it. Have you s off?
Click to expand...
Click to collapse
No I'm not s-off
I'm S-Off with the latest Viper Rom and my battery life is also crap since the update.
sharky17 said:
I'm S-Off with the latest Viper Rom and my battery life is also crap since the update.
Click to expand...
Click to collapse
There is a new kernel in the sprint Android development section(I use it on badboyz ROM)... with a few tweaks from flars kernel app I use, battery life has improved for me.