Database Info

[RECOVERY] G2x ClockworkMod flash for Mac

Disclaimer: flashing is a lot more risky than rooting so proceed at your own risk. This has only been tested with the G2x.
This uses the free VirtualBox (from Oracle) and a 900 meg vitrual machine I created to allow flashing recovery (clockworkmod or stock) from a mac. If you run into any problems with the first download link, try the second (it requires free registration).
This will give you a running linux virtual machine that has g2x root/unroot, clockworkmod (and stock) recovery flashing, and the android sdk (including adb) set up. You can root or unroot as well as flash clockworkmod recovery or the stock recovery using some double-clickable scripts. The android sdk is on there too in case you want to play around with adb. The clockworkmod version installed is 3.1.0.1 external with ext4 (http://forum.xda-developers.com/showthread.php?t=1086687) but you can download other versions and flash them pretty easily - just check the Readme.txt in the nvflash folder.
The clockworkmod flash here is the mac equivalent of http://forum.xda-developers.com/showthread.php?t=1056847 - though this thread just uses a linux virtual machine to get it done.
The username and password on the virtual machine are both "android" (without the quotes of course).
Requirements:
a few gigs of hard disk space
about 300 megs of RAM
intel mac
a sense of adventure
download virtualbox and the extension pack from http://www.virtualbox.org/wiki/Downloads
http://download.virtualbox.org/virtualbox/4.0.8/VirtualBox-4.0.8-71778-OSX.dmg
http://download.virtualbox.org/virt...alBox_Extension_Pack-4.0.8-71778.vbox-extpack
install virtualbox
install the extension pack (just double click it once virtualbox is installed)
download the linux virtual machine (thanks to propain4444 for the hosting) http://articulatevisuals.com/g2x/virtualbox_image_32bit_0_3.tar.bz2 or (requires free registration for this one) http://www.4shared.com/file/19DywhVS/virtualbox_image_32bit_0_3tar.html
decompress the virtual machine download (double click) if it didn't happen automatically
in virtualbox choose Machine -> Add… from the menu bar and choose the android_g2x.vbox file inside the android_g2x folder created by the decompressed virtual machine download
once the vm boots up you'll see the root/untoot and nvflash folders on the desktop with double-clickable scripts inside
After following the requirements above, to connect your phone for flashing with nvflash do the following:
plug the USB cable into your mac
turn the phone off
remove the battery
hold down volume up and volume down then plug the USB cable into the phone
Nothing will happen on the linux vm (unless you ran the tail_kernel_log.sh script in the nvflash folder) but you *should* be able to then run the flash-clockworkmod-recovery.sh script. If it doesn't see your device try disconnecting from USB and doing the steps above again. If you want more visibility into whether or not it's connected then double-click the tail_kernel_log.sh script and watch for a line to appear when you plug your phone in (with volume buttons held down of course).
If this helped you please click the Thanks button on this post. Thanks to baykakes for helping with the initial testing and propain4444 for the registration free download hosting. Countless thanks and credit to krylon360 for the updated ClockworkMod, Chris Soyars (ctso) for the initial test2 ClockworkMod and linux scripts in the g2x forum that motivated me to do this, koush for ClockworkMod and many others here whose knowledge helped make this possible.

YEY you posted it!
Once everything is downloaded IT'S REALLY EASY FOLKS!

Hey OP, thanks for developing and posting this. I can confirm that this works well and that it is really easy once the necessary files are downloaded.

I'm a newb, but after all these steps are done we should be able to save the stock ROM and I can download another ROM?

Mikeglongo said:
I'm a newb, but after all these steps are done we should be able to save the stock ROM and I can download another ROM?
Click to expand...
Click to collapse
That's exactly what you should be able to do. If you get it all installed and run the flash-clockworkmod-recovery.sh script successfully then you can do the following.
In preparation, download your ROM of choice to some place on your MicroSD card. If it's cyanogenmod you'll also need to install google apps. If you want to download it to your MicroSD card (gapps) and you'll install it later with clockworkmod. Once this is done back up the stock ROM:
power off the phone
hold down power and volume down until you see Android with a bunch of app icons then release both buttons
when the screen with red text comes up press volume down to scroll to "backup and restore" then hit power button to select
Backup should be highlighted so hit power to select
wait for the backup to complete
Now you should have a folder in /sdcard/_ExternalSD/clockworkmod/backup with a timestamp and the contents of your backup (the path may vary if you're on something other than the stock ROM). At this point you'll want to
navigate to "wipe data/factory reset" and let it complete
navigate to "advanced" => "Wipe Dalvik Cache" and let it complete
finally back to "install zip from sdcard" -> "choose zip from sdcard" and find the zip file with the ROM you downloaded above and install it
if you installed a ROM like cm7 that requires the google apps separately choose "install zip from sdcard" again, "choose zip from sdcard" and find the gapps zip you downloaded and install it
When it finishes you can reboot and setup your new ROM. You can of course backup the new ROM like you did before. At any point you can reboot into recovery (power off then hold power and volume down) and use restore to restore a previous backup.

worked great, thanks so much for your work!

Awesome, this might actually be what I was looking for, a big thanks to you.
Just one question, since T-mobile is sending me a new phone, shoud be here by thursday, might as well not install NVFLASH until thursday correct?

Mikeglongo said:
Awesome, this might actually be what I was looking for, a big thanks to you.
Just one question, since T-mobile is sending me a new phone, shoud be here by thursday, might as well not install NVFLASH until thursday correct?
Click to expand...
Click to collapse
Yeah, assuming you need to send your current one back you might just wait for the new one. Though you could flash cwm now, backup your stock ROM, flash some new ROMs just for fun then restore the stock ROM and flash the stock recovery before sending it back :-D. This virtual machine also includes my easy root/unroot scripts as well...

I may be able to host the VM image for you - Send me a PM if interested.

So, this is the "full" clockwork flash for a mac right? Not the "fake" one i keep hearing about.
Basically, this is flashing clockwork as described here (only, for a mac):
http://forum.xda-developers.com/showthread.php?t=1056847

propain4444 said:
So, this is the "full" clockwork flash for a mac right? Not the "fake" one i keep hearing about.
Basically, this is flashing clockwork as described here (only, for a mac):
http://forum.xda-developers.com/showthread.php?t=1056847
Click to expand...
Click to collapse
yes, the real clockworkmod as described in that thread. it's the external sdcard version of the 3.1.0.1 with ext4 support - though you can download and flash other versions if you want (see the Readme.txt in the nvflash folder)

jnichols959 said:
yes, the real clockworkmod as described in that thread. it's the external sdcard version of the 3.1.0.1 with ext4 support - though you can download and flash other versions if you want (see the Readme.txt in the nvflash folder)
Click to expand...
Click to collapse
Thanks - Let me know if you're interested re: hosting the VM.

Since I'm most likely flashing this way, what's a VM? Just because I'm a newb

Mikeglongo said:
Since I'm most likely flashing this way, what's a VM? Just because I'm a newb
Click to expand...
Click to collapse
virtual machine. in this case it's a linux computer that runs in a window on "virtual" hardware. that's what VirtualBox provides - the software to emulate a computer and allow you to run these virtual machines.
i went this route because nvflash is only available for windows or linux machines. a windows vm would not be free but a linux vm is and the nvflash (and root/unroot) tools run quite well on it, in fact arguably better than on windows since you don't need any device drivers

Ooops sorry I wrote in here meant to message you

How do you do the internal SD flash recovery?!

Mikeglongo said:
How do you do the internal SD flash recovery?!
Click to expand...
Click to collapse
Check the read me file in the g2x folder of the downloaded package. I think all you have to do is put rename the recovery file in the nvflash folder. Someone correct me if I am wrong, but I think the script is made to flash by name. So as long as you rename the file you want and rename the old file (so it is not flashed) you should be good.
Sent from my LG-P999 using XDA App

Edit: Nevermind.

gshine said:
Edit: Nevermind.
Click to expand...
Click to collapse
So did it end up working? Normally you need to watch the terminal that opens up and read the text in it. That should tell you when it's done, if it's successful, and what to do when it's finished.

Yes. not sure what happened on the first try, but the second one worked fine. I've backed up my original ROM, and installed CM7. I'm happy...for the moment!
jnichols959 said:
So did it end up working? Normally you need to watch the terminal that opens up and read the text in it. That should tell you when it's done, if it's successful, and what to do when it's finished.
Click to expand...
Click to collapse

[Q] Did i completely brick my tf101?

i tried to unbrick this using
http://forum.xda-developers.com/showthread.php?t=1123429
but now that i followed the instructions all i have is a black screen nothing even pops up. can anyone help me fix this im freaking out right now.

Can you give us more info? Were you rooted? Did you screw up flashing a rom or something? A few weeks ago I had to unroot my TF so I could RMA it and I found that a lot of the posts on here were either outdated or linked to an outside source, which was outdated.
When I got my TF back I decided to re-root it and it was a lot more painful than when I first did it about a month earlier, IDK if I had my images swapped and I was flashing the wrong files or what but it took freaking forever.
I'll upload a stock 3.2 image for you that has to be flashed with nvflash and it will unbrick your tablet. If you want to be rooted use Roach's nvflashable version of Prime instead and that should also fix your TF.

i have a b60 model i was not rooted i tried but failed because i couldnt get superuser to work. i was trying to flash back to stock because i could not get any updates so i figured if i go back to a clean 3.2 i would be ok. then i tried putting it back to stock using one of the post here. then when i tried everything went smooth but then i tried turning my tf101 on and it would not turn on. could you help me fix this? ill be very grateful to you give you a thanks and when i get a job donate to you if we get this working. thank you
edit: i still can get into nvflash but thats about it. idk what to do now

Installing ADB
1. Under the Choose packages to install dialog in the Android SDK choose Android SDK Platform Tools (you don't need all the other crap) and hit install.
2. Right click on My Computer and then select Properties and then Advanced System Settings, then click Environmental Variables and add the location of the folder that contains ADB to the PATH variable in the second pane entitled System Variables (ex: [path that the main folder is in]\android-sdk_r12-windows\android-sdk-windows\platform-tools)
3. Reboot.
4. You should now be able to access ADB via the command prompt (run --> cmd) simply by typing adb
Flashing Back to Stock 3.2
1. Download it from here and extract the archive with winrar, replace the nvflash linux binary with the windows equivalent, open up download.sh and remove the ./ from the beginning of nvflash and also the first line of the file
2. Change the file extension of download.sh to download.bat
3. Right click it and click run as administrator and then let it do it's work and you should be on a fresh install of Honeycomb 3.2 in no time!

I need an easier guide...

To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...

I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though

I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.

DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate

My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...

DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt

I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?

DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have

How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?

DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium

I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"

DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium

You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone

DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium

If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?

DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium

Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/

DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium

Is there perhaps any way to perform a ROM backup with ADB?

DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium

[Q] Flashing a ROM without being able to boot phone.

So,
I'm a dumbass and accidentally flashed an "update package" rather than a full ROM. I can not get past the "HTC ONE" white screen now..I have full access to recovery and bootloader, but can't boot the phone to mount as "Disk Drive" so I have no way to put the .zip file I need on the SD Card. Is there a way to put the correct .zip...even a stock ROM onto the SD Card without the phone being able to boot? I looked around and couldn't find anything.
Thank you so much.
-Brian

Boot the phone into recovery, go to mounts and storage, mount system. In adb push the file to /sdcard/
Sent from my HTC VLE_U using xda premium

If you need more details, let me know
Sent from my HTC VLE_U using xda premium

strker45 said:
If you need more details, let me know
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Sent you a PM. Thank you

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

Hi, I'm working on exactly the same thing. I am only about 20 hours in and have learned quite a bit, but not having an SD card you can slip into a PC card slot is a major challenge. I have managed to get recovery back on the phone, and am successfully connected via fastboot. I can't figure out the ADB shell...I've installed SDK manager and have tried to enter the ADB shell, but cannot. Keep getting error messages. WHen I attempt to flash a rom via fastboot, the process starts, but then quits with the error that my media does not include android-info.txt or android-product.txt. I have tried every tmo ROM available, and the Nandroid back up. It is a paper weight? Thanks to anyone who can shed some light!

rjsvoon said:
Hi, I'm working on exactly the same thing. I am only about 20 hours in and have learned quite a bit, but not having an SD card you can slip into a PC card slot is a major challenge. I have managed to get recovery back on the phone, and am successfully connected via fastboot. I can't figure out the ADB shell...I've installed SDK manager and have tried to enter the ADB shell, but cannot. Keep getting error messages. WHen I attempt to flash a rom via fastboot, the process starts, but then quits with the error that my media does not include android-info.txt or android-product.txt. I have tried every tmo ROM available, and the Nandroid back up. It is a paper weight? Thanks to anyone who can shed some light!
Click to expand...
Click to collapse
That's not how to flash roms, perhaps that's why. If you don't understand adb you really should not be rooting or unlocking anything until you have a better understanding of the tools you have available. Otherwise you end up in here asking if your phone is bricked when really you just have no idea what you're doing in the first place. Flash recovery in fastboot, then flash the rom from recovery.
Sent from my HTC One S using XDA

Yea I figured it out..I had a recovery working though.
With regards to rsvjoon,
As stoneyjonez said...you need to flash a recovery (Say CWM Touch) using fastboot...something along the lines of "fastboot flash recovery recoveryimagefilehere.img" and then reboot into recovery...etc etc.
I followed this this step-by-step process exactly and got it to work, I recommend the same.
Cheers

hello...i as well need a step by step about pushing the rom to /sdcard/ in adb....if you could pm me that i would be thankful!

Thanks...and you're right. But I have successfully flashed CWM recovery...I just can't get anything on the phone to flash. Fastboot starts the process but ultimately I get an error with each rom I try that it can't continue because I'm issing those two text files. So anyway, your point is well taken. In the past, once I had recovery, I'd just slip the micro SD card into my computer and pop a rom on it. totally different deal without that capability.
---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------
brwetz said:
Yea I figured it out..I had a recovery working though.
With regards to rsvjoon,
As stoneyjonez said...you need to flash a recovery (Say CWM Touch) using fastboot...something along the lines of "fastboot flash recovery recoveryimagefilehere.img" and then reboot into recovery...etc etc.
I followed this this step-by-step process exactly and got it to work, I recommend the same.
Cheers
Click to expand...
Click to collapse
Thanks brwetz. That is exactly the process I followed when I originally rooted my phone...and everything was swell. I fongooled things when I flashed a custom rom (which also worked just fine) and then decided to restore my Nandroid. for whatever reason, that process left me in recovery with nothing on the SD card to flash back.
Thanks again for the response.

rjsvoon said:
Thanks...and you're right. But I have successfully flashed CWM recovery...I just can't get anything on the phone to flash. Fastboot starts the process but ultimately I get an error with each rom I try that it can't continue because I'm issing those two text files. So anyway, your point is well taken. In the past, once I had recovery, I'd just slip the micro SD card into my computer and pop a rom on it. totally different deal without that capability.
Thanks brwetz. That is exactly the process I followed when I originally rooted my phone...and everything was swell. I fongooled things when I flashed a custom rom (which also worked just fine) and then decided to restore my Nandroid. for whatever reason, that process left me in recovery with nothing on the SD card to flash back.
Thanks again for the response.
Click to expand...
Click to collapse
What *I did* to put a .zip file on my phone without being able to boot it up was this:
-Go into Recovery -> Mounts and Storage.
-Plug your phone into your computer using USB cable
-Make sure it says "Unmount /sdcard/" and "Unmount /system/". If they do not say that, just press them (they are toggles)
-Make sure the ROM.zip file is in the same directory as your AndroidSDK/adb (for example, mine is C:\AndroidASK\)
-Go into command prompt and type "cd c:\whereveryouradbislocated"
-Once you are in your AndroidSDK (adb) directory, type "adb push romname.zip /sdcard/romname.zip
-Unplug phone from computer, close command prompt
-Go back in Recovery to main menu and do a factory reset/wipe cache partition/wipe dalvik cache (I can explain those more if needbe)
-Again go back to Recovery Main Menu -> Install Zip from SD Card -> Choose file from SD Card -> Select the romname.zip file you just pushed from your computer and install that .zip
-Reboot phone, be patient as it will take a minute to completely boot up.
-_-_-_-_-_-_-_-_-_-_-_-
If you need further instructions, please PM me.
All of this information deserves much thanks to strker45 and doktartaru for their endless help getting me through the process.
EDIT:
Should I make a walkthrough thread about this just incase anyone else has this problem?

brwetz said:
What *I did* to put a .zip file on my phone without being able to boot it up was this:
-Go into Recovery -> Mounts and Storage.
-Plug your phone into your computer using USB cable
-Make sure it says "Unmount /sdcard/" and "Unmount /system/". If they do not say that, just press them (they are toggles)
-Make sure the ROM.zip file is in the same directory as your AndroidSDK/adb (for example, mine is C:\AndroidASK\)
-Go into command prompt and type "cd c:\whereveryouradbislocated"
-Once you are in your AndroidSDK (adb) directory, type "adb push romname.zip /sdcard/romname.zip
-Unplug phone from computer, close command prompt
-Go back in Recovery to main menu and do a factory reset/wipe cache partition/wipe dalvik cache (I can explain those more if needbe)
-Again go back to Recovery Main Menu -> Install Zip from SD Card -> Choose file from SD Card -> Select the romname.zip file you just pushed from your computer and install that .zip
-Reboot phone, be patient as it will take a minute to completely boot up.
-_-_-_-_-_-_-_-_-_-_-_-
If you need further instructions, please PM me.
All of this information deserves much thanks to strker45 and doktartaru for their endless help getting me through the process.
EDIT:
Should I make a walkthrough thread about this just incase anyone else has this problem?
Click to expand...
Click to collapse
Thanks very much! I'll do this when I get home tonight. I'll let you know how it goes...If i get it up and running I'll buy you a CASE of beer!

Not a problem.
I posted a more in-depth walkthrough here. Hope it helps possibly even better.

brwetz said:
Not a problem.
I posted a more in-depth walkthrough here. Hope it helps possibly even better.
Click to expand...
Click to collapse
I am back in business! I was able to flash the CWM Rom 9.0.0 and then ultimately restored the stock Nandroid made available here. It's a beautiful thing. I bought you some beers! Thank you very much.

Anybody know how to flash the rom through fastboot instead of recovery by pushing the boot.img and system.img from the ruu? sd card isnt mounting in recovery for whatever reason so I don't have access to the .zip files on my sd card. more details in my post from brwetz's thread here.
Thanks in advance for any help.

rjsvoon said:
I am back in business! I was able to flash the CWM Rom 9.0.0 and then ultimately restored the stock Nandroid made available here. It's a beautiful thing. I bought you some beers! Thank you very much.
Click to expand...
Click to collapse
How are those beers? hahaha

Beer music
brwetz said:
How are those beers? hahaha
Click to expand...
Click to collapse
You're the one that should be drinking the beers! Did you not receive donation?

rjsvoon said:
You're the one that should be drinking the beers! Did you not receive donation?
Click to expand...
Click to collapse
lol wow no I didn't..I didn't even know we could do that. I'll update my PayPal...

[Q] How make the TF101 Stock and unroot?

Hi
I've been having heavy troubles with the "Android Revolution HD" ROM, my battery lasts forever while in use, but drowns easily and extremely fast when in sleep / shutdown mode.
So I give up, I am going to sell this tablet and I don't want this ROM any more, I don't want my devince Root. I want to get it back to the way it was when I opened the box.
The only think I'd like to get is the Eee Pad Transformer TF101 Firmware: V9.2.1.27 original from Asus to keep using the Android 4.0.X, nothing else.
Since all my attemps of install / reinstall / stock / root / unroot became a mass failure and later on I end coming here and QQ for help I am here to ask what need to be done before doing anything on the tablet.
So here is the summarized question:
How make the TF101 Stock and unroot?
Thank you
And sorry for my silliness

Here is a solution for you, "Instructions for unbricking/flashing ASUS stock firmware" part.
http://forum.xda-developers.com/showthread.php?t=1688012

pstryju said:
Here is a solution for you, "Instructions for unbricking/flashing ASUS stock firmware" part.
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
It just doesn't work (as I was expecting) after doing exactly everything it says, it start installing something and then that is it, nothing happens on my tablet.

Filipebergami said:
Hi
I've been having heavy troubles with the "Android Revolution HD" ROM, my battery lasts forever while in use, but drowns easily and extremely fast when in sleep / shutdown mode.
So I give up, I am going to sell this tablet and I don't want this ROM any more, I don't want my devince Root. I want to get it back to the way it was when I opened the box.
The only think I'd like to get is the Eee Pad Transformer TF101 Firmware: V9.2.1.27 original from Asus to keep using the Android 4.0.X, nothing else.
Since all my attemps of install / reinstall / stock / root / unroot became a mass failure and later on I end coming here and QQ for help I am here to ask what need to be done before doing anything on the tablet.
So here is the summarized question:
How make the TF101 Stock and unroot?
Thank you
And sorry for my silliness
Click to expand...
Click to collapse
Download any firmware on the asus site. Extract the downloaded firmware (eg. WW_epaduser9_2_1_27UpdateLauncher.zip) take the file extracted (eg. WW_epad-user-9.2.1.27.zip) and place on sdcard. Follow the same procedure for installing a custom rom.

gilpederiva said:
Download any firmware on the asus site. Extract the downloaded firmware (eg. WW_epaduser9_2_1_27UpdateLauncher.zip) take the file extracted (eg. WW_epad-user-9.2.1.27.zip) and place on sdcard. Follow the same procedure for installing a custom rom.
Click to expand...
Click to collapse
How do I place things into the SD?
I can only place them into the internal storage, which "Full Wipe" will wipe it out?

Filipebergami said:
How do I place things into the SD?
I can only place them into the internal storage, which "Full Wipe" will wipe it out?
Click to expand...
Click to collapse
Sorry, put the file on the external sdcard. I also used a full wipe script. It takes a little more than installing a custom rom but it works.
I would like to take a question with you. I have already installed several custom ICS rom or JellyBean on my TF101, but the HD videos on youtube are with small crashes. But with Android 3.2.1 works well. This has happened to you?

gilpederiva said:
Sorry, put the file on the external sdcard. I also used a full wipe script. It takes a little more than installing a custom rom but it works.
I would like to take a question with you. I have already installed several custom ICS rom or JellyBean on my TF101, but the HD videos on youtube are with small crashes. But with Android 3.2.1 works well. This has happened to you?
Click to expand...
Click to collapse
I have no MicroSD card into my tablet, only internal storage

Filipebergami said:
It just doesn't work (as I was expecting) after doing exactly everything it says, it start installing something and then that is it, nothing happens on my tablet.
Click to expand...
Click to collapse
Please provide further details. What does easyflasher's window/log say? I've used this hundreds of times of not more to go back to stock or fix issues. Did you install the proper APX drivers?

Lethe6 said:
Please provide further details. What does easyflasher's window/log say? I've used this hundreds of times of not more to go back to stock or fix issues. Did you install the proper APX drivers?
Click to expand...
Click to collapse
It says everything was installed successfully and yes APX drivers are fine I've had others troubles with ROMs so I have it installed properly.
http://img10.imageshack.us/img10/9625/es5b.jpg

Filipebergami said:
It says everything was installed successfully and yes APX drivers are fine I've had others troubles with ROMs so I have it installed properly.
http://img10.imageshack.us/img10/9625/es5b.jpg
Click to expand...
Click to collapse
Did you see any text on the TF display? It should show some text when it is flashing.
Also, when in recovery you can use ADB to push the ww-epad firmware to your tablet's sdcard. Update the driver for the naked driver ADB and then:
adb push ROM.zip /sdcard/
If you need ADB, you can get the adb and dll files required to run here: https://dl.dropboxusercontent.com/u/34321735/adb.zip

frederuco said:
Did you see any text on the TF display? It should show some text when it is flashing.
Also, when in recovery you can use ADB to push the ww-epad firmware to your tablet's sdcard. Update the driver for the naked driver ADB and then:
adb push ROM.zip /sdcard/
If you need ADB, you can get the adb and dll files required to run here: https://dl.dropboxusercontent.com/u/34321735/adb.zip
Click to expand...
Click to collapse
Hi frederuco, you saved me once.
http://forum.xda-developers.com/showthread.php?t=2144143
Do I need to do this all over again?

Filipebergami said:
Hi frederuco, you saved me once.
http://forum.xda-developers.com/showthread.php?t=2144143
Do I need to do this all over again?
Click to expand...
Click to collapse
Yup!
Push the rom to flash to the /sdcard/ and you should be good to flash. Obviously dontjisnafter the full wipe.

frederuco said:
Yup!
Push the rom to flash to the /sdcard/ and you should be good to flash. Obviously dontjisnafter the full wipe.
Click to expand...
Click to collapse
Am I doing this right?
http://img24.imageshack.us/img24/6711/rlof.jpg
http://imageshack.us/f/545/wxne.jpg/

Almost....
You need a space between the .zip and the /sdcard/

frederuco said:
Almost....
You need a space between the .zip and the /sdcard/
Click to expand...
Click to collapse
I am getting error like last time,
http://img850.imageshack.us/img850/2954/lemh.jpg

Try using this version of adb: https://dl.dropboxusercontent.com/u/34321735/adb.zip
It is just the adb.exe and the two dll files required to run it.
I use those in a folder called c:\adb and then put the asus.zip in there and try it.
Also, try executing adb devices to make sure it can connect to your tablet. It should find 1 device.

frederuco said:
Try using this version of adb: https://dl.dropboxusercontent.com/u/34321735/adb.zip
It is just the adb.exe and the two dll files required to run it.
I use those in a folder called c:\adb and then put the asus.zip in there and try it.
Also, try executing adb devices to make sure it can connect to your tablet. It should find 1 device.
Click to expand...
Click to collapse
I still getting error, here is my screen if this helps:
http://imageshack.us/f/534/4vsd.jpg/
and the error log:
http://imageshack.us/f/32/ogc1.jpg/

on your PC try running these, then try to push the file again:
adb kill-server
adb start-server

frederuco said:
on your PC try running these, then try to push the file again:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Here:
http://img850.imageshack.us/img850/2543/h9vj.jpg

Hmm, not sure what to say....
Do you have another PC you can try it on? At least try a PC reboot if nothing else.
Or perhaps a Linux live cd. ADB is native to Linux, just run from a terminal window.