I have a verizon Samsung Galaxy tab. I would like to use clockwork recovery. The tab is rooted and I used ROM manager from the marketplace to flash the recovery for a Samsung Tab (Verizon). When I flash the ROM everything is successful. However, when I boot into recovery the Android System Recovery <3e> shell loads which doesn't allow nandroid backups etc... all the neat recovery tools that come with clockwork recovery.
I searched around the forum and saw a thread titled how to replace Android System Recovery with a Custom ROM. These were the commands
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
I went into abd shell I tried the commands but by the time I got to the third line I keep getting permission errors before I can even finish typing the command. I cut and paste the command string from "mount-->" thinking I just wasn't typing fast enough and it still doesn't work.
Is there another way to remove the Android system recovery so that ROM manager will work properly?
Have a look at installing boushh's kernel, it probably going to be the best option around for you.
Sent from my X10i using XDA App
I don't know what that is?
I have also same problem ı tryed many flashes ı coudnt fix it yet.if you allready fixed could you please share thanks.....
Related
Ok im a newbie, and i don't know nearly as much as any developer here but i've been doing my best to follow the rom updates for the g1. I have installed all the CM updates, and also before that the jesusfreke rom.
I installed this CM5 and while it worked well the battery was draining, i tried to reboot into recovery mode to do a wipe and reinstall to see if it would help, to my horror the recovery doesn't start it just stays in the G1 screen.
The phone boots into android fine, but won't let me get into recovery to change anything. I think this is due to the fact that i ran CM updater with a theme and might have been for 4.x? so it hanged but i thought it wasn't a problem.
I would greatly appreciate if anyone could help point me into were i should look, i looked every where and haven't found the right information or understood it.
Thanks.
ok guys im not sure why the recovery was taken out but i was finally able to get it back running this is what i did which i found in other sites.
from an old post in the forum :
"Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img "
I had a similar issue as op, I just reflashed the recovery through adb - since I needed to updated my recovery anyway - and it worked.
same problem
i tried typing into terminal emulater to get recovery back, is that what i need to do
help
what do you mean you reflashed throughn adb
help
tried typing commands into terminal emulator and still no recovery,what can i do ,help
I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.
I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!
MIne is Nexus one. It's just rooted.
http://forum.xda-developers.com/showthread.php?t=611829 the newest Ra recovery for n1 is here.
There was a note:
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android).
I tried on my n1 and I booted back to stock recovery......
How could I fix it?
philanini said:
MIne is Nexus one. It's just rooted.
http://forum.xda-developers.com/showthread.php?t=611829 the newest Ra recovery for n1 is here.
There was a note:
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android).
I tried on my n1 and I booted back to stock recovery......
How could I fix it?
Click to expand...
Click to collapse
after you flash the recovery, without rebooting, just run these two commands:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
gravufo said:
after you flash the recovery, without rebooting, just run these two commands:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
Thank you friend.
I used the fastboot-windows.exe in cmd to flashed the recovery ,and I don't know where to run your cammands.
philanini said:
Thank you friend.
I used the fastboot-windows.exe in cmd to flashed the recovery ,and I don't know where to run your cammands.
Click to expand...
Click to collapse
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Eeeeeek - sorry!
gravufo said:
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Click to expand...
Click to collapse
Thank you man! I will post the result.
gravufo said:
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Click to expand...
Click to collapse
Thank you my friend. I tried what you've told me, unfortunately,and it said not found there.
However, I tried MiuiRomInstaller.apk ,it flashed a clorkworkmod recovery. Then I flashed RA recovery back, luckily I succeeded!
I could use that change my rom now.
Thank you Gravufo.
philanini said:
Thank you my friend. I tried what you've told me, unfortunately,and it said not found there.
However, I tried MiuiRomInstaller.apk ,it flashed a clorkworkmod recovery. Then I flashed RA recovery back, luckily I succeeded!
I could use that change my rom now.
Thank you Gravufo.
Click to expand...
Click to collapse
Your welcome, glad it worked one way or the other
gravufo said:
Your welcome, glad it worked one way or the other
Click to expand...
Click to collapse
Man~I restored and tried your way again, This ok now.Thank you!
Just flashed my NC to Cyanogenmod nightly 11, it boots fine into the ROM but for some reason none of the google apps are there. I installed them through the CWM recovery menu, as well as the nightly build and the OC'd kernal.
Everything went smooth except the gapps arent there. So I go into CWM and tell it to boot into recovery and it reboots to a black screen, have to hold down power to get it to reboot and it will reboot into Cyanogenmod just fine.
I couldnt get the SD card to boot, I'm thinking that its not formatted to the zero bit. Gonna have to research on how to do this as I only have Win7 available to me at the moment. Any ideas here? Do I need to go back to stock?
I have CWM 3.0.0.9, do I need to downgrade?
I just tried to manually downgrade the CWM but I still get the same problems =/
adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push recovery-clockwork-3.0.0.8-encore.img /boot/uRecRam
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Any help would be appreciated, or if I'm just being a dumbass and can't search for crap let me know. Just want to get this fixed.
To continue my little thread with myself haha, I installed CWM 3.0.0.5 and now it works, so something must have happened with EXT4 and the boot sector. Just gotta work on getting my gapps.
Hope this helps someone...or at least makes you chuckle =p
make sure to read: http://forum.xda-developers.com/showthread.php?t=971197
the other day I realized that I did not have the OC kernel installed for CM7, so decided it was time to get that on there. I was unable to boot into recovery via ROM Manager or manually (using n+power). ROM manager was telling me 3.0.1.0 was installed, so I was a bit confused about why this was happening. I tried re-installing CWM via adb, that was a no go as well.
I then resorted to irc for help, people explained the proper way to use the key combo and then told me I was lying when I told them I didn't have the "touch the power of reading" splash
video of nook booting: http://www.youtube.com/watch?v=PGScwmoS7HU
so after a bit more poking and questions, found out the splash is within u-boot.bin, and somebody suggested I pull u-boot.bin from stock 1.1 image and push that to /boot.
Code:
1) download and unrar http://www.megaupload.com/?d=D7GFVHCQ
2) adb shell busybox mount / -o rw,remount
3) adb shell busybox mkdir /boot
4) adb shell busybox mv /boot/u-boot.bin /boot/u-book.bin-bak
5) adb push u-boot.bin /boot/u-boot.bin
6) adb shell busybox umount /boot
PROBLEM SOLVED. can boot into CWM after replacing u-boot.bin. I think this was related to attempting to format sdcard within CM7 on nook
So I have the same problem ... "Loading ..." screen and inability to boot into CWM after flashing with ROM Manager.
However your instructions are missing a step. You have the user creating the /boot directory with mkdir but not mounting /boot ... but at the end you have us umount /boot.
I sort of remembered this process from when I installed the HC pre-release, so I found my old bookmark. Following is your instructions with the missing step. Doing this made CWM load for me using power+N
Code:
# download and unrar http://www.megaupload.com/?d=D7GFVHCQ
adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
[i]adb shell mount /dev/block/mmcblk0p1 /boot[/i]
adb shell busybox mv /boot/u-boot.bin /boot/u-boot.bin-bak
adb push u-boot.bin /boot/u-boot.bin
adb shell busybox umount /boot
PS. I'm guessing this still isn't the RIGHT way to fix this issue, as I still can't get the reboot to recovery option working (I'm using CM7 nightly 39). However search function on the forums is offline, I'm very tired, and I'm about to go on a road trip early tomorrow so I'm not going to keep trying to fix it right now. If someone wants to post better info to get CWM 3.0.1.0 and ROM Manager working better for CM7 I'd love to see it. But I got my ALSA update installed so I'm happy for now
I've not been able to use Reboot into Recovery (from holding the power button) for a while now. However, the option from ROM Manager usually works, as does holding the n key while booting.