yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] ernst99999:
hello,

can any body maybe help me with almost same problem. I have also CWR 5.5.04 and had the problem of rebooting in cwr. My first thought was to load a new rom and install it. But when i connect to TF with adb and try to push a file it says "read-only file system" Further more i found out that alle dirs on my tf diapeared. Got 1 back by making a backup through cwr. But even when i tryed to push a file to that dir it keeps saying "read-only file system". :confused:

Hope someone has a bright idea to unbrick this one. Otherwise i have to try get it repaired by Asus. :eek:

---------- Post added at 07:14 PM ---------- Previous post was at 06:46 PM ----------

Update:

for testing i made a 1Kb test.zip file andtryed it to adb push to TF.

I found that i can adb push to /data and /cache. When i try to push to /system then i get read-only file system, when i try to push to /recovery it says no such file or directory. All above locations do not appear in cwr when i try to install zip from sdcard.

Can any body tell when i can try to push a file to.
[Eee Pad Transformer General] partio:
you should push the new recovery to /data/media

adb push recovery.zip /data/media , and then , install it from the bad recovery 5.5.0.4

see my post above to complete procedure
[Eee Pad Transformer General] ernst99999:
I found it out myself :D :D

@partio But thru after i read your post, first i was still hopeless because you mentioned /sdcard. But it gave me an idea. For the logfile mentioned writing a file from /tmp/recovery.log to /data/media. After a couple of more tries to push i found that /data/media was the place !!! :cool:

Thanks every one :) :D :)
[Eee Pad Transformer General] didier74:
Hi,

My problem is that once the good cwm is copied to the root of my internal memory, trying to flash it through bad recovery, it starts and says "aborted".

By the way, i also do not have any /data/media folder.

any idea please? Thanks.
[Eee Pad Transformer General] partio:
maybe a bad download o incorrect recovery ??

which is the recovery are trying to install ?

the root of your internal memory is /data/media for the recovery , you cant see trough windows explorer
[Eee Pad Transformer General] partio:
some progress ?
[Eee Pad Transformer General] didier74:
Thanks for your help.

The recovery i am trying to install is:

nvflash_cwm_recovery-5027_rogue_rburrow-tf101-r1

zip file can be opened normally after download, then i think it has been correctly downloaded.

Thanks.
[Eee Pad Transformer General] partio:
nvflash recovery zip dont work for this , iis the other link : cwm_recovery-5027_rogue_rburrow-tf101-r1
[Eee Pad Transformer General] didier74:
Really? Thank you, will try this as soon as I get back.

Thanks.
[Eee Pad Transformer General] partio:
the nvflash zip is for the nvidia nvflash tool.

the other zip wihtout "nvflash", is to flash trough cwm himself.
[Eee Pad Transformer General] didier74:
good evening,

the flash did work with cwm_recovery-5027_rogue_rburrow-tf101-r1, all is fine thank you VERY VERY much for your help and solution.
[Eee Pad Transformer General] partio:
4 - once installed , dont press reboot system now , make a cold boot directly

5 - once you've booted your rom , run terminal emulator.

type : su (if superuser appp ask to you , allow). will give you a #

type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

type : exit

type : reboot

your tf restart without cwm loop , and you will see a progress bar installing the new cwm .

Now you can install any new rom from your sdcard usually through cwm.
[Eee Pad Transformer General] didier74:
....you probably saw my words before i edited it, you are right i had forgotten to end your solution which is perfect. Thank you again very much.

Have a nice evening.
[Eee Pad Transformer General] partio:
ok, I'm glad you've solved the end
[Eee Pad Transformer General] didier74:
Thank you very much
[Eee Pad Transformer General] dundada08:
i currently cannot access recovery at all. i tried to flash CWM through rom manager and reboot to recovery manually (power + vol down), rom manager, and the quick boot. none worked and my tablet simply reboots. does anyone have an idea on what's wrong and how i can fix this? all your help is appreciated!
[Eee Pad Transformer General] partio:
its your first attempt ?

or have overwritten the previous one via rommanager?
[Eee Pad Transformer General] baseballfanz:
Manually it's

Vol down plus power button,

When you see words at top left corner push Vol up immediately within 5 sec.

For app use "Transformer reboot recovery"
[Eee Pad Transformer General] dbug2008:
recovery loop fixed, but....

Now I cant see my sd card in recovery. I can boot into ICS, and I can veiw the card with file manager, but cant see the sd card contents in recovery. Any help would be appreciated.
[Eee Pad Transformer General] partio:
recovery 5.5.0.4 cant read sd card.

