Post Reply

ROOT BOUNTY FOR SGH-527 with 4.4.2 KitKat Update

30th June 2014, 06:10 AM   |  #1  
OP Member
Flag Flint~Town (Murder City, USA)
Thanks Meter: 59
 
66 posts
Join Date:Joined: Oct 2013
More
Greetings, fellow Mega-Maniacs!

I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.

I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).


The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.

I'm in for $10 at the moment, and I'll piss away more if needed down the line.

Who else is in? LETS GET THIS DONE, PEEPS!

Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Last edited by kmt5150; 30th June 2014 at 08:51 AM.
30th June 2014, 11:10 AM   |  #2  
Teyshablue's Avatar
Senior Member
CowTown!
Thanks Meter: 164
 
182 posts
Join Date:Joined: Sep 2010
Quote:
Originally Posted by kmt5150

Greetings, fellow Mega-Maniacs!

I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.

I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).


The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.

I'm in for $10 at the moment, and I'll piss away more if needed down the line.

Who else is in? LETS GET THIS DONE, PEEPS!

Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE

In for at least $20.
The Following User Says Thank You to Teyshablue For This Useful Post: [ View ]
30th June 2014, 01:26 PM   |  #3  
Eddie Bombay's Avatar
Senior Member
Thanks Meter: 60
 
573 posts
Join Date:Joined: Jun 2011
Put me down for 2 bucks.
30th June 2014, 03:55 PM   |  #4  
DarkAngel's Avatar
Senior Member
Flag Arizona
Thanks Meter: 229
 
464 posts
Join Date:Joined: Aug 2006
More
I know you stated you had tried it all but I have a couple questions for you.

#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.

#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?

================

Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....

================

1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .

1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.

( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).

The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.

2. Once flashed and booted into recovery, you'll be on the main screen.

( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.

3. Tick on Philz settings.

4. Tick on Re-root System (Super SU).

5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.

6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.

7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )

8. Enjoy being rooted afterwards.

=======================================

If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.

Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Last edited by DarkAngel; 30th June 2014 at 08:20 PM.
1st July 2014, 02:37 AM   |  #5  
Grarak's Avatar
Recognized Contributor / Developer
Flag Vienna
Thanks Meter: 7,286
 
2,467 posts
Join Date:Joined: Jan 2012
Donate to Me
More
Quote:
Originally Posted by DarkAngel

I know you stated you had tried it all but I have a couple questions for you.

#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.

#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?

================

Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....

================

1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .

1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.

( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).

The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.

2. Once flashed and booted into recovery, you'll be on the main screen.

( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.

3. Tick on Philz settings.

4. Tick on Re-root System (Super SU).

5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.

6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.

7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )

8. Enjoy being rooted afterwards.

=======================================

If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.

Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.

Bootloader is locked
So no recovery flashing

Sent from my GT-I9205 using XDA Free mobile app
1st July 2014, 09:10 AM   |  #6  
DarkAngel's Avatar
Senior Member
Flag Arizona
Thanks Meter: 229
 
464 posts
Join Date:Joined: Aug 2006
More
Quote:
Originally Posted by Grarak

Bootloader is locked
So no recovery flashing

Sent from my GT-I9205 using XDA Free mobile app

Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.

Sorry then, my method will not work straight forward. Good luck.
3rd July 2014, 06:46 PM   |  #7  
OP Member
Flag Flint~Town (Murder City, USA)
Thanks Meter: 59
 
66 posts
Join Date:Joined: Oct 2013
More
Prompt
Quote:
Originally Posted by DarkAngel

I know you stated you had tried it all but I have a couple questions for you.

#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.

#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?

================

Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....

================

1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .

1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.

( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).

The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.

2. Once flashed and booted into recovery, you'll be on the main screen.

( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.

3. Tick on Philz settings.

4. Tick on Re-root System (Super SU).

5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.

6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.

7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )

8. Enjoy being rooted afterwards.

=======================================

If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.

Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.

Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Last edited by kmt5150; 3rd July 2014 at 06:47 PM. Reason: Added info.
3rd July 2014, 10:25 PM   |  #8  
jstinger9489's Avatar
Junior Member
Thanks Meter: 2
 
14 posts
Join Date:Joined: Sep 2012
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/show....php?t=2722073

I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
8th July 2014, 08:42 PM   |  #9  
OP Member
Flag Flint~Town (Murder City, USA)
Thanks Meter: 59
 
66 posts
Join Date:Joined: Oct 2013
More
Prompt
Quote:
Originally Posted by jstinger9489

http://forum.xda-developers.com/show....php?t=2722073

I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.

Will definitely try this again when my phone gets here tomorrow and post updates...
The Following User Says Thank You to kmt5150 For This Useful Post: [ View ]
10th July 2014, 12:28 AM   |  #10  
OP Member
Flag Flint~Town (Murder City, USA)
Thanks Meter: 59
 
66 posts
Join Date:Joined: Oct 2013
More
Prompt
Quote:
Originally Posted by jstinger9489

http://forum.xda-developers.com/show....php?t=2722073

I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.

Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."

UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Last edited by kmt5150; 10th July 2014 at 03:17 AM.
Post Reply Subscribe to Thread

Tags
galaxy mega 6.3 root, i527ucubne7, kitkat root, mega, sgh-i527
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy Mega General by ThreadRank