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.
Related
Is this an efficient method of moving apps to SD? Apparently, it works anywhere from an hour to a few weeks but eventually crashed my phone and I have to wipe and flash.
In terminal emulator
busybox cp -a /data/app /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
Then in Recovery Terminal (Alt+X on JF menu in Recovery Mode)
mount data
rm -rf /data/app
ln -s /system/sd/app /data/app
rm -rf /data/data (optional)
ln -s /system/sd/data /data/data
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
reboot
The method is so simple and works well, that is until it breaks . Apps2SD never seems to work right for me. I will read up on the other methods but I would like to know why this doesn't work well and if there is something I can add to this to make it work better.
aaronratner said:
Is this an efficient method of moving apps to SD? Apparently, it works anywhere from an hour to a few weeks but eventually crashed my phone and I have to wipe and flash.
In terminal emulator
busybox cp -a /data/app /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
Then in Recovery Terminal (Alt+X on JF menu in Recovery Mode)
mount data
rm -rf /data/app
ln -s /system/sd/app /data/app
rm -rf /data/data (optional)
ln -s /system/sd/data /data/data
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
reboot
The method is so simple and works well, that is until it breaks . Apps2SD never seems to work right for me. I will read up on the other methods but I would like to know why this doesn't work well and if there is something I can add to this to make it work better.
Click to expand...
Click to collapse
Why don't you just download a ROM that already moves everything to the sd for you?
I'm all ears. Which ROM do you recommend? Link? I like JF but am open to suggestions.
aaronratner said:
I'm all ears. Which ROM do you recommend? Link? I like JF but am open to suggestions.
Click to expand...
Click to collapse
Cyanogen's ROM. http://forum.xda-developers.com/showthread.php?t=537204
alritewhadeva said:
Cyanogen's ROM. http://forum.xda-developers.com/showthread.php?t=537204
Click to expand...
Click to collapse
Def cyanogen's.
Downloading and flashing now. Thanks.
aaronratner said:
Downloading and flashing now. Thanks.
Click to expand...
Click to collapse
no problems, we're happy to help.
No problem Be sure to wipe just in case
Interesting ROM. I wiped and flashed. It is not seeing my partition. My phone storage is at 40MB. My partition is ext2 and I suspect that it needs to be ext3. Is there a way I can reformat the SD card via the phone (this is how I did it originally using Apps2SD). I am using my class 6 8GB card for this (I will eventually move back to my 16GB once I get the process right). I have ~600MB on my ext2 partition but it's only showing that there is 12K using "df system/sd" in TE. My previous data that I had moved there using the method that started this post in no longer there. Before I drive myself crazy reading everything about this (which I will do tonight when I have more time to dedicate to it), perhaps there is a quick answer.
Do you have cyanogen's latest recovery? 1.4? IF you do try upgrading to ext3. In recovery console
upgrade_fs
reboot
While trying to get cyanogen's latest recovery on the phone I erased my old recovery from the phone as per this post http://forum.xda-developers.com/showthread.php?p=3915123 by cyanogen (first post). Now I cannot get his recovery image since when I use Home+Power it takes me straight to the Recovery Console as though I used Camera+Power. I can connect to my pc via USB and fastboot is working but it will not let me flash the recovery image to the phone. Am I screwed?
aaronratner said:
While trying to get cyanogen's latest recovery on the phone I erased my old recovery from the phone as per this post http://forum.xda-developers.com/showthread.php?p=3915123 by cyanogen (first post). Now I cannot get his recovery image since when I use Home+Power it takes me straight to the Recovery Console as though I used Camera+Power. I can connect to my pc via USB and fastboot is working but it will not let me flash the recovery image to the phone. Am I screwed?
Click to expand...
Click to collapse
can you normally power up? Just hold power
Okay. Thank God for Nandroid. LMAO. I was able to load an old Nandroid backup to the phone so I can get get to JF's recovery utility. I would like to flash cyanogen's latest recovery to the phone. What is the best way to do that? Can I use My Android Manager 0.5.1?
aaronratner said:
Okay. Thank God for Nandroid. LMAO. I was able to load an old Nandroid backup to the phone so I can get get to JF's recovery utility. I would like to flash cyanogen's latest recovery to the phone. What is the best way to do that? Can I use My Android Manager 0.5.1?
Click to expand...
Click to collapse
Told you nandroid was handy! Just place cyanogen recovery on your sdcard and type this in terminal emulator
su <wait for #>
flash_image recovery /sdcard/cm-recovery-1.4.img
reboot recovery
enjoy new recovery!
aaronratner said:
Okay. Thank God for Nandroid. LMAO. I was able to load an old Nandroid backup to the phone so I can get get to JF's recovery utility. I would like to flash cyanogen's latest recovery to the phone. What is the best way to do that? Can I use My Android Manager 0.5.1?
Click to expand...
Click to collapse
the adb commands, you can't really mess up
adb shell flash_image recovery /sdcard/cm-recovery-1.4.img
I truly apologize. I am doing this half-assed. I normally read a thousand threads before I do anything to my phone. I decided to do this on a whim while eating dinner. Probably not the best idea. Anyway, I think I got it working OK for now but I do want cyanogen's recovery and apps to sd working properly. I re-flashed cm 3.6.8.1 until I can properly sit down and figure things out. After never posting anything on a forum in my life this is suddenly my 17th in a few days.
aaronratner said:
I truly apologize. I am doing this half-assed. I normally read a thousand threads before I do anything to my phone. I decided to do this on a whim while eating dinner. Probably not the best idea. Anyway, I think I got it working OK for now but I do want cyanogen's recovery and apps to sd working properly. I re-flashed cm 3.6.8.1 until I can properly sit down and figure things out. After never posting anything on a forum in my life this is suddenly my 17th in a few days.
Click to expand...
Click to collapse
That's how it starts, I started at like 4 Posts over a year, then all of a sudden, I got sucked in and now look at me... 472 Posts... T_T
aaronratner said:
I truly apologize. I am doing this half-assed. I normally read a thousand threads before I do anything to my phone. I decided to do this on a whim while eating dinner. Probably not the best idea. Anyway, I think I got it working OK for now but I do want cyanogen's recovery and apps to sd working properly. I re-flashed cm 3.6.8.1 until I can properly sit down and figure things out. After never posting anything on a forum in my life this is suddenly my 17th in a few days.
Click to expand...
Click to collapse
Well I hope you can get this working, good luck! Lol I almost have 1,100 posts in 4-5 months
I will get CM3.9.1 w/Recovery 1.4 on my phone tonight (somehow). I will read everything first and I don't think I will have an issue. So far, the only thing I need to figure out is how to get the recovery 1.4 on the phone. Other than that, CM3.9.1 looked really nice for the five minutes I had it on my phone. Looking forward to it and stay tuned as I muck up my phone some more. LOL. Will post if I have issues.
Thanks for your extremely fast responses. They are much appreciated.
Cyanogen 3.9.2 is out btw
is there a guide anywhere on this or could someone give me a rough guide?
Do I need to format the partitions I made on my SD to run Hero, when flashing to another ROM that uses APPS2SD like Soulife's Rogers? I'm getting untold weird problems with this ROM - syncing etc.
Also, looks like APP2SD might not be working - 45MB free space is this right?
(For the record, all I did was a 'wipe' and then flash - which didn't seem to get rid of most apps)
Thanks!
You need to wipe your ext partition before switching roms.
That will get rid of the apps that stayed.
Hmm.. I digg my double post even though I only clicked once. Thx xda
can you wipe with the 'repair ext filesystems' option in cyanogens bootloader?
didn't seem to work for me. :?
with adb:
adb remount
adb shell
rm -r /system/sd/*
reboot recovery
then flash the update
thanks!
when I do
rm -r /system/sd/*
I get:
cannot remove '/system/sd/*': No such file or directory
So I guess there's nothing there anyway? ... looks like it when I 'ls' the directory anyway... confused as to why my apps keep on showing up after flashing ???
what a minute I adb'd in when it was in bootloader mode would that effect what I see?
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
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 was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
wolffboy212 said:
I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
Click to expand...
Click to collapse
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Do "Method one: Eight interrupted Boots" and post what happens afterwards
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Geezer Squid said:
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Click to expand...
Click to collapse
Paul22000 said:
Do "Method one: Eight interrupted Boots" and post what happens afterwards
Click to expand...
Click to collapse
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
wolffboy212 said:
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
Click to expand...
Click to collapse
I had the same thing happen. I tried plugging it into my Macbook, but nothing happened. I plugged into my Windows PC, and it came back to life.
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Syco54645 said:
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Click to expand...
Click to collapse
i have a nandroid back up and i cant get into recovery mode.
Because you deleted boot. Use a nookie froyo SD card and put the contents of boot back manually.
wolffboy212 said:
i have a nandroid back up and i cant get into recovery mode.
Click to expand...
Click to collapse
Which button combo are you trying to use to boot into recovery mode? If you haven't already, make sure you're using the three-button method.
Sent from my Nooted friend...
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
It is not three buttons. Only need home and power.
wolffboy212 said:
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
Click to expand...
Click to collapse
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Syco54645 said:
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Click to expand...
Click to collapse
Bare with me I know very basic unix and linux commands but I do have the brain capacity to figure things out (not boot partitions).
I was on the command line and I couldn't get into the nook color stuff just the nookie froyo stuff on the sdcard.
suggestions?
Please read CW recovery thread. All answers are in there!
Really, please take time to browse through existing threads before posting questions which have already been answered several times.
Anyway, considering the number of people asking, here goes:
Note: You can do all this from the Nook, without the need of ADB, except for the fact that you will need gapps on nookie in order to install terminal and root explorer (although you could install those apps by directly installing APK's), see http://nookdevs.com/NookColor:_Nookie_Froyo_Tips, Third-party app support
Please read entire thread before attempting anything!
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
OR,
If you're able to access ADB (available when booting CW recovery and mounting /system and /SDcard, format from android required on SD to work here), CREDIT GOES TO Duloz, try this:
adb push uRecRam.bak /sdcard/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /sdcard/uRecRam.bak > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Click to expand...
Click to collapse
Note: Don't worry about errors concerning unmount.
If you're not back in business, post your questions, being very clear about what worked and what didn't.
Thank you.
Sent from my HTC Desire using XDA App
Back from Clockwork Recovery to Virgin (Factory) Recovery ... works like a charm!
samuelhalff said:
Please read CW recovery thread.
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
Click to expand...
Click to collapse
Works perfectly, thanks! I actually used adb instead of root explorer to do the copy and mount (etc.) commands, and did a manual 8-times power start interruption, but essentially the same. This made my poor "sound-failing" Nook a virgin again so I can swap it out at the store today. Crossing fingers that they will provide quick and easy exchange service (and let me test the sound on the replacement before I leave the store!)... Then, back to Autonooking (and even back to Clockwork Recovery...) again; now that I know how to go back and forth.
Owe you (or y'all) a beer!