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.
as well as those other comand... i cannot find right now... dont know where i found them, but i think they made the same ....
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.
i would really like to use the fixed 5.5.0.4CWM from roach of of his thread.4. from terminal, i used your command "dd if=/Removable/MicroSD/roach3201/recoveryblob of=/dev/block/mmcblk0p4
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.
i would really like to use the fixed 5.5.0.4CWM from roach of of his thread.4. from terminal, i used your command "dd if=/Removable/MicroSD/roach3201/recoveryblob of=/dev/block/mmcblk0p4
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 bad cwm is gone.
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
I Installed cwm recovery today... tried to flash a custom rom 2-3 times
but nothing happens. i have attached an image of the recovery when it starts it had an error-mics not found E...... something like that the error is in the attachment kindly find whats the problem and give a solution of it............. looking forward for the solution...
What's this in clockworkmod?
E:can't find misc
E:can't mount /cache/recovery/command
E:can't find misc
E:can't mount/cache/recovery/log
E:can't open/cache/recovery/log
E:can't mount/cache/recovery/last_log
E:can't opent/cache/recovery/last_log
E:can't find mics
PLease help me clockwork is doing nothing no restore no backup no wipe dalvik cache and no flashing it only says successfully installed need to reboot but after rebooting nothing happens #HELP
while booted into CWM 5.5.0.4 ...
step 1: use adb to push a good recovery [I used Rogue XM v1.3.0 (CWM-based v5.0.2.7)]***
step 2: flash the zip
step 3: use the adb shell to execute the following command
*** Do not flash stock recovery. There is no good reason to do it (stock recoveries are generally pretty useless) and you are flirting with trouble if there are signature checks that your custom components might fail. Use trusted custom recoveriesCode:echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
I'm not sure what that partition is, but it might be as simple as something like echo boot | dd etc... or whatever the correct boot flag is. Not sure if it has to be done in the rom or the recovery, but it seems this would reset the command?
Edit: just tried it from the rom of my un-borked tf and now I have recovery bootloops. Will try a cold boot and clear.
sent from my cyanogen(mod) vision
Edit: from terminal, I typed
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
And it rebooted to the rom...
It might require more testing- I wasn't using the bad cwm version, but it seems promising. I'm not sure if there will be other worse effects, like no access to recovery!
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mkdir /btmac
mount /tmp /tmp tmpfs
mount ext4 /dev/block/mmcblk0p1 /system wait
# mount ext4 /dev/block/mmcblk0p1 /system ro remount
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache
mount ext3 /dev/block/mmcblk0p4 /staging wait nosuid nodev
chown system staging /staging
chmod 0770 /staging
mount ext4 /dev/block/mmcblk0p7 /data wait nosuid nodev
chown system system /data
chmod 0771 /data
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache