yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Bait-Fish:
I could be wrong, or have some this wrong, but the numbers aren't matching my system versus rajat12345's requested info. This may explain why the devlog.img didn't dd, there is no devlog. EDIT: Below was from my consumer GS4,not the Dev Edition, but it doesn't appear to change much. The blocks don't match the OP's requested image name.

root@android:/dev/block/platform/msm_sdcc.1/by-name # ls -l

lrwxrwxrwx root root 1970-03-09 12:03 aboot -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 1970-03-09 12:03 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 1970-03-09 12:03 backup -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 1970-03-09 12:03 boot -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 1970-03-09 12:03 cache -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 1970-03-09 12:03 carrier -> /dev/block/mmcblk0p28

lrwxrwxrwx root root 1970-03-09 12:03 efs -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 1970-03-09 12:03 fota -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 1970-03-09 12:03 fsg -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 1970-03-09 12:03 hidden -> /dev/block/mmcblk0p27

lrwxrwxrwx root root 1970-03-09 12:03 m9kefs1 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 1970-03-09 12:03 m9kefs2 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 1970-03-09 12:03 m9kefs3 -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 1970-03-09 12:03 mdm -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 1970-03-09 12:03 modemst1 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 1970-03-09 12:03 modemst2 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 1970-03-09 12:03 pad -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 1970-03-09 12:03 param -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 1970-03-09 12:03 persdata -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 1970-03-09 12:03 persist -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 1970-03-09 12:03 recovery -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 1970-03-09 12:03 rpm -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 1970-03-09 12:03 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 1970-03-09 12:03 sbl2 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 1970-03-09 12:03 sbl3 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 1970-03-09 12:03 ssd -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 1970-03-09 12:03 system -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 1970-03-09 12:03 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 1970-03-09 12:03 userdata -> /dev/block/mmcblk0p29

root@android:/dev/block/platform/msm_sdcc.1/by-name #

22=backup

23=fota

32=?

29=userdata!

[MENTION=4139454]asharad[/MENTION] That's alarming. Am I reading this right? Pulling my "system.img" share to be safe.

What are the implications here?

Honest mistake or are the blocks different between consumer and dev edition? Did I/we get duped into putting our info on the cloud?
[Verizon Samsung Galaxy S 4] SamuriHL:
Do you guys have the following path:

/dev/block/platform/msm_sdcc.1/by-name

If so, can someone list what's in it? The folder after platform might be different. So check platform first to see what's in there. But the by-name folder should give a list of what the partitions are and how they map.
[Verizon Samsung Galaxy S 4] Bait-Fish:
One BIG qualifier. I just got the above info from my consumer phone, not the Dev. I could be off base for sure. It scared me and I reacted. Looking into it on the dev phone *slaps forehead*
[Verizon Samsung Galaxy S 4] sphyyr:
I have an ATT with the latest MF3 update, no root or anything and I have that folder path, if there is anything I can provide information wise to help out let me know please.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Below is from the Developer Edition. That path exists you asked for Sam. The first list is by 'ls' and the second by 'ls - l'.

aboot apnhlos
backup boot
cache carrier
efs fota
fsg hidden
m9kefs1 m9kefs2
m9kefs3 mdm
modemst1 modemst2
pad param
persdata persist
recovery rpm
sbl1 sbl2
sbl3
ssd
system
tz
userdata
-l <
lrwxrwxrwx root root 1970-01-04 16:33 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 16:33 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 16:33 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 16:33 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 16:33 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 16:33 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 16:33 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 16:33 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 16:33 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 16:33 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 16:33 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 16:33 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 16:33 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 16:33 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 16:33 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 16:33 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 16:33 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 16:33 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 16:33 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 16:33 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 16:33 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 16:33 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 16:33 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 16:33 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 16:33 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 16:33 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 16:33 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 16:33 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 16:33 userdata -> /dev/block/mmcblk0p29
root@android:/dev/block/platform/msm_sdcc.1/by-name #

Edit: Pasting the copy into a txt document seems to be playing with the formatting but it looks like all the info is there. Changed it to a code box from hide.
[Verizon Samsung Galaxy S 4] asharad:
I've pulled my dropbox links for now.

What data is held in "backup" and "fota" ?
[Verizon Samsung Galaxy S 4] Bait-Fish:
[MENTION=4139454]asharad[/MENTION], Did you ever get a link up and share your link to the "system.img"?

