yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mega] sashusmom:
sashusMOM- :p her!! Thanks Silesh;) Will try with the "box Thingy" directions first!:o
[Samsung Galaxy Mega] Silesh.Nair:
You never know these days!!! :)
[Samsung Galaxy Mega] sashusmom:
True!!

Well, @ boi- gave it a try with emulator- got to the next to last line and it closed the box- never got to put in the last line with your name. Now you know why I hate adb. I don't know if I put in extra spaces or didn't put spaces where they should have been. I've run python scripts for drm removal stuff, but that was on the old PC with a working adb.

Maybe someone with a little more know how to do that kind of stuff will be more helpful. I am not very techie :( I do well with blood and guts thou!!

I'm willing to try again if you have any better ideas.

*************************************************************************

Retried and I got with the first line su not found- kind of thought I needed root to use it. Am I wrong?

How was that going to send you what you need anyway??? If you need to PM me, feel free.

**********************************************************************

Installed S Manager- looks like does not need root to use it. But again, I don't know how to use the darn thing!!!
[Samsung Galaxy Mega] BoiBundy:
I'm sorry for the inconvenience, I woulda created a script but I figured it would be quick and painless to drop you the adb commands.

I was asking because I don't know all of the exact changes that came to KK.

Hm.. is kingo root not working for KK. If not then nevermind. I thought for sure that the root was working.:(

And to pull some of the info that I'm going to need, S manager will need to access root which it does.
[Samsung Galaxy Mega] sashusmom:
No inconvenience- I'm willing to do what I can- which probably isn't much, but I will try!

Tried kingo, towelroot 1&2- they do not work on KK. If you can figure out another way and I can do it, let me know.

************************************************************************************

So, I got a little excited here. I tried kingo again, and it reminded me to turn on usb debugging. So I checked, and couldn't find it. I realized I never tapped 7 times on the build number to turn on dev. mode! Duh!!!

Tried kingo again, and TR 1&2, but sadly, usb debugging didn't help at all.
[Samsung Galaxy Mega] gerg6986:
OTA KitKat update

I did the ota update and now my phone won't boot and when I go into the factory recovery it says unregistered software detected please take to nearest at&t dealer immediately. Can someone help me please?
[Samsung Galaxy Mega] BoiBundy:
Hope this helps~

Can you get into download mode:

Pull battery for 5 secs

Replace battery

Hold vol-down and Home key while powering on phone

If you see a little android in the middle of the screen you're in the right place.

NOW make sure you have Odin v309 and TAR Firmware package:

http://xdaforums.com/showthread.php?t=2739011 (That should be it)

Extract that package Odin v309.zip (DO NOT EXTRACT: I527UCUAMK2_I527ATTAMK2_I527UCAM.TAR)

Open OdinV309

Click on AP and find the file titled: I527 Tar.Tar.Md5

it should load right up

Hit start and let it do its magic.

Any other questions, just ask. Hope this helped.;)
[Samsung Galaxy Mega] sashusmom:
That stinks. I've read about this before when the update first came out. If you have an att store, I would bring it there. I think the last guy got a new phone.
[Samsung Galaxy Mega] gerg6986:
OK thanks guys I think I'm gonna try to get a new phone first...
[Samsung Galaxy Mega] tinfox:
Get a Nexus!
[Samsung Galaxy Mega] BoiBundy:
+1

I would still see if the phone goes into download mode:

Pull battery, replace battery, hold vol-down and home button while powering the device on.

and if you see the little android. PROFIT! Then take the phone back
[Samsung Galaxy Mega] gerg6986:
Yea it goes into download mode, I'm hoping to get a new mega because I have had nothing but problems with this 1 and I'm tired of it lol
[Samsung Galaxy Mega] sashusmom:
Good Luck! Let us know how it goes;)
[Samsung Galaxy Mega] malybru:
Mod Edit

Thread cleaned.

Please pay attention to what the ^^^[OP]^^^ has to say.

Thank you

malybru

Forum Moderator
[Samsung Galaxy Mega] sashusmom:
SEE!!! even Malybru doesn't want to hear me sing!:p Thank you sir or madam :) (Mod Edit) ;)
[Samsung Galaxy Mega] hopsin4444:
Thanks man
[Samsung Galaxy Mega] captemo:
WOW......was so busy here for a few weeks and now I can hear the crickets chirping again.

I think our phones are bi-polar......peaks and valleys
[Samsung Galaxy Mega] icemikesr2:
The truth always comes out. There was never a recovery in my opinion. If there was why would it take so long to duplicate again? Honestly I tried to help in the other thread but got no responses from either person. This phone is what it is. Take the good with the bad
[Samsung Galaxy Mega] captemo:
I still think it is obtainable, just going to take some work and patience. In my experience here last couple years, when it is quiet is when the anticipation builds. Not saying its true in this case, but many times there is something brewing.

A little bummed there has been no progress reported, but it is their time they dedicate for the benefit of others. I cant do it myself, so I patiently wait. I have no negative response, cause that is not going to make things happen any faster.

So be patient my friend, and stick around.
[Samsung Galaxy Mega] sashusmom:
Towelroot V3 is out

Towelroot v.3 is out and I am reading about it now. Geohot is introducing modstrings- the instructions are posted below. I am trying to make some sense of it.

from the towelroot.com website when you click on do it yourself- Reading it my head is starting to spin!!!! Exorcist anyone?:eek:

== Introducing modstrings! ==

Modstrings are a way to modify the exploit parameters for your obscure phone.

This is only if your device can't be towelrooted. ( which is our i 527 Mega )

Click "welcome to towelroot v3" 3 times and enter text.

1337 method(0-3), align(0-1), limit_offset(0-8191), hit_iov(0-7), temp_root(0-1)

method: which syscall is used in the blocking thread, try them all

align: which alignment to use for the iovs, try them all

limit_offset: 0 is probably the right value here, otherwise close to the samsung value and a multiple of 4

hit_iov: which iov to overwrite to cause block

temp_root: do a temp root putting su and daemonsu in /sbin, good for HTC and Motorola, doesn't fix exploit

To fix, align and method are probably your best bet(4*2=8 values), hit_iov maybe, limit_offset if you are desperate.

== Examples ==

Most phones: "1337 0 1 0 4 0"

New Samsung: "1337 0 1 7380 4 0"

Temp root: "1337 0 1 0 4 1"

**************************************************************************************

Does anyone understand this stuff?? I downloaded TR v. 3, installed it on the Mega, opened it and it looks like the same as the other 2. My phone is updating so I didn't hit "make it Rain" yet. I don't see anywhere to make any adjustments listed above.

***************************************************************************************

Duh!! I should read my own posts!!!! When you open TR, I needed to tap on the welcome sign and that opened a box to make adjustments.

So you just keep changing the value till you hit the right combo.

Would temporary root do anything for us?? Any value in it??

******************************************************************************************

I tried the 2 easiest combos with only 8 tries- align and method- no luck. Will try the next with Hit_iov next. Don't have a good feeling here. the next combo has 56 tries to cover- 7*8=56. That makes sense but I could be wrong.

Temporary root doesn't work anyway.
[Samsung Galaxy Mega] dparrothead1:
Hopsin, all of the keyboards are missing?
[Samsung Galaxy Mega] hopsin4444:
Oh I know man the same thing happened with the recovery file they all corrupted I changed my file holder to megiafire I'll post the link here in a minute they are all not re uploaded but there are some

---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------

New hopsin-kat custom KEYBOARD link

http://www.mediafire.com/?o6ol2du2styqp
[Samsung Galaxy Mega] waltm78:
Ok here's a different topic...Android L. Anyone taking a look at the preview yet?
[Samsung Galaxy Mega] dparrothead1:
I installed the keyboard and it's fugly!
[Samsung Galaxy Mega] hopsin4444:
One of mine!?
[Samsung Galaxy Mega] captemo:
I think he was referring to an android L keyboard.
[Samsung Galaxy Mega] dparrothead1:
No.....the L!!!!! Lol!!!!!
[Samsung Galaxy Mega] hopsin4444:
Oh lol I was like great what now man haha
[Samsung Galaxy Mega] dparrothead1:
Woke up this morning and found my Mega had tried to update itself during the night, again. Thank goodness for root!!!!
[Samsung Galaxy Mega] MeatHammer311:
US Cellular Samsung Mega SCH-R960

I have this phone and it was already updated to 4.4.2 when I got it. Does anyone have a REAL root method for this version of android? Thank you for your help!
[Samsung Galaxy Mega] starmaster10:
Haha..talk about nature call on the go. :D
[Samsung Galaxy Mega] sashusmom:
Capt!!! You are much younger than I thought!:p
[Samsung Galaxy Mega] captemo:
Not yeeeet
[Samsung Galaxy Mega] captemo:
Thats because I am very immature.

Sashusmom
[Samsung Galaxy Mega] MeatHammer311:
Modstring Help?

Can anyone help me figure out how to use modstrings with towelroot to make it work with my Mega?? Thank you!!
[Samsung Galaxy Mega] Opie Knievel:
I don't know how to get towelroot to work on your Mega but if you have a computer you can use Kingo to root it. That's what I did. It's simple to use and it works great.

Maybe you should read this article before using Kingo. I just saw this.

http://androidnews.co.in/2013/11/08/psa-use-kingo-root-vroot-root-android-device/
[Samsung Galaxy Mega] MeatHammer311:
Thanks!

My mega was updated to 4.4.2 out of the box. None of the current root methods work with it. Towelroot is my only hope at cracking this. But I need help with the modstrings to make it work. I appreciate you sharing that with me. I have scoured the internet looking for a real root. And geohots is the only one I can trust. Just need help making it work.. Thank you!
[Samsung Galaxy Mega] Opie Knievel:
Sorry, I forgot to ask if you were on 4.2 or 4.4. Have you tried any modstrings at all?
[Samsung Galaxy Mega] MeatHammer311:
Want to.

I want to try them I am just not sure where to begin. If you or someone here could point me in the right direction I can figure it out pretty quick.

---------- Post added at 05:36 PM ---------- Previous post was at 05:04 PM ----------

I tried the modstring that is provided on the towelroot website. No luck. phone rebooted
[Samsung Galaxy Mega] sashusmom:
I have tried the easiest ones to try. I think it is a total of 8 or 10 combinations. It doesn't work. The next combos to try are in the hundreds. Not worth my time.

To try combinations, you tap on the towelroot app at the top once you open it, and it will open a box so you can change the number combos. It's a matter of trial and error. But you have to keep some sort of log so you know what you have tried-what failed, and most importantly, what worked so you can share that combo.
[Samsung Galaxy Mega] MeatHammer311:
I am willing.

I am willing to try modstrings as many as I can I just need to know what numbers I need to play with. This is the modstring provided on the site. Just tell me which ones to change??

1337 0 1 7380 4 0
[Samsung Galaxy Mega] sashusmom:
There is a link in the towelroot site that has instructions- a sort of how to. You click on the word yourself and the following pops up-

The following is from Geohot's towelroot site, directions for using TRv3:"

"== Introducing modstrings! ==

Modstrings are a way to modify the exploit parameters for your obscure phone.

This is only if your device can't be towelrooted.

Click "welcome to towelroot v3" 3 times and enter text.

1337 method(0-3), align(0-1), limit_offset(0-8191), hit_iov(0-7), temp_root(0-1)

method: which syscall is used in the blocking thread, try them all

align: which alignment to use for the iovs, try them all

limit_offset: 0 is probably the right value here, otherwise close to the samsung value and a multiple of 4

hit_iov: which iov to overwrite to cause block

temp_root: do a temp root putting su and daemonsu in /sbin, good for HTC and Motorola, doesn't fix exploit

To fix, align and method are probably your best bet(4*2=8 values), hit_iov maybe, limit_offset if you are desperate."

== Examples ==

Most phones: "1337 0 1 0 4 0"

New Samsung: "1337 0 1 7380 4 0"

Temp root: "1337 0 1 0 4 1"

1337 0 1 7380 4 0

I did this line and none of them worked. To fix, align and method are probably your best bet(4*2=8 values), hit_iov maybe,"

this line - limit_offset if you are desperate. is the one with hundreds of combinations.

Good luck!
[Samsung Galaxy Mega] MeatHammer311:
Not sure.

I am not sure what that means. is it the last two digits in that or what. I am new to this. Thanks
[Samsung Galaxy Mega] sashusmom:
I learned by following the instructions geohot posted.. if you open the TR3 apk, tap 3 times, the window opens and you can re write the numbers in their sequence.. I no longer have TR installed, so i can't try it for you.. just try the easiest ways he suggested just to learn how to use that tool. it will reboot and thats a sign it didn't work.. when you know how to use it the last way has hundreds of combinations. keep track of what you have tried and try to do it in an organized manner.

good luck. pardon my all small letters....typing one handed at the moment.. read the TR thread for tips on how to use it.

*****************************************************************************************************************************************

OK. I have 2 hands now. This is not something I can tell you how to do. You have to understand how it works before changing the numbers. All I can suggest is to read the TR thread.

http://xdaforums.com/showthread.php?t=2783157

It's all trial and error. If you don't understand what you are doing it is a waste of your time. So read,read,read. Sometimes it takes me reading it 5 times before it sinks into my thick head, and a light turns on!!! Good luck!

If you happen to hit on the right combo, Many in this forum will cheer for you for hours!! :)
[Samsung Galaxy Mega] MeatHammer311:
Exynos SoC

