yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 General] :
It's possible albeit a little difficult for a normal end user.

I am a normal end user, but I read his documentation and I'm going to try it, I'll post results soon...

EDIT: yeah not that easy, ill look into it but by the time I'd be time so would Cyanogenmod lol
[AT&T Samsung Galaxy S 4 General] some_douchebag:
If it works please let us know, and also archive and upload the files. Thank you in advance.

---------- Post added at 02:54 PM ---------- Previous post was at 02:49 PM ----------

Understood, any idea how long it would take you if you were to do it? I wanna get a good idea how long it would normally take for these things to be released to the end user.
[AT&T Samsung Galaxy S 4 General] :
Me?

A while.

Someone who's experienced about 15 minutes i'm already one step through.

EDIT: seems to be a lot more in depth than I thought. I give up before my mind explodes haha I extracted my aboot.img from my device but I'm not sure where to go from there; Ill leave it up to the experts.
[AT&T Samsung Galaxy S 4 General] some_douchebag:
Really? If that's the case it's a bit odd that cyanogenmod hasn't patched it yet.
[AT&T Samsung Galaxy S 4 General] mattdm:
People always seem to forget that these devs are adults with lives and jobs...he's probably at work. It's possible he doesn't even know the exploit is released yet.
[AT&T Samsung Galaxy S 4 General] :
Yes, exactly just give it till tonight...

What Im waiting for is Paranoid Android haha
[AT&T Samsung Galaxy S 4 General] d1md:
Size of twrp.img package

Is it normal for the twrp.img package for the GS4 (AT&T) to be 10MB? I wanted to confirm I received the right one before I brick my junk.

10483712 2013-05-23 15:05 openrecovery-twrp-2.5.0.1-jflteatt.img

Nevermind...the TWRP is supposed to be 10MB. Checksum verified. Also, Dan's example shows that CWM is 9MB. It's been a while since I tinkered with recovery images.
[AT&T Samsung Galaxy S 4 General] some_douchebag:
true enough, my apologies.
[AT&T Samsung Galaxy S 4 General] mocsab:
Need a little guidance -

I am not a dev - but - I can follow instructions when they are not too technical - I am confident I can do this - I have gone thru a number of other Bootloader unlocks that required a number of difficult steps -

I just need easy to follow instructions -

I would appreciate someone offering a simple guide - I tried to use the steps outlined in the Dev Section but need a little help getting started -

I realize you probably think I don't have any business even trying - but with the help and support of people who know a lot more than I do - I have learned quite a bit already - with a little help - I can get to where you guys are now - (at least the ones who have already run the loki tool -

Its been a while since I pushed files with ADB to my phone - and then I had SDK installed - is that what I need to use to do that?

Any help fellow XDA ers?

I know I could wait until something easier comes along - but I don't wanna wait - I am tired of waiting - and I hope a fellow XDAer will take pity on an old man who knows enough to be dangerous but isn't afraid to try -
[AT&T Samsung Galaxy S 4 General] brojoe11:
Very well said. I'm waiting on the same. Hat's off to you.:good:
[AT&T Samsung Galaxy S 4 General] ogxku5h:
+1 sir.
[AT&T Samsung Galaxy S 4 General] yeahmann:
Got TWRP installed. Backed up the stock ROM and copied to my comp just in case. Just waiting for a patched CM10.1 now. Which forums should we expect it in? I want to know which one to refresh every 5 seconds.
[AT&T Samsung Galaxy S 4 General] JuannTwo3:
In case tou were still wondering thats what size kine was as well and it worked! :D I did this on my break at work via a terminal emulator
[AT&T Samsung Galaxy S 4 General] d1md:
My walk through

Disclaimer - I have been out of the android game for a while so I am bit rusty - there may be errors. I wanted to make sure I can restore the original recovery image before actually flashing the new recovery.

I used a combination of Term Emulator (Root enabled) and my ubuntu machine.

Here are the commands I used on my ubuntu-12.04_64 system

- Download and unzip ./loki-master.zip to directory (I used ~/Downloads/)

- Download the platform specific recovery image from TWRP - select the proper device and carrier) and place into ~/Downloads/loki-master/

- Download the Android SDK Tools only from Google

- place in your apps directory - I have it as /opt - "gunzip" and "tar -xvf <filename>"

- Now you have the tools but require a the updated platform specific tools so cd to /opt/android-sdk-linux/tools and execute "./android update sdk --no-ui"

- Next modify your Bash runscript to include env settings:

"sudo vi ~/.bashrc"

####### paste this into the file at the end #####

export PATH=${PATH}:/opt/android-sdk-linux/tools

export PATH=${PATH}:/opt/android-sdk-linux/platform-tools

########

- I start another session and confirm the env PATH settings

- Perform a "which adb" to make sure you are using the proper command from /opt/android-sdk-linux/platform-tools

- Get the aboot.img as described in Dan's README.txt

via Term Emulator on GS4 - "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"

then "chmod 644 /data/local/tmp/aboot.img"

- Pull the file to ubuntu

----- screen output ------

me@D20:~/Downloads$ adb pull /data/local/tmp/aboot.img

3311 KB/s (2097152 bytes in 0.618s)

--------------------------

- Modify the image with the loki_patch tool

me@D20:~/Downloads/loki-master$ ./bin/loki_patch-linux-x86_64 recovery aboot.img openrecovery-twrp-2.5.0.1-jflteatt.img twrp.lok

[+] loki_patch v1.0

[+] Detected target AT&T build JDQ39.I337UCUAMDB or JDQ39.I337UCUAMDL

[+] Output file written to twrp.lok

- Push the file back to the GS4

me@D20:~/Downloads/loki-master$ adb push twrp.lok /data/local/tmp

4048 KB/s (10484224 bytes in 2.529s)

- So, from here it is simply executing from Term Emu on the phone "/data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok"

Again, I have not done the last step because I want to confirm the ability to restore the original recovery just in case. But, you can be brave or wait like me until a backout plan is available.

Evening Update - after some researching, I figured the best way to get the stock recovery back on there if need be is via the stock restore method (Kies or whatever it is called). In reality, I would only have to put the stock recovery and stock OS if this phone was being resold or returned under warranty. I went ahead and made the jump on the last step. Success - and a full backup.

Thank you Dan for the great work.
[AT&T Samsung Galaxy S 4 General] sloanster:
I with you Pink, I've got the CWM Pro but I believe I have shook it off for the last time...:eek:
[AT&T Samsung Galaxy S 4 General] EpicMango:
Since mods get mad with individual threads...I'ma post it here

What does this mean for running Stock Android from the Google Edition S4?
[AT&T Samsung Galaxy S 4 General] SysAdmNj:
Kind of two separate things, no?

You'll be able to flash custom roms with this but on the Google Edition you'll get android stock updates before anyone else and you can also flash custom roms if you like.
[AT&T Samsung Galaxy S 4 General] Jonnyredcorn:
After reading this thread I'm so put off of the gs4 its ridiculous. I don't really understand why it was locked in the first place. Would an unlocked boot loader have prevented the sale of 10million devices they've sold so far? If we(the XDA community) are so small of a user base that they don't care if they lose us as customers for locking the boot loader using the same ideology why lock it in the first place?

Not that it matters as the same people who said they would pass on the gs4 because of the locked bootloader and Samsung's new found lack of support for developers ended up getting one anyway. The gs4 with Dans exploit is more like a jailbroken iPhone than the developer friendly Android devices that allow us to spit in iPhone users faces.

The only way I'll get a gs4 is by upgrading to a gs4 for $199 then selling it on eBay and then buying the Google edition. From what I've read so far it seems that by the time I can get a gs4 it will be patched and impossible to unlock.

While I love Samsung's products I think I'll wait and see what Motorola has up its sleeve or the Nexus 5 so that I can continue to do whatever I want to my device. Those of you that currently have GS4's and can use the exploit, I'm jealous, I do wish I could have a gs4 now but like I said, when I'm able to get one I've read several posts stating that it will be likely patched and impossible to unlock, unless of course Adam comes through with his R&D thread.

Thankfully Task650 will continue to support the gs3, so all I'm really missing out on is the 1080p screen since I'd likely be flashing his AOKP on the gs4 anyway once its released.

\END RANT

Sent from my SGH-I747
[AT&T Samsung Galaxy S 4 General] mocsab:
close - so close

Ok - I went back to the Dev Thread describing how to get the loki exploit and CWM installed -

I very carefully followed the steps and got thru all but the last step I think = I got the following error message see image -

I double checked and I thought I had all the right files - named correctly - in the right place - ?

Any thoughts? I feel like I am really close to getting this done - .???

I think I figured it out - tried again and this time it says it works - trying to confirm I have CWM installed now.

JUST CONFIRMED _ CWM INSTALLED - woot woot!
[AT&T Samsung Galaxy S 4 General] geoldr:
Locked bootloader is to help prevent android viruses, exploits and things of that nature for the regular consumer.

And you mean Task650
[AT&T Samsung Galaxy S 4 General] sabre31:
The truth is I see more and more android oem doing this like Samsung is. I think the future will be all locked bootloader across the board and kernels that won't even allow root. Nexus will be where it's at. They are all copying apple and locking down. Now that Samsung is big time they act more and more like apple and won't care.
[AT&T Samsung Galaxy S 4 General] Jonnyredcorn:
Lol yes 650 I was watching the Xbox One unveil video and had 360 on the mind. If that was the case then why patch the exploit and not allow the people that want to unlock it unlock it. What I'm getting at is the openness we all love about Android is being raped by two of the biggest US carriers. The fact that Samsung allowed them to do this is ridiculous too. Samsung could have easily stated that AT&T & VZW cannot lock the BL on the gs4 if the wish to sell them. Its not like that would deter them from selling the most anticipated device of 2013. The only thing I can think of is that Samsung signed something long ago before they had the power in the mobile industry today that gave the carriers this power.

Regardless I didn't see unlocked bootloaders destroying drones of captivates, i777's, skyrockets, or gs3's. Why now?

Sent from my Nexus 7
[AT&T Samsung Galaxy S 4 General] mocsab:
As I stated in my earlier post - I am not a developer -no where close - but I read a lot and by trial and error figure stuff out - I was having trouble installing the Exploit originally - mostly because I was not able to get an ADB connection to my phone - I tried using SDK manager, but it didn't work -

I had seen someone else mention using the Motochopper file because it already had the necessary ADB files - so I got a Command Prompt (right click and shift) in that file - after having moved all of the Loki and modified recovery files there - and then when I tried to push the files via ADB - it worked. (I had a hiccup at first - but that was my fault for not typing the commands exactly like the Dev had instructed - and to be honest, I was sort of flying by the seat of my pants typing the commands he wrote and hitting enter when I thought I should - in any event, I eventually did it right and it worked.

I have since installed TWRP - and am now looking into a loki ready rom and kernel - and can't wait to get back to 'flashing" ....

Funny - how DjrBliss named the exploit after the Norse God of Mischief - wonder if that is intentional or just by chance? :laugh:

THANK YOU to all who helped me - I really love XDA and the brotherhood/Sisterhood that exists here - (not meaning to sound sexist or anything) mostly, thank you to Djrbliss for his incredible work - I have already sent the $50 I promised for unlocking the bootloader - I am sure everyone else who committed to the Bounty - will live up to their promises. (whether they give it to Charity as he requested or make a donation to him so he can)
[AT&T Samsung Galaxy S 4 General] fortesquieu:
I don't think it was Samsung's idea to put a locked bootloader on the phone. It was probably ATT and Verizon's idea.

As you know, they are the only 2 variants to have the bootloaders locked.

If Samsung was the culprit, then ALL of the variants would be bootloader locked.
[AT&T Samsung Galaxy S 4 General] mocsab:
You give Samsung too much credit - they want to sell as many phones as they can - so if ATT and Verizon insist on having a locked bootloader, Samsung is more than willing to oblige. They want to beat APPLE _ damn the torpedoes and full speed ahead.

To be honest, while we feel very strongly about this stuff, I would venture that "flashers" - Devs and MODDERS make up a very small percentage of the universe of Cell Phone Buyers/Owners (I work in a tech related company and there are three people in the entire group of over 100 that I know of that flash and root their phones) - so while we may feel it is the most important thing for US - most people just don't care - and don't really understand it anyway. To Samsung's point of view It's just Business (as was often said in the Godfather) It isn't personal - it's just business.
[AT&T Samsung Galaxy S 4 General] yeahmann:
No patched CM10.1 yet? What's taking so long?
[AT&T Samsung Galaxy S 4 General] burhanistan:
They were waiting for your final revisions.
[AT&T Samsung Galaxy S 4 General] mocsab:
LOL- :good:
[AT&T Samsung Galaxy S 4 General] mocsab:
Tmobile roms?

I have installed TWRP - thanks to the efforts of djrbliss and his Bootloader exploit - and I understand that roms have to have Loki installed in order to flash them on our phones - -

My question is - Is it the ROM that needs to have LOKI or the Kernel? or both? KTWEAKER has been "Loki-ized:" so would it be enough to flash a TM rom that did not have Loki installed - but immediately follow that by flashing the KTWEAKER Kernel?

Or - is it necessary for Loki to be in the ROM when you flash it?

I am curious because they have had such a head start on creating ROMS and they obviously don't need LOKI to make them work - wondering if we can do something along these lines to be able to enjoy ROMS meant for other phones?
[AT&T Samsung Galaxy S 4 General] :
I think its just the kernel. Not 100 percent sure though
[AT&T Samsung Galaxy S 4 General] 21cdb:
I installed a T Mobile ROM and immediately followed that with the KToonsez kernel. It booted up fine and I even had connectivity right off the bat, but I added the ATT APN to make sure everything will work flawlessly. No issues so far.

I'm not sure if the kernel flashing was necessary, but I assumed it was since KToonsez did some loki magic to it.
[AT&T Samsung Galaxy S 4 General] Jonnyredcorn:
I basically agreed with both of you in my posts if read carefully enough. I did blame AT&T and VZW. However i did also kinda state that Samsung didn't have the balls to say no we won't lock them. VZW & ATT wouldn't have passed up the gs4 over locked bootloaders. I read somewhere where they used the baby elephant on a chain analogy. Where the baby elephant cant break the chain but once it's grown up it's still chained and completely capable of breaking it but won't because it doesn't know it can. Samsung is now that large elephant and can basically make the calls.

I know we make up a small portion and our small portion is probably a pain in Samsung's ass. I guess what I'm more upset about is the direction my favorite tech company is going. Also don't let me forget that even though I don't have the device I am grateful to Dan and everyone else for putting this exploit together. My worry is by the time I can get one I won't be able to unlock it and thus won't get one unless I do it the pain in the ass way by upgrading, selling, and getting the Google edition.

Again, end rant lol

Sent from my Nexus 7
[AT&T Samsung Galaxy S 4 General] :
What rom from tmobile did you flash?
[AT&T Samsung Galaxy S 4 General] 21cdb:
Wicked.
[AT&T Samsung Galaxy S 4 General] yeahmann:
I would patch CM10.1 myself but I want to give the younger devs a chance to prove themselves. Yeah, that's it. You're welcome.
[AT&T Samsung Galaxy S 4 General] Cusa:
Hahaha
[AT&T Samsung Galaxy S 4 General] shabbypenguin:
actually.... http://awesomescreenshot.com/02d1b9wmda

:P
[AT&T Samsung Galaxy S 4 General] mocsab:
Please forgive me - I should have read more thoroughly - THANK YOU! I also used your thread and instructions to get the LOKI flash on my phone -

One question I asked in another thread and am just looking for confirmation - Can I flash a TW ROM from TMOBILE that does not have the LOKI thing installed - and follow that by flashing the KTWEAKER Kernel which does have LOKI?

Someone said they had done this - I just wanted to confirm before I tried it.

?
[AT&T Samsung Galaxy S 4 General] shabbypenguin:
so long as when you go to boot you have a loki'd kernel youll be fine :)

and no need for apologies, you asked where he got the idea from. :) i didnt do anything more than suggest a name to him :)
[AT&T Samsung Galaxy S 4 General] :
5$ paypal to the first person that gets me LTE on the tmobile rom wicked. Aka I most likely need a flashable modem for att.
[AT&T Samsung Galaxy S 4 General] fortesquieu:
Samsung can be THAT big elephant. BUT, ATT and Verizon combines for about 65% of market share, you don't want them to be unhappy. What if they get pissed off at Samsung and starts to promote iPhone more? Just saying.
[AT&T Samsung Galaxy S 4 General] Jonnyredcorn:
The iPhone promotes itself, as does the galaxy line now. It was apples decision to lock their device down, Samsung has a choice I believe as the gs3 and gs2 sold excellent without locked boot loaders. Its just I'm worried that since I can't get a gs4 now I may not be able to get one when I'm able because I won't be able to flash custom firmware. I know I'm only one customer but Sony must believe that gave this community has an impact as they have become very developer friendly as of late.

Sent from my Nexus 7
[AT&T Samsung Galaxy S 4 General] shabbypenguin:
take /system/etc/apn-configs.xml from stock and put it in the rom in teh same place.
[AT&T Samsung Galaxy S 4 General] :
If that works you get 5$ paypal. I wasn't joking. haha
[AT&T Samsung Galaxy S 4 General] shabbypenguin:
if it doesnt then a lib swap would be needed and edits to build.prop more than likely
[AT&T Samsung Galaxy S 4 General] :
Okay so doing it now, hope it works

---------- Post added at 01:18 AM ---------- Previous post was at 01:12 AM ----------

Nope , I have 4g but no LTE which I do have since I have another phone right near me

any ideas?
[AT&T Samsung Galaxy S 4 General] evodon84:
Try the PTA APN under mobile networks

sent from tapatalk
[AT&T Samsung Galaxy S 4 General] mocsab:
Cool name and it seems to fit perfectly!

---------- Post added at 07:04 AM ---------- Previous post was at 06:57 AM ----------

You don;'t need a modum - just flash the rom and after you flash the rom and a kernel that has loki in it , do a google search for "ATT APN Settings" - then go to your APN settings in your phone and create the APN Settings.

You will be good to go. You do APN settings at system//connections/more networks/mobile networks/access point names

Then just create the new APN -

Good luck -hope this helps.
[Sony Xperia Miro, Tipo (Dual), J, E] Takyang:
Hi, i installed Purple walkman in cwm, after i wipe dalvik cache because it was the description, now every reboot, my phone show

"android apps update x/47" This is problem?

How can i solve this problem to not show this?
[Sony Xperia Miro, Tipo (Dual), J, E] xrhstospro:
no problem...its an update for your apps by this .zip
[Sony Xperia Miro, Tipo (Dual), J, E] Takyang:
But every reboot?
[Sony Xperia Miro, Tipo (Dual), J, E] c4cyro:
It would stop once its done starting the apps

Sent from my ST23i
[Sony Xperia Miro, Tipo (Dual), J, E] Takyang:
You don't understand me.

I get android updating message every restart. It's ok? Or this is a problem?
[Sony Xperia Miro, Tipo (Dual), J, E] xrhstospro:
flash it again and see if it stop after first reboot
[Sony Xperia Miro, Tipo (Dual), J, E] Takyang:
Ok, i flash it again

Need to wipe dalvik cache again?
[Sony Xperia Miro, Tipo (Dual), J, E] xrhstospro:
i never wiped dalvik...so dont wipe nothing...just reboot
[General Accessories] suffer1989:
Ravpower RP-WD01 WiFi-Disk Connectivity Review

There are many reviews about this device:

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

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

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

All of them really praise it for its core functionality. However, the threads didnt answer some of my questions. Here I will reiterate the main points of the other reviews, as well as provide answers to more advanced senarios.

First of all, I wanted to see if the Ravpower's wifi passthrough mode added much latency to internet usage. I connected it to my home wifi network, and ran some tests, some directly on the home wifi network, and some on the ravpower's hotspot network.

Home wifi :

http://www.pingtest.net/result/81588240.png

http://www.speedtest.net/result/2726637216.png

Ravpower Wifi network :

http://www.pingtest.net/result/81588291.png

http://www.speedtest.net/result/2726188377.png

As you can see, as far as latency is concerned, there is not much difference between browsing on your home network and accessing the internet through the ravpower hotspot. I can't test really high speed internet access, since our lines arent too good, and this is the highest speed I can get with relative stability.

You can access the connected media directly through the wifi hotspot, either using a mobile app, or even using a standard linux distro with Samba support. After applying the admin username and whatever password you set, I was able to get full read/write access to my media, and I was able to play 1080p30 video off of it perfectly.

Pleasingly, you can also access it through your home's wifi network. It will assign itself an IP address (which you can find out through its control panel), and then you can access the shared resources present on the drive, straight from your desktop if need be.

This makes it perfect for a carputer type of setup, where you can have the Ravpower attach onto the WIFI hotspot provided by your mobile/internet modem, and then you can share the media with your phone or tablet. Using a CIFS app, should be able to map the drive into android and allow your favourite apps to manage your music/movie collection almost like it was natively in the system, although I haven’t figured that bit out yet. I’ll get back to you guys when I make progress in that regard.

Overall I'm VERY pleased with this, and once I figure out CIFS and how to mount it to my internal directories, I’ll be ecstatic.
[General Accessories] thebeest:
Hi there. I bought a Ravpower after being disappointed with the iUSBport not being compatible with my Transcend portable HDD and I have not been let down this time!

To get it working with ES or AndSMB you need to set the login details correctly as guest access did not work for me. I could login and see IPC$ but couldn't access the storage device(s) and got the "Invalid operation" error when I tried to access IPC$. I changed the settings in ES/AndSMB to the following:

Server: 10.10.10.254

Username: admin

Password: whateveryouhaveset

Change the Server and Password to suit. I had to restart the device a few times for changes to apply as the first time I tried ES it did not work. "MobileFun" just doesn't quite cut it so having proper samba support with this device is a real plus! Hope that helps!