if you have installed the same 5.5.0.4 fixed recovery , you should install another to work with sdcard.
[Eee Pad Transformer General] thelangosta:
Still stuck

Okay, I have tried Roach's method as described above through adb and still cannot get it to work.

When I enter the code he suggests at the prompt(C:\android-sdk\platform-tools>) I get "/dev/block/mmcblk0p3: cannot open for write: Permission denied".

Did I miss something during adb setup? It took me 1.5 days to get it to even recognize my device. I have no more hair to pull out and would really like to get a properly working recovery on my tab. I know how to cold boot it but, that really doesn't solve the problem.

Can anyone help please? I am not too proud to beg at this point.
[Eee Pad Transformer General] gee one:
try typing "adb shell" first. Then the dd command.
[Eee Pad Transformer General] thelangosta:
Thanks, I will do that after it recharges a bit more. It has been random rebooting lately and of course did it during the night last night leaving me with only 10% battery... and I can't flash a new ROM til I have the recovery working. I wonder if we can get one of the nice kernel devs to get these tabs to charge while connected to a computer?
[Eee Pad Transformer General] thelangosta:
Tried it again

Okay so I tried that and it is still giving the permission denied error. Also, tried the "echo boot..."command and got the same error so something must not be set up correctly on either the PC or the tab. It would be cool just to be able to fix the recovery loop in terminal on the tablet and not involve the PC. At least one major variable would be out of the picture. I only need adb to stop the loop as I have Roach's fixed and repacked versions on my internal storage.

Background info:

-stock rooted ICS

-USB debugging on

-sync icon in status bar along with usb and debugging icons

-installed borked recovery from ROM manager(over Rogue while trying to get Roach's fixed version on) doh!!!

P.S. gonna try to set up adb on the laptop with Linux Mint 12. Will post again if that works better.

EDIT: Nope, not working on Linux Mint 12 either. I get the very same "Permission Denied". Going to walk away for a little while before I do physical harm to my tab. I guess I have narrowed it down to my tf and eliminated the computers. I am just very frustrated with the whole thing right now and need a break. Thanks in advance to anyone who can help.
[Eee Pad Transformer General] partio:
can you coldboot to your ics rom , or only recovery mode ?

if you can boot your rom : http://xdaforums.com/showpost.php?p=24266780&postcount=287

if you can boot only recovery mode : http://xdaforums.com/showpost.php?p=24304452&postcount=293
[Eee Pad Transformer General] thelangosta:
That did it!

Thank you! I can finally move on with my life. It was driving me crazy(my wife said I was driving her crazy)that I could not get it to work with ADB. If you can cold boot this is such a simple method. It took me 2 minutes to go from borked CWM to Roach's repacked touch recovery. Wish I would have known about this 2 days ago.;) Would it be possible to change the OP to make it easier for those of us who need simple commands? I know this line of code is in the OP but it says to do it in ADB which just wasn't working for me. Anyway, Thank You to everyone who worked on this.
[Eee Pad Transformer General] bukithd:
Not sure how to cold boot straight from the bad recovery on the able to access from method. Do I hold the power button down till it shuts off then cold boot or what?
[Eee Pad Transformer General] baseballfanz:
Just hold Vol Down plus Power button, you'll see words at the top left corner.

After which just wait till you get the options to cold boot or wipe data.

Choose cold boot
[Eee Pad Transformer General] dasunsrule32:
Not trying to hijack this thread, but what was the fix to get tar to restore files >2GB? I have enabled LFS in busybox to no avail. Still getting issues:

/data/media/clockworkmod/backup/2012-04-05.17.50.56 # ls -lh
-rw-rw-rw- 1 root root 5.0M Apr 5 17:51 boot.img
-rw-rw-rw- 1 root root 10.5K Apr 5 18:03 cache.ext4.tar
-rw-rw-rw- 1 root root 16.0E Apr 5 18:03 data.ext4.tar
-rw-rw-rw- 1 root root 5.0M Apr 5 17:51 recovery.img
-rw-rw-rw- 1 root root 326.6M Apr 5 17:51 system.ext4.tar
/data/media/clockworkmod/backup/2012-04-05.17.50.56 # du -hsx *
5.0M boot.img
12.0K cache.ext4.tar
2.1G data.ext4.tar
5.0M recovery.img
326.6M system.ext4.tar

This is a custom recovery I've built for the LG G-Slate v909. Thanks. :)
[Eee Pad Transformer General] partio:
to display the content of data.ext4.tar :

tar tvf data.ext4.tar

to extract :

tar xvf data.ext4.tar

to extract individual files from tar (picture.jpg example)

tar xvf data.ext4.tar picture.jpg
[Eee Pad Transformer General] dasunsrule32:
Eh, that's not what I'm asking. I understand how to do all of that. :)