The modstrings won't ever work because of the Exynos SoC your device uses. A simple search would have reveled that. Any Samsung device with a Exynos SoC can't be towelrooted. You could help by submitting (like in the very FIRST post) an adb logcat for your device so maybe geohot can start to work on something. ~ Eodmule XDA Member

I was just informed that this phone cant be rooted. If anyone can send a logcat for your mega to geohot can see if there is something he can do! Thank you
[Samsung Galaxy Mega] dparrothead1:
I'm afraid you have this device confused with the Tab 3 7". The I527 CAN be rooted......just not if you installed the 4.4 update.
[Samsung Galaxy Mega] sashusmom:
I have done that twice- with TRv.1 and TRv2. Please don't assume it wasn't done :p. By me and someone else in the party thread. I have read every page in that thread. I was told by Grarak that the exploit PinkiePie found is not in our kernel, so it won't work. I have read that the exynos processor(is that the same as exynos SoC?) is being rooted with TR on some devices- I think the Note 8 threads. I waited for rooted stock kitkat to come out before I jumped on board with civato's kernel. So I read a lot in that forum in the last 2 days. The only thing I didn't send geohot was a logcat with the 3rd TR. I have decide that nothing will root this phone on 4.4.2. Hopefully I am wrong.
[Samsung Galaxy Mega] Grarak:
This phone uses a snapdragon 400 msm8930ab

So it can be rooted according to geohot

