yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] EM|NEM:
ok first of all to unlock again you need your unlock token from htcdev. the command is "fastboot flash unlocktoken Unlock_code.bin" without the " "

but you don't need to do that if you just want to get back to stock. leave the bootloader locked and run an RUU from here

one of the sprint ICS ruu should work. I have a gsm device so i'm not really sure which RUU
[HTC EVO 3D] ryanrmc:
Oh thank you so much! Any of the ones with ICS will work?
[HTC EVO 3D] hossman:
What hboot is on your phone?
[HTC EVO 3D] ryanrmc:
1.58.0000
[HTC EVO 3D] hossman:
I'm pretty sure there is no ruu for that update. Since you're s on, it will not work.

Your only option is to get your bootloader unlocked, and reinstall your recovery
[HTC EVO 3D] ryanrmc:
How
[HTC EVO 3D] ryanrmc:
Ok I got it unlocked
[HTC EVO 3D] hossman:
Sweet!

Now flash 4ext through fastboot

---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------

Then you can flash a stock Rom and be golden!
[HTC EVO 3D] ryanrmc:
4ext? What about CWM?
[HTC EVO 3D] hossman:
4ext is far superior for the evo 3d.

Especially if you are s on

Make sure smatflash is on, and flash only stock based roms.

There is also twrp, but ask around and you'll find that 4ext is preferred.
[HTC EVO 3D] ryanrmc:
Alright. I will do so later today.
[HTC EVO 3D] hossman:
I sent you a pm, hopefully that helps you
[HTC EVO 3D] ryanrmc:
Ok! I now have 4ext recovery mode. Can I get a custom rom?
[HTC EVO 3D] hossman:
Make sure smartflash is enabled

It's in one of the menus

Try butterz sense for rom
[HTC EVO 3D] ryanrmc:
And I can do this with s-on?
[HTC EVO 3D] hossman:
Yes,

Just make sure smartflash is.on
[HTC EVO 3D] ryanrmc:
Alright. Thanks!!

Oh what about venom?
[HTC EVO 3D] ryanrmc:
(bad)

isntallation aborted
[HTC EVO 3D] hossman:
Check md5

---------- Post added at 09:50 PM ---------- Previous post was at 09:50 PM ----------

Make sure you perform a full wipe
[HTC EVO 3D] ryanrmc:
What is md5?
[HTC EVO 3D] hossman:
http://lmgtfy.com/?q=what+is+md5
[HTC EVO 3D] ryanrmc:
I downloaded another butterz sense, but it still says the same error.
[HTC EVO 3D] hossman:
Try wiping everything

Then reboot recovery

Then wipe again

Then flash

If that doesn't work try any other stock sense based Rom. Butterz should work so just keep trying different Roms till you find one that works.

Just don't flash any jelly bean base
[HTC EVO 3D] ryanrmc:
Thank you so much.. would you like me to thank every single one of your posts?
[HTC EVO 3D] hossman:
I assume you got it working?
[HTC EVO 3D] ryanrmc:
Yes!!!
[HTC EVO 3D] hossman:
Good deal!
[General Questions and Answers] msti_oliveira:
Hi to all, anyone know if 64g microsd is supported by the Padfone A66? :confused:

currently I'm using a 32 gb microSD and it works fine, but i want more memory on my padfone and i want to buy a new microSD

I hope someone help me :good:

Tanks to all
[JAM, MDA Compact, S100 General] joey jojo:
hi there, my mates xda mini on t-mobile was lost on his device as he tried to install a version that wasnt meant for his device, now he dont have any OS as it removed the rom and couldnt install the other, so its a clean device, i have downloaded the rom from the FTP site and i find the file is

tmobile.nb1

how do i get this installed on his device???

im new to this myself and no idea how to do it, i have heard this and that among the forums and i am assuming that you transfer this to an SD card and install it from there, if this is what you do then how do you do it??? is it simple, or is there an extractor i can use to turn it into an installer????

PLEASE HELP, :D
[JAM, MDA Compact, S100 General] jfran:
its not a process for the light hearted, however is it a xda mini your friend has or the mda compact, without the clarification we cant really progress.

All he needs if it is the mini is to install the xda mini rom files, however if it is the compact you will need to do a bit more.

Reply if further assistance is needed

