yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] BeansTown106:
To me this looks like a more in depth version of kexec.. but without all t b e rebooting.. im still at work so I have only had time to glance at this but im still hoping for more of an irom type unlock or leaked aboot..
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
I'll make a CASUAL sometime this weekend for it. I'm almost positive that I can make it a one-click after reading a bit about it...

It is a very dangerous procedure. However, I've been working on making steps to allow developers to easily package CASUAL applications as a part of the build process. Once I finish getting things worked out, I could probly write a generic "flash kernel/recovery/kill OTAs" build-script which would just require a developer to deposit the file into a zip file, execute a packager and upload.. anyway, that's something for the future..

From what I'm seeing, [MENTION=4229979]djrbliss[/MENTION] exploit will be patched over quickly. Qualcomm + Samsung + AT&T will all object :) Awesome work [MENTION=4229979]djrbliss[/MENTION] and that's an amazing exploit man.

Because of that, it will have a limited lifespan... I will see if I can get something set up quickly and release the CASUAL+CASPAC+CASPACkager with instructions soon.
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
No, the way this works, from my understanding, is....

Booloader loads kernel header with instructions as to where to load

Bootloader pulls kernel from EMMC and loads it into memory specified by header

Bootloader checks are overwritten by values specified in kernel header.
[AT&T Samsung Galaxy S 4 Android Development] BeansTown106:
Kk ill look more in depth into it when I get home fron work
[AT&T Samsung Galaxy S 4 Android Development] raitchison:
Wouldn't you always be able to downgrade via ODIN and still use this method even if they fix it? I'm not a dev but I'd think anything they can fix via an OTA will be revertable by downgrading.
[AT&T Samsung Galaxy S 4 Android Development] KY Wildcats:
in other words, only one month until we can get our Google Edition S4s!
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
You can downgrade firmware...but not actual bootloaders and the deep stuff related to bootloaders, at least that's how it was with my Samsung infuse - as soon as you upgraded to gingerbread you could never load a froyo bootloader however you could still run froyo if wanted - so no, anything fixed in an ota will not be fixable through an Odin downgrade
[AT&T Samsung Galaxy S 4 Android Development] blkghost22:
got a custom recovery installed and making my back up now....
[AT&T Samsung Galaxy S 4 Android Development] fix-this!:
thanks for comment and your dedication.
[AT&T Samsung Galaxy S 4 Android Development] greenzone560:
Yep, thats how it works I read the article. Pretty much in plain words it boots with emmc (which is unsecured) and which exits with no errors in the kernel, then it makes the phone think that its secure and it overwrites the old bootloader. Yeah Adam this is somewhat dangerous for most people to use. Is there a way to overwrite if you mess up? Or does it lock down the boot sequence forever?
[AT&T Samsung Galaxy S 4 Android Development] mohan_kr:
Actually, I don't see any danger here? The bootloader is untouched. So if you mess up you should always be able to ODIN back. The big issue is if people take OTA updates and the bootloader is patched and *if* none of the QFuse/Counter is touched, then you def. have a possibility of brick if flashing the loki' patched boot/recovery image, since it is tied to the bootloader as distributed by Dan.
[AT&T Samsung Galaxy S 4 Android Development] greenzone560:
Here is a custom recovery already with the exploit...I just tried it and it worked flawlessly :) I now have a custom recovery!

http://xdaforums.com/showthread.php?t=2262996
[AT&T Samsung Galaxy S 4 Android Development] Relys:
Very easy to install too. :)
[AT&T Samsung Galaxy S 4 Android Development] xdeslitx:
so does this mean we can flash ROMs now with the LOKI'd TWRP?

or can we only use the LOKI'd ROMs?
[AT&T Samsung Galaxy S 4 Android Development] greenzone560:
I tried several roms and none seem to be able to take the boot.img properly. Something about the OS not being authorized by AT&T.
[AT&T Samsung Galaxy S 4 Android Development] xdeslitx:
thanks for confirming that. so from what i understand we can only flash roms that have been loki'd like "CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT" correct?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
This has already been covered in the first post of this thread...

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

