yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] prking07:
The thing is mine is not canadian. It is from Puerto Rico from the carrier Claro PR. It just so happens to be a i337m also. Thats why im trying to figure out if this thing is bootloader unlocked or not.

Also when I rooted I never had the lock icon on boot like most did. Dont know if thats something to look for.
[AT&T Samsung Galaxy S 4 Android Development] DespairFactor:
Does the 1337M have a different stock recovery than the other variants? Has someone figured out a way to go back to the stock recovery successfully? It seems that is modifies the binary status when you flash TWRP.
[AT&T Samsung Galaxy S 4 Android Development] PeterGuru:
Mine never had the lock icon either ...

Mine never had the lock icon either ...

Perhaps this is a way to tell if your bootloader is already unlocked, but I could be wrong. Canadian variants of Samsung devices, specifically those similar to AT&T models, almost always have the letter "M" at the end of the model number. Perhaps yours is also one of these variants.

Peter

---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------

To be honest, I really don't know. Sorry!

Peter

---------- Post added at 02:40 PM ---------- Previous post was at 02:31 PM ----------

Message for Dees_Troy, the OP.

Any idea when some of the notable bugs will be fixed?

Here's what I can report so far (mentioned in one of my earlier posts http://xdaforums.com/showpost.php?p=41015833&postcount=8):

1) Extremely sensitive to touch, especially when using keyboard. It is quite common to get double and triple-entries when hitting a key.

2) Clock is out of whack, and it's not consistent. One day I may be 1h45m out, while last night I was about 2h50m out (always ahead of real time)

3) Screen does not come out of sleep by touching the screen. You must press the Home button. Perhaps this is standard for Samsung devices with a Home button, but I seem to recall that my Note II did not require you to hit the Home button.

Thanks,

Peter
[AT&T Samsung Galaxy S 4 Android Development] RMXO:
Did you set up for compression on the backup? Just asking since you didn't state that you used compression.
[AT&T Samsung Galaxy S 4 Android Development] PeterGuru:
No compression ...

No, I do not use compression. Right now it's not too much of an issue, but will keep your suggestion in mind if I run into storage issues.

Thanks,

Peter
[AT&T Samsung Galaxy S 4 Android Development] gdevil:
My phone doesn't show that lock icon either, and it never does it, it is I337M too, but it isn't of any of the Canadian Brand, I'm from Mexico, I only want to know if I flash this (CWM) and soft brick it, Can I restore it back via Kies or Odin perhaps?

Regards

Genaro
[AT&T Samsung Galaxy S 4 Android Development] RMXO:
If you set for compression, your backup will be a lot smaller. Their compression works very well & I use it on all my TWRP backups.
[AT&T Samsung Galaxy S 4 Android Development] JJ5150:
Goo Manager does its thing then says "No Recovery Found for this device".
[AT&T Samsung Galaxy S 4 Android Development] PeterGuru:
Recovery available on for Canadian variants ...

I see that you're in the U.S. I'm assuming, therefore, that you have an AT&T unit. As such, no recovery is yet available as far as I know. The recovery through Goo Manager is for the Canadian variants, and other otherwise similar SGH-I337M variants.

Peter
[AT&T Samsung Galaxy S 4 Android Development] penguinjoe:
I can vouch on the unlocked bootloader for the Canadian SGH-I337M. No problem loading recovery, but installing the SuperSU was rough as hell with TWRP's inability to scroll.

I know the SGS4's digitizer is new this time around and really sensitive, but please Dees_Troy, can we tune it down when the SGS4s are detected? I'm itchin to load up SM10.1 but don't want to go there with TWRP this wonky.
[AT&T Samsung Galaxy S 4 Android Development] hostilebynature:
ugh..i put my phone into a bootloop.

im on rogers s4...i rooted the phone with motochopper, then i flashed the recovery no problem. i then downloaded a rom and gapps and booted into twrp.

i hit wipe, then i formatted the system..which was dumb because i lost my rom and gapps and had to upload to phone again. i rebooted it then added the files again and booted back into recovery, flashed and it failed...so i tried to reboot and when i did it said my phone wasnt rooted anymore and if i wanted to install supersu...i clicked yes (damnit) and that put my phone into a bootloop.

any ideas?

