Related
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
My apologies, as I wasn't sure where to post this.
For a long time now I've been running CM7 both the nightlies and the weeklys with no issues. Yesterday I decided I would try Neutrino ROM and installed GT 2.5. After that I noticed I had no data connection so I attempted to patch the ROM using Notorious's recommendations to no avail so I installed 2.2 and the Google addons, Sync, etc..
All was working great, however everyone said 2.5 was better in the forums so I installed it again today and attempted to patch as explained and this time was successful. I had data connection again and all was well. About an hour later I went to use my phone and it was completely black.
I attempted to power it up and nothing happened. I finally had to pull the battery and was able to get it to boot up properly, however my data connection was gone again. I ran the sysctl -p command in terminal again and rebooted it to no avail. I finally decided to go back to 2.2 which worked properly last night, however after installing from the zip and the addon zips it went to the 'Dual Core' screen and then rebooted back to the 'Dual Core' screen and keeps doing that.
I attempted to go into Recovery Mode, however when it says 'Entering Recovery Mode' it just goes black and I can't power it back on. I then have to reseat the battery before I can get it to work.
I guess at this point, is there anything I can do to get my phone back? I've seen the hard brick messages and I don't have that (yet), but I am not sure, because I apparently can't get that far. Thanks for any help you can provide.
-Dave
Sounds like a hardware problem to me. I recommend taking it to a service center ( for me ATT has one I use.) and sometimes they can boot it up. Or they can maybe give you ideas.
Just to confirm you can't boot anything right??
Sent from my Atrix with XDA Premium App
Thanks for the response. I was unable to boot into Android Recovery, however I hadn't tried the others. After numerous searches I found information on how to use moto-fastboot to install RomRacer's Recovery image and after doing that I was able to get into Recovery (phew!). I did a complete wipe on the phone (Dalvik, system, etc) and installed Neutrino 2.2 with Lite gapps, United States (GPS), Sync, and Gtalk (for video) and shockingly it finally booted into the rom. I think at this point I'll leave it alone after restoring my apps via Titanium Backup.
My phone is now working again. Hopefully I can keep it that way.
JeRrYFaR said:
Thanks for the response. I was unable to boot into Android Recovery, however I hadn't tried the others. After numerous searches I found information on how to use moto-fastboot to install RomRacer's Recovery image and after doing that I was able to get into Recovery (phew!). I did a complete wipe on the phone (Dalvik, system, etc) and installed Neutrino 2.2 with Lite gapps, United States (GPS), Sync, and Gtalk (for video) and shockingly it finally booted into the rom. I think at this point I'll leave it alone after restoring my apps via Titanium Backup.
My phone is now working again. Hopefully I can keep it that way.
Click to expand...
Click to collapse
Awesome good to hear. I would change the title or at least add, solved problem
Sent from my Atrix with XDA Premium App
Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP
EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!
Hey guys. I'm trying to figure out what's going wrong with my Transformer. I'm not experienced with Android development/ROM's so please bare with me.
Rooted my first Android device about a month ago. Made a stupid mistake placing the ROM I was planning to use on the external SD card & didn't backup the install I wiped. Recovered with an official Asus ROM & after about two hours fiddling around I managed to root & load my first ROM (Revolver, whoot!). Very pleased with myself!
Have been using the Revolver ROM for a month without any problems. No deep sleep etc, everything worked perfectly. Using the latest version of Clockworkmod, also no issues so far. Strange thing is that since last monday everytime I (re)boot the device it loads CWM instead of the Android OS. I can get back into Android bij holding volume down during boot & choose to cold boot. Not a big issue but very annoying & can't seem to find the fix.
Searched Google & XDA for a solution. Updated Revolver to 1.3.1 beta, also found the repack by Koush for CWM. Tried fixing permissions, clearing cache, clearing dalvik, wiping & starting over, etc. Everything I tried so far does not fix the CWM-loop I seem to be stuck in.
Would really appreciate some help, I'm probably looking in the wrong direction here. Thanks in advance.
Found something
Finally got out of the CWM loop, found a solution here: http://forum.xda-developers.com/showthread.php?t=1622814&page=2
Strange thing is that after I flashed it with the fix CWM changed to the touch mod I recently installed but never seemed to work. If I understand correctly the fix only deleted the first few lines in the config where the boot in recovery flag should be.
Afterwards I factory wiped the unit & flashed it with a clean ROM. Currently re-installing my apps. I do not have a good feeling on this, tablet seems sluggish last couple of days & I can hear a soft click when the unit reboots. Same sort of click a laptop hdd would make.
Think it's dying on me...
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