I pulled links and deleted files from the cloud. I took pains not to do anything to this phone including setup, customization, accounts, or user info. Hopefully nothing really was possibly leaked. Guess I'll PM rajat12345 since we haven't heard a response.
[Verizon Samsung Galaxy S 4] asharad:
No, the only files I shared were mmcblk0p22 (fota) and mmcblk0p23 (backup). I would have shared system.img (userdata!!!) within the next hour. My device has been my primary driver since Tuesday, so I'm glad you stopped me when you did.
[Verizon Samsung Galaxy S 4] Bait-Fish:
While we're at it, can you make a proper boot image since you didn't touch the kernel like I did. It is listed at mmcblk0p20 (see above). You could cd to that same path and issue 'ls - l' to list everything on your device.

I will dd the proper recovery.img on mine.
[Verizon Samsung Galaxy S 4] asharad:
boot.img

/dev/block/mmcblk0p20

http://db.tt/VIj5tU9s

Md5 d7d0693384050fb4b6bbdafefbeafd18
[Verizon Samsung Galaxy S 4] SamuriHL:
Excellent. Now the OP can see exactly which blocks he wants and extract them.
[Verizon Samsung Galaxy S 4] Bait-Fish:
recovery.img

/dev/block/mmcblk0p21

https://app.box.com/s/ydvc0exmeeu4uzdn0tuy

MD5 6e14b9d5158d4c05609f0ea2c02cfb17
[Verizon Samsung Galaxy S 4] twizzlejr:
So what's going on rajat12345 any news on your progress
[Verizon Samsung Galaxy S 4] Bait-Fish:
The files we gathered were from the wrong memory blocks. I am working on the system dump from /dev/block/mmcblk0p16 now. Seems to be another large file. Terminal Emulator is staring back blankly at me . . .

Edit: Spelling correction
[Verizon Samsung Galaxy S 4] asharad:
Do you need me to pull any other partitions, or is the boot enough?
[Verizon Samsung Galaxy S 4] SamuriHL:
You guys can pull them using the by-name path, as well.
[Verizon Samsung Galaxy S 4] Galaxys4bean:
Just letting everyone know i looked on rajat12345 profile and he is from india so he may be on at different times than us!
[Verizon Samsung Galaxy S 4] asharad:
oh really? I find that rather curious.
[Verizon Samsung Galaxy S 4] frr1:
Yea where is the OP

He needs to update on the progress

all this work these guys are doin we need the OP to use these files to unlock the bootloader already
[Verizon Samsung Galaxy S 4] SamuriHL:
Curious? Why? It's just a link.

dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img

That'll extract the boot partition, as an example.
[Verizon Samsung Galaxy S 4] asharad:
Well, if he had asked for those instead, we wouldn't have mistakenly uploaded our userdata partitions.
[Verizon Samsung Galaxy S 4] SamuriHL:
Not everyone knows about them. :) I've been studying all things S4 in the past couple weeks which is why I know about it.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I didn't know that was possible either. Good way to ensure you're getting the right one, just a longer path.

Is there an easy way to copy the path on the phone to speed up entry and reduce possible typos? I haven't seen a way to copy the path or repeat the last command (terminal emulator, root explorer, ES file explorer).
[Verizon Samsung Galaxy S 4] asharad:
If you have ADB it makes it really easy.
[Verizon Samsung Galaxy S 4] rmanaka:
Thank you, [MENTION=4139454]asharad[/MENTION]!

Thank you, [MENTION=4211058]Bait-Fish[/MENTION]! I ALMOST dd'd your previous recovery.img onto my phone after I decided to go the Philz touch CWM method to root since I figured I could recover from a borked recovery flash easier than a boot.img bad flash...plus you had posted the MD5!

Glad I was making nandroids today and then checked the thread before doing anything else!

BTW, I reset to Factory Default and then made a TWRP nandroid of the phone including all partitions listed in Philz's recovery. Sorry that I didn't do that before rooting, SuperSU 1.51, but I think this nandroid can be used to get pretty close to a stock DEV Edition if somebody wants to make it into a tarball that can be flashed in ODIN. PM me if you are interested in the TWRP recovery!