---------- Post added at 10:36 PM ---------- Previous post was at 10:23 PM ----------

also i cant seem to mount usb-storage...any ideas??

im trying to copy over files from my computer to my phone and cant
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
I could never mount or copy files to my Note 1 when it was boot looped.
[AT&T Samsung Galaxy S 4 Android Development] penguinjoe:
You are a brave (or foolish) soul to try rom-ing on one of these so early. Personally I'm gonna wait a few months for the dust to settle and CM10.1 to mature for this variant. As well this recovery isn't quite there yet so I don't want to depend on it.

About the only thing I can think of is to push the stock image back on via odin (will remove the root) and root it again. This tactic usually got me out of boot loops in the past when a wipe wouldn't clear it.

Sammobile.com has up-to-date official images.
[AT&T Samsung Galaxy S 4 Android Development] hostilebynature:
yeah im doing that right now..downloading the rogers firmware as we speak...then ill root it again and try again ;)

it's close to impossible to break these things...i still have my galaxy nexus as my backup phone until i get this back up and running...besides..if all else fails..i have the handset protection thing that i pay $8 a month for...ill just smash it and get a new one. :P

i dont feel bad doing **** like that based solely on how much rogers (and the other 2 big carriers charge for service...**** em, they make a killing off off us)
[AT&T Samsung Galaxy S 4 Android Development] ZPaul2Fresh8:
Works great!
[AT&T Samsung Galaxy S 4 Android Development] mrdindon:
Same here,

But since it was too sensitive to touch pressure I wasn't able to enter my password to decrypt the device or maybe the decryption wasnt working ?

I hope it gets fixed :)

I get a ''E: Failed to Decrypt Data''
[AT&T Samsung Galaxy S 4 Android Development] force70:
Thanks for the update....did this update resolve the hanging which sometimes occurs at startup?

sent from my S3, S4 or Note 2
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
I don't think anyone know's yet. Still can't get update thru goo.manager. Still says latest is 2.6.0.0. Also thru goo.im the i337 is still not on the 2.6.1.0 list yet so not sure whats going on
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
the update hasnt made it to their websites jflteatt link yet. but it is on their jfltexx link. if you know how to repack the recovery for jflteatt you could get it now.

edit: nevermind i've done it for us. here is a flashable zip of 2.6.1.0 that works for jflteatt. have installed 2 android 4.3 aosp roms and they work fine. also the UI seems to be a bit more responsive than 2.6.0.0.

http://d-h.st/6pG
[AT&T Samsung Galaxy S 4 Android Development] Suzook1:
Shows up for me..goo is the safest way to install right?

---------- Post added at 01:40 AM ---------- Previous post was at 01:26 AM ----------

This is why I hate twrp. Phone rooted with custom ROM. Phone works great. I install update via goo and restart recovery and boom yellow triangle with unauthorized software notice. Mother #$%##%*&$$$&&&##@((+&
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
unauthorized yellow triangle = recovery not loki.
[AT&T Samsung Galaxy S 4 Android Development] Suzook1:
How can that be when its done through goo manager. Triangle away will fix booting but now recovery is FUBAR..how can I fix.....agh
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
That is because you're using a Google Edition ROM and you're buildprop says 9505G

When you ran goo it told you it will install recovery for the wrong phone model but you said yes?

Hmm you're way out is to keep trying to get back into rom from by going to download mode and rebooting from there. Change you're buildprop to Att model and re run goo. Make sure this time you got the right recovery coming you're way
[AT&T Samsung Galaxy S 4 Android Development] Suzook1:
grave so if I am understanding you, your saying I should continue to try and boot into recovery and when I get the yellow triangle, do power vol down the continue and hope it cycles into twrp recovery. Once there, what do I do ?
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Oh and its not TWR as you elegantly put it. Its the.......
[AT&T Samsung Galaxy S 4 Android Development] devilsadidas:
..

.

---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------

Is this loki'd?
[AT&T Samsung Galaxy S 4 Android Development] trueking7:
I have these same questions.

