Database Users

Upgrade from kies not working

for some reason, i can connect to kies with no problem, but when i go to upgrade the firmware to the newest JI6 official, it fails and shows the attached picture. any ideas? I need to get this update because my vibrant is acting up pretty ba and as far as I know, this is the only current fix. I dont want to use the samfirmwares.com version because I want the official version. Help!

What version of Kies are you on? I'm on 1.5.1 and I never see an update. Maybe 1.5.3 can see the update?

Just updated mine about an hour ago through kies. Worked fine.
Kies Version: 1.5.1
Prior Rom: Bionix 1.4
Kernel: Stock

im on 1.5.3 and it still wont work, i just tried it again. I tried rebooting the pone and computer and still nothing worked. it just keeps saying unable to update. when you installed kies, did you install it as the UK as your country or US?

Mine says "PC Connection only available in idle screen Close running applications" when I try to connect with Samsung Kies mode???? What am I doing wrong?

Back out of everything on the phone, make sure you are in Kies mode. Run Kies first, then connect phone.
I have yet to see on the forum where somebody went from the JI5 from Kies to JI6 either OTA or through Kies. I've tried 1.5.1 and 1.5.3.81 for Kies and neither will update my phone.

Updating through Kies right now. I had to do the regedit fix for Kies 1.5.3.
EDIT: Whew, phone isn't bricked. Just made it past the Vibrant screen.

is it possible that kies may brick the phone?

How long is the Kies update taking for you guys? I'm pretty sure I'm hung up. It made it through the downloading, and now it's about a 1/4 of the way through the upgrade bar, but hasn't moved for an hour and a half.
I am totally stock. No mods, no nothing.

nateball said:
How long is the Kies update taking for you guys? I'm pretty sure I'm hung up. It made it through the downloading, and now it's about a 1/4 of the way through the upgrade bar, but hasn't moved for an hour and a half.
I am totally stock. No mods, no nothing.
Click to expand...
Click to collapse
that's not good. if i'm in your condition maybe i'm already sweating. maybe just wait a little more.
i tried to do this but the kies hung up when it's copying my contacts.

Well, it's not gonna do me any good to sweat. I'm over two hours now of just watching it sit there 25% done. No movement at all, computer's cpu is at 0% use. I think I have to pull the plug and then call Tmob if the phone is messed up.
Just to be clear, I was 100% stock, no root, no fixes, nothing other than apps installed from the marketplace. Here goes nothing...

nateball said:
Well, it's not gonna do me any good to sweat. I'm over two hours now of just watching it sit there 25% done. No movement at all, computer's cpu is at 0% use. I think I have to pull the plug and then call Tmob if the phone is messed up.
Just to be clear, I was 100% stock, no root, no fixes, nothing other than apps installed from the marketplace. Here goes nothing...
Click to expand...
Click to collapse
what happened? me too, i unplugged my phone before anything goes wrong.

ive made the backup of my contacts, but after that it cant continue to update, it fails every time, i guess i am stuck waiting for the ota unless someone has a fix for kies

My phone now only shows an image of a mobile phone and a desktop with a caution sign in between them. The same image shows if I restart using the power button, pull the battery, shake it vigorously, etc. I do believe I am now the proud owner of a non-functioning phone. Kies will not recognize it, nor does windows recognize it when it is plugged in. Crap.
I guess I'm off to the T-mobile store to try and get a replacement.

im in same boat i have no clue what im doing wrong? im i missing steps here?
if has any idea what i need to please help.
im a bone stock

Well, I'm pretty sure that we are now lacking functioning firmware on the phone. I'm thinking a new phone is the way to go, but maybe they can do something at the store.

Anyone where the update is stuck, you will probably have a soft brick at this point. However, this does not mean your phone is broken completely, it just means you will probably have to get into Download Mode and Flash via Odin.
Have fun