"I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?

Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin."
[AT&T Samsung Galaxy S 4 Android Development] xdeslitx:
thanks didnt see that thread :good:
[AT&T Samsung Galaxy S 4 Android Development] dannyyyyy:
I dont even have an at&t s4 but damn you guys are working hard!
[AT&T Samsung Galaxy S 4 Android Development] bhp090808:
You can flash any tmobile tw based rom as long as you flash a lokifyed tw kernel right after. Flashed 3 so far. Running death star ver. 2 right now
[AT&T Samsung Galaxy S 4 Android Development] thacounty:
Oh Snap! Didn't know that. Trying this soon...
[AT&T Samsung Galaxy S 4 Android Development] neo_styles:
Sub'd on this. Glad you're not backing down without a fight, OP.
[AT&T Samsung Galaxy S 4 Android Development] Jonnyredcorn:
I assume the same can be said for i9505 ROM's?

Sent from my Tablet
[AT&T Samsung Galaxy S 4 Android Development] jthrasher47:
Yes you can I am running omega right now
[AT&T Samsung Galaxy S 4 Android Development] Proweedsmoker:
Sorry to stray, but does the same apply for VZW phones also, just flash a lokid kernel after the rom and were rolling?
[AT&T Samsung Galaxy S 4 Android Development] mattdm:
Guys. This is not the place for this type of discussion. Take a look at the the rules:

So take it somewhere else, ok?
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
There is a new developers only section in the AT&T S4 forum. I think this thread would be better served there so the Devs can keep it clean.
[AT&T Samsung Galaxy S 4 Android Development] fix-this!:
when the google based s4 hits in late june will that help us get this bootloader fully unlocked? i assume that phone will be very similar to ours?
[AT&T Samsung Galaxy S 4 Android Development] :
The t-mobile one is similar and the didn't help so I doubt it.
[AT&T Samsung Galaxy S 4 Android Development] fix-this!:
right but the google edition might, unless adam corrects me here. i dunno im just hoping it will. :silly:
[AT&T Samsung Galaxy S 4 Android Development] JohnMonsour:
There is really no reason for a fully unlocked bootloader. We have achieved kernel access via dans loki kernel exploit. The only differnce is that if you want to chamge the boot image it has to be in loki format. That's really the only difference. And with xposed framework we can virtually change every aspect of the rom without kernel access. Just root.

check out my newb pack for the att gs4. http://xdaforums.com/showthread.php?t=2292932
[AT&T Samsung Galaxy S 4 Android Development] toxicpaulution:
We do need an unlocked bootloader. If we do not achieve it, when a patch comes out it will cover up our exploit. That's why we need to unlock these boots.
[AT&T Samsung Galaxy S 4 Android Development] lowspeed:
Agree, when new batch of phones come out patched...
[AT&T Samsung Galaxy S 4 Android Development] King Cole:
There's also security in knowing that your bootloader is unlocked that you do not get with the current Loki exploit.
[AT&T Samsung Galaxy S 4 Android Development] plwalsh88:
How would that help any more than all the other unlocked variants already in use?
[AT&T Samsung Galaxy S 4 Android Development] JohnMonsour:
Well the only way the Damn bootloader is getting unlocked is if samung either leaks a bootloader unlock or officially releases it like motorola did back in the day for the atrix. The encryption is pretty much uncrackable with modern technology.... so it would have to be a brute force and a huge stroke of luck. I think we can do it. But if we figure it out unofficially than it will just be hardware patched in newer gs4s anyway....
[AT&T Samsung Galaxy S 4 Android Development] russiandivxclub:
So ....... uncrackable ? Last time I heard that word some kid in Korea hacked H5 Direct TV card in about 30 minutes ..... But seriously i337 owners are screwed ? Any "official" word on this one ?
[AT&T Samsung Galaxy S 4 Android Development] lgkahn:
Sticking with my s3 running a Canadian to so I have tethering and integrated sip... att can bite me if they think I am buying one of there phones where they locked the boot loader.

Sent from my GT-N8013
[AT&T Samsung Galaxy S 4 Android Development] Mike:
Stop posting here. Notice how all the development talk and community strive for a complete unlock has ceased, at least in this thread, once all you guys came in with your unrelated comments. Keep it on topic of development. If you want to throw in random comments or your opinion on the bootloader being locked by your carrier/Samsung then take it somewhere else.

"The rules