Thanks everybody participating in this thread...VERY educational!:)
[Verizon Samsung Galaxy S 4] frr1:
with all these files can the bootloader be unlocked now?
[Verizon Samsung Galaxy S 4] :
Patience, my friend, patience. :good:
[Verizon Samsung Galaxy S 4] Cruiserdude:
Gotta wait for the OP. I don't think he's made it exactly clear what he's trying to do, and I don't want to speculate, as that would merely pollute the thread and confuse people. I have an idea, but we'll know soon enough if it works or not. Just don't go trying to dd any of this stuff from a dev edition to your retail version. Not yet, anyway.

Sent from my VZW Galaxy S4 Google Play Edition :)
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I'm guessing that a tar of this won't work if you have CWM as recovery? Or does it overwrite everything including recovery. I'll be more than happy to make a tar of it for people. I'll send you a PM.
[Verizon Samsung Galaxy S 4] SamuriHL:
For those doing the dd stuff, you can write a batch file to do it if you wish. Something like:

adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/boot /sdcard/boot.img'"
adb pull /sdcard/boot.img c:\some\local\path\boot.img

And repeat those lines for all the partitions you wanna pull down. Obviously adb either needs to be in the same dir as the bat file you create or in your path.
[Verizon Samsung Galaxy S 4] rmanaka:
HAHA! Your dump was a lifesaver (well at least saved me a bunch of trouble)!

I was playing around with Chainfire's Triangle-Away trying to get rid of the Samsung Custom padlock on boot and let TA replace the recovery.img. It might have replaced it with a stock retail recovery (or who know what), so every time the phone booted it went to a recovery screen (blue writing on top left of screen) THEN went to the Samsung Boot Screen followed by the Verizon boot animation.

I dd'd the recovery.img provided by [MENTION=4211058]Bait-Fish[/MENTION] (into the proper partition) and am now back at a stock recovery.

I probably could have ODIN'd Philz-touch CWM but thought I'd test the dump just for kicks...Works great!!!:laugh:
[Verizon Samsung Galaxy S 4] Bait-Fish:
Very cool! Happy to have helped.

Edit: system.img is done, uploaded, and PM sent.
[Verizon Samsung Galaxy S 4] saltytaco:
Lol I've been following along the thread a lot but I still don't understand whats going on, Is the OP still involved?
[Verizon Samsung Galaxy S 4] :
Yes. He mentioned earlier in the thread that he's away for the weekend.
[Verizon Samsung Galaxy S 4] Bait-Fish:
His last post yesterday was that he was on vacation for the weekend.
[Verizon Samsung Galaxy S 4] asharad:
Lol, I have many posts in the thread, and I don't understand.
[Verizon Samsung Galaxy S 4] PetrichorXFi:
Perhaps if the OP, and any other dev, post thier strategies we can regain access to our bootloader sooner. More brains working together = better/faster solution
[Verizon Samsung Galaxy S 4] rmanaka:
Links sent to both a CWM backup and a TWRP backup (both zipped)!:)

Thanks!
[Verizon Samsung Galaxy S 4] Covert_Death:
they don't want to split that bounty ;)
[Verizon Samsung Galaxy S 4] rmanaka:
There's actually two things going on in this thread...the OP wanted a dump of a few partitions from a STOCK Developer's Edition S4, and a few of us who have stock phones were trying to figure out how to obtain a stock recovery tarball so that we could revert back to a stock phone if something got corrupted as we were dumping the phone.