nateball said:
My phone now only shows an image of a mobile phone and a desktop with a caution sign in between them. The same image shows if I restart using the power button, pull the battery, shake it vigorously, etc. I do believe I am now the proud owner of a non-functioning phone. Kies will not recognize it, nor does windows recognize it when it is plugged in. Crap.
I guess I'm off to the T-mobile store to try and get a replacement.
Click to expand...
Click to collapse
that was my experience using kies too (whether 1.5.1 or 1.5.3). since then, i've used odin (v1.3) about 6 times (not a lot, i know) with all successes. don't let it scare you.
to get into download mode just do the following.
1) pull battery then put it back in so the phone is completely off
2) disconnect usb from phone (but leave it connected to pc)
3) while holding down volume up and down buttons together, insert usb cable
that should take you straight to download mode.
then load up odin (check the bible for flash instructions -- pretty simple though). what i did was flash to JFD, then flashed to JI5. worked like a charm.
honestly, kies was a nightmare to get working and once it did, it messed up. odin has been simple and painless. one note, after flashing with odin, first boot may be slow. when i flashed JI6 OTA over JI6 leaked, it took about 10 minutes, at least, to boot.
good luck!

I know it's not helping you guys: but my Kies update (newest release) was smooth sailings after I did the registry fix.
I did none of the backups suggested (I tried so many times before so they were already done this time)
Let me know if you want details about my config.
Sent from my SGH-T959 using XDA App

Thanks for all the suggestions everyone, but I did make judicious use of the search button and google before I took it back to the store. I tried every single combination of button presses for every single mode, from every single forums posts I could find. No luck at all. The T-mob guys also had no luck, and it just so happened that a Samsung rep stopped by to see how the Vibrant was being received by the public and he couldn't get any recovery mode to work either. (He had no idea about when Froyo might be out though..... just in case you were wondering) Anyhow, I'm pretty sure that I for one believe in the myth of the hardware locked Vibrants.

[Q] Galaxy tab factory setting modified

I have a Sprint tab.
And I have been using it normally.(meaning I only browse and play games with it)
After two days it runs out of battery, upon reboot it restored to when I have used it for like 30 minutes (downloaded a few apps and synced my gmail acc).
I didn't pay much attention to it until I restarted it again, guess what, it restored again, exactly like I have used for 30 minutes or so.
I thought there was something wrong with the setting so I used factory reset. However, it DIDN'T work, it still restores to the 30 minutes state, with my account synced and everything...
Lately I tried to flash it but it fails at the end.. with the msg "Complete(Write) operation failed."
Now I have problem booting the machine and it's verging on being a brick...can someone help out??

Need more info before anyone will be able to try and help you:
What ROM are you currently on?
What ROM are you trying to flash to?
Are you trying to flash with Odin or Hemidal?
How did you setup the flash (eg. re-partition or not etc)
What state is the Tab in now?

bdl1969 said:
Need more info before anyone will be able to try and help you:
What ROM are you currently on?
What ROM are you trying to flash to?
Are you trying to flash with Odin or Hemidal?
How did you setup the flash (eg. re-partition or not etc)
What state is the Tab in now?
Click to expand...
Click to collapse
sry 4 not being clear...
To your questions:
I'm not sure what ROM because it keeps failing so I tried almost all ROMs, even GSM ones... I flashed with Odin with re-partition and now I just want to get it back to normal
I can use the tab right now but there're lots of errors coming up and if I try to reboot, it goes back to the 30 minutes state...
not sure that clarifies things or not...
In essence, I guess some of the contents are locked and can't be replaced by flashing

You should give this a try if you haven't already. A lot of progress has been made on the sprint ROM since you stated this thread.
http://forum.xda-developers.com/showthread.php?t=869819

linuxkidd said:
You should give this a try if you haven't already. A lot of prophetess progress has been made on the sprint ROM since you stated this thread.
http://forum.xda-developers.com/showthread.php?t=869819
Click to expand...
Click to collapse
I did and the problem persists.
I'm officially done with the tab and hope Samsung will repair it for me.