Keep this thread clean. I'm asking for strict moderation. If your comment doesn't advance the thread, it will be reported and put in que to be deleted. The whole point of this thread is to maintain high information density. This isn't a support thread. If someone has a "user-level" question about something, take it to a new thread in the Q&A forums. The mission isn't to support everything.. We're focusing on just one thing and that's:

Lets get this bootloader unlocked"
[AT&T Samsung Galaxy S 4 Android Development] igotroot:
Anything new Adam?
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
nope. As long as Samsung leaves Loki operational, we will be fine.
[AT&T Samsung Galaxy S 4 Android Development] :
Don't you think it's a little suspicious that AT&T / Samsung has taken quite a while since the last update to push one out?

International variants have gotten about 3 since the loki exploit
[AT&T Samsung Galaxy S 4 Android Development] alacrify:
I think you post a lot, and don't help as much as you should. Your point?
[AT&T Samsung Galaxy S 4 Android Development] :
My point being is that they're obviously patching it and it has been patched on the Galaxy S4 Active which is almost identical. That's my point. And I help plenty enough. XDA isn't my entire left.

Anyways back to the topic of the matter carry on.
[AT&T Samsung Galaxy S 4 Android Development] _Dennis_:
Since when do US carriers push updates as fast as international? Honestly I'm not surprised when we go 5-10 updates behind international phones.
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Well it appears it may be time to look back into this...adam have you checked out the new update? The current root method has been confirmed not to work...and im assuning loki has been patched as well
[AT&T Samsung Galaxy S 4 Android Development] scott14719:
I propose cleaning this thread out and moving it to the "Developers only" discussion area to keep off-topic posts out of it. I think that will provide a better environment for this type of thread.

I think Adam would have to make the request...if he wants to.
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
I haven't have you tried flashing the stock rom first then flashing this?
[AT&T Samsung Galaxy S 4 Android Development] Aou:
I found out, sort of. As you probably saw in my other thread, I flashed sb2 and sbl3 (technically along with RPM) from the latest MF3 OTA update. The result was the phone resorting to emergency boot, showing up in QPST as being in Download Mode. Problem I have is, no signed .hex file. My Riffbox should be here later this week, along with a handy, no-solder PCB to keep my device in original condition. I'm counting on it being able to push something bootable to at least bring my Odin back. From there, I could survive of course (even if I was forced to update the rest to MF3, ...).

Enough chit-chat. I want to ask you some questions. I'm hoping you have a moment to address these properly.

If an efuse is blown with an update (with MF3, seems to be the case - odin will refuse to load MDB or MDL - mentions something about the fused number being greater than the firmware number), can JTAG override this check? e.g. could MDL sbl2 and sbl3 be placed back on the device via JTAG or even DD, given they are signed and would be accepted by sbl1?

Further, could a rooted MF3 user (who's taken the full update but managed to keep root) use recovery or DD to forcefully restore an MDL version of sbl2, sbl3, RPM, TZ and ABOOT? It appears sbl1 was left untouched, so what would prevent it loading sbl2 if it were somehow present? Obviously a modified aboot could prevent reflashing these, but I'm looking at DD and recovery specifically.

Did you ever find the answer to, "what happens if we flash a whole new bootloader chain to the device?"? If I'm able to restore my device easily with JTAG, I would be interested in trying this as well, if its worth anything.

Once I obtain JTAG, would you be interested in an additional guinea pig for a short period while I have my phone disassembled? If you have anything that might be worth a shot, but still recoverable via JTAG, I would gladly try it.

Thanks for your time, and your invaluable contributions. I can understand your frustration with this thread and the general community right now, and the overall lack of respect that's been shown to you in this thread alone. I'm hoping that we can pick this up again and perhaps look on it with new light, now that MF3 has released and brought forth chaos.

also, it would be cool to run some native linux on the S4, dontcha think? ;)
[AT&T Samsung Galaxy S 4 Android Development] Aou:
Answer: Flashing any part of the new MF3 bootloader will indeed blow the e-fuses - but not only to block Odin from flashing the older bootloader... but also to block the older bootloader from booting at all. Even JTAG cannot restore MDL to these devices at this time.

First of all, I was a fool to think that an MF3-updated, rooted user (via rootkeeper, or whatnot) could have a custom recovery. Because of the patched ABOOT, the Loki exploit is gone - no custom recoveries or custom kernels.