Sent from my Galaxy S4 running Omega v9 with Audism kernel v16 : good :
[AT&T Samsung Galaxy S 4 Android Development] Airtioteclint:
Thanks worked great. :good:
[AT&T Samsung Galaxy S 4 Android Development] devilsadidas:
This is def working so much better
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
No recovery is gone. You need to go to download mode and then hit cancel from there to reboot into Rom. Then change build prop and then load the right version
[AT&T Samsung Galaxy S 4 Android Development] :
Doesn't say it is, so I would flash loi-doki anyway--won't hurt--:)
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
It is lokid, and says in the zip name.

To those wondering...I have not experienced any hanging on the tarp screen...at least not compared to 2.6.0.0
[AT&T Samsung Galaxy S 4 Android Development] :
I only looked at OP, so appreciate info--:good:
[AT&T Samsung Galaxy S 4 Android Development] oak:
Thanks for the flashable zip, freebee269.

2.6.1.0 seems to work great.
[AT&T Samsung Galaxy S 4 Android Development] stoned99:
After flashing it, I can no longer boot into recovery, it boots in download mode. I changed my nuild.prop as suggested but that didn't fix it. Goo managers says I dint have any recovery installed...maybe I shouldn't have used twrp manager?
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Install ROM manager from play store. Install cwm recovery. Click on setup recovery if it tells you that you currently don't have one.

Once a list of devices shows up click menu.. a option that says show all devices will pop up, click it.

Scroll down till you see Samsung galaxy S4 (your model of device here!!!) Install recovery. Once you do, reboot to see if it goes into recovery. If it does you have recovery now and can try flashing twrp again.

Do you have an att i337 or the Canadian i337M...? I assume canadian because of your signature?
[AT&T Samsung Galaxy S 4 Android Development] stoned99:
Good idea for Clockwork mod but it didn't work either. There were no s4 in the list :( so I edited again my build.prop, same results. I guess my only solution is now to flash back the original firmware in odin then restore my custom rom.

Yes I have a Canadian s4.

Thanks for the help
[AT&T Samsung Galaxy S 4 Android Development] Febby:
On the list did you press the menu button as I told you to enable the show all devices? ... im pretty sure the galaxy s4 is in the list.

Step one: go to default device list and press menu:

Step 2: See the show all devices option after you click menu? Click it.

When you press it this will show up.

Step 3: press ok and then scroll down to samsung galaxy s4.

Step 4: after you select your model and fladh... That's all.