Sorry to dig up an old thread.
Long time lurker of the forums first time poster.
I bought the Sprint tab while over in the States for Christmas and it has been running fine since then.
But 2 weeks ago i started gettting multiple fc's and battery was draining very quickly.
Since then i have tried factory resets on multiple occasions and flashing quite a few different ROMS all to no avail.
Did you end up getting anywhere with this issue at all?
I live in Australia and it is going to be a PITA to get this fixed through warranty with Samsung.

Please help me: Corrupt TMO Tab

Hello,
Please Help!! My stock (firmware but rooted) TMO Tab started locking up and then progressed into constant reboots, lockups and semi hard resets (I lose all screens and they are back to stock, email accounts are gone in stock client, but apps are still there and a lot of other information is still there like wifi, bluetooth setting/devices etc.) Also, sometimes, the device hangs on the Samsung logo on boot up and I have to power down holding the button for 10 seconds and then turn back on..
It is almost like I got a virus. I did a hard reset the other night, went to bed with about 80% battery and it was completely dead in the morning. Last night went to bed with 91% and it was dead in the AM. Something is wrong and draining my battery.
Tmo is not standing behind their product because I bought it without a contract and said Samsung would either refund me or send me a new one(which I knew it couldn't be right), and it wasn't. They said send it in for 10-14 days and they will send me a working model.
So given all the problems I am having which seem to be software related, which software should I install? Something I won't have problems with or will still allow me to accept future Tmo updates if needed or wanted.
Also I am upset over the email limit(one month unlike the VZ version etc) on the stock email client so a Euro version would be fine if it had that feature and I also am not using the Tmo network so a disabled 3G network for data is not a problem.
Thanks for your help and suggestions.
Best,
BC

Please help me...
Update: My Tab was stuck on the Samsung logo for the longest time this morning(like 3 hours). I did the volume up/power button and wiped but still was stuck. It finally booted up but I am sure it is going to lock up and I will have to go through the same thing hoping to get it to boot up.
What could've caused it? What should I do while i have it on? Should I update to the Euro software and if so, which one? There are so many choices and not sure which one to do. Also, would I be able to go back to the stock tmobile s/w if I can return it for a replacement?
One thing that i noticed in the apps is a folder called error 1.0.0 but I cannot uninstall it. Is this normal and does anyone else have it? The other thing is that I still have the same memory available as when I had all my apps, email etc in it. Like it didn't really erase everything.
Please help and point me in the right direction. I have been scouring the net for 4 hours now and I don't know which way to go.
Thank you,
BC

Perhaps you poked around in the files system and accidently removed something? I would go to the Roto Stock firmware package thread, and flash that to repair a corrupt file system. Only a guess on my part, but it won't do any harm.

Well I suppose but I don't recall messing around with anything. I was hoping that while I had to change or repair my software, I should put the best on that there is to offer.
What software do you use or recommend?
Thanks for the reply! This is driving me crazy! I have had to turn off and back on at least 15 times today trying to get it to work amd habe wiped like 5 times.
Do you think I should just try and get a replacement from tmobile?
Thanks,
Brian

Woah, slow down partner. Make a Titanium Backup to the external sd card then remove it. Flash Rotohammers stock T Mobile firmware. Reroot with SuperOneCLick. Reinsert the external SD and reinstate your apps with Titanium. If things are still wonky after that then it's probably a hardware problem.
EDIT: I'd flash using Odin 1.7. It's just easier than Heimdall to me. Personal preference I suppose.

halftonehero said:
Woah, slow down partner. Make a Titanium Backup to the external sd card then remove it. Flash Rotohammers stock T Mobile firmware. Reroot with SuperOneCLick. Reinsert the external SD and reinstate your apps with Titanium. If things are still wonky after that then it's probably a hardware problem.
EDIT: I'd flash using Odin 1.7. It's just easier than Heimdall to me. Personal preference I suppose.
Click to expand...
Click to collapse
I did the backup and reinstalled after one of the wipes but it keeps locking up and not booting up. I haven't had it on 1 time successfully yet today and it past 10PM...
The main reason I would like a different firmware is because I want the full functionality of the email client like in some of the other tabs and android devices.
Tmobile and i don't know who else (I read ATT) crippled the email and it doesn't have the option to have all email on the device which is great for short trips without the laptop.
What about some of Roto's other firmwares? Like i said previously, I am not using Tmobiles data or service so it doesn't matter. I also read that the browser and overall was really smooth.
Is it ok to root with z4root? I have the app on my sd card and that is how i've done it before.
Thanks for your suggestions and i appreciate all feedback. I have to do something because this device has become a paperweight.
Thank you,
BC

bconfer said:
I did the backup and reinstalled after one of the wipes but it keeps locking up and not booting up. I haven't had it on 1 time successfully yet today and it past 10PM...
The main reason I would like a different firmware is because I want the full functionality of the email client like in some of the other tabs and android devices.
Tmobile and i don't know who else (I read ATT) crippled the email and it doesn't have the option to have all email on the device which is great for short trips without the laptop.
What about some of Roto's other firmwares? Like i said previously, I am not using Tmobiles data or service so it doesn't matter. I also read that the browser and overall was really smooth.
Is it ok to root with z4root? I have the app on my sd card and that is how i've done it before.
Thanks for your suggestions and i appreciate all feedback. I have to do something because this device has become a paperweight.
Thank you,
BC
Click to expand...
Click to collapse
hey dude you sound nervous as hell man, relax. as long as you can get your phone in to download mode. you will be ok. flash rotos tmobile stock firmware. if it works hooray! if not flash rotos jme 4

Still out of commission
I am not nervous, just annoyed as hell.
I flashed the stock tmobile firmware, booted it up and it crashed after about 10 minutes and I am back stuck on the samsung logo. I haven't been able to get it to boot up for about 5-6 days. I have wiped many times and no dice.
Should I wipe cache partition? Try the JME software?
Thanks for your help!
BC

[Q] eLocity just quit...won't boot up

I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
My a7 was running well for about a week since it quit...but today when I booted up device, it failed to recognize sd card...same card used for updating to mod 1.4...same card I've been using to listen to my music, etc...but now won't recognize...I've tried two different micro sdhc cards..formatted, reformatted, but device continues to display mount sd card...all else works fine! Does anyone have any new ideas? I can't even reinstall mod since a7 can't read my cards. Thanks for any input that would be helpful. I understand these issues are ongoing for many out there...what to do?

deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Mine has hung on a black screen on me. Seemed that it didn't fully come out of sleep mode.
I was able to recover by holding the power button for 15 seconds to hard power down. No data loss.

deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Exact same thing happened to me this morning. Tried to reset - not happening. Hard powered down. Don't have time to try anything else right now. I'm new to the forums and new to android. Wish me luck! I've been loving my A7, and much appreciation to Dexter and all the other knowledgeable hackers/modders/posters.

hey the same thing happened 2 me twice. Once the first day after i got it, since i had only had it for 1 day i wiped it reinstalled dexter's mod 1.41 and it worked. First app i installed was backup root. Now, a week later the exact same thing is happening. This time i dont want to wipe it because of all of the apps i have installed, games ive played etc. Any ideas? Could we just try reinstalling dexter's md without wiping? Or wiping reinstalling and recover from a backup?
Also have you installed busybox? I had just installed it both times before it failed to turn on. Maybe its just coincidence but you never know..
-D
Thanks to anyone who can help! and also thanks Dexter for all your hard work as well as everyone else that has contributed to the elocity, im lovin it! (when it works )

success!!!!
I got it to work! I don't have a permanent fix but if it happens again just boot into recovery and reinstall the dexter's mod update 1.41 and it works again! No wiping required. This isn't a permanent fix but it will work until we find one
-Dylan

Hasn't happened to me (yet) but I didn't upgrade to the newest ROM. I'm still using 1.3and it has been very stable. Only issue I've had was when I tried to use Killswitch to go to sleep mode when the cover is shut (great idea) but it didn't work and froze all except the live wallpaper. Weird.
Good luck, guys.

in the event it does happen to you, you might want to check out my apx thread for reflashing the factory firmware if you can't get your tablet unstuck. theres alternatives if you don't want to get stuck again.

The method you outline seems so complex...way above my abilities, but makes me wish I had followed though on some early programming training opportunities. That was the road not travelled.

okantomi; while i wouldn't encourage others to follow thru with procedures they fear would cause more harm, i would mention that if you google up my nick you'll find i've been able to do much w/ android software and devices while not knowing anything about programming. if i can do it, anyone can. i just wanted some themes for my phone.
i'm just an android hobbyist by night (and when i get a chance during the day), and a computer tech by day. no programming expertise, but i can reasonably reverse engineer and port software and components using simple file managers like ztreewin(trialware).
don't be mistaken that the folks out there providing you solutions necessarily know anything about programming or software development. just how to chef up files at different levels. i understand this doesn't go for everybody.

Thanks for the encouragement. I'm impressed with what you've been able to do. It is also nice to read upbeat comments about the A7. There is something sort of special about a device that you really almost have to build yourself... putting so much into it... biting your fingernails to nubs with each ROM flashing. You don't get as attached to any device that is 100 percent complete right out of the box, though of course there would be a lot less aggravation.

[Q] Help! bricked?

I bought a refurbished TF101 about 6 months ago. I rooted the device and tried various ROMs until I settled upon "Revolver 4 by Gnufabio | 4.1.1 Stable". Life was good, no random reboots, no sleep of death just great. I then installed a game called "Dead Trigger" that came up recently on the Play store. The game did not load, crashed without a FC message and so I uninstalled it promptly. Then I started getting video corruption on my Live Wallpaper (Blue Skies). Random reboots soon followed. Time to start over.
I used CWM and wiped the tablet from there (data, cache and Dalvik) and reinstalled Revolver. It did not work. I used the EasyFlasher tool to return my tablet to Stock using the Asus provided firmware from their website (.24). It seemed to work well, as I started over with my "new" tablet and synced to my account, etc, etc, etc. But now I can't use it without it rebooting every 30secs to 1min. It will go into a Sleep of Death on a random basis also. I have not installed any programs on it, I tried not allowing a restore of my Google settings and cannot for the life of me figure out what is going on.
I am unaware of the SBK version, as their is no indication on the tablet of its serial. What vital step am I missing here to revive this tablet? Any help would be appreciated.
Thanks
StevieJake

steviejake said:
I bought a refurbished TF101 about 6 months ago. I rooted the device and tried various ROMs until I settled upon "Revolver 4 by Gnufabio | 4.1.1 Stable". Life was good, no random reboots, no sleep of death just great. I then installed a game called "Dead Trigger" that came up recently on the Play store. The game did not load, crashed without a FC message and so I uninstalled it promptly. Then I started getting video corruption on my Live Wallpaper (Blue Skies). Random reboots soon followed. Time to start over.
I used CWM and wiped the tablet from there (data, cache and Dalvik) and reinstalled Revolver. It did not work. I used the EasyFlasher tool to return my tablet to Stock using the Asus provided firmware from their website (.24). It seemed to work well, as I started over with my "new" tablet and synced to my account, etc, etc, etc. But now I can't use it without it rebooting every 30secs to 1min. It will go into a Sleep of Death on a random basis also. I have not installed any programs on it, I tried not allowing a restore of my Google settings and cannot for the life of me figure out what is going on.
I am unaware of the SBK version, as their is no indication on the tablet of its serial. What vital step am I missing here to revive this tablet? Any help would be appreciated.
Thanks
StevieJake
Click to expand...
Click to collapse
The RR and SoD come standard with asus stock FW for most people, there is a new .27 update you could try that apparently fixes things, but it made things worse for me
The serial number is generally on a sticker next to the charger port of the tablet half, B4O > B60 and some B7O are SBK1, after that are SBK2
If you are SBK1 you can use NVFLASH to clean install the OS
I decided on Stock FW Rooted and CWM with PERI, then Guevors Kernel
So far so good, stable for a couple days now

Thanks for the quick reply. I did try the .27 update OTA update after getting back to Stock. No help.
The sticker in question is missing. Unknown SBK. I used EasyFlasher using SBK Ver1 and it worked to install the Stock .24 OS fine.
I will give the Stock FW Rooted a shot and see if that works
StevieJake

steviejake said:
Thanks for the quick reply. I did try the .27 update OTA update after getting back to Stock. No help.
The sticker in question is missing. Unknown SBK. I used EasyFlasher using SBK Ver1 and it worked to install the Stock .24 OS fine.
I will give the Stock FW Rooted a shot and see if that works
StevieJake
Click to expand...
Click to collapse
If the flash worked with sbkv1, then more than likely the unit is sbkv1. Otherwise, it shouldn't have worked at all . As the other poster said, RR and SoD is pretty common with the stock Asus firmware for some people -- you might try returning to Revolver now that you've gone back to stock, and start on Revolver again with a clean slate.
I am also running the same setup as the previous poster, stock .27, rooted with guevor's kernel. Been that way for only a day right now, so I can't say much about it yet.

Okay, so here is what I have done. I first used NvFlash to flash Stock .24 successfully. I then extracted the ASUS .24 firmware file (zip only) to the MicroSD card which the system took as an update and installed over my good work. It works, albeit with reboots still. I at least got it working and will try some more ROMs (Stock .27 first) with the suggested kernel. I just wish I could get back to the stable Revolver I had earlier.
Thanks for the help and suggestions.
StevieJake

steviejake said:
Okay, so here is what I have done. I first used NvFlash to flash Stock .24 successfully. I then extracted the ASUS .24 firmware file (zip only) to the MicroSD card which the system took as an update and installed over my good work. It works, albeit with reboots still. I at least got it working and will try some more ROMs (Stock .27 first) with the suggested kernel. I just wish I could get back to the stable Revolver I had earlier.
Thanks for the help and suggestions.
StevieJake
Click to expand...
Click to collapse
If you used NVFLASH to get back to stock, you could have just let the FOTA update you to .27
Then you can root and so on after that
NVFLASH returns the tablet to factory settings, ie. as it was when you unwrapped it on day 1

Not good. My tablet seems to be in an internal storage hell. Every Rom I try to install will crash with moderate use after booting. I have tried NvFlash, EasyFlash, Wolfs Ultimate flash and downgrade, every variation of stock HoneyComb and ICS I can find. I cannot keep this thing stable beyond 5 minutes of use. I have tried multiple factory resets and wipes, run "Superwipe Full" multiple times and nothing seems to work. What can I do to recover this tablet before I just give up and send to ASUS (god help me) for assistance? Any help would be appreciated
Thanks StevieJ

Ouch. Sorry to hear about your troubles. Horror stories like this have prevented me from diving into the root and custom rom scene with my one and only tab. [I am leaning towards a Nexus 7 when it comes out, and will perhaps root etc when I get that. I feel like it's a safer endeavour with a non-locked bootloader]
I'm interested in finding out what may be causing all this, so I'll be subscribing to this thread. Sorry I can't provide anything more than good luck to you.
Sent from my Transformer TF101

Ouch is right! I have rooted every Android device I have ever owned and this the first I have ever had this much trouble with. I just wish I could say I did "X" to cause it to happen. Oh well, maybe somebody knows something I have overlooked.
Note: I have Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8) running fine on the rom and it reboots into recovery okay.
StevieJake

steviejake said:
Ouch is right! I have rooted every Android device I have ever owned and this the first I have ever had this much trouble with. I just wish I could say I did "X" to cause it to happen. Oh well, maybe somebody knows something I have overlooked.
Note: I have Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8) running fine on the rom and it reboots into recovery okay.
StevieJake
Click to expand...
Click to collapse
Have you tried running it without the WIFI on? I went to my folks place with mine and it rebooted all the time as soon as it started up. It turned out to be a WIFI issue with the Dynalink router my parents were running.
Cheers, Matt.

