Hi Guys,
Please help me.
I could never download apps after 5 to 10 downloads. Doing factory reset was the only help.
So I replaced all my /system/app folder with nz apps using
http://forum.xda-developers.com/showthread.php?t=704817.
Now my launcher does not start. When I boot Galaxy S logo comes after that nothing. When I touch touch sensitive buttons they light up. Nothing comes on the screen. Just dark black.
However I can reboot to Android System recovery mode holding Home + Vol Up + Power.
I'm now trying to create a new update zip with my old apps directory.
However I don't know how to mount sdcard in recovery mode.
$ mount -w -t vfat /dev/block/mmcblk0 /sdcard
mount: Operation not permitted
$ mount -w -t yaffs2 /dev/block/mmcblk0 /sdcard
mount: Operation not permitted
$
Could anyone please help?
Following does not work either. Please help.
$ echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
cannot create /sys/devices/platform/usb_mass_storage/lun0/file: directory nonexistent
$
karunadheera said:
Hi Guys,
Please help me.
I could never download apps after 5 to 10 downloads. Doing factory reset was the only help.
So I replaced all my /system/app folder with nz apps using
http://forum.xda-developers.com/showthread.php?t=704817.
Now my launcher does not start. When I boot Galaxy S logo comes after that nothing. When I touch touch sensitive buttons they light up. Nothing comes on the screen. Just dark black.
However I can reboot to Android System recovery mode holding Home + Vol Up + Power.
I'm now trying to create a new update zip with my old apps directory.
However I don't know how to mount sdcard in recovery mode.
$ mount -w -t vfat /dev/block/mmcblk0 /sdcard
mount: Operation not permitted
$ mount -w -t yaffs2 /dev/block/mmcblk0 /sdcard
mount: Operation not permitted
$
Could anyone please help?
Click to expand...
Click to collapse
The only way you can update the system is through ODIN. It's not like HTC where you can use a zip file. Just get the stock rom use odin to put it on your phone and you will just need to start from scratch.
Hi psychoace,
Thank you very much. I will give it a try. At home Odin could not detect my phone on XP Prof. Will try on office Vista.
psychoace said:
The only way you can update the system is through ODIN. It's not like HTC where you can use a zip file. Just get the stock rom use odin to put it on your phone and you will just need to start from scratch.
Click to expand...
Click to collapse
Hi psychoace,
It worked like a charm, thank you for your guidence. However the Market still cannot download apps. All stuck at "Starting Download".
Regards,
karunadheera
karunadheera said:
Hi psychoace,
Thank you very much. I will give it a try. At home Odin could not detect my phone on XP Prof. Will try on office Vista.
Click to expand...
Click to collapse
thanks
Related
I get a bootloop on the seconds splash screen with the little green android popping out.
I've tried wiping and reflashing multiple times, as well as repairing the file system extensions. Sometimes, however, it gets to the third "HTC" screen, but then goes back to the green android popping out.
No luck. I'm coming from Cyanogen Mod 4.0.1
If anyone has any ideas, I'd appreciate it.
Thanks.
nasman1993 said:
I get a bootloop on the seconds splash screen with the little green android popping out.
I've tried wiping and reflashing multiple times, as well as repairing the file system extensions. Sometimes, however, it gets to the third "HTC" screen, but then goes back to the green android popping out.
No luck. I'm coming from Cyanogen Mod 4.0.1
If anyone has any ideas, I'd appreciate it.
Thanks.
Click to expand...
Click to collapse
did you wipe the ext partition?
you need too
Sorry for the noob question, but how do I do that?
Here be sure to follow this or this guide.
i wuld recommend u do the manual partition and only delete the ext2 partition and remake it for a lot more simpler process i.e only rm 2 n rm 3 after print so that your sd card files are not deleted
Dare{D}evil said:
Here be sure to follow this or this guide.
i wuld recommend u do the manual partition and only delete the ext2 partition and remake it for a lot more simpler process i.e only rm 2 n rm 3 after print so that your sd card files are not deleted
Click to expand...
Click to collapse
yup thats how i did it, but if you dont want to go through all that, you can follow these steps: http://forum.xda-developers.com/showthread.php?t=535797
1.) Turn on the phone holding the home key and power to boot. Attach the phone to your computer via usb.
2.) Wipe your phone from the menu in cyanogen
3.) Open console ALT + X and enter the following commands. Press "Enter" after each line. This wipes the ext partition.
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*
or this in adb
adb remount
adb shell
rm -r /system/sd/*
Click to expand...
Click to collapse
Note: this will delete your apps on your sd as well as userinit files or w/e was there
Code:
to backup your ext partition to your current directory: adb pull /system/sd/ %CD%\sdbackup
to restore back to sdcard: adb push %CD%\sdbackup /system/sd
the easiest way to wipe ext3 partition is in the recovery console with
Code:
mke2fs -j /dev/block/mmcblk0p2
that is all. one command. and all is gone.
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
My SGS shows the boot up screen/noise, then just sits on a black screen and vibrates occasionally
I'm able to press the 3-buttons and boot up into ClockworkMod Recovery, however nothing seems to fix it. I've tried applying update.zip, wiping cache, factory reset, loading the restore-update.zip, and "restore" to the only checkpoint, but nothing works.
I screwed up when installing a theme, these were the first part of the directions:
1. adb shell
2. su (grant su rights on your phone when asked)
3. mount -o rw,remount /dev/block/mtdblock3 /system
3. rm system/framework/twframework-res.apk
4. rm system/framework/framework-res.apk
5. rm system/app/settings.apk (if no file is found try Settings.apk ... no ide if it matters tho)
Click to expand...
Click to collapse
I got this far, then realized that the files I needed to replace those with were on the internal SD, but IN A ZIP. So I couldn't use them. RMing the old ones meant nothing worked anymore.
Now my phone is in debug mode, can't seem to get su access (although I can use adb to a limited extent), and I can't get it to work
Any help for me?
I have3 the same problem Have you found out how to fix it?
Looks like your going to have to use odin to reflash ive had this many atime from unsuccesful modding and always worked.
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.....
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.