jim
[JAM, MDA Compact, S100 General] joey jojo:
it is the mda compact, what he did was 9as he is new to this stuff0 tried to install an xda2s software to it, and it took his old rom off the device, it then tried to install then he got the error message and would not go any further, now as mentioned earlier, i have the file from the ftp site which im guessing more and more now that i just put that file on an sd card, and flash it, only thing is, it mentions something somewhere i read that you need to copy files from the old rom which he dont have and i dont have access to. what do i do, as he is going to india for 6 months in 4 weeks and if he sends it away for repair he wont get it back in time... and im his only hope as it happened to me, only thing, i have xda 2s and im on o2, so i just got the rom from here, which was an installer from the pc through the usb connection...

please help!!!! :D
[JAM, MDA Compact, S100 General] jfran:
So I can assume that the screen just says serial on top and v1.00 at the bottom, ie the bootloder screen, if this is the case there is some hope however you will need a few tools and some patience

ntrw

romupdate utility

SD card reader / writer

at least 256MB SD card

once you have that, just follow the instructions for the ananasky ROM update, however the rom that you will be patching is the tmobile.nb1 one on the ftp site, or you could go ahead and try the anansky patch itself

as before let me konw how u are progressing

jim
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
The title says it all.

After a number of successful flashes. the last one of which was to cleanrom 1.5 my wifi was not working.

I then went to use the lokifyed 3way to to return to stock and begin again.

The process died in mid download (1st time ever)

Then powered down. rebooted phone (no recovery... it is gone.)

I can get to download or "firmware upgrade encountered an issue"

tried 3 way tool again to return to stock

"no pit partition" a few times

now:

<ID:0/008> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/008> Odin v.3 engine (ID:8)..

<ID:0/008> File analysis..

<ID:0/008> SetupConnection..

<ID:0/008> Initialzation..

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

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

<ID:0/008> aboot.mbn

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

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

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

<ID:0/008> Removed!!

<ID:0/008> Added!!

Am I SOL?

about to try the CASUAL tool to see if that works...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
An emergency firmware recovery with KIES would fix it but then you'd have MF3. The recovery partition has been wiped. The ODIN flash succeeds, but the last step of booting into recovery to wipe doesn't happen because there is no recovery. Try flashing a recovery with ODIN. If you can access it, just flash a ROM.

Try flashing a recovery with ODIN.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
repartition an option?

Question:

Can I use ODIN to repartition with the "SGS-I337.pit" file? Would that fix the partitions and then I could rerun the 3way tool?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Make that your last resort before Kies or JTAG. Try flashing a recovery in ODIN first.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Thanks. Off to find a odin'able recovery...

Thanks. Will search for a odin usable recovery.

Will report back later...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Do you think this will work?

http://xdaforums.com/showthread.php?t=2360859&page=2

Sound like a slightly similar situation...

maybe...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Don't mess with that, it's MF3
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
So is cleanrom 1.5 which is where this all started... i.e. cleanrom 1.5 wireless not working then 3 way tool to return to stock (mdl)...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Yes but those files are the MF3 aboot, and sbl1, 2, and 3... It would be just like accepting the OTA...

Did you try ODIN a recovery?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Yeah. Tried odin recovery,

tried the pit file.

tried casual

tried several other things did a lot of reading.

All to no avail...

So in choosing between an expensive paper weight with a yellow triangle I am going the Keis way and hoping that is recovers the phone. I am confident that someone will find an exploit... if not then.. well it could be worse: I could be using a iphone...

Thanks for your help. I post the results of keis...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] xBeerdroiDx:
listen to GiantBallSack. an MF3-based rom or rooted-stock MF3 are completely different that OTA in that you still retain maneuverability/root
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
It should fix it, I had to fix one an S3 ROM was flash to, and Kies did the trick.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] xBeerdroiDx:
i'm not sure what to think about a thread involving a GiantBallSack and SaltyFoam... :D
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
...

First off: I did a lot of reading of your knowledge share... a good education: Thanks.

Yes I understand. what you are saying except that I am out of ideas.

Tried a stock recovery (tar file) in odin...

tried original firmware.

Tried various tools.

Tried repartitioning

tried some other tools...

and as of 10 seconds ago keis also will not repair it...

So:

To sum up

I can go into download mode.

I can not go into recovery (I will try a few more times)

straight boot goes to firmware error...

Any other ideas?