Most of this thread has to do with determining which partitions to dump, how to dump them, and then how to create the stock recovery package (since Samsung doesn't seem to have provided such a beast)...

The OP should be back soon and hopefully will have news about the consumer ME7 unlock!
[Verizon Samsung Galaxy S 4] ozzzzysh:
Be it good or bad news, I'm just glad SOMEONE is communicating and trying something. I wonder how many people are actually trying to unlock our phone.. Probably less than we hope. I'm a programmer, but this is way over my head. I know web stuff, like PHP, I'm just starting to get into java and whatnot. I wish I could help more. haha
[Verizon Samsung Galaxy S 4] saltytaco:
Same I'm a C++, Java, and Lua programmer and don't know how much of this works, I guess since i'm just a game programmer lol
[Verizon Samsung Galaxy S 4] TechSavvy2:
Not posting strategies, more like pm'ing behind the scenes. Do you really want exploits posted in plain sight where Verizon can see them? Thats why Dan withheld loki until after the device was released. Also why you NEVER see the progress post made or who is working on what. Trust me, more are working on it than we know about.

Not that they don't eventually figure it out anyways....but still....
[Verizon Samsung Galaxy S 4] PetrichorXFi:
Ah good point! I suppose there is a balance we need to find.... enough info to allow the community to gain bootloader access in a timely manner, while keeping Verizon from locking us out.
[Verizon Samsung Galaxy S 4] Au_A7:
Sorry if I'm wrong but doesn't the dev edition come with a micro sd that puts the phone back to stock?
[Verizon Samsung Galaxy S 4] asharad:
The only thing it comes with is a battery charger. No SIM, no microSD.
[Verizon Samsung Galaxy S 4] magicalwilly:
the future is looking dark :/
[Verizon Samsung Galaxy S 4] bajasur:
Why? Did you guys read that the OP is on vacation this weekend... I'm sure he will jump back on when he's back. I think he is in to something... plus he already said he unlocked the bootloader... I think the future is looking bright

---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------

See above
[HTC Sensation XL] Ragi9:
Can anyone make something like this for the Sensation XL (Stona s ROM)

http://xdaforums.com/showthread.php?t=2177506
[HTC Sensation XL] nipsadinio:
d-h.st/d08

Someone posted it on the screenshot section. Hope it helps.
[HTC Sensation XL] Ragi9:
The File is dead !!!
[Nexus 7 (2013) Q&A] mystycs:
Just got my Nexus 7 opened it up first thing installed MXPlayer and it crashes. Anyone else have this issue?
[Nexus 7 (2013) Q&A] cyberprodigy:
I'm pretty sure MXPlayer isn't compatible with 4.3 yet.
[Nexus 7 (2013) Q&A] saadahmeddar:
On 4.3 it crashes like hell

Keep calm and wait for latest update
[Nexus 7 (2013) Q&A] Ambrosios:
i haven't had any issue with MXplayer.....although for some of my media, i had to use software decoding rather than hardware
[Nexus 7 (2013) Q&A] cyberprodigy:
You need to download the MXPlayer made for 4.3 from their homepage. Here is the link:

https://sites.google.com/site/mxvpen/download
[Nexus 7 (2013) Q&A] Nbsss:
I've had no problems, I have mxplayer set to s/w and have played movies from 1tb hard drive connected by otg...
[Nexus 7 (2013) Q&A] aiiee:
It was crashing then I updated it today. Now it doesn't crash!
[Nexus 7 (2013) Q&A] stevemw:
Upgrades are on Play store as of yesterday
[Nexus 7 (2013) Q&A] macaumen:
After update, it works perfectly.
[T-Mobile Samsung Galaxy S 4] realizerecognize:
What are some things I could delete or move to SD to get more internal memory. I am running liquid smooth ROM. I know there used to be an apps to SD option through titanium backup but I don't see it anymore.
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
Have you read any of the other numerous threads on the subject of internal memory? This subject has been covered so many times and it's always the same thing.
[T-Mobile Samsung Galaxy S 4] richardlibeau:
Use folder mount to move big files to ex card. This phone does not have option yet to move apps to sd unless you use a rom from another carrier on it.
[T-Mobile Samsung Galaxy S 4] Skipjacks:
This!

The easy bet is that it is your rom backups. That has been the answer for all 900 other people who have made this same thread.
[T-Mobile Samsung Galaxy S 4] richardlibeau:
That's why you always save backups on the ex card. Never save them on internal sd.
[T-Mobile Samsung Galaxy S 4] realizerecognize:
I always search before making a post. Haven't started too many posts... Sorry I couldn't find the answer :/ but thank you other guys for the help. I wasn't sure if backups could go to SD because of them being through cwm. But yes I knew they were taking a lot of my memory away.
[T-Mobile Samsung Galaxy S 4] realizerecognize:
Next questions search. Getting backups to SD..
[T-Mobile Samsung Galaxy S 4] oif0709:
To get back ups to sd, first you search your recovery since they are not all created equal. On cwm I know you have the option right after you select backup and restore. It is a few selections down. Not sure on twrp, Im sure its easily spotted though.
[T-Mobile Samsung Galaxy S 4] realizerecognize:
Figured out how to back up to SD. Thanks for the help!
[Security Discussion] pauloviegas:
I left my Lenovo TPT unattended for two days on.

When I've tried to use it again I got a message that encryption did not end correctly to make a reset to original values.

This was strange and because recovery was not working I did tried that step as well without success.

Due to low battery, I manage to access settings and came to realize that there are strange certificates install like TURKTRUST Digital Certificate which I came to realize is reported to be a virus http://eromang.zataz.com/2013/01/04/...ctive-attacks/

In recovery I see that I cannot mount the internal SD or data. I can connect trough ADB but I'm not an expert able to use it properlly.

Any ideas on how to recover my TPT?

Using adb I manage to get the logcat ...hope someone is expert enough to go around this problem.

I only need to format / mount SDCard and data which is blocked now ...

Thanks in anticipation.
[Verizon Samsung Galaxy S 4] thefederer:
I am running Hyperdrive ROM rls 7. I have tried many things to get MMS picture messages to work on my phone again after they have stopped unexpectedly. I can send group MMS text messages however whenever I send a picture (no matter the size) it just continually loads and never sends. I have tried reinstalling various nandroid backups to no avail with fixing the problem. Could it be that i reinstall my textmessage data using titanium backup? does anyone have the stock messaging app apk? maybe reinstalling it would help, i really don't know at this point.
[Verizon Samsung Galaxy S 4] Tortuga:
Are you connected to wifi? MANY people have reported issues both on stock and various ROMs with sending MMS while wifi is connected. Try disconnecting your wifi and see if they send. While connected to wifi, the MMS messages are supposed to trigger 4g connection which transmits the data via Verizon's network. In many phones/ROMs this doesn't work right. I'm not aware of an end-all resolution though.
[Verizon Samsung Galaxy S 4] thefederer:
Unfortunately they do not send regardless of whether WiFi is enabled or disabled.
[Verizon Samsung Galaxy S 4] Tortuga:
What kind of mods do you have installed with Hyperdrive? You may have to switch to a different ROM or rooted stock ROM to re-test. I don't think it's broken in Scott's ROM, but could've been an app or mod that broke it.
[Verizon Samsung Galaxy S 4] thefederer:
I don't have any mods installed with Hyperdrive, only the ones that come with it. I have already tried restoring a nandroid backup i made right after I rooted but it doesn't work there either.
[Verizon Samsung Galaxy S 4] Tortuga:
Maybe try a full wipe and clean install of a different ROM? If that doesn't work, I guess I would ODIN back to factory stock. If it doesn't work there you are all set to take to Verizon store and show them. You'd be eligible for a warranty swap, but I've never gone through that before, so I don't know how it completely works.
[Asus  Eee Pad Transformer Prime] 404dinosaur:
Hey guys, I'm having trouble unlocking the bootloader on my TF201.

Every time I launch the ASUS supplied app and click the unlock button, I get the message that an unknown error has occurred and to try again later. This has been occuring for several weeks since I tried to do this.

Android Version : 4.1.1

Build Number: JRO03C.US_epad-10.4.2.18-20121122

If it helps, I did have to RMA my tablet due to the unknown serial number issue when I first got it.

Any help would be greatly appreciated!!
[Asus  Eee Pad Transformer Prime] flueterflam:
sorry...

Unfortunately, this thread is all about your problem:

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

I just posted an update, so you may want to check the last page of that thread. The short answer is...without doing something, you probably won't get it fixed. Also, doing another RMA, probably also won't help. My post is *very* detailed, and hopefully it helps you understand why RMAing probably won't fix the problem (unless, of course, you have no serial number...which is a necessity). :)
[Asus  Eee Pad Transformer Prime] 404dinosaur:
Thank you so much for your reply!

What firmware and android version were you on when you contacted ASUS via email?
[Asus  Eee Pad Transformer Prime] flueterflam:
If you're asking what I had when I first contacted them and then sent in for the RMA...I don't recall anymore. It was at least 4.1.1 and TW 10.4.2.17 (or newer).

After the RMA, they reimaged it and I had the following when I contacted them the final time (and they ultimate ended up fixing it, server side):

Android version: 4.1.1

Kernel: 3.1.10-00004-gc770ddc android@Venus)) #1 SMP PREEMPT Thu Oct 18 15:38:00 CST 2012

Build number: JRO03C.WW_epad-10.4.2.17-20121018

Pad EC version: TF201-PAD-0215

In the email, I also included my serial number and wifi MAC address for their reference.
[Asus  Eee Pad Transformer Prime] 404dinosaur:
Alright thank you, because when I first contacted them they said the problem was unfixable because I was not on 4.0. I'll try contacting them and tell them I am on 4.0. This really helps, I appreciate it.

;
[Asus  Eee Pad Transformer Prime] flueterflam:
No worries. Best of luck!