Step 5(optional) Flash to a stock i337m ROM and try flashing the i337m twrp recovery. :)
[AT&T Samsung Galaxy S 4 Android Development] stoned99:
Wouhou! Success! I hadn't click on the show all devices option... oops... Once it was installed, I went to Goo Manager's website and downloaded the tar for 2.6.0.1 and installed through mobile odin. I don't really care at the moment if Goo doesn't detect a recovery for my device. thanks for all the help
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Nicely done. You got a working recovery again. Enjoy. :)
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Thanks... On my 2.5.0.3 I was able to backup and wipe "preload".....but on this latest version preload isn't mentioned at all. When flashing new Roms I always wiped preload.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
I started hanging at teamwin blue startup screen again on newest 2.6.1.0. This is about the 5th time it's hung so far, anyone else?
[AT&T Samsung Galaxy S 4 Android Development] oak:
Ya, I hung too. Not as often as 2.6.0 though. And so far, only when recovery is called from a 3rd party app.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Yea same here, not as much as previous release. Can't really pin point it yet whats tripping the hang but seems if I do the normal vol up power & home button recovery boot its fine but if I do it by 4 way boot it hangs most of the time. Hmm, not a huge deal but still annoying...
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Not sure what it was but flashed 2.6.1 again wiped dalvik & cache then fixed permissions seems to be booting into recovery fine now. I've booted about 10 times to check & so far no hang...:confused:
[AT&T Samsung Galaxy S 4 Android Development] upndwn4par:
I haven't tried the latest version yet, but tripping the hang definitely has something to do with the USB port. I have flashed with TWRP hundreds of times and I have noticed that it almost never hangs when the device is connected to a computer or outlet. And if it does hang, plugging it to a computer or outlet immediately kills the hang.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Ahh, very well could be. Nxt time it happens I will see if it does it while pluged in or not...Thanx for the heads up...:good:
[AT&T Samsung Galaxy S 4 Android Development] oak:
I had 2.6.1.0 hang during a backup. I've reverted to 2.5.0.2 for now. 2.5.0.2 has never caused me a single problem.
[AT&T Samsung Galaxy S 4 Android Development] sky_fox:
I hate to say thisbut the last page of this thread was just detailed by iB4STiD . I mean he actually just wrote the guide telling you DO NOT update recovery through goo using kangabean because while you're on goo it is scanning your buil.prop a d it is eeing and registere GT-9505G , this is not your m9del and has an unlocked bootloader but WE DO NOT. SO it installed a custom recovery with a .Lok file built into it. @__x gotta read more man. Its not hard to get your rec9very back but what if this would have hard bricked your phone!!!?? Im sorry this happened and if you need help at all ill help you out. But try to learn from this mistake so it doesn't happen anymore. Good luck, bro. Sorry.
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
at first i didnt have any hangs on the twrp sign. today i had 2 hangs. my thought was "dammit it's still doing it!". i havent noticed the hang being caused by usb. i too will check next time it hangs if i am unplugged from usb or not.
[AT&T Samsung Galaxy S 4 Android Development] sky_fox:
Who uploaded the the twrp 2.6.1.0 ? Can you guys please make a cwm touch updated .zip?
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Nice gentleman right above your post did, [MENTION=5147371]freebee269[/MENTION]. Post #583, give the man a thanks
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
just the regular clockwork touch recovery? the 6.3.0.6 version?
[AT&T Samsung Galaxy S 4 Android Development] SUDroid:
How do you temporary boot into custom recovery on the s4 (I337M)?
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Vol up, home button, & power same time then when it vibrates let go of power but still hold other two till you see recovery screen
[AT&T Samsung Galaxy S 4 Android Development] SUDroid:
But isnt that stock recovery. I want to boot custom recovery without flashing it permanently on the device.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
That's any recovery for Galaxy S4 custom or stock. But your going to have to install a custom recovery if you want to boot into custom recovery
[AT&T Samsung Galaxy S 4 Android Development] SUDroid:
Can u flash custom zips in stock recovery like the xposed framework disabler?
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
No, if you want to flash your going to have to install a custom recovery. But to be honest with you if your going to do any tinkering besides just root, your going to want to install a custom recovery... :good:
[AT&T Samsung Galaxy S 4 Android Development] SUDroid:
Is it possible to revert back to stock recovery? And how and where do i find the file?
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Yes it is but you will have to odin back to stock. If you haven't already downloaded mdl firmware, it would be wise to download that also bc you never no when you may need it. You can get it from here...Link... You will need to register but its free to do so. Inter correct device then from there your looking for mdl build. Download that & use it to odin to stock
[AT&T Samsung Galaxy S 4 Android Development] rantoca:
thanks FreeBee

I tested in different way and work great

again thanks and have a great week
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Mine was doing great for a day and today almost every time I booted it hanged. Back to 2.5.0.2 for me as well.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Yea, same here. It's hanging more & more with me wether usb plugged in or not. Looks like I may have to go back to 2.5 as well
[AT&T Samsung Galaxy S 4 Android Development] ronnie498:
I went back to 2.5 about 5 mins after flashing the new, kept hanging
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Yah as soon as it hung for me in grabbed usb cord and nope. Didn't work either. Too bad. I like twr. 2.5 works great just can't format system or roms freeze. So I switch between cw to format and back to twr to install and run. Fun stuff. Glad it's so easy to swap recovery at least.
[AT&T Samsung Galaxy S 4 Android Development] sky_fox:
I believe either you didnt read correctly or maybe not know the differnce between CWM (clock work mod) & TWRP (team windows recovery project). I asked for a .zip to cwn(clock work mod ) touch . He didn't upload a cwm touch. He uoloaded a twrp 2.6.1.0 as it says in his post on post #583 thanis for trying to help but please know what youre saying so you dont make people waste their time. Thanks anyways though .
[AT&T Samsung Galaxy S 4 Android Development] _eroz:
I don't know if you read correctly or not but you do know that this is the twrp thread. If you want a cwm touch .zip you should go and ask in the cwm touch thread.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Oh, I read correctly & yes I do no the difference between the two recoveries. Maybe you need to go back & read the very first line from your first quote. I simply stated the users name that posted the upload for the twrp zip bc you asked who!!
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
:good:

---------- Post added at 12:28 AM ---------- Previous post was at 12:24 AM ----------