Secondly, for the same reason as #1 above, if someone tries to restore an MDL bootloader onto a device that's fused for MF3, it will hard-brick.

I would still like to find this out. I was not able to JTAG/restore my brick yet, and I'm thinking it's because I need the MF3 Kies package. Even still, with the device being fused for MF3+, I probably won't be able to test this unless the replacement bootloader chain is also fused the same (i.e. an unlocked, samsung-signed bootloader chain that also happened to blow the same e-fuses... unlikely to be found). Nonetheless, I'd be willing to try anything with the brick I have here.

This offer stands. If/when I successfully JTAG this thing, I'd be willing to throw anything at it. Just send a link, and I'll flash it. ;)

At this time, it would appear that development for the unlocking of the I337's bootloaders have essentially come to a halt. After all, what Dev would want to risk the MF3 update on their phone to try to crack it (or even root it) when it means they would risk losing Loki/root/all? Every reasonable Dev out here is going to avoid MF3 like it's the plague.
[AT&T Samsung Galaxy S 4 Android Development] upndwn4par:
Hopefully Adam will. ERDs are given devices by xda, so maybe he can score an S4 strictly for research purposes. :)

I think the take home message here is that we all need to consider moving on to a more developer and customer friendly OEM (like HTC or Sony). This is sad because Samsung makes great devices.
[AT&T Samsung Galaxy S 4 Android Development] svs57:
Let me ask a very stupid question.

Why can not we flash the bootloader from i9505 on i337?
[AT&T Samsung Galaxy S 4 Android Development] Aou:
I was definitely going to try this if I got my device up and running again, but with all the e-fuses that didn't work out.

My guess as to why it wouldn't work anyway (even on a brand-new, MDB/MDL device): They've likely written the ibl to only accept firmware intended for the i337. Unless someone can confirm that the ibl on both devices are the same?
[AT&T Samsung Galaxy S 4 Android Development] AdamOutler:
It's not even worth it to flash anything over to "test". Read back a few pages through all the mish-mash and you'll find where I talked about the security features. Each bootloader is signed per-device model per Qualcomm bootloader signing procedures. On top of that, the bootloaders are revisioned using the monotonic counters of the e-fuses.

In order to make something work, we would need one of the following

Qualcomm's private signing tool(might be possible) --Samsungs private signing keys(never going to happen)

A way to change the keys on the device (may be possible through Knox)

A leaked "engineering bootloader" --Signed by Samsung with proper keys --For the i337 --For the second revision bootloader

A vulnerability in SELinux (probly wont happen) which allows us to load a KExec module (i don't think this exists)

A vulnerabilty in the way the bootloaders load kernels or firmware

A vulnerability in the way the hardware loads the bootloaders

A security vulnerability in the Qualcomm bootloaders, which is what everyone who can read Assembly language is looking for.

A tool from Samsung.

Personally I'm hoping for 2, 3 or 8.. I don't like these cat and mouse games.. They're rediculous.
[AT&T Samsung Galaxy S 4 Android Development] JRman:
FYI: New S4 on 8/3 still has MDL

FYI: Just received my S4 (Amazon.com order) today (8/3) and was scared it might have MF3 already.

No worries, still MDL... :)
[AT&T Samsung Galaxy S 4 Android Development] nrhpd527:
I was scared to death the other night because a bad load of TWRP (through Goo Manager) bricked my S4 to the point of needing to use the emergency recovery feature of Kies. Thus, I naturally thought I would come out of that with MF3 firmware. Thankfully, Kies is still pulling down the MDL firmware and I was able to get rooted and get Infamous Alpha 4.5 loaded after I finally convinced Kies to work. It was a tense couple of hours though with a bricked phone.

Would have made for an uncomfortable anniversary...hey babe, I fubared my phone, dinner out is off since I have to go spend that money on a new phone....
[AT&T Samsung Galaxy S 4 Android Development] aturbs:
tl;dr
[AT&T Samsung Galaxy S 4 Android Development] thatsupnow:
What the hell did you quote the whole op for? This thread should just be locked there's nothing going on here (except for what Adam puts in) but a bunch of noobs having problems with what they consider bricks. At&t = SOL!
[Android Apps and Games] KaFrEEkAbOom:
Fruitacious Slot Machine

