Related
So I hd just installed tiamat 1.4.4 on my WIFI XOOM and everything worked great until I did the overclocking to 1.7..it started restarting all the time. at a certain point I couldn't get back to my homescreen. So I preceded to do all the things we tend to do in this situation. Factory reset/reinstall 1.4.3..1.4.2/ etc. Nothing seems to be able to fix this bootloop issue. I can use fastboot commands...and while it bootloops I can do adb commands. Not sure what else I can do..any suggestions?
Look at the Tiamat thread in the Development section. Go back several pages to yesterday afternoon. Several users had the same problem, and found a couple of solutions.
Sent from my Xoom using Tapatalk
nope
Yeah, I did everything on that list and nothing. I have even started to try to go back to stock 3.1 from here
http://forum.xda-developers.com/showthread.php?t=1080963
but I can't flash the recovery image and the userdata image. I get a command write failed<unknown error>
Well I managed to get back to stock 3.0.1...sadly...but it wasn't easy. Fastboot kept yelling at me every time I wanted to flash a new image. I think I'll stick to 1.6 GHZ or at least something that won't get set on boot next time. thanks anyway for the help.
From what I have seen, you want to make sure that "Apply at Boot" is not selected until you have established a stable overclock speed.
Also if you change kernels it lets you get into setcpu to change your settings (down scale) so not really necessary to downgrade from 3.1, just a thought (out of experience btw),
Cheers.
Hi,
I have had a TF101 for over a year. However it was used by someone else who upgraded it 0.17 and when it came to be me was unreliable and would often randomly reboot and then get stuck on the 'EEEpad' screen (before it says ASUS etc).
I am new to Android (been on webOS for a few years) so rooting etc is new ground for me, but I am pretty technical. Had lots of webOS patches and overclocking installed.
I 'upgraded' to 0.24 and then started reading as much as I can on this site after the reboots remained. I now realise I made two fundamental mistakes
1) Going to 0.24 at all seems to be a no-no from what I'v read.
2) I didn't do a clean restart before upgrading.
I'm not too worried about staying with stock but I do need the thing not to re-boot as often (15 times yesterday !!), so I am wondering.
1) Is 0.24 on a factory reset machine better for rebooting ? If so how do I get back to that state given that I have 0.24 already so can't reset and then re-install 0.24 (as I think I should have) ?
2) Is the only way to make it reliable to go for a customised ROM/Kernel/Bootloader etc ?
3) If (2) is true and I need a different ROM/kernel etc which is the most reliable ?
I know I need to do the downgrade, root, clockworkmod etc but can probably handle that from other threads.
Many thanks for anyone taking the time to respond.
1: A factory reset *May* help, but there's problems with official ICS anyway.. I haven't tried stock ICS and have no intention of trying it with all the horrid reports I read.
2: I would say this is your best option, put a ROM on, you won't regret it.
3: You will need to flash a ROM, boot it once, then wipe caches again and flash a kernel. As for kernel IMO your best choice is Guevor's kernel, (I'm using v20.6 and it's perfect.) As far as ROM I recommend ARHD or Revolver if you like stock look, and Megatron or AOKP if you like AOSP based roms. (its all preference here)
15 reboots in one day? Have you tried a factory reset yet? That sounds excessive.
But I have zero problems with ARHD 3.4 and Guevors kernel.
As the 2 previous posters suggest - I think a factory reset could possibly help.
If not then I would root, and install a custom ROM. I'm using Revolver and stock kernel with zero RR or SOD. I tried Guevor's kernel and it just didn't agree with my particular TF-101. I also tried ARHD and it worked great but I just prefer the aesthetics of Revolver. Good luck and I sure hope you get your reboot issues fixed soon.
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
rege0039 said:
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
Click to expand...
Click to collapse
As you have had the unit over a year --> old serial# --> it has to be nvflash-able. So you have an option for an easy one-step installation.
Erm, OK - now I am a bit lost !
I want a rooted machine, Clockwork mod and a chance to try custom roms and kernels.
I seem to be able to find instructions for one but not the others, some want to put back stock rom but I am don't want that.
Sorry to be thick, and maybe I'm looking in a panic and getting lost but is there some instructions to follow to take it from 0.24 to being rooted and able to load custom roms. If I get to Clockwork mod I know how to use that to flash etc as I had it on my touchpad before I want completely to Android.
nv-flasable - what does that mean ? Can I check my serial number to know I can do it ? Stickers seems to have come off so not sure I know serial
Sorry for sounding confused and not looking enough - I really have tried but can't seem to get instructions that go from where I am to where I need to be !!!
Thanks again.
NvFlash
NvFlash is a utility that older tabs (With Sbkv1) can use to easily flash a recovery on the system. ASUS has basically two passkeys for the TF101 to get into APX mode, Sbkv1, and Sbkv2. Sbkv1 is the passkey everyone has, and Sbkv2 is currently unknown/locked. What Sbk you have is based on the serial number of your tablet (you can look at the box if you still have it, or find the stickers, also when did you purchase the tab, if it was before July 2011 then you for sure have Sbkv1, if not it may be Sbkv2) If your serial number starts with B60 or below (B50 B40 etc...) it has Sbkv1, if it has B70 or higher, it has Sbkv2. Find out what Sbk you have (it should be version one) then download NvFlash from Rayman's thread. Search nvflash unbricking released in the development forum. Once you have that get an NvFlashable recovery (I recommend Rouge XM touch recovery 1.5, since it reads from internal and external memory, again search in development.) Boot your tablet into APX mode and connect to your computer (Turn off, hold Volume-UP and power.) Install the driver, then follow instructions from NvFlash thread to flash the new recovery. Once you have this, you can place a ROM on your tab (All roms are pre-rooted, no need to install superuser) boot into your new CWM recovery with Power + Volume-DOWN, then press Volume-Up after a few seconds. Wipe data/factory reset, wipe cache, wipe Dalvik-cache, install zip from... find your ROM.zip (don't extract it) and install! Then reboot and let it install, after booting once, you can go back into CWM recovery to install a kernel.zip that you also place on your tab (I recommend Guevor's kernel, make sure you wipe cache and dalvik-cache again.) Then you're all set!
Any other Q's?
Ok. I think I follow all that. Many, many thanks.
I will go to work tomorow and look for the box, but I'm pretty sure it was bought before July 2011.
Need to do something, sure it's cos I am now counting but today held the record at 29 reboots ! Four within 8 minutes at one point.
I think I will go Android Revolution and the kernel you mentioned.
Would be great to bo rooted as I have Titanium license as well.
Thanks again. webOS forums were always good, XDA proving so as well.
Nvflash was just released for Sbkv2, so just use NvFlash, it's easiest good luck!
Thanks for following this up with the latest news !
As far as I can see the wheelie setup is for LINUX only ?
I'm on Windows 7, I could set it up as a dual boot but am complete newbie at Linux !
It's not that bad to set up, just download virtualbox from Oracle, then an ubuntu.iso installation, and run it as a virtual machine within windows. Easier than dual boot. It isn't too hard to set up, essentially download and extract.
So ...
Good news is got it rooted, clockworkmod installed (using the Rogue version that was suggested) and then went installed Android Revolution latest version. Did all the required resets, dalvik and cache wipes etc.
Great I, thought, until ...
All day to day it has rebooted frequently even though I installed no other s/w - just what comes with Android Revolution. It seems to more frequent when the device has powered down after a period of inactivity.
Is it now time to start thinking this is a h/w problem ?
Will a different custom ROM be worth a go or would a different kernel help (which I haven't tried yet) ? If so I wasn't sure which version of the suggested kernel (Guevors) I should go for as there seemed to a lot of them.
Once again, thanks for any and all time. NVFlash was a revelation and really not that hard once I had the drivers installed.
Have now installed v21 of the kernel and got CPU tuner to change minimum cpu speed, wasn't sure about voltages.
Is there a recommended way to set cpu speed, governors and voltages ?
At the point of thinking this will never be stable again. Not even getting 30 minutes without a random reboot.
Try version 17c of guevor's if 21 is giving you issues, and any Cm9 based build will have overclock change built in. I don't use overclock apps, they give me problems. Make sure you SuperWipe, then try reinstalling ARHD (or a aosp/aokp/etc rom) flash either 20.1version6 guevor or 17c and don't overclock (default it overclocks a bit to 1200). See if it is finally stable, if not you might have borked hardware :/
It's charging at the moment, after I night of rebooting I presume.
I've got the SuperWipe zip so I will run that (which I didn't before but did do a reset, cache and dalvik wipe) and then put Revolution on after that.
I looked at Megatrons ROM as well - any comments on its reliability ?
I've not noticed it only does it when the device has been left for a few minutes. If I keep using it and don't let it sleep then things seems OK.
Megatron is really stable, I've found. I like aosp better too.
Those who experience rr or SoD can downgrade via nvflash to Any custom rom , prime 1.4 for example, and then upgrade by way of cwm to an ics aopk to make those problems disappear?
EDIT: megatron is very stable and have an awesome battery life. And the pop ups telling us there's a new update is great too
Sent from my Transformer TF101 using XDA Premium HD app
Hi,
Have been away with unreliable internet access but am now back.
I'm starting to think there must be a h/w problem as nothing seems to make the thing stop rebooting. The only pattern I can see is that if the device is being charged (either from the mains or by being plugged in to the keyboard) then it seems to stay up. Not sure if a certain battery level makes a difference.
I went through the whole SuperWipe clean and Revolution install, then put on the 17c kernel (At least I think I did About shows 2.6.39.4-g8fc25a9-dirty for the kernel, is that right ?) and am still have lots of reboots.
Tried Megatron with the same kernel and couldn't get wifi but still got a couple of reboots.
Any other suggestions ?
Or does anyone know a way of getting repairs done on this in the UK ?
You'll want to RMA to ASUS if nothing works :/
I would have posted this in the Sensation Android development area, but I don't have sufficient privileges to do so.
I no longer have WiFi.
I am using the 4.1.2 CM Kang, and I originally had WiFi working with that ROM, but it stopped working about a weeks ago, and I can't get it to come back.
If I watch the Wifi on/off toggle, I can see it blink white for a split second then return to grayed out about once every 5-10 seconds.
I've checked the WiFi settings, and the only thing that looks peculiar is that the region code under Advanced says "Europe," but when I try to change that, it just reverts.
I have tried a factory data reset,re-flash of the ROM, and installing newer versions of the ROM with no luck.
Does anyone have any suggestions?
tried this ?
WiFi will not turn on
ganeshp said:
tried this ?
Click to expand...
Click to collapse
I tried to install WiFix Manager, and I followed the directions closely, but WiFi still will not turn on.
The country code always reverts back to Europe in the Advanced WiFi Settings.
I'm on T-Mobile US, running AOKP aokp_pyramid_unofficial_Oct-19-12.zip; a JB ROM; 4.1.2
I previously tried the CM10 Kang for the HTC Sensation, but switched ROMs to make sure that it wasn't issue with the ROM.
To be clear, my problem is not that the WiFi radio never locks to a particular signal, it's that the WiFi radio won't even turn on.
When I go to WiFi settings it just says, "Turning on WiFi...," and never actually turns on.
My best guess was that it had something to do with the WiFi country code, but that's really just a stab in the dark; open to suggestions.
Thanks
bump
Surely, there's someone out there that can help?
kosstheory said:
Surely, there's someone out there that can help?
Click to expand...
Click to collapse
In order of easiest and quickest to longest time it will take to do each one...
Install the latest version of the ROM (10/23) overtop of your existing rom (5 minutes)
If that doesn't work...
Do a full wipe and install a fresh copy of the latest version. (15 minutes, with Nandroid backup)
If that doesn't work...
Format your SD card (save all the contents to your computer first) (40 minutes between copying every to the computer and back to the SD card)
NON ROM RELATED OPTION IF YOU ARE S-OFF
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops. (5 minutes, but a little more involved)
My guess is that the full wipe and fresh install is the most likely to work the first time.
Skipjacks said:
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops.
Click to expand...
Click to collapse
is there a sensation specific guide for this procedure?
Still perplexed
How do I know which kernel and radio combination should work best with my ROM. I switched out to AOKP to see if that was the problem, and I believe I'm using the 3.33 Kernel, but I don't know how to check to make sure it installed correctly.
Had the same problem as you but a full wipe and reflash would bring it back. Seems to be a CM10 problem since it happens with Bruce's and Paranoid roms. Try a Sense rom and see if wifi works.
Is OpenSense considered a "Sense ROM?"
http://forum.xda-developers.com/showthread.php?t=1926858
Try that rom, more stable and better performance than all the popular roms.
I had the same problem only option was another room Android_Revolution_HD-Sensation_6.8.0 (this is the rom)
so long, and thanks for all of the fish...
I figured it out.
I bought a Samsung Galaxy S III. WiFi is working again.
Thanks for all of the help!
wifi cm10
I have tried several CM10 roms. It is as you said about the region code. It reverts back to the original and doesnt save it on the settings
Even though editing db file doesn't work. Actually it changes the country code. I guess the ROM changes it during booting. Because while it boots you can see that the wifi is connecting first then goes off. I have tried several roms. DOnno what the problem is. probably JB both on cm10 and aokp
I had a MZ600 (yes, 3g only) which was running EOS 3 stingray build 150...... I want to now get it activated with verizon and they say they can do it, but for some reason it fails every time they try.
In attempt to fix the issue I have flashed the more approp eos 3 cdma stingray nightly, but have had the same issues....
What should I do next? Should I...
Do a data/system format and try the eos cdma stingray again? (would need quick refresher on this one, so I dont end up wiping TOO MUCH to still do the flashing through twrp)
Do a adb to some stock rom (would need help finding the correct files for this option)
Something else?
Thank you in advance for any advice you might have, but hurry.... ive got a itchy flashing finger.....
airboss78 said:
I had a MZ600 (yes, 3g only) which was running EOS 3 stingray build 150...... I want to now get it activated with verizon and they say they can do it, but for some reason it fails every time they try.
In attempt to fix the issue I have flashed the more approp eos 3 cdma stingray nightly, but have had the same issues....
What should I do next? Should I...
Do a data/system format and try the eos cdma stingray again? (would need quick refresher on this one, so I dont end up wiping TOO MUCH to still do the flashing through twrp)
Do a adb to some stock rom (would need help finding the correct files for this option)
Something else?
Thank you in advance for any advice you might have, but hurry.... ive got a itchy flashing finger.....
Click to expand...
Click to collapse
The radios probably need flashed to the ICS version http://goo.im/devs/teameos/radios/imm76l-radios-update.zip and you will need to use the latest Rogue recovery CWM Rogue Touch v1.5.0 to flash them (the rest of the recoveries will not error, but they will also not generally successfully flash the file.)
airesch said:
The radios probably need flashed to the ICS version http://goo.im/devs/teameos/radios/imm76l-radios-update.zip and you will need to use the latest Rogue recovery CWM Rogue Touch v1.5.0 to flash them (the rest of the recoveries will not error, but they will also not generally successfully flash the file.)
Click to expand...
Click to collapse
thank you!
.... did as you suggested and all went well .....
but then......
I called verizon and it still failed to activate...... uggggg....... now what?
I think that Im game for even going back to the stock verizon route...... just need to know how exactly to do even that......ive got way too many solutions rolling around in my head, I can no longer make sense of any of them though! Hand holding may be required here..... sorry
Rootzwiki links because Motorola has removed their old page and I don't remember where else to get them. You will need fastboot on your pc to do this and flashing the images will wipe everything off your Xoom, so copy/backup everything you want to save up onto your pc/external sd card before you do so. The fastboot commands are also listed in the link I posted.
Hi all,
I was given the TF700 by my grandma as she no longer used it and I've been trying to solve the issue of it being so sluggish etc, so I've managed to unlock the bootloader, flash a custom ROM however, since I tried to flash the KatKiss ROM, the WiFi refuses to work. Every ROM after that has had no WiFi either. I tried to flash back to stock, as was suggested to see if that would fix the WiFi issues, to see if that would help, however now it won't boot past the boot animation - no matter what ROM I try and use.
I'm refusing to give up on this guy as it has the potential to be an amazing tablet... Y'know, when I can actually get it to turn on.
I've checked and I'm on the latest bootloader (US_epad-10.6.1.14.10-20130601 - I'm hoping that's right?)
Does anybody have any suggestions? I can successfully boot into Kang TWRP and flash things via recovery, but I can't get any ROM to boot past the boot-animation. I don't want to get rid of the tablet, but I'm unsure of what to try next. As I can still get it powered on and into bootloader/TWRP, I figure there has to be some kind of hope. Have I missed off any details that may be needed?
If anyone could help me out, I'd be eternally grateful!
reterosexual said:
Hi all,
I was given the TF700 by my grandma as she no longer used it and I've been trying to solve the issue of it being so sluggish etc, so I've managed to unlock the bootloader, flash a custom ROM however, since I tried to flash the KatKiss ROM, the WiFi refuses to work. Every ROM after that has had no WiFi either. I tried to flash back to stock, as was suggested to see if that would fix the WiFi issues, to see if that would help, however now it won't boot past the boot animation - no matter what ROM I try and use.
I'm refusing to give up on this guy as it has the potential to be an amazing tablet... Y'know, when I can actually get it to turn on.
I've checked and I'm on the latest bootloader (US_epad-10.6.1.14.10-20130601 - I'm hoping that's right?)
Does anybody have any suggestions? I can successfully boot into Kang TWRP and flash things via recovery, but I can't get any ROM to boot past the boot-animation. I don't want to get rid of the tablet, but I'm unsure of what to try next. As I can still get it powered on and into bootloader/TWRP, I figure there has to be some kind of hope. Have I missed off any details that may be needed?
If anyone could help me out, I'd be eternally grateful!
Click to expand...
Click to collapse
It sounds as if you are not formatting properly between flashing roms.
Try that first: Wipe > Format data > type yes
let it finish, the process takes a good hour. Then convert /data to f2fs
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Flash the rom and gapps.
I bet it'll boot this time
berndblb said:
It sounds as if you are not formatting properly between flashing roms.
Try that first: Wipe > Format data > type yes
let it finish, the process takes a good hour. Then convert /data to f2fs
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Flash the rom and gapps.
I bet it'll boot this time
Click to expand...
Click to collapse
Thank you so much! I'd been formatting but maybe not properly.
I'll give it a go once it has some charge in it - it's been trying to boot for about 7 or so hours now. I'll report back with anything if it helps.
So, I've managed to get the tablet to boot - but I'm still stuck with no working WiFi. It just greys out and says disabled. Bluetooth seems to work, but, I can't even connect to my phone to use it's data connection via Bluetooth tethering. I managed to get it to boot on KatKiss 7.1 - any ideas on the WiFi issue? Is there a flashable zip to fix WiFi drivers?
reterosexual said:
So, I've managed to get the tablet to boot - but I'm still stuck with no working WiFi. It just greys out and says disabled. Bluetooth seems to work, but, I can't even connect to my phone to use it's data connection via Bluetooth tethering. I managed to get it to boot on KatKiss 7.1 - any ideas on the WiFi issue? Is there a flashable zip to fix WiFi drivers?
Click to expand...
Click to collapse
Nope, the rom should have everything you need. Don't know man - this is pretty unusual. You probably should flash it back to stock to have a point of reference.
If wifi still won't work on stock it's gotta be hardware.
Flash the stock blob in fastboot and then start from scratch:
https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
berndblb said:
Nope, the rom should have everything you need. Don't know man - this is pretty unusual. You probably should flash it back to stock to have a point of reference.
If wifi still won't work on stock it's gotta be hardware.
Flash the stock blob in fastboot and then start from scratch:
https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
Click to expand...
Click to collapse
Thanks for the link, but the official ASUS link in the post you've linked to is dead :/ I'll have a look after work tonight and see if I can find it anywhere else and whether I can get it working or not!
https://www.asus.com/us/supportonly/ASUS Transformer Pad Infinity TF700T/HelpDesk_BIOS/
I tried all of the above steps and re-flashed KatKiss to find that the WiFi still did not want to work, which resulted in not being able to get past the setup wizard. I'm not sure what to try next, but at least it was worth a shot. Thank you for your help!
Well - did wifi work on stock?
You know about this bug right? From the OP:
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
berndblb said:
Well - did wifi work on stock?
You know about this bug right? From the OP:
Note that current gapps setup wizard will crash as it is not fully compatible with android 7.1.2 (KatKiss >= 022)
unless you turn on wifi manually after the language selection in the initial setup.
(if you don't have a dock, use the extra wifi button in the navbar)
Click to expand...
Click to collapse
Just seen this! Yeah, the WiFi worked fine on stock, but any custom ROM I tried had the same issue, so I'm not 100% sure what caused it. I sold the tab on after flashing it back to stock, though.
Thank you for your help though!