Hey ! I today had a problem with my transformer. I was on stock ics rooted rom and I wanted to give a try to the CM9 with cornerstone rom.
I made a nandroid backup before wiping everything. When it launched, I wanted to connect to internet as usual. But I encountered the problem wich is the topic. The wifi icon (I'm talking about the color, not the toggle button wich was stucked on OFF) was stucked between the OFF-ON step, you know when you click on it, the color change a bit before being lighted wich mean it's on. When I watched Wifi in parameters panel, it was stucked on : Wifi activation.
I waited some hours but nothing happened.
So I tried to come restore my last rom, so I performed a wipe (even if it is maybe useless) and then I backed up. But the problem remained on my back up!
Finally I installed the same rom as the nandroid backup on the back up and it worked.
I just posted this cause I did not find anything on google or xda, so I hope it will help someone a day.
I'm having this problem as well. I'm trying various combinations of flashing Revolver 1.3 and back to my NAND backup. So far, everything restores just fine but the WiFi is still an issue. I may have to try an ICS stock ROM then back to Revolver and so on. I'm sure one of those combinations will work.
Ironically, I used EOS Cornerstone and got back to my Revolver backup without issue but using the CM9 Cornerstone seemed to give me the problem. I'll post back if something works.
****************
Ok, I got WiFi working again without issue. After numerous attempts of using the Revolver 1.3 and 1.3.1 update, the only thing I did differently was install Revolver 1.3 ONLY. I didn't flash the 1.3.1. Upon bootup, I got the typical setup screens and sure enough WiFi was good and it picked up my Adhoc tether without issue and I connected successfully.
I then rebooted into recovery to restore my NAND backup. No issue at this time that I can tell.
I can't tell anyone for certain if this will work but if you are using your NAND backup of Revolver I would:
1. Boot into recovery
2. wipe data/cache
3. Install Revolver 1.3 only. Then reboot like normal.
4. Go through setup screens upon reboot and make sure Wifi works. If it does, don't restore settings and apps from Google, there is no point.
5. Reboot back into recovery and restore your NAND backup.
Hope this helps anyone else. I may shy away a bit from the Cornerstones until we can see some more WiFi stability on them.
Wifi Issue
I had the same issue, I had to flash the Full ICS Rom from asus then restore my nand backup. Seems like going from cm9 back to another rom breaks the wifi even after you wipe. Let me know if this fixes your problem.
Heres the link for the ASUS stock ICS Rom.
http://forum.xda-developers.com/showthread.php?t=1514658
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
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
Good morning.
After update from cm-13.0-20160723-NIGHTLY to cm-13.0-20160724 system and most of apps crashes. I waited for new build with hope that it will repair this problem, but today when I was trying to download update, I got message that Download manager app cannot download it, so I downloaded update to PC.*When*I was plugging my S4, I didn't get any answer that my S4 is plugged into PC! My S4 was only charging from PC. Okay. Then I tried send this .ZIP file from my PC to S4 via Bluetooth, but transfer failed! My next try was downloading update via Google Chrome. Unexpectedly it worked, but when I was looking for this .ZIP*file*to flash it in recovery, I didn't found it, but I*found an old build, which I downloaded a year ago, so finally I flashed it. System was rebooting for over a dozen minutes and nothing else, so I came back to cm-13.0-20160724, but now it totally f**ked up, because I can't reboot S4 to recovery! What the f**k is going now and how can I fix it?
Thanks a lot for any help.
Kubex52 said:
Good morning.
After update from cm-13.0-20160723-NIGHTLY to cm-13.0-20160724 system and most of apps crashes. I waited for new build with hope that it will repair this problem, but today when I was trying to download update, I got message that Download manager app cannot download it, so I downloaded update to PC.*When*I was plugging my S4, I didn't get any answer that my S4 is plugged into PC! My S4 was only charging from PC. Okay. Then I tried send this .ZIP file from my PC to S4 via Bluetooth, but transfer failed! My next try was downloading update via Google Chrome. Unexpectedly it worked, but when I was looking for this .ZIP*file*to flash it in recovery, I didn't found it, but I*found an old build, which I downloaded a year ago, so finally I flashed it. System was rebooting for over a dozen minutes and nothing else, so I came back to cm-13.0-20160724, but now it totally f**ked up, because I can't reboot S4 to recovery! What the f**k is going now and how can I fix it?
Thanks a lot for any help.
Click to expand...
Click to collapse
Fyi CM will be dead soon, so I hear. So don't expect too much from them in the near future.
You may always try to put your phone in download mode (3 button trick) and then flash latest custom recovery using the appropriate version of Odin. If it works for you, continue by powering your device off after flashing succesfully. Switch back on using 3 button trick to access recovery mode. While you at it, fully wipe the device (not usb otg). Don't root if prompted to. Then flash your choice of stock or custom rom.
Happy days!
Cm13 always bugy.use cm13 optimise build 20160618 from android original thread.I m using any bug.
Please be noted:
You're using bleeding-edge version of CyanogenMod. For the best experience and stability, use a stable build instead like Optimized CyanogenMod by JDCTeam for jfltexx or GearCM for i9500.
Sent from my ASUS_Z00A using XDA Labs