Fruitacious Slot Machine is is Totally Free!

Virtually Experience this fruit-themed slot machine with Fruitacious Slot Machine Free

THIS GAME IS ABSOLUTELY FREE. NO REAL WORLD MONEY IS INVOLVED.

THIS IS THE BEST FREE TO-PLAY FRUIT SLOT MACHINES APP!

Come see for yourself

Unlike slotomania or Slots Royale, Fruitacious Slot Machine for Android brings the very best user experience out of your Android smart phone. With the abundance of fruit images and colorful graphics, Fruitacious Slot Machine renders well on 99.9% of all devices for FREE.

1. Enjoy the fruit-themed user interface that is unlike any other app on the market today. Fruitacious Slot Machine FREE is the only app that delivers a realistic but clean interface while still giving you that casino-type feel

.

2. Fruitacious Achievements

Unlike the top apps like slotomania and Slots Royale, the people here at Fruitacious Slots have developed an extensive achievement system that will have you playing for hours. The difficulty ranges from casual to dedicated. We cater to those who play every so often to the almost addicts! (we won't tell anyone though :])

3. The Fruitacious Slot Machine Global Leaderboard. This global slot machine leaderboard shows your submitted virtual cash and your rank to other live players who play the exact same Fruitacious Slot Machine that you do. Not many slot machines on the Android market today provide such a level of competition.

4. High Definition Graphics

Highly detailed graphics have been added to this game so you utilize the full power of your phone rather than wasting it. We rather you play your Slotsfree with bonus and in Hd!

5. Enjoy the Background music and real casino sounds while you spin. We set the atmosphere right from the first spin. Sure to make you keep spinning!

Screenshots

Get it from here
[Droid RAZR M General] RikRong:
Lately, I've seen some confusion concerning Matt's utilities. I'm just posting this for clarification. If you have a locked bootloader, you CANNOT revert back to 4.1.1. Please do not try, you will soft brick. If you want to revert, you need to unlock your bootloader. 4.1.2 is rootable with Motochopper, which is included in utility 1.20. You can also unlock the bootloader on 4.1.2. No, 4.1.2 will not re-lock your bootloader, if you have already unlocked it.

Also important: please charge your battery, before attempting any flash in fastboot, before any modifications, or flashing ROMs in recovery. There have also been many soft bricks that were a result of a dead battery. Last, but not least, always ask questions if you're not sure. That's what we are all here for.

Version 1.10 is if you are on 4.1.1 and have not taken the OTA update:

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

Version 1.20 is for 4.1.2 updated users:

http://xdaforums.com/showthread.php?t=2249773
[Droid RAZR M General] brandon71:
Hopefully this will help to keep some people out of trouble lol and please everyone make sure the utility is for your phone not another
[Droid RAZR M General] Erisnoob:
Yes perfect! hopefully it will help...however, cant make people read or search....but great effort and good thinking!
[Droid RAZR M General] brandon71:
Yea that's the hard part lol
[Droid RAZR M General] netizenmt:
I didn't realize not having the boot loader unlocked would prevent you from reverting to 4.1.1. Thanks for the clarification.
[Sony Xperia ZL] riz157:
Hi all

I was wondering if anyone could recommend a reliable place to buy this phone for the UK?

I know its unavailable in the uk but can anyone recommend reliable online seller or purchase from Pakistan as I'm currently on holiday.

thanks for reading.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] lunercrab:
Ok so had the HTC one...nice phone but some things bothered me....I returned It am I'm planning on getting the 4...I'm a little concerned on how much I'm hearing the 4 is laggy...I loved my 3 so I hope it won't disappoint...anyways in case it does, does best buy charge a return fee like att does?...Im still really not sure what to go with in the end so I'd like to play around with the 4 a while...plus I know it's probably not worth it but depending on price best buys mobile insurance seems a bit nicer then the att one....
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Apoyyo:
No, Best Buy does not have a restocking fee. You can return/exchange within 15 days for a different phone if you don't like the S4
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] lunercrab:
Sweet maybe I'll go there...only thing is not due for upgrade til may 8th...can get early upgrade on may 1st from att...wonder if I can do the same from bb
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Apoyyo:
You can, all you need to do is have them call AT&T and they can do it over the phone.