Do a research before posting ****
[Samsung Galaxy Mega] dparrothead1:
Exactly!
[Samsung Galaxy Mega] sashusmom:
Thanks Grarak for posting. I did the easiest 10 combos with TR3. The next combos are in the 100's. Just didn't have the patience to do it:( Wouldn't be so bad if the phone didn't reboot in between tries. Seems the logcat either didn't record or I lost it before I could send it to geohot.
[Samsung Galaxy Mega] captemo:
WORD to your mother
[Samsung Galaxy Mega] MeatHammer311:
I was told..

I was told that info by another xda member. Glad someone here has some hope of rooting this amazing phone. I am up to try anything so if you have an idea lemme know. Thanks
[Samsung Galaxy Mega] sashusmom:
Do you have an external sd card that is now unwritable?

So I went and updated my Note 8 tablet. There is now a kitkat 4.4.2 rooted stock samsung rom using a kernel that bypasses samsung bootloaders and removes knox. So I spent my time the last 2 nites wiping and installing the rooted samsung stock rom for the Note 8.

I have philz touch recovery on it and I updated to the latest version. Flashed, and all was well except for my sd card. It was flaky with stuff not being seen, and recovery could not see the install stuff I had on it. :(So I copied contents to my laptop, reformatted it in fat32, and reloaded the backup. It had trouble with some stuff- files wouldn't load complete, so I had to check contents of files and mover over the balance. A real PITA.:mad:

Put it back in my tablet, recovery could read it fine. But my titanium BU would not back up due to "Insufficient space". :confused: Did some research, changed permissions of sd card with root explorer. That sd card still said in TitBU unwritable and same error as above. :confused:

Well......after a lot of searching in the note 8 threads, and following some to s4/s5 threads, Guess what I found out????

The update of 4.3(that we were denied by att for our Mega) broke the ability to write to the external sd card- especially 3rd party apps. I couldn't even write to the internal storage after changing the save folder in TB.

Unfortunately, that broken code was carried over to the kitkat roms in pretty much all devices. I haven't tried titBU in our i527 Mega. Anyone who updated to kitkat have this problem???

Well I found a fix for rooted devices, but our Mega is not rooted so we can't use it if our phones are affected.

For any of you with other devices on kitkat with the ext. sd write problem, here is the app in the play store that fixed it on my Note 8. sd fix kitkat writable. You will find it in your app drawer under the n's- Next app SDFix.

https://play.google.com/store/apps/details?id=nextapp.sdfix

You must be rooted. I ran it, and it fixed the problem. TitBU finally backed up to my ext. sd card. Had to change the folder in TitBU again. That was a little tricky. The sd card and folder was now writable.

Unfortunately I had reformatted my sd card in the tablet( before I knew the rom had broken that function), so again I have to restore all my stuff from backup on my laptop.

WHO knew?????? I hadn't read anything on this problem. Anyone else?
[Samsung Galaxy Mega] DaHulk07:
Root

So am I to understand that after updating to the 4.4.2 that you can root it, if so im updating but wud love a custom rom
[Samsung Galaxy Mega] captemo:
No you cannot.......even if could, still need recovery.
[Samsung Galaxy Mega] sashusmom:
From my post 137- directly above yours- I went back and bolded that line.

" Well I found a fix for rooted devices, but our Mega is not rooted so we can't use it if our phones are affected. "

There is no root method for kitkat for our Megas. And as capt. said- we have no custom recovery due to our locked bootloader. These 2 are different animals- especially with this monster. On 4.2.2 we are rooted with no ability to flash anything- no custom recoveries or roms dev'd for the i527. I believe we are the only one with the locked bootloader. Correct me if I'm wrong capt. Are we the only Mega with a locked bootloader?
[Samsung Galaxy Mega] dmxwyrw:
So wheres hopsin4444?

I owe someone a couple of SMHs.
[Samsung Galaxy Mega] captemo:
it has NOT happened in this thread yet, and I am sure most would agree.........

lets not turn this into a "bash Hopsin4444" thread. the guy had the courage to try..........I don't, I wouldn't know where to begin.

whatever the circumstances in his life, it is HIS life. good or bad, we don't control. no body has heard anything from Biobundy either. this was supposed to be a collaboration between them and others, yet I don't see folks bad mouthing him.

you never know, maybe they are secretly working with others and just trying to stay away from distraction? you never know.

remember.....it is very easy to badmouth and criticize what someone is doing or how they are acting, but to come up with a solution yourself is very different. easier said than done, but if you cannot contribute to productiveness, then what choice do you have but to be a spectator and supportive.

this is the "WE WIN- THEY LOST" philosophy.........

we have no recovery, roms, root....etc.

they have been trying, and everybody is saying, "they failed"

but if a recovery were found today, folks would be saying "we have a recovery"

I am sure my wording is kind of jumbled here, but I guess my point is to remain optimistic. how can we have the only device where these things are unobtainable.

everyone needs to keep up the good work and there will be a full body massage for any breakthroughs (to females only)
[Samsung Galaxy Mega] sashusmom:
:eek: I'll pass Capt!!:p I agree with your thoughts on dev bashing.

Geohot did not release any info prior to his breakthroughs on jailbreaking iphones. He just released and everyone had a party.

Same thing with towelroot. There was no discussion or prior knowledge of what he was up to with androids. He was never known to work on androids till now. He just released TR, and everyone had a party!!:good: My only thought is Cagusa should be kept in the loop since he sent his phone off with no strings as a loaner and tester. I am also staying positive.
[Samsung Galaxy Mega] dparrothead1:
I don't think anyone is trying to "bash" Hopsin. No one is asking for an ETA or demanding anything.

I understand he is doing this on his own time and doesn't owe us anything. It looks as if Biobundy has left the building but Hopsin is on here pretty much every day! How hard is it to post 3 liitle words "Still working hard"?

And, BTW, he still has Caguas's phone and Caguas hasn't heard from him since the 8th even though he has sent Hopsin several pm's.
[Samsung Galaxy Mega] sashusmom:
I was generally speaking dparrothead. On the other thread hopson started there were definitely bashers. And yes, I did read he still has caguas's phone. He is still hopeful and so am I:fingers-crossed: I always keep an open mind, heart, and give someone the benefit of the doubt:p

My husband still doesn't understand my optimism:laugh: Even after 29 years!!
[Samsung Galaxy Mega] captemo:
I was just trying to keep an off topic thread off topic. We all know it just takes 1 comment and it snowballs.
[Samsung Galaxy Mega] Teyshablue:
I'm just gonna blame captemo....and that parrot guy!
[Samsung Galaxy Mega] dparrothead1:
Yeah, let's take em out back and beat the crap out of them!!!! Oh, wait.....that's me......never mind!!!?
[Samsung Galaxy Mega] sashusmom:
Just got a laugh from that one parrothead:D
[Samsung Galaxy Mega] Moscow Desire:
Now, I will make this perfectly clear.

Off Topic is "1" thing.

Bashing people back and forth is a totally different thing.

Any more shenanigans, and I'll simply close the thread. Been cleaned way too many times.

Clear?

Thanks!

MD
[Samsung Galaxy Mega] Teyshablue:
That went well. lol
[Samsung Galaxy Mega] captemo:
Good talk
[Samsung Galaxy Mega] MeatHammer311:
About to sell.

I am about to sell my Mega for a rootable phone. I need root for a few important things and not having it is killing me. And geohotz was just hired by google so I am sure he wont be doing any more one click apps any time soon. This sucks...
[Samsung Galaxy Mega] captemo:
Todays possibilty of root and unlocking the bootloader.......
[Samsung Galaxy Mega] sashusmom:
You're killing me here capt:rolleyes: