yashsingh1/xdaforums huggingface dataset:
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] manhanhangda:
next step in Linux

Thank you,

I'm try install Linux and fastboot complete. but in next step, We still use KFFirst Aide or KF SRT in Linux or go again to windows ? please show me next step,

thank you very much

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

After I go to the Fastboot on my kindle,

I try to KF SRT and KF FirstAide to do everything. but my computer just show Waiting for device ( use Windows, i dont know about Linux)

So, can you show me clearly what i should do.

Thank you very much
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] mcswank:
I did something similar and bricked my kindle. Here's what worked for me.

1) In windows I downloaded the KFHD System.img Recovery Tool (KFHD_SRTv2.1- 8.1.4) found here.

2) I extracted the zip file to a separate directory named KFHD_SRT_v2.1.

3) I turned off my kindle.

4) I opened a cmd prompt and navigated to the KFHD_SRT_v2.1 directory created in step 2.

5) I ran the SR Tool.bat file.

6) I selected option 1 for Enable Fastboot.

7) I answered n to the question "Is your device turned on?"

The tool then displayed the following:

Please connect your device to the computer

< waiting for device >​

8) I plugged a normal micro USB cable into the kindle and then into the windows PC. The kindle turned itself on and after a few seconds the kindle was in fastboot mode.

9) I downloaded these three files from links found here and copied them to the KFHD_SRT_v2.1 directory created in step 2.:

kfhd8-twrp-2.7.0.0-recovery.img

kfhd8-freedom-boot-8.4.6.img

kfhd8-u-boot-prod-8.1.4.bin​

10) I returned to the cmd prompt and did the following:

fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin

fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img

fastboot -i 0x1949 flash recovery kfhd8-twrp-2.7.0.0-recovery.img

fastboot -i 0x1949 reboot​

11) The kindle rebooted into the twrp recovery and I was able to install the CyanogenMod 11.0 ROM found here.

I hope this helps you too! :)
[JASJAR, XDA Exec, MDA Pro General] BORNII:
hi like the title says can anyone please tell me the gprs and mms settings for 02 payandgo searched everywhere but with no joy.02 say it is only a contract phone therefore cannot be used on payandgo.
[JASJAR, XDA Exec, MDA Pro General] hanmin:
You've searched everywhere???? Really???

http://xdaforums.com/viewtopic.php?t=41356&highlight=
[JASJAR, XDA Exec, MDA Pro General] BORNII:
Hi i did try these settings along with 2 others but i keep getting "cannot connect for an unknown reason check your connection settings" it acts like it is about to connect but then this message appears. i can get the mms to work but not the gprs and on wifi it is really good.
[T-Mobile, Samsung Galaxy SIII] Cronoss:
It was probably rooted and then the root was lost somehow.

Just flash it with the non knox 4.3 rom from mrrobinson.
[T-Mobile, Samsung Galaxy SIII] Cobra281:
you can revert back to the latest stock firmware with only root injected\implemented into it. you'll have all the stock features(and bloat, which you can remove, since you'll have root access, using an app like titaniumbackup.

download the firmware in this thread:

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

you want the latest official pre-rooted firmware(listed below), where it says T999. make sure it's for T999, and NOT T999

L

!

T999_UVUEMJC

Official JB Firmware - Latest JB 4.3 Firmware

and you'll need Odin for PC, to flash the firmware:

http://www.androidfilehost.com/?fid=9390275921635705049

follow these instructions on how to flash, starting from "Second"

http://xdaforums.com/showthread.php?t=1771687
[T-Mobile, Samsung Galaxy SIII] flipster64:
Thanks guys.

Got Odin. Watched a good root video. Now to download the ROM I want. 4.3 sounds intriguing, as long as it still has WiFi calling.

I'll go read that thread. I can be taught, but sometimes I need help finding where to start. :)
[T-Mobile, Samsung Galaxy SIII] Cobra281:
4.3 absolutely has WiFi calling. that's a T-Mobile feature that will always remain on the OTA(over the air) updates, unless they decide to do away with that technology. there were many changes made from 4.1.x to 4.3. by the way, to disable the wi-fi from always scanning in 4.3, you have to turn off\uncheck the option in Settings > Wi-Fi > press "Menu" > Advanced > "Always allow scanning", when you do the update.

4.3 features, as per wiki;

Bluetooth low energy support.[112]

Bluetooth Audio/Video Remote Control Profile (AVRCP) 1.3 support

OpenGL ES 3.0 support, allowing for improved game graphics[112]

Restricted access mode for new user profiles[112]

Filesystem write performance improvement by running fstrim command while device is idle[113]

Dial pad auto-complete in the Phone application[112]

Improvements to Photo Sphere[114]

Reworked camera UI, previously introduced on Google Play edition phones[115]

Addition of "App Ops", a fine-grained application permissions control system (hidden by default)[116]

4K resolution support[117]

Many security enhancements, performance enhancements, and bug fixes[118]

System-level support for geofencing and Wi-Fi scanning APIs

Background Wi-Fi location still runs even when Wi-Fi is turned off

Developer logging and analyzing enhancements

Added support for five more languages

Improved digital rights management (DRM) APIs

Right-to-left (RTL) languages now supported[112]

Clock in the status bar disappears if clock is selected as lockscreen widget

http://en.wikipedia.org/wiki/Jelly_Bean_(operating_system)#Jelly-Bean
[T-Mobile, Samsung Galaxy SIII] flipster64:
Ok, there's one thing holding me back now. I've read a few things about different modem (baseband) flashes, and that I might have to flash a different modem onto my Galaxy S3 SGH-T999 for this to work. I note that my current baseband is T999UVDMD5 which matches the stock image name for 4.1.2 (which is also my current OS version) but the name of the stock image for 4.3 is T999UVUEMJC ... which would suggest to me that this is different modem firmware. Or do I not need to worry because the modem is included in the 4.3 firmware tar file? I have a hunch the latter is the case because it isn't mentioned on that HOWTO page but I really want all my ducks in a row to minimize my chances of bricking or losing data.

T-Mobile Image

November 2013 - 4.3 JellyBean - New!

Note: This is based off of the stock image TMO T999UVUEMJC

Do not flash a prior release after flashing this, it has been reported to cause bricks, read the thread for more information.

Perm Mirror: Download - root66_TMO_T999UVUEMJC_2.7z

April 2013 - 4.1.2 JellyBean

Note: This is based off of the stock image TMO T999UVDMD5

Perm Mirror: Download - root66_TMO_T999UVDMD5.7z

Incidentally, I've been looking for a good primer page like this ... this is excellent.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Ok... modem is basically firmware, from what I'm reading.

I've tried to download the root66_TMO_T999UVUEMJC.tar to the phone using Odin, but I'm getting a secure check fail sbl2 error when I do. Not finding any information on why that might be.

It is a bit strange to me that when I boot into the recovery mode it's telling me it's an i747, though the sticker and the "about" in the os say SGH-T999... but they may be the same thing for all intents and purposes.

I CAN transfer the file to the SD card using Kies, and I have, but it doesn't show up as an option to load from external storage, and I'm guessing the Odin connection and settings do something special to cause the flash to be available and work in the first place.

So ... have we seen a secure check fail sbl2 before, and do we know what it means? I'm going to keep looking but I've had no luck so far.

Well no good luck anyway.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Here's what Odin is telling me on the PC side

<ID:0/009> Added!!

<ID:0/009> Odin v.3 engine (ID:9)..

<ID:0/009> File analysis..

<ID:0/009> SetupConnection..

<ID:0/009> Initialzation..

<ID:0/009> Get PIT for mapping..

<ID:0/009> Firmware update start..

<ID:0/009> sbl2.mbn

<ID:0/009> NAND Write Start!!

<ID:0/009>

<ID:0/009> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[T-Mobile, Samsung Galaxy SIII] flipster64:
Yeah ... this is where I'm stuck. Odin won't flash that de-knoxed 4.3 tar from DocHoliday. It did let me flash Clockwork Mod and I can get into that and back things up, and I was able to add the SuperSU zip (but I don't see the SU program after it boots so I don't think I actually have root.) It's weird.

I read on one forum I might have to flash an alternate recovery onto it to get it to work. I have it downloaded but I'm a little leery of that until I understand the possible implications. I noticed last time I looked at the recovery console it says the counter's up to 3 (after CM... it was at 2 when I bought the thing) and then there's something about Qualcomm Secureboot being set to Enable, but I can't tell if that's good or bad from reading posts on it. My phone didn't come with a warranty so I'm not terribly concerned with tripping the counter (though it would be cool to reset it at some point, it's not a priority at all).

Anyway, I'm still trying to learn more about what all this means before I proceed.

I have visions of bootloaders and img files and tar files and zip files flying around my head. Meantime I'm still on 4.1.2, apparently a de-bloated T-Mobile build with no wifi calling.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
It sounds like Odin might be falling due to your phone having an att build.prop. If you are sure it is an sgh-t999, want to keep root, and have the know how, you can make this process a lot easier by updating your firmware to the last one before the 4.3 update (otherwise you will be stuck with Knox). Afterward update your recovery and flash a more current touchwiz ROM.

Make sure to read the entire OP of these threads and flash in recovery.

To update your firmware without having to use Odin, read the following thread:

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

There is a few options when it comes to choosing a custom recovery. I'm currently using Philz. If you get Philz, make sure to get the d2lte version. The thread for Philz recovery is below:

http://xdaforums.com/showthread.php?t=2201860
[T-Mobile, Samsung Galaxy SIII] flipster64:
When put the phone in download mode it says product name is SGH-i747 ... but I've never seen another SGH-T999, so for all I know they all say this. Is this why you're thinking it has an ATT build.prop? It does have the T-Mobile logo when starting up and shutting down. I can go read more on that. I wonder if there's an Android OS for dummies book.... I've been working with DOS, Windows, & Linux for decades, it can't be THAT hard to understand.

I need to get comfortable doing CM backup and restore. Yeah, you're right, I don't want Knox -- but there is a de-knoxed 4.3 build out there on the forum which is what I intend to flash when I finally get to a point where Odin will let me flash it. Or I see you've linked some threads that talk about other ways.

I'll go read those threads you linked and see what I can absorb from them. Thanks!
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Most T-Mobile and AT&T s3 ROMs are cross compatible. It sounds like it is a sgh-t999. If it has an AT&T ROM on it, that would make ODIN throw out errors (to prevent bricking your phone) until you have your build.prop identity the device as an sgh-t999.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Oh, man. The road blocks. They are legion. And sometimes circular :eek:

I've tried updating the bootloader (from CM v6.0.3.1) as described here:

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

But CWM aborts the installation:

Finding update package

Opening update package

Installing update

assert failed: getprop(ro.product.device) == "dttmo" || getprop("ro.build.product") == "d2tmo"

error in external/sd/T999_UVDMD5_firmware_v4.zip

(Status 7)

Installation aborted.

Which I figured has something to do with what it's finding in build.prop as mentioned above. Except I just looked in my build prop, and it says it's an SGH-T999 made by samsung.

ro.build.product.model=SGH-T999

ro.product.brand=samsung

But then it says that ro.product.model is obsolete, and to use ro.product.device ... which looks like it's set to ... canada? ro.product.device=d2can

Which certainly doesn't match dttmo or d2tmo.

So ... edit the build.prop file, then?

I downloaded an editor to do it. It does whine about not being able to open /storage/sdcard0/buildprop.tmp, not sure if that's going to be an issue. I "re-rooted" with CWM_SuperUserv3.0.7 so I can now use root explorer again (which is how I looked at the build.prop file) ...

At that point I guess I'd flash the radio/bootloader above, reboot to Odin mode, and try the Knox-Free 4.3 flash again?

Any red flags going up?
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
I'd highly recommend updating your recovery before doing much. Once you do that, try flashing the bootloader and the 4.3 ROM.The only red flag would be if you plan to use Odin since it is identifying as a different phone due to the build.prop.

Also, it sounds like the previous owner messed up when they modified the build.prop. You really shouldn't need to worry about editing it if you plan to switch ROMs since any new ROM is going to replace it anyways.
[T-Mobile, Samsung Galaxy SIII] flipster64:
By recovery I think I understand you're saying the latest version of CM ... which I see for my phone is 6.0.4.5 (SGS3 T-Mobile).

I am also reading I can flash a ROM with CM, though all of the ROMs I've seen so far (including the one I want to use) are .tar files and I think CM uses zips.