Thanks for listening...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Flashing ODIN-CWN6.6.1.2.tar (through odin results in:

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> recovery.img

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

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

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

ODIN of "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5"

returns:

same as above...

I am at a lose... will keep reading...

Thanks.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Do have the PIT? If so, put it in the PIT field and try again. If it fails, do the same with the PIT and check repartition.

---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------

If we made a ROM together it could be SaltyFoam from GiantBallSack
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
ROTFL!!! :laugh:

In any case: with the pit file (re-partition check and unchecked) the result is the same...

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> aboot.mbn

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

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

<OSM> All threads completed. (succeed 0 / failed 1)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
I can probably build the equivalent of that MF3 kies unbrick with MDL files... I'll need a little time, all I currently have is the aboot.mbn, and tz.mbn, both extracted from a stock ROM
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
hmmmm.

See the attached image... this makes me think that a odin flashable mf3 stock rom might work... does such a thing yet exist?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Interesting...

What can I do to help?

Besides testing...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Give me about 20 minutes to pull these files from my S4 and make a .tar for you. MF3 is your last resort.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
I have been using smartphones since the nokia e71x (well kind of smart)

I have been through a

Samsung wm1,s,s2,s3,s4... this is the first softbrick I have experienced... What a PIA!!!

Thanks.

Digitronically yours,

Saltheart Foamfollower
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
I started modding with the V3 RAZR
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
By the time android became a thing I was very involved with SQL Servers and enterprise monitoring at a fortune 50 bank, 4 kids, a wife, a dog, car notes and mortgages...

I did not have enough brain left to get into the nitty gritty of this stuff...

But now... I drive a bus... like Ralph Kramden!!! After I finish getting my HAM license I will make time to delve deeper into these little critters...

Thanks again for all your help...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Alright I've pulled all of the files included in the MF3_BTL_FIX.tar.md5 from my phone with MDL and created the equivalent.

Now you have to keep in mind that he pulled those files directly from the MF3 update and I pulled them from my phone, so as always, you flash at your own risk.

For the savvy, here was my method for creating it:

adb shell
su
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl2.mbn bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/sbl3.mbn bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.mbn bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/rpm.mbn bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/tz.mbn bs=4096

exit

tar -H ustar -c sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn > MDL_BTL_FIX.tar

md5sum -t MDL_BTL_FIX.tar >> MDL_BTL_FIX.tar
mv MDL_BTL_FIX.tar MDL_BTL_FIX.tar.md5

Here it is:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Ah... I see... I was trying just know to figure out how to read the system.img.ext4 included in the rom image with the 3 way tool to get those files...

Thanks for the 'script' version....

My glasses just broke and everything is blurry...

So: I follow the same instructions as the mf3 version...

Give me 5 minutes...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
Those are the commands to pull them off of a phone. If you want to extract them from an Update, you can do that too, but the method will be different.

If you extract the stock ROM, you only get aboot.bin and tz.mbn, so you would need to find the MDL Kies update to extract them from. Unpack it with 7zip.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
No Love...

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> MF3_BTL_FIX.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> aboot.mbn

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

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

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

<ID:0/004> Removed!!

<ID:0/004> Added!!

Wife is calling and daughter wants to know when I a tucking here in.(7 y/o). I will try to return in a while... if not early AM...

Thanks again for the help and education...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
You flashed the MF3 one? If mine doesn't work, you are down to a Kies Emergency Firmware Recovery.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Yeap...

<OSM> MF3_BTL_FIX.tar.md5 is valid.

Keis already failed.

I will retry in the morning...

Fresh reboot of computer.

Another cable

Another usb port

Fresh ideas...

If something occurs to you please share...

I suspect that the clue is in the image I posted...

"SW REV. Check Fail: fused 2 : Binary 1"

Thanks again for your help.

Have good night...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] GiantBallSack:
I posted the one I made with MDL files a couple of posts back. If you are weary of flashing it, I understand.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
You're right that the "SW REV. Check Fail: fused 2 : Binary 1" is the clue here.

Someone correct me if I'm wrong, but...

What's happened is that somehow or another, you have an MF3 bootloader (or at least part of it?). This has permanently incremented e-fuse(s) within your phone, and this will prevent you from trying to load the MDB or MDL Odin "return-to-stock" packages. Quite simply, Odin on your phone recognizes that this firmware is older than your current MF3 bootloader, and will refuse to flash it.

IF