As you can see, files over 2.1G show as 16.0E with ls. Basically, any tar file over 2G won't restore from tar. This also breaks nandroid from restoring the files correctly. I'm in the middle of testing using gzip rather than just tar.
[Eee Pad Transformer General] partio:
I see, but you can try to extract the tar to see if the problem is the tar, or is the recovery you are trying to restore the backup (I imagine you are trying to restore a backup you made in a recovery on a different one)
[Eee Pad Transformer General] disnomia:
It works, finally here is the solution

I also stuck with this recovery..............what a mess

Thank you partio and to everyone who make this fix possible!!
[Eee Pad Transformer General] sronweb:
I have the following problem after the installation of bad CWR causing recovery loop I have followed the instruction and then it was finally booting.

But currently I can only "cold boot" and even if apparently I can install a recovery from Rom manager (it update the version number) then when I reboot it stuck on Asus logo. Then there is no way to start from recovery anymore.

Please, I need some help to find the correct procedure before I brick the device.... Thank you
[Eee Pad Transformer General] sandroaw:
Can't boot into CWM

Hi,

I have a C10 sbk2 TF101 that I successfully rooted using the "unlockroot tool".

After that, I've installed the CWM apk but I can't go into recovery with CWM, only into the stock recovery.

Can anyone give me an advice how I'm doing wrong and what can I do?

I intend to flash the Android Revolution HD but without CWM I can't...

Thanks
[Eee Pad Transformer General] baseballfanz:
Not even the right place to ask your question. It has nothing to do with the topic. Search for RecoveryInstaller to install cwm
[Eee Pad Transformer General] eniac0:
Well here goes me looking silly.

i read most of the pages in this thread looking for a solution that will fix the bootloop on my TF101. i did find the post linking to this thread:

http://xdaforums.com/showpost.php?p=24266780&postcount=287

But here's the thing, the bad CWM fails to mount my sdcard. Most likely caused by one of my attemps at factory resetting the device. At the beginning i started by accepting the asus firmware update, it rebooted and thats where i realized there was a problem. so i tried using the CWM factory reset, flushed all possible cache and nothing fixed the problem obviously.

So the current status is that im stuck with the CWM 5.5.0.4 bootloop problem and it cannot read my sdcard, but I CAN coldboot, at least there's that.

It was easy enough to follow the guides on the net to root the TF but i realize at my own dismay that I'm about as n00b as they come on being able to fix my own mess.

Any ideas?
[Eee Pad Transformer General] gee one:
That is standard with cwm 5.5.0.4. That version only sees the internal sd card. Some of the other recoveries use both or just the external. This happens a lot more than it should- just be glad that you didn't super wipe everything first and then realize you had no rom and no system.

Use the cold boot into android and save whatever rom you would like to flash onto the internal sd card. I think it's called /sdcard. The external sdcard is /Removable/MicroSD/.

If you really want to redeem yourself, then you can use adb to push the rom to the internal sd card while in recovery.
[Eee Pad Transformer General] eniac0:
i wish it was that easy.

i can ADB while (cold) booted, but i can't adb while in recovery, im getting an error saying the device won't start (windows).

while in recovery, it cannot mount /sdcard, it gives an error. im not sure how to get to the microSD, its not really in the options i see.

i have installed terminal and im able to follow the instructions only starting from #4 here: http://xdaforums.com/showpost.php?p=24559092&postcount=6

but unless i find a way to flash while booted, i don't see how i can fix the bad cwm. possibly nvflash? but i just learned about it so i don't know how to use it just yet.
[Eee Pad Transformer General] gee one:
ohh, I see- you can't mount the internal sdcard. More details about the error would be helpful. You might be able to do this manually in recovery, but I forget which partition is the sdcard, perhaps /dev/block/mmcblk1p1 or /dev/block/mmcblk1. You have to find a mount point that cwm will see. google "man mount" if you need help with the syntax.

Try the commands in terminal and when rebooting to recovery, use the hardware buttons,not the menu/software. I do recall one other thread recently where someone was stuck and the usual fixed simply didn't work.

nvflash will work, but the sbk, secure boot key, is not available for all models. Search the forums for more info abou this to see if it's an option for you.
[Eee Pad Transformer General] dasunsrule32:
It's a busybox issue in cm9 apparently. In stericcsons busybox, issue isn't there. It exists in recovery and the OS.
[Eee Pad Transformer General] eniac0:
as i select "choose zip from sdcard" it simply says:

E:can't mount /sdcard/

id provide it the command to mount it myself but how am i supposed to do this? no adb or terminal access in recovery. (or is there an option i don't see?).

i followed step #4 in my previous post and was able to stop rebooting straight in recovery, but so soon as i tried to flash a firmware update (the one from asus) i got brought back to the same error. i get that i need to flash that recovery but im still stock trying to flash anything from the recovery menu.

ill try nvflash as a last resort, i feel as though im only missing a small thing using the current technique.
[Eee Pad Transformer General] gee one:
If you fixed the bootloops through terminal, then you can flash a new recovery through the staging partition. I think roach has an older one that is a zipped up blob file. Unzip and flash the blob to staging. After that, you can hopefully get back to a more sane system/recovery. There should be plenty of posts about the staging partition. Whichever recovery you use, make sure it will read your ext sd card and, ideally, the blob shouldn't have any else besides a recovery. I think roach's old 3201 will work.

The command from terminal is "dd if=/your/blob of=/dev/block/mmcblk0p4" then reboot. If it works you should see a blue progress bar and then have a new recovery.

Good luck.

sent from my transformer
[Eee Pad Transformer General] eniac0:
You totally saved my bony ass @gee one

for those in my situation that are still stuck.

1. I've re-run the terminal command to re-write the boot recovery flag (http://xdaforums.com/showpost.php?p=24559092&postcount=6)

2. reboot from terminal (without exit)

3. put this recovery on my microsd: http://goo.gl/RpVJ8

4. from terminal, i used your command "dd if=/Removable/MicroSD/roach3201/recoveryblob of=/dev/block/mmcblk0p4"

5. reboot from terminal (without exit)

6. (let the tab boot as usual to test there is no bootloop)

7. reboot again and enter recovery (pwr + vol down), then vol up.

8. tada! Roach's recovery 3201, as a proof that old and bac cwm is gone.

and now to ask another question.

Asus's firmware is available to upgrade my tab to 9.2.1.21 (i think). can i flash stock firmware and expect roach's recovery to pick it up? Or alternatively, what's my best way to upgrade to the latest firmware?
[Eee Pad Transformer General] khivang92:
can someone show me how to fix my problem ? I installed cwm 5.5.0.4 to my asus tf101. Now it has the "bootloop" error and I cant coldboot into my rom T.T

Thanks a lot.
[Eee Pad Transformer General] baseballfanz:
Can you get ADB working?
[Eee Pad Transformer General] CarlHutson:
probz in germany

i posted this prob on a big german android help homepage but it looks like noone can answer my questions. Please be kind to me, as im trying to wirte this problem "understandable" in english.

I really dont know how or where to start but what i can tell is: I flashed a CWM Update with Rom Manager and got stuck for a while, caus i didnt had the time to sit down and take some time to fix / search the net for this prob.

i think ill post an overview of what i know, what i CAN do and NOT :(

1st : I´ve got an ASUS Transformer TF101G - BA0KA . installed random Custom Roms all over the last months to test and find the best that fits me. Latest i was trying to take the CM9 nightlies and the last i updated was a nightly from the beginning of april (or so)...

#1- I CANT get into CWM anymore (dunno why) but i think its cause of an update error through ROM Manager. There was a popup with something that called "successful" though...

#2- I can cold boot into Android, but.... WHY EVER, i ****ing dont get it... i cant get any acces to my transformer, when i plug in usb cable...

#3- i cant start anything with ADB, because this . usb debug mode wont start, cause of #2-prob...

#4- booting into bootloader (volume down +POWER and wait) - and wipe... doesnt take effect..

#5 using those commands i found in the terminal .... doesnt take effect:

as well as those other comand... i cannot find right now... dont know where i found them, but i think they made the same ....

only thing is: with those commands: i can use the reboot command, and it successfull reboots, with loading androird directly after bootloader....

I was happy when this worked, but then i tried to get into CWM and PADOWWZ ---> same prob again...

#6 - APX Mode WORKS! i tried it and even installed the driver package form this stupid rootkit tool (sorry mate) , wich doesnt work for my TF101(G!!!!!) dafuq...

#7 i would have posted a pic of my "stuck screen" when i try to start CWM, but i am not allowed under 8 posts in this forum :(

i hope SOMEONE can help me....:(
[Eee Pad Transformer General] eniac0:
from the look of it, it seems you could use the solution i posted just a few posts above this one. if you can cold boot, that is all you need (and a micro sd card)

i was stuck in the boot loop, with no adb access from recovery.

use terminal emulator to push the rom into staging, then reboot. if you use the links i provided, it will reflash your recovery with roach2010's cwm 3.2.0.1 which is functional. from that point, you should have a "sane" system and be able to adb and do what you wish to do.

i can only vouch for the WW version, that is, my own TF. i don't know if i have a B80, B90 or BWhatever, i don't know where to read that info.

but the bottom line is: if you can cold boot, use terminal emulator to push roms to staging.

(edit)

i just re-read your post, you mention that the command of=/dev/block/mmcblk0p3 bs=1 seek=0 doesn't work. how did you do it? to me, it made a different if i exited or not prior to reboot. for mine to work, from terminal i typed reboot right after the mmcblk0p3 command.

if this command does get you rid of the bootloop, don't go into cwm yet! just reboot and let android boot normally. THEN use terminal to push roach's 3.2.0.1 recovery into staging (see my post a couple 4-5 posts before this). once you pushed into staging, you should be good to go. do try my steps one by one.

thats all i can do to help.
[Eee Pad Transformer General] khivang92:
I dont know how to use adb, so i'm using "nvflash" method.

when i open "download.bat" file, it close immediately.

my tf101 is b70 model.

how can i unroot my device ?

thanks.
[Eee Pad Transformer General] CarlHutson:
could u please explain me this command line in detail?!!?

i would really like to use the fixed 5.5.0.4CWM from roach of of his thread.

is this red marked position the zip file?! does terminal open it just as a folder, or what? "Removable/MicroSD/roach3201/recoveryblob of=/dev/block/mmcblk0p4"

---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------

could u please explain me this command line in detail?!!?

i would really like to use the fixed 5.5.0.4CWM from roach of of his thread.

is this red marked position the zip file?! does terminal open it just as a folder, or what? "Removable/MicroSD/roach3201/recoveryblob of=/dev/block/mmcblk0p4"

so would it be possible to replace that line with the new zip file - foldeR:

"dd if=/Removable/MicroSD/cwm_recovery-5504_roach-tf101-r2/recoveryblob of=/dev/block/mmcblk0p4"
[Eee Pad Transformer General] eniac0:
ok, im going to reply to my own post so we can have all the steps listed.

step #1 resets the boot recovery flag to 0 (fixes the bootloop). once you ran that in terminal, from your TF. type "reboot". normally, your TF will boot normally (not go in recovery)

the reason i chose to install roach's 3.2.0.1 is because it can mount the micro sd, whereas 5.5.0.4 can only mount the internal sd, but also because my goal was to install something that is proven to be stable.. 3.2.0.1 has been around for some time and roach himself still uses it, so its safe. the goal here is to get your recovery partition into something usable. you can chose the fixed 5.5.0.4 if you wish, but i really cannot say if it will install properly or not (because i haven't tried it). but like gee one said, whatever you choose, choose a rom that has only a recovery partition in it.

step #4 describes the exact line to use from terminal to copy the rom to the staging partition. on my micro sd, i had created a folder called "roach3201" in the root of the microsd and placed the blob called "recoveryblob" in it. the blob itself is in the zip file that you can download from the url of step #3. the "mmcblk0p4" part is the path to the staging, you can leave that as is.
[Eee Pad Transformer General] CarlHutson:
eniac0

"ITS WORKING!! ITS ****ING WOOORKIIIING!!"

even if you just copy pasted something, that was written by another guy.

YOU ARE MY HERO! if u got a life in any game like bf3 or something, feel free to contact me: vR4w
[Eee Pad Transformer General] eniac0:
good stuff, glad we sorted it out. in my experience, with this sort of problem, the real difficulty is finding the right version of the right file and doing things in the right order. sometimes its a small detail we missed.

personally ivve decided to revert to stock because i was greatly annoyed by this and realized that i dont really do anything that requires root at the moment.

i don't really have a life in a game world, i play some rocksmith and ufc 3 on the ps3, but that largely varies on what hot games are out now.

'til next time...
[Eee Pad Transformer General] czaplin:
That worked for me, too! Fantastic thread!

Thank you so much!