I don't suppose you can just un-tar the ROM and zip it ... can't be that easy ... can it?
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Right, you will need to either update CWM or change to a different recovery such as TWRP or Philz (Philz is based on CWM but has a lot more features.

You're right. Most ROMs are installed/flashed in a custom recovery in ZIP format rather than Odin. Making an Odin package compatible with recovery isn't nearly as simple as unpacking a .tar file and zipping it.

You can find a lot of ROM options that are possible to flash in the development section of this board.
[T-Mobile, Samsung Galaxy SIII] flipster64:
I've updated to Philz CM 6.07.9.

My modem is already T999UVDMD5 ... if I flash the update in this thread (http://xdaforums.com/showthread.php?t=2282603) I'm guessing it will overwrite CM and put the stock recovery back. So I decided to skip that part and try the update again.

I'm getting this here...

<ID:0/006> Added!!

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> sbl2.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

I have root ... I can go in and look at build.prop and edit it, but it won't let me save it.

I guess I need to find a different way to flash.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Well, I THOUGHT my bootloader must be locked.

But I'm unsure now ... I mean ... I'm rooted. I can flash stuff with Philz Custom CWTouch ...

It's that FAIL! (Auth) that's getting me.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Odin will continue to fail until your build.prop is fixed. Really, all you need to do is pick a custom ROM from these forums and flash using Philz. Afterward, you should be back in order. Just make sure you follow the instructions in the ROM's thread and also make sure the ROM is for the t999
[T-Mobile, Samsung Galaxy SIII] flipster64:
So there are custom roms that are zips instead of .tars on this forum, then?

Or Can Philz flash a .tar?

I'll look for a custom rom zip out there for my phone.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Yes, most of the ROMs that are found in: http://xdaforums.com/galaxy-s3-t-mobile/development are in a .zip container rather than a .tar and flashable in a custom recovery, such as Philz.

One other suggestion, after you get root properly working, make sure to backup your IMEI by opening a terminal app (found on Google play) and type the following command:

su reboot nvbackup

Your phone will reboot and backup all necessary data.

You might also benefit from reading the following threads:

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

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

The first thread is a bit outdated but still has good information in it.
[T-Mobile, Samsung Galaxy SIII] flipster64:
I flashed a 4.3 ROM from here according to these directions:

http://xdaforums.com/showpost.php?p=46872485&postcount=2&nocache=1&z=69548066239804

booted up ... but for some reason it won't recognize my sim? Same one it's been using the last two weeks?

Anybody run into this?
[T-Mobile, Samsung Galaxy SIII] flipster64:
Hmmmm ... in addition, when I tried to use Odin to flash DocHoliday's official one (after flashing the UVUEMJC modem), I still get:

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> root66_TMO_T999UVUEMJC.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> sbl2.mbn

<ID:0/007> NAND Write Start!!

<ID:0/007> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

The phone says (on the download screen) SECURE CHECK FAIL : sbl2

You know, right before that, it says QUALCOM SECUREBOOT ENABLE .... don't know if that is a feature that is locking something.

the build.prop file does have the d2tmo properties now instead of d2can .... and the region is US and language en, as opposed to CN and vl in the old one. So ... it looks like it SHOULD be MORE friendly to my carrier... not less.

Sim works fine in my HTC G2 (with micro adapter). Just stopped working in the S3 after the update.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Hmmm... missed this. I do have the IMEI ... and I did do a CM backup a few days ago....

I suppose this is why I was supposed to do that.

Sigh.

Let's see if I can restore it.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Did you flash the modem the ROM's post says is a prerequisite?

Prerequisites:

Samsung Galaxy S III SGH-T999

Root and Custom Recovery Installed

T999UVUEMJ4 Modem http://www.androidfilehost.com/?fid=23196940996969671

ROM File

Knowledge of what you're doing

Patience
[T-Mobile, Samsung Galaxy SIII] flipster64:
Yes. Flashed the J4 modem since it was linked, then the ROM, and booted.

It behaved like an upgrade. Matter of fact, it said it was upgrading android as it booted. And it kept all of my apps and my wallpaper, which I did not expect. I have WiFi, just no network (it says to insert a sim, which was already inserted.) So for the time being it's back in my HTC so I have a cell phone while I figure more stuff out.

After that, since the rom was based off a release with JC at the end of the modem name, I then flashed that modem, which made no difference, but that was in the instructions to flash DocHoliday's tar via Odin ... which still wouldn't flash.

I need to find out if IMEI is the issue ... they moved Phone Status in 4.3 ... having trouble finding it to see if it even has the same IMEI. Not sure how that works. If that is the problem, there is a tool out there to generate a new one using your IMEI number. But like I said I'm not sure that's the issue.

Is the IMEI embedded in the modem, or a file the modem uses?

The other question is ... can this be completely wiped from CM and flashed to a 4.1.2 image now? I'd read somewhere you can't go back, but it might've had something to do with Knox, which is supposedly removed from this ROM.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Found the status information. And I think the problem is the linking to the radio .... Baseband Version UNKNOWN

Also says IMEI Unknown, and IMESV UNKNOWN.

So it COULD be IMEI.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
I'd try doing a clean install before messing with your IMEI. If it comes down to it I'll pm you a link to what you need to fix your IMEI.

---------- Post added at 07:36 AM ---------- Previous post was at 07:35 AM ----------

Side note, make sure to follow the IMEI backup instructions I posted once that is sorted out
[T-Mobile, Samsung Galaxy SIII] flipster64:
Ok, I've generated an IMEI file using the SG3 IMEI generator here

http://xdaforums.com/showthread.php...rect)|utmcmd=(none)&__utmv=-&__utmk=257010824

However, when I dial *#7284#, I don't get an option to choose anything but PDA and MODEM ... and I can apparently only pick PDA (radio buttons).

Has to be a way to slip this file where it needs to go....
[T-Mobile, Samsung Galaxy SIII] flipster64:
Oh yeah, I'll definitely be backing up the IMEI once it's all working again.

One thing I'm NOT sure of I'd be willing to try is to go back to the CM backup if going back from 4.3 to 4.1.2 won't brick the phone, get it working again the way I had it working yesterday, back up my IMEI, and maybe try a 4.1.2 tmo stockmod after that just to get WiFi calling. 4.3 looks really nice, though :) Maybe an upgrade after THAT would be more ... smooth.

One day, I'd like to find someone to "sit down" with and go over "pictures" of basic architecture here and generally where these pieces fit.
[T-Mobile, Samsung Galaxy SIII] flipster64:
By "clean install" do you mean go back and flash the modem, then flash the ROM again? Or try a stock ROM with CM? Odin doesn't want to flash any ROMs ... I get that sbl2 permissions error.

Is the IMEI stored in the files that get flashed by CM, or does the ROM pick it up from somewhere else that isn't affected by the flash?

If the IMEI is stored in the ROM itself, then my guess is it's "gone" unless I can safely restore my CM 4.1.2 backup. If that's something that can be done without bricking, that seems to me to be the safest way to get it back and back it up. Otherwise, I've generated a new IMEI file using my IMEI number from the phone itself and that tool I mentioned.
[T-Mobile, Samsung Galaxy SIII] flipster64:
It's warnings like the second one on this page that concern me:

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

DO NOT flash this if you are running latest 4.3 (*MJC) firmware. It WILL brick your device. Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release.

That's why I'm hesitant to restore my 4.1.2 CM backup. Knox is supposedly removed from the *MJC firmware I flashed so it may not be an issue.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Clean flash meaning, making sure the ROM is still on your sd card, going into recovery, wiping the system, data, cache and dalvik partitions. Afterwards, flash the ROM. Keep in mind that this deletes everything so, make sure to backup anything important on your phone.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Ok, clean install done. Blew everything away with CM beforehand. Asked me for my google account and wifi password.

But still no baseband or IMEI.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Would it be safe to restore my old CM backup of the 4.1.2 mod that came on the phone?

And if so, would the IMEI file(s) still be in the backup? Or do you think there's a way to inject my generated IMEI into the current clean install of 4.3?
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
Yeah it sounds like it is an IMEI issue then. You should be and to restore your old backup. It won't have the IMEI in it but it will tell us if it's a problem with the ROM you choose or if your IMEI was corrupted.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Well, here goes nothin'.....

Not sure ... does a CM backup backup the modem and everything, or am I probably going to have to flash a TMD5 modem, too?

It's currently restoring.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
It won't backup the modem. However; the modem should work regardless of the ROM you flash.