this is the case, the only known cure at this time is to proceed with fully moving forward with the MF3 update, including bootloaders, recovery, kernel, etc. ... And being permanently stuck that way. No root (unless you get lucky with a "rootkeeper" app), no custom recovery, no custom roms.

What again did you flash to your phone that got you stuck this way? Is it possible that you took the MF3 OTA update by mistake? Does CleanROM 1.5 actually include bootloaders?! (if it does, that's a ridiculously serious problem!)

In any case, best of luck to you. It appears you have the attention of some of the best helpers on this side of XDA working with you. Don't lose hope on your phone yet - if you're still able to get to Download mode, there's still some hope! You might be stuck with MF3+ forever, but at least you're not hard-bricked. I know that Adam and a few other developers are currently looking into a new root method for the MF3 firmware, but it's looking pretty bleak. Also, the "Loki" exploit was patched, so a new version of that would have to be made as well.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
I am such a duffus!!! I meant to flash the one you sent... too many hours in front of the screen,,,,!

DOH!!!

Dope Slap!!!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
correct file this time... same end...

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> MDL_BTL_FIX.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> sbl2.mbn

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

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

<OSM> All threads completed. (succeed 0 / failed 1)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
So on a whim..

SO: having run out of ideas I remember reading about folks that repeatedly blast commands at the phone to 'break through' the blockage.

I loaded the mf3 fix (MF3_BTL_FIX.tar.md5) into odin and started repeatedly trying to write these images with no pause after a few tries it completed successfully (see below).

Going to try Keis again to see if it fairs better now than before...

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> MF3_BTL_FIX.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> aboot.mbn

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

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

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

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> aboot.mbn

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

<ID:0/004> rpm.mbn

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

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

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> aboot.mbn

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

<ID:0/004> rpm.mbn

<ID:0/004> sbl2.mbn

<ID:0/004> sbl3.mbn

<ID:0/004> tz.mbn

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Thanks...

You are spot on.

To Recap:

I was on cleanrom 1.0. All was good.

wipe/reset...

flashed cleanrom 1.5: Wifi not working.

wipe/reset

tried to flash cleanrom 1.0: for some unknown reason the download/flash died in the middle (first time ever in many years of this)

Reboot to: "Firmware upgrade error etc."

No recovery mode to be found...

After a plethora of three finger salutes I accept that download mode is all I have.

3 way tool -> return to stock. Fail fail fail. always an fail (auth) or sw check secure error on the phone.

Keis wont fix it: it keeps saying the the MDL version is the latest rom and is not finding the MF3 version on the samsung server (wtf?) (so clearly it would fail)

I find this http://xdaforums.com/showthread.php?t=2360859&page=1 It strikes me as a similar problem.

After many back and forths pushes and such I get the MF3_BTL_FIX.tar.md5 to push via odin...

Now I still have no recovery but still have download mode.

I am guessing that If I can get an odin image of the stock MF3 recovery I could push that onto the phone.

I also assume that if I had an odin pushable mf3 rom image I push that.

As to root... I would rather have a working phone with no root than a brick with a yellow triangle...

I also have mondo respect and admiration for all of you folks out there that do the deep digging....

Thanks

Again,

Salty...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
Pretty much. Please see your other thread for my post about how we can get a copy of at least one of these.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] T90:
Steven R. Donaldson fan eh? Love that series! Can't wait for his next release!

Sorry, back on topic!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
Yeah, I originally read the books in the 1980's.

That character always struck a chord...

The power of a good healthy laugh...

The cleansing by fire...

the pathos of the crew on the ship, the selfless sacrifice, the long stories taking the time they take...

Stone and Sea...

So much good material... I have the last book on preorder at amazon (http://www.amazon.com/gp/product/0399159207/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1)

Good stuff.

Have had this email address since the beta days of gmail...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeboo:
So ODIN-flooding the phone actually restored the BL?! This would be interesting..
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SaltyFoam:
So it seems...

Out of sheer frustration I figured I would abuse the usb port... in the back of my head I was hoping that if it was a cable or port problem 1 chance x might work.

So every time as soon as it failed I just pressed start again. Much to my surprise on the third (?) try it did not fail.

The problem now is that I still have no working recovery on the phone.

Question: How do I affirm that the boot chain is actually correct (i.e the correct aboot, rpm, sbl2, sbl3, tz) if I can't boot into recovery or a working OS?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
Just read the last couple posts here about the Odin-flooding. That's REALLY interesting! ..... ...... ....o_O