It seems alot of people are getting confused with rooting of the phones, and what they need to do, and it mostly seems like people from other phones, and well the obviously new person. I just want to help with his, as some of the threads are getting and I can see it being tough to follow a 40 page thread.
It seems to me alot of the confusion seems to come from the fact of the lack of locked bootloader, along with using ODIN to flash. I'm quessing everyone from HTC phones is used to a multi step process in regards to flashing root, as you have to load a hacked bootloader, turn soff etc.
If you have a stock ed2 charge. All you need to do is run jt's root/voodoo/cwm kernel found here http://forum.xda-developers.com/showthread.php?t=1092114
ffd173 in post 108 has some nice instructions on it. http://forum.xda-developers.com/showpost.php?p=14080378&postcount=108
The stock rooted roms you are seeing are (root stock ed1, root stock ed2) you can consider a rooted basic backup. Do not use CWM either the one from jt's kernel, or rom manager for backup and restore until a recongized dev says its okay. Use titanium backup for your backups and restores. It has been recommended a few times to not even touch ROM Manager yet, based on the way it is written to work vs what is here and how it is written
***one thing to note is that if you install a kernel using the voodoo lag fix, you must disable it prior to flashing back to any sort of stock based kernal/rom or any non kernel with the lag fix.
I am semi new with this as well coming from HTC phones, and only having this for this being my 3rd day. If I missed something in here or made a mistake please let me know and I can adjust and maintain this....havent had much sleep for a while and its getting to me
***one thing to note is that the kernel has now the voodoo lag fix such as these stock roms, you have to disable to voodoo lag fix.
Not sure what youre saying here. Are you saying that you have to disable the voodoo lag fix to install root stock ed1 or ed2?
Updated it. My apologizes.
First time poster: sorry if this is covered someplace, but the forum is quite extensive, and I couldn't find this particular issue anywhere.
I own a Rogers Captivate which I rooted, kept on stock rogers 2.2 firmware, but upgraded the kernel to Onix 2.0.5. I discovered the ROM kitchen today, and thought I'd try 2.3.3 (I got XWJVH v3). I turned off my lagfix, did a factory reset, cleaned my caches and attempted to flash within CWM. I think the flash was only partially successful: I am able to get the phone to boot into android about 40% of the time.
What concerns me is that even though I have installed ROM Manager, and a CWM app came pre-installed with this ROM, I do not appear to have any recovery loader. When I try with quickboot or from my PC the phone just sits at the "I896" splashscreen. It may be worth noting that I attemped this with whatever stock kernel the Kitchen gave me, as well as two versions of Talon. Heimdall has been successful in flashing these alternate kernels for me, Odin doesn't seem to see the phone at all. I have many NANDROID backups, but if I can't get into recovery, I seem to be stuck!
During normal boot (and some unsuccessful recovery attempts) the phone goes into a mode in which the graphics are not displayed properly - I cannot describe this any better than being reminiscent of when an NES catridge was dirty and needed cleaning.
If someone could provide me with some advice, or point me towards a 2.1, 2.2, 2.3 ROM that I can flash on a Canadian GS within Heimdall, I'd appreciate it.
-T.J.
Give Serendipity 7 a try and don't look back.
http://forum.xda-developers.com/showthread.php?t=1107894
http://serendipity7.weebly.com/
Very easy install and a custom kitchen for all your add on needs.
Okay ... Don't laugh at me !! Have had the Charge since release date. This whole time I have been running stock rooted EE4 with CWM Voodoo Lagfix. I had to have a replacement phone sent to me as my CDMA radio died. Phone still worked on LTE radio. CDMA would be intermittent at best.
On to my question. I am planning to give GB a try and I am reading in threads about the toolbox and to access it via Term? I am assuming term is terminal function. This part is entirely new to me. Could someone point me to some term primers so I can research this?
Also, I have downloaded and extracted my Bloated_EG2__Gingerbread_ ODIN. Then I have
GummyCharged_GBE_2.0
GummyChargedGBE2.1
CWM_Recovery4008
I am assuming the EG2 includes CWM. If not, which will be easy enough to find out when I go to enter recovery, I will install the CWM I have downloaded. From what it appears to me, GBE_2.1 is an update to GBE_2.0 .... Thus I assume I need to install 2.0 followed by 2.1
Does this include voodoo lagfix? Or is that not needed when I up the phone to GB 2.3?
Just trying to sort this out and be informed before I start flashing this thing. The phone is stock out of the box EE4 as of right now.
Any help will be greatly appreciated.
Thanx In Advance,
Steve
Chopstix9 said:
Okay ... Don't laugh at me !! Have had the Charge since release date. This whole time I have been running stock rooted EE4 with CWM Voodoo Lagfix. I had to have a replacement phone sent to me as my CDMA radio died. Phone still worked on LTE radio. CDMA would be intermittent at best.
On to my question. I am planning to give GB a try and I am reading in threads about the toolbox and to access it via Term? I am assuming term is terminal function. This part is entirely new to me. Could someone point me to some term primers so I can research this?
Also, I have downloaded and extracted my Bloated_EG2__Gingerbread_ ODIN. Then I have
GummyCharged_GBE_2.0
GummyChargedGBE2.1
CWM_Recovery4008
I am assuming the EG2 includes CWM. If not, which will be easy enough to find out when I go to enter recovery, I will install the CWM I have downloaded. From what it appears to me, GBE_2.1 is an update to GBE_2.0 .... Thus I assume I need to install 2.0 followed by 2.1
Does this include voodoo lagfix? Or is that not needed when I up the phone to GB 2.3?
Just trying to sort this out and be informed before I start flashing this thing. The phone is stock out of the box EE4 as of right now.
Any help will be greatly appreciated.
Thanx In Advance,
Steve
Click to expand...
Click to collapse
EG2 is really old, you may want to go with a more recent GB leak like EP1Q/EP1W/EP3H... second no rom packages include CWM but are for the most part all rooted, CWM you will have to install with Odin after the rom then flash Gummy 2.0 and the 2.1 patch with a bootup between each rom flash to make sure it worked properly
edit: probably should've answered more questions Gummy 2.0 has a kernel with voodoo lagfix so it will enable after flashing the rom on first bootup, also the command terminal is fairly straightforward to use, I think the Gummy rom threads have a how-to in the OP on basic terminal commands... also as for your radio not working, it was probably a 4G sim issue as the CDMA and LTE radios are both controlled by the sim so if one doesn't work the other won't either, there may just not be as strong a CDMA signal so it seemed like it wasn't working
Great info thanx .... now when I go to update to 2.0, from the reading and even watching the video, I am going to delete all caches prior to flashing the 2.0 ... with the 2.1 just being a patch, can I just install it after verifying 2.0 works? Or should I delete the big 3 again before that one?
Chopstix9 said:
Great info thanx .... now when I go to update to 2.0, from the reading and even watching the video, I am going to delete all caches prior to flashing the 2.0 ... with the 2.1 just being a patch, can I just install it after verifying 2.0 works? Or should I delete the big 3 again before that one?
Click to expand...
Click to collapse
just cache and dalvik I think (might not even need that but I'd probably do it to be safe), don't delete data or it will wipe Gummy off and you'll have to reflash
Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!
No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App
You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup
I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?
All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.
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 :/