Huh?

I format /system and everything else almost every time I install a ROM.

Which is a minimum of once a week.

And I've been running 2.5.0.2 ever since it was release, except for ONE DAY that I was on 2.6. That was one day too much for me and I immediately went back to 2.5.0.2. Every thing I've ever used it for has worked flawlessly.
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
It happens more with TW variants
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
So your saying you format data on your S4 under wipe tab, the one that you have to type yes to continue & you have no problems after doing that?
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Yeah, I do that one also. I do every single wipe available in 2.5.0.2, including the /data option that requires you type "yes" before it proceeds with the wipe.

Never had a problem with any of them.

You guys do?
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Wown thats interesting. Yea, & quite a few others have had problems after they format data. Makes me wonder if that's actually what's causing it then
[AT&T Samsung Galaxy S 4 Android Development] freebee269:
That option wipes encryption on the internal SD. Try to install a touchwiz based rom after that. On boot you will get an encryption error from the rom. It's not advised to do that format at all.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
That was my take on this as well, sounds like he has had better luck than most...:confused:
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Or not using TW roms
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Yeah, I run AOSP ROM's. THe only time I have had TW on there is when I ODIN back to stock to fix a soft brick.

Well, actually I had Google Edition ROM also. But only for a few days and I don't really remember if I did a full wipe or not. I probably would have though, becasue that's my standard MO.
[AT&T Samsung Galaxy S 4 Android Development] topgun303:
TWRP 2.6.0.0 is stuck on teamwin screen. Cant get into recovery.
[AT&T Samsung Galaxy S 4 Android Development] obriane217:
Just press & hold power button till it boots back into recovery. It gets stuck at times. I had to go back to 2.5.0.2
[AT&T Samsung Galaxy S 4 Android Development] bo8:
Known issue that happens often. Flashing and using version 2.5.0.2 yields no such issue and it's just as good as 2.6.0.0
[AT&T Samsung Galaxy S 4 Android Development] Idan73:
Seems like 2.5.0.2 is the pinnacle of development on sgs4. Every subsequent version gets stuck more and more. Today after dozen tries and hangs on twrp screen, had to boot to download first to bypass recovery load, in order to boot phone and flash old version via mobile Odin. Anyways seems like dev does not even read comments here anyways...

Sent from my SGH-I337M
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
So, I just tested formatting everything including /system and /data with 2.5.0.2 and it worked fine with TouchWiz ROM's.

I was able to browse the internal SD card without problems.

When you guys wipe /system and /data, are you making sure to reboot back into recovery afterwards, before installing a ROM?

Here are my exact steps. I just documented this while I was testing a couple ROM's that I wanted to check out.

1) Restored to stock via ODIN using: I337UCUAMDL_I337ATTAMDL_ATT

2) Rooted & installed TWRP 2.5.0.2 with Casual_Root_Recovery.

3) Rebooted to recovery and wiped everything, including /system & /data.

4) Rebooted to recovery again and did factory reset.

5) Installed Kangabean GE ROM.

6) Waited five minutes, then set it up.

7) Rebooted twice.

8) Rebooted to recovery and wiped everything, including /system & /data.

9) Installed Kangabean Google Edition ROM.

10) Waited five minutes, then set it up.

11) Rebooted twice.Rebooted to recovery again and did factory reset.

12) Rebooted to recovery and wiped everything, including /system & /data.

13) Installed GoldenEye TouchWiz ROM AND ktoosez TW kernel.

14) Waited five minutes, then set it up.

15) Rebooted twice.Rebooted to recovery again and did factory reset.

16) Rebooted to recovery and wiped everything, including /system & /data.

17) Installed GoldenEye TouchWiz ROM *only*.

18) Waited five minutes, then set it up.

19) Rebooted twice.Rebooted to recovery again and did factory reset.

Going back to AOSP again now. C-Ya :P

ps. here are my wipe steps:

1) Advanced wipe & select Dalvik/system/data/cache

2) Factory reset

3) Format data (the "yes" option)

4) Reboot to recovery

5) Factory reset

6) Install ROM
[AT&T Samsung Galaxy S 4 Android Development] Febby:
Has anyone tried contacting the creators of twrp about the s4 issues? I mean a proper email report of the issue so they can try to work on it. :)