hairy1 said:
Have you tried running it without the WIFI on? I went to my folks place with mine and it rebooted all the time as soon as it started up. It turned out to be a WIFI issue with the Dynalink router my parents were running.
Cheers, Matt.
Click to expand...
Click to collapse
Funny you should ask that. I just NvFlashed 9.2.1.24 and was using the tab with no WiFi, no account information and everything worked just fine. I then enabled WiFi to see what would happen and it still worked, but I had not logged in with any account information yet. It still worked fine, as I was able to surf the web with no problems. I then tried to add my account information and started getting crashes using the Play Store, syncing my accounts, etc. It seems to be linked to updating account information and not just WiFi. I will investigate further
Thanks
StevieJake

Adding an account, even a new account, will bring down the tablet. It reboots until it is only a dark screen that requires APX mode (VolUp +Pwr) to rebuild the tablet. I can get into recovery and also factory reset mode (VolDwn + Pwr), but that is it. I'm so confused

I found a CWM backup I had from back in March. It restored fine, but still had problems that resulted in multiple crashes and eventual death again. Oh Bother!!
StevieJake

Fixed it!
Here is what I did. I was always to get the tablet into APX mode (Vol Up + Pwr) so I NvFlashed 9.2.1.24 from this site:
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/. I did this 5 times, never letting the tablet fully reboot after I got the "success" message upon completion. I then did a data wipe (Vol Dwn +Pwr, then select Wipe Data and then Vol Up, Vol Up) 5 times. I then used the same NvFlash 5 more times and let the tablet fully reboot and entered my Google credentials. I had prepared a MicroSD card with the zip file extracted from the ASUS site that contained the latest firmware (.27) and placed in the root directory of the MicroSD card. The tablet recognized it as a system upgrade and installed the firmware grade with no problems. The tablet rebooted fine and showed the installed firmware. I then did a data wipe as described above 5 more times and then let the tablet reboot fully and once again entered my Google credentials. The tablet now runs all programs without faults, has no video artifacts on the live wallpaper I use (Blue Skies) and is running just great. I am able to update all apps with out errors from the Play Store which was also an issue.
I hope this helps someone to get their tablet back, as I used all the resources on this forum to bring this wacky method to restore my tablet. Thanks to all you unnamed posters for your help
StevieJake

