Related
I'm quickly finding the D2G is the least supported of the Droid devices and have the feeling I should have just bought the D2. It's been a bear trying to get information on this phone, let alone any decent ROMs that are working. That said I've got some issues with flashing backups, so here's the details.
Droid 2 Global
- CM7.1 (DROID2WE version) installed.
- Droid 2 Bootstrapper 1.0.0.5
- Clockwork Mod 5.0.2.3
First off, all the online documentation, including CM's site that CWM can be loaded by: "Hold the X key on the keyboard & the Power button until the device boots to the recovery." is incorrect. Doing so pulls up the PHONE recovery; the best way to get CWM to boot is to wait until the "M" logo comes up and the backlight on the screen turns off, then pressing and holding the power button for 5-10 seconds.
Now, I've tried both entering into recovery from ROM Manager, then creating a back up and rebooting into CWM recovery, then creating a backup. In both instances, the recovery will not restore; each and every time I've tried, I get this error: "Error while formatting /system". Keep in mind that I did NOT change the name of the backup (which I'm told can cause this error).
Supposedly, according to ROM Manager's page on the Market, the latest update was supposed to resolve the error/restore problem, but I've flashed 5.0.2.3 several times with no avail. I emailed Koush, but haven't received a response. To add to the issue, I haven't been able to get any other ROM to flash to the phone, like Liberty 3, for example, unless I flash SBF back to 2.4.330; it's almost like the phone doesn't like dealing with more than one ROM.
Anyone know what I'm doing wrong? I can't find anyone else with the same issues in a finite post and certainly no wikis to explain the matter. I have an OG Droid that doesn't have any of these problems so I assume this is related to the D2G and not because I'm doing something wrong.
**EDIT** Scroll to last post for the resolution.
D2G has a locked bootloader. The custom ROMs are made for a certain kernel. A GB-based ROM won't load on the 2.4.x base, and vice versa, a Froyo ROM won't start on the 4.5.x base.
To install CWM, you need to use Droid 2 Recovery Bootstrap from the Market. With stock ROMs booting into CWM is only possible by first booting into the OS, and then choosing Reboot Recovery in the Droid 2 Bootstrap Recovery app you installed before.
(I have never used ROM Manager because it's not really supposed to work well with the D2G.)
Also, it's worth noting that the “official” CM7.1 ROM is based on the Froyo kernel from 2.4.x firmware.
I've got the Droid 2 Recovery Bootstrap installed. But that still doesn't explain why all the videos and people I see online can switch in between ROMs on other phones, but it's so hard on the D2G, or that I can't get a backup to install properly.
I've read online that using the Droid 2 Recovery Bootstrap to reboot into recovery isn't advised; can anyone confirm?
It's not advised for CM7 and MIUI; those have their own recovery access methods, and CWM comes preinstalled. In CM7, you have to long press the power button, tap “Reboot”, and choose “Recovery” from the reboot menu.
On the most current (ICS-based) MIUI, you have to use the boot menu (press the Volume Down button during power on when the notification LED turns blue while the red Motorola logo is still displayed).
On stock firmware, however, the only way to access CWM is using koush's Droid 2 Recovery Bootstrap and its Reboot Recovery option.
For most other phones, you just replace the stock recovery with CWM, and that gives you the same version of CWM whenever you boot into it.
On Motorola phones with locked bootloaders, CWM versions might differ between different ROMs, because CWM is installed as just another system component with the ROM itself, not outside the ROM inside the boot/recovery partition.
I am, however, unsure why are there such issues for you with backup and restore; I was able to use backup and restore on multiple occasions, and last time I did it was just 2 days ago when I switched between MIUI and stock about 7 times without resorting to SBF even once.
I thought the first few times it didn't 'restore' was because I installed CM7 incorrectly or that I didn't install the bootstrap correctly, but I've SBFd and installed CM7 at least 4 times now and I've never been able to restore; every time I do, I get the 'Error while formatting /system' message.
I really hope I'm just doing this wrong (though I don't see how) and someone can steer me in the right direction.
Wipe data/ cache?
If u use rom manager, go recovery via rom manager
I've done that every time, including wiping the cache partition AND Dalvik under 'advanced'. I found out it was the CM7 version I had installed, which was the 'stable' version that installs over Froyo. It was messing up all sorts of things. I installed one of the RevNightlies over the Gingerbread OTA and most of my problems resolved. I've still had a few instances of a backup not restoring right though... is that a common issue?
**EDIT**
Problem solved, thanks to the guys over @ Rootzwiki. If you have the D2G, you need to flash CWM for the Droid X (2nd-init). I did and backups/restores are working perfectly.
This is a HUGE issue, IMO. There's zero documentation on CWM online, so hopefully people will see this thread if they encounter the same issues I did.
beepea206 said:
**EDIT**
Problem solved, thanks to the guys over @ Rootzwiki. If you have the D2G, you need to flash CWM for the Droid X (2nd-init). I did and backups/restores are working perfectly.
This is a HUGE issue, IMO. There's zero documentation on CWM online, so hopefully people will see this thread if they encounter the same issues I did.
Click to expand...
Click to collapse
I was also having this issue. Thank you for doing the research!
It's pretty frustrating because in ROM Manager, there's a Droid 2 Global option which you would think would be the obvious choice. Apparently D2G's really need DX-2ndInit.
I'm in DX-2ndInit Recovery on my D2G and it's actually doing functions instead of pretending. It's happily restoring a Nandroid backup that I made under the old original version of CWM that the D2Bootstrapper installed.
Edit: Nandroid Restore worked perfectly! All's going very well now and my phone is now running on AT&T on a GoPhone SIM. Looks like it can even jump on HSDPA!
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?
Nandroid restore, if that won't work nvflash?
you mean use NVflash to do the rom install vs the recovery?
I made a topic about this, check my post (not able to give you a link right now sorry)
I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?
Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612
You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.
I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.
This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.
Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.
If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app
It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8
rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.
The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.
Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!
You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.
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 have been running CWM recovery and installing Wingray nightlies on my MZ604 without any problem for more than a year. A couple of days ago I flashed what I think was a partially downloaded ROM. This soft bricked my Xoom (somewhat unsurprisingly). I ended up in a boot loop so I used this method http://www.xoomforums.com/forum/motorola-xoom-development/18743-how-flash-sbf-rsd-method.html to get out of it.
That worked fine leaving me with a stock Xoom running 3.1.
I then unlocked the bootloader and flashed CWM Touch using adb. I then booted into recovery and flashed the universal Xoom root from here http://forum.xda-developers.com/showthread.php?t=1242241.
Again, this worked fine so now I had what appeared to be a fully functional Xoom running CWM Touch and 3.1. So far, so good.
The final step was to install a recent ROM so I booted into recovery again, flashed the latest Wingray nighly and the GApps package as I have done on numerous occasions (after doing a factory reset and wiping the cache and the Dalvik cache). This appeared to work just as it has always done but now my Xoom just sits at the M logo and nothing else happens. I can still boot into CWM Touch but my Xoom won't get past the M logo in normal boot.
Since everything seemed to work exactly as I would expect right up to the final boot, I'm somewhat mystified as to what is wrong. Can anyone give me any suggestions as to what to do next?
Now I can actually help you. I saw this a day ago but did not respond yet because I did not test my method.
It's been stated by a few in the eos 4 wingray thread that nightlies 204-205 are TEST builds. Only one person said that but from what everyone else is experiencing this appears to be true. You are not alone mine was bootlooping and never getting past the splash animation either.
You don't need to fix or flash a new recovery. All you have to do is use a lower build such as 203 and you'll be fine. I'm testing some roms right now and they work fine now. I did upgrade to twrp recovery as well.
I'm sorry you went through the whole boot loader process again.
At least it's a simple fix. I'd recommend monitoring the eos4 thread and see when people post about newer builds working. I'm sure 206 will fix everything.
Best of luck.
Thanks for the suggestion but unfortunately it didn't work. I did get past the M logo and the multicoloured splash screen appeared but it just got stuck there.
I tried going back to 203 and that didn't work. I also tried going way back to 155 (with the appropriate Google apps package) and that didn't work either.
I am starting to wonder if there is something about the way I am flashing these that isn't working. I have done it so many times that I am rather baffled as to what is going on this time but I think I shall try flashing using Odin and see if that gets me any further. It's all rather frustrating as I haven't been able to use my Xoom for days now.
I have now fixed this although I am not absolutely sure whether my diagnosis is correct.
By flashing Wingray 203 and a very old GApps package, I got past the splash screen. The Google setup program then crashed but at least it had booted. I then tried 203 and the second most recent GApps package (dating from January I think) and it worked.
My guess is that there is some weird interaction between the most recent versions of Wingray and the most recent GApps package (and possibly other factors) but at least my Xoom now works.