I wouldn't expect flashing the same thing numerous times to have any more effect than the first flash, but if that's what it took for your tab to be re-born, so be it!
Congrats on the fix.
Sent from my Transformer TF101

Not so fast!
Although the tablet did last longer (almost 2 days), it ultimately failed again to an unbootable state. Its back to the drawing board again.........
StevieJake
rootblock said:
I wouldn't expect flashing the same thing numerous times to have any more effect than the first flash, but if that's what it took for your tab to be re-born, so be it!
Congrats on the fix.
Sent from my Transformer TF101
Click to expand...
Click to collapse

It may just be giving up, electronics are stupid sometimes and fail for no reason. I had a brand new HDD that worked for two days, I left the computer off for three weeks and when I turned it back on the HDD wouldn't even spin up :-/ Good luck buddy.

Okay, I'm done. Just got my RMA and am sending this puppy in. Thanks for all the help, I will try to post the results later when I get it back. Glad I made the impulse purchase for the Nexus 7, as I will not be totally without a tablet.
Thanks for all the help again
StevieJake

RMA and back from the Dead!
Well I got it back from ASUS after the RMA. It had a short visit in Texas, was returned promptly and appears to function normally. I never received any feedback from ASUS on receiving the tablet, what was wrong with it, what they did to it or when they shipped it. But its fixed. Running .27 latest firmware and seems to handle everything I can throw at it.
They did a bang up job so far and I am more than happy with their service.
StevieJake