yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] erdinc:
I used to partition my SD card manually but since I can't use upgrade_fs to upgrade from ext2 to ext3

I have uesd Amon's RA to partition my SD Card ( 16GB , 1024 EXT , 96 SWAP ) I've also upgraded ext2 to ext3 then to ext4 .

The problem I'm having now is that my apps are staying in my phone's memory . I used to have round 54 MB free now I have 29 MB free With the same apps .
[G1 Android Development] jakijal:
u sure its the apps? seems a little weird. unless you changed your spl or maybe all the cache build-up.
[G1 Android Development] rumsey:
Hey Amon, I'm hoping you can still help me with this problem. The original post is here: http://xdaforums.com/showpost.php?p=5544710&postcount=1186

I've attached the recovery.log, however it doesn't contain any info whatsoever after the nandroid backup begins as far as progress. I'd like to find out what could cause a never ending inflatable data.img but I don't know what log would show that. It seems to be looping somewhere, somehow.
[G1 Android Development] dumfuq:
I had something similar happen to me once. The lost+found directory on the partition in question thought it was 2T. After deleting everything in it everything worked fine.
[G1 Android Development] rumsey:
Thanks for the heads up, I'll try deleting everything from /data/lost+found and /system/sd/lost+found (im not even sure how or why this second one exists) and try again. By the way, what does "thought it was 2T" mean?

edit: I've tried to remove all the files and folders from lost+found and my explorer crashed. It continued to crash any time I tried to browse that folder again. I opened a terminal and tried to ls the folder and instead of a ls with nothing like you would expect I got the following message: ls: ./d25022b1: No such file or directory so this could indeed be causing some kind of issue. My first thought was to delete lost+found entirely and recreate it with the same permissions but any attempts to delete it just seem to hang. Any ideas?
[G1 Android Development] dumfuq:
2T = 2 terrabytes (not even possible)

use adb

adb remount
adb shell
rm -rf /data/lost+found/*
[G1 Android Development] rumsey:
You're right! It's the lost+found folder. It shows up as empty with an LS but i did an LS of the entire /data/ dir and this was the result: http://pastebin.com/hCxN6XpL

Look at 6121 on. lost+found loops forever. Is there a way I can delete the folder successfully completely and recreate it?
[G1 Android Development] dumfuq:
you shouldn't have to delete the directory, just the contents. I think I actually had to 'rm -rf' more than once in succession on the same directory. Might have even had a reboot in there too, I don't really remember.
[G1 Android Development] rumsey:
I found the culprit

2.0T /data/data/com.android.browser/cache/webviewCache
[G1 Android Development] erdinc:
Yes I'm sure it's apps2sd , I haven't changed anything same spl same rom build , just a new sd card
[G1 Android Development] dicer42:
I got an error when mounting my /data:

[ 2539.095092] yaffs: dev is 32505861 name is "mtdblock5"

[ 2539.095153] yaffs: passed flags ""

[ 2539.095184] yaffs: Attempting MTD mount on 31.5, "mtdblock5"

[ 2539.128601] Checkpoint read object 1545 type 1 chunk 33336 does not match existing object type 3

[ 2540.559753] yaffs tragedy: Bad object type, 1 != 3, for object 2126 at chunk 15777 during scan

[ 2544.319458] yaffs tragedy: Bad object type, 1 != 3, for object 1545 at chunk 33336 during scan

[ 2545.564971] yaffs_read_super: isCheckpointed 0

[ 2549.124267] save exit: isCheckpointed 1

This results in mkyaffs2image (when using nandroid) writting endlessly onto the sdcard. data.img just gets larger. any ideas how I can fix this without wiping?

There doesn't seem to be a yaffs2.fsck on the recovery. Any chance of finding those 2 files by hand?
[G1 Android Development] xaueious:
I think something similar happened to me the other day too. Trying to make nandroid results in nandroid trying to make a data.img file until my SD card was filled completely (several gigs worth of space).

I resolved my problem by running:

fastboot erase userdata

I think fastboot erase also does some sort of low-level format, so give it a shot.
[G1 Android Development] G1ForFun:
Sooo I know you can jump to console and then type "recovery" and go back to recovery. But then when you want to go back to console, it just hangs.

Is that normal...?

To clarify....Recovery.....Console......Recovery......(Attempt to go to Console but hangs)
[G1 Android Development] dicer42:
That would probably resolve my problem, but would also delete my complete /data partition, right? That is exactly what I do not want to do without a working backup ;)
[G1 Android Development] blackjackboy:
You know what would make this awesome? A wipe all function. One click to wipe everything. Also, you could include ext repairing too in that same function. Just a suggestion.
[G1 Android Development] arefin:
Please Answer

I have seen this questiom beinmg un-answered, at least I expect something from the developer of this great peice of software - a simple "I dont know" will also make me happy

The thing is: I have three backups on my sdcard/bart folder.

whenever I try to switch to any ROM other than the latest one, I get an error: something like nandroid restore could not be performed due to some error and I should take a look at the system/sd/nandroid.log to know the cause. Problem is this nandroid.log never existed in all my attempts, I have tried 'cat .... system/sd/nandroid.log' and so on...but no veil.

I could do this even a few days back when on 1.5.2, this does not work with 1.6.2, so I went back to 1.5.2 again but it does not work either!

Its a good problem at least to have been answered....

did I mention that this script is great?! well if not then I must say, its awsome, great work there!!
[G1 Android Development] jakijal:
i think it is that way because you never really did anything to fully close/exit console. so it doesnt really open up properly.
[G1 Android Development] Firerat:
recovery&exit

;)

will let you go back to recovery, and then back to the console without having to reboot
[G1 Android Development] Amon_RA:
Right after you get the error :

cat /cache/recovery/log

or

use the option "move log to sd" from the menu , you can find the logfile on the fat32 partition on you sdcard => /sdcard (not system/sd)
[G1 Android Development] toeshot:
go into your sdcard, I suggest via computer but not necessary, go into the bart folder and go into the nandroid folder. rename the backup folder to original name be removing the nandroid appendices. For example you named your backup MyBackUp when nandroid makes it's backup it adds -xxxxx-xx (something like that)

making it MyBackUp-axcfd-2313123

remove everything after the name putting it back to MyBackUp

should work then
[G1 Android Development] toeshot:
Sounds like Apps2SD isn't running. do you know if it is built into the rom you're running or have you tried downloading the A2SD script?
[G1 Android Development] jj71787:
I accidently messed up my sd card so now i repartitioned my sd card with 512mb on ext4, 408mb on fat32, and 95.8mb on swap.The apps are not saving on the sd card. How can i get the apps back on the sd
[G1 Android Development] jj71787:
anyone?

10char
[G1 Android Development] dumfuq:
If the order you listed them is the order you partitioned them in, then that's your problem.
[G1 Android Development] philosophics:
Hey mang, what if I wanted .... a different recovery background image?

Carebears are cool and all but....

I'm willing to do the grunt work so don't worry about holding my hand...
[G1 Android Development] DroidDavi:
before you guys get mad im a noob i know but i dont want to F up my phone so yea

i have the 1.5.2 version of amon ra if i wanted to update to this i would just go to the current recovery img then USB-MS toggle move it to my sd card and just flash it just like i would flash a rom ?

and help will be thanked
[G1 Android Development] philosophics:
no.

put the recovery.img on to the root of your sd and type in the terminal emulator

$su

#flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img

#reboot-recovery
[G1 Android Development] G-Fetus6:
after i did a wipe. the image for the care bare just went away. the words are still blue, but the picture went to the HTC pic
[G1 Android Development] gadget421:
can you use bart, then put the saved bart file on a different phone?
[G1 Android Development] Amon_RA:
You would need to unpack the recovery img, just like you would unpack any other boot image, replace the background image, and repack it. :-)

Unpack and repack scripts are posted on xda.

You could also just pm me your image and I could make one for you if I find the time :p
[G1 Android Development] philosophics:
Hella! That would be cool cause I tried to do it once but didn't want to mess anything up. When I find the image I want, I will let you know mang.

Thanks!
[G1 Android Development] badbob001:
With CM5 coming to the Dream with the new Apps2SD method, I suppose we would need to wait for a new Recovery version to support that?

UPDATE: ok, checked the nexus-specific thread. Development has stopped. :(
[G1 Android Development] W.O.P.R:
Flash via ADB and got the following:

/ # mount -a

mount -a

/ # flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img

flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img

flashing recovery from /sdcard/recovery-RA-dream-v1.6.2.img

mtd: erase failure at 0x003e0000 (Input/output error)

mtd: erase failure at 0x003e0000 (Input/output error)

mtd: skipping write block at 0x003e0000

/ #

I was coming from 1.5.2. I rebooted after I got the failure's above and went back in to the recovery console and it says it is at 1.6.2 and I see all of the options listed in the initial post, so the failure seems to be nothing, or is it?
[G1 Android Development] bert269:
Any idea of how to get RA-1.6.2 to backup CM 507 ext partition??

Guys - any idea on how to backup the ext partition with Nandroid + ext option (or something similar) with RA-recovery on CM 507?

Thanks for feedback.
[G1 Android Development] quierotacobell:
Use BART from the console, same thing.
[G1 Android Development] bluedragon1982:
hey, can you update your recoover for CM5.0.7 that you will be able to backup and restore /sd-ext (the A2SD that cyanogen implemented)b please
[G1 Android Development] rhondalicious:
NM, android 2.0 issues.
[G1 Android Development] quierotacobell:
Just create a directory "/system/sd" and you're set. Or you can use bart.
[G1 Android Development] secure_6:
BART not working (for me) either

I read (thru the posts) that I'm not the only one unable to Nand+ext backup..

I tried using Bart instead.. the msg I'm getting is "run Bart thru the console...

Embarrassed to ask... but.. how do I do that? I know, I know... I feel like a noob enuf...lol

Any help is and will always be appreciated.
[G1 Android Development] Firerat:
go to console ( second option or alt+x )

mount /system
mkdir /system/sd
umount /system
recovery

assuming you are on a cm5 based rom, that will 'fix' it
[G1 Android Development] zimphishmonger:
Any chance of updating this recovery w/ the newest BART?
[G1 Android Development] secure_6:
THANK YOU

A big thanks!! that did the trick!!!!
[G1 Android Development] Firerat:
I've not looked , but isn't it just a case of unpacking the ramdisk and repacking with the updated script?

I've got the source code somewhere, I suppose I could have a look and see if the bart is coded into the bin, or just calls the script
[G1 Android Development] dumfuq:
there's actually repacked ones for dream and sapphire at the end of the bart thread.
[G1 Android Development] lolmensch:
sry for that noobish question. i know its dumb but I have no idea:

mounting ... failed: Device or resource busy

EDIT: Solved. had to switch off phone totally. not just reboot.
[G1 Android Development] Just_s:
apps2sd

I'm LOST as a n00b can be.

This recovery is NOT yet fully compatible with the new apps2sd method! (as implemented in CM5.0.7)

So does this mean that I cannot use apps2sd at all or that I have to do some sort of work around? Mostly, I just want to know how I can use/access all of the apps I downloaded when I was on Cyanogen 4.2 (yesterday). I moved to CM-5 this a.m. and all was working great. Then I decided to change SD's, using Amon Ra 1.6.2 to partition the new SD, but now I can't enable apps2sd in the settings and don't know how to do much else. I moved everything from before onto my new SD via USB after partitioning, but I have no idea how to access any of that from my G1 now. It used to "just work".

I followed the tip from firerat...

go to console ( second option or alt+x )

Code:

mount /system

mkdir /system/sd

umount /system

recovery

...but I don't even know what that did or what I would do next. I'd even go back to before I flashed Amon Ra 1.6.2 if that would work, but I don't know how to do that either.

Ultimately, I would just like to be on Cyanogen 5, be able to use all of my downloaded apps and have them all stored on my newly partitioned 16GB SD. It was all working fine this a.m. on my 2GB SD before I flashed Amon Ra 1.6.2

Any help?

-Lost N00b :confused:
[G1 Android Development] Jason_V:
After doing this, you can use BART in the Recovery Console. I downloaded the latest BART (1.3.1) and moved it into the /sbin/ folder and ran it in recovery. When you reboot you will be back to the recovery's version, rather than the new one, but you can do the same thing over again to gain the newer feature set.
[G1 Android Development] Sleeepy2:
now that you have made the /system/sd folder you can just use Amon RA 1.6.2 like normal.

Select the backup/restore option and then Select nadroid + ext.

It will work just like it should.
[G1 Android Development] TCDroid:
can't flash v1.6.2

I've had 1.5.2 for awhile and i'm just now getting around to flash v1.6.2. the problem is that I put it on my sdcard and tried to flash via console Entered everything correctly. It says flash was successful but after a reboot my recovery image is still v1.5.2. i tried doing this via console and the terminal any ideas? because at this point i haven't a clue. BTW i did have this same issue when coming from v1.3 to 1.5.2 i ended up unrooting and rerooting to get it on there. I just don't want to have to go through that whole process every time there's an image update. :( Thanks for any advice you have;). OH i forgot i'm running cm-5.0.7 , latest radio, 4gb cl6 ext3/swap on G1
[G1 Android Development] Adam182:
im trying to flash the latest version onto my phone and just keep getting the error that the file and directory dont exist, any ideas? im definatly typing it in correctly aswell - Adam
[G1 Android Development] Firerat:
where and what are you typing?

I'm going to guess, the recovery console, and your not typing

mount -a

first
[G1 Android Development] Adam182:
im typing flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img in the recovery console, if i type mount -a it just gives me some dumb error and ive read i dont need to even type it - Adam
[G1 Android Development] Firerat:
what is the 'dumb error' you get?

oh , btw , you read wrong, or you read incorrect advice

you *do* need mount -a , you can't find the file /sdcard/recovery-RA-dream-v1.6.2.img, because /sdcard is not mounted

I'm going to guess you have CM5, and the error is because the ext partition can't be mounted

mount -a
mkdir /system/sd
mount -a

would fix it ( assuming it is cm5 )

and save yourself some typing

flas<tab> recovery /sdc<tab>reco<tab>

where <tab> is <alt> then q
[G1 Android Development] Amon_RA:
Updated to v1.7.0-test1

I've updated the recovery so it supports the new app2sd method (using /sd-ext instead of /system/sd) as implemented in CM v5.0.7.

This is a test version for the G1/Dream only (Rogers Dream will be posted once stable), please let me know if you find any bugs.

Download :

recovery-RA-dream-v1.7.0-test1.img - MD5Sum: 14c2cce5127161cdaebd64330a25bba9

Changelog :

- Fixed some minor bugs
- Recovery and scripts use /sd-ext instead of /system/sd as mountpoint to support the new apps2sd method (implemented mostly by Chris Soyars)
- Added an option to backup/restore Google proprietary Android system files (backuptool.sh written by Cyanogen)
- Removed "move apps2sd"-option as it's not needed anymore with the new apps2sd method
- Updated BART to v1.3.1 (updated by Dumfuq to support /sd-ext)
- Added a wipe cache only option
- Nandroid now backups/restores /cache again by default
- Dalvik-cache wipes /cache/dalvik-cache now
- Removed SDCARD: prefix in output when chosing zip to flash
- Changed colors and background to Cyan
[G1 Android Development] th3k1d:
Flashing now!

Do you mind if i put some mirrors up for the file? rapidshare is really unusable at certain times..

EDIT

Flashed and backed up both nand+ext and proprietary apps with no errors, seems to work fine for me! :)

also heres a mirror: recovery-RA-dream-v1.7.0-test1.img
[G1 Android Development] Sleeepy2:
Forgot that I am on rogers and flashed this recovery. doh. flashed the 1.6.2R

back. lol

waiting for the rogers version ;)
[G1 Android Development] xaueious:
Does this fix the background reverting to HTC after flashing update.zip as well?

Wipe cache only is what we have needed for the last few Donut ROMs.
[G1 Android Development] revwillie:
I searched and found this post with apparently no answer. I tried to flash 1.7.0 and it got out of memory errors. Also, my recovery is totally gone now. Can't recover backups to get it back since I need recovery to recover backups.
[G1 Android Development] Boomgawd:
waiting patiently for 1.7.0R

Super news! Thanks for comming back to update your recovery!

simply the best!
[G1 Android Development] rgv151:
try to flash again, and it works
[G1 Android Development] revwillie:
tried five times. same error
[G1 Android Development] DroidHead:
Re: [Recovery] [02-Mar-2010] RA-dream-v1.6.2 (also for the Rogers Dream)

I am having the out of memory problem too... tryed 15 different ways to flash with no help or resolution.

Anyone have an idea?

-------------------------------------

Sent via the XDA Tapatalk App
[G1 Android Development] revwillie:
Cyanogenmod.com forum thread

Can you install and run ROM manager? ClockWork Recovery Thread
[G1 Android Development] alongenemylines:
I also received out of memory error, but it seems the recovery flashed just fine. I've been in and out of recovery console a few times, and have had no issues.
[G1 Android Development] jdh2001:
I also got the memory errors when I tried to flash this. Rebooted into recovery and got stuck on the splash screen. I rebooted and re-flashed the recovery a 2nd time with no errors.
[G1 Android Development] Proxin:
Weird, 1.7.0 worked flawlessly for me with no memory errors. It restored and backed up nand+ext properly as well.

The only thing I would prefer is a 'stock' theme for it again... like Recovery 1.6.2. I really prefer the generic HTC logo and green font, don't know why.
[G1 Android Development] revwillie:
yes, the low memory thing is strange. I seriously chewed through two and a half charged batteries today flashing and reflashing, but now all is fine.

It got 1.7.0 to flash and it works nicely. I guess I need the new features being on CM 5.0.7 test builds, but I sure do miss grumpy eclair bear. Here's my vote to bring him back once 1.7.X is out of 'test'
[G1 Android Development] philosophics:
What's up with the blue mang?
[G1 Android Development] Neejay:
THANKG GOD I'm not the only one!!! I made a post about this last week and didn't really get too many replies. It seems you have to keep trying for some reason for it to finally flash...
[G1 Android Development] Firerat:
all you need to do is make /system/sd

thats it, even ra 1.5 would work
[G1 Android Development] Ohsaka:
Are people with the memory error trying "fastboot erase recovery" first?
[G1 Android Development] AustinAce:
I say the next recovery image should have chuck norris on it lmao

Chuck Norris's G1 never bricks.
[G1 Android Development] Boomgawd:
+1 Grumpy Eclair Bear

When the 1.7.0R is release, how about that grumpy eclair bear!

;)
[G1 Android Development] Boomgawd:
LOL @ Chuck Norris Jokes!

LOL @ Never Bricks!
[G1 Android Development] Amon_RA:
Out of memory problems

Out of memory problems probably mean that you have some bad blocks in your recovery partition. Because of these bad blocks you don't have enough space to flash this recovery.

You can check the amount of bad blocks by running the following command in recovery (adb or console) :

# dump_image recovery /sdcard/recovery.img

You have bad blocks if you get output during the dump like these :

mtd: MEMGETBADBLOCK returned 1 at 0x02700000 (errno=0)

mtd: MEMGETBADBLOCK returned 1 at 0x03160000 (errno=0)

If you don't have any output during the dump your recovery partition has no bad blocks.

You can also try :

- copy recovery-RA-dream-v1.7.0-test1.img to the root of your sdcard

- on your pc : fastboot boot recovery-RA-dream-v1.7.0-test1.img

- via adb or console : flash_image recovery /sdcard/recovery-RA-dream-v1.7.0-test1.img
[G1 Android Development] W.O.P.R:
Worked for me, at least the flash. Have not tried any of the functions yet.
[G1 Android Development] Neejay:
I got it, using the usual SAME commands I've been using. Didn't do anything different.

It flashed perfectly, but it was random as hell when it chose to work.

I used the

su
mount -a
flash_image recovery /sdcard/recovery.img
[G1 Android Development] philosophics:
I had no problems flashing the new recovery. No errors or anything.

then again,

decided it's easier in fastboot....
[G1 Android Development] jerrycycle:
Thanks for the update. No issues to date.
[G1 Android Development] Amon_RA:
Updated to v1.7.0 (Rogers Dream included)

Change-log :

v1.7.0

- Fixed some minor bugs
- Recovery and scripts use /sd-ext instead of /system/sd as mountpoint to support the new apps2sd method (implemented mostly by Chris Soyars)
- Added an option to backup/restore Google proprietary Android system files (backuptool.sh written by Cyanogen)
- Removed "move apps2sd"-option as it's not needed anymore with the new apps2sd method
- Updated BART to v1.3.1 (updated by Dumfuq to support /sd-ext)
- Added a wipe cache only option
- Nandroid now backups/restores /cache again by default
- Dalvik-cache wipes /cache/dalvik-cache now
- Removed SDCARD: prefix in output when chosing zip to flash
- Added Cyan version (There's no difference with the normal version, only the wallpaper and textcolor changed)
[G1 Android Development] vincom2:
I tried flashing through adb while the phone was booted normally and got plenty of stuff like

mtd: read error at 0x00480000 (Out of memory)

mtd: read error at 0x004a0000 (Out of memory)

mtd: read error at 0x004c0000 (Out of memory)

mtd: read error at 0x004e0000 (Out of memory)

mtd: write error at 0x00000000 (Out of memory)

mtd: re-read error at 0x00000000 (Out of memory)

mtd: write error at 0x00000000 (Out of memory)

mtd: re-read error at 0x00000000 (Out of memory)

mtd: skipping write block at 0x00000000

mtd: write error at 0x00020000 (Out of memory)

mtd: re-read error at 0x00020000 (Out of memory)

mtd: write error at 0x00020000 (Out of memory)

mtd: re-read error at 0x00020000 (Out of memory)

etc.

Then I tried rebooting to recovery to do the dump_image thing, but somehow I wasn't able to reboot into recovery anymore: the phone would start to splash1, then display "FASTBOOT USB" in red in the top-left corner. I used fastboot to boot the 1.7.0 recovery image, then did a dump_image and didn't get any complaints about bad blocks. So I rebooted back to fastboot (the more normal fastboot mode with the skating androids) and fastboot flashed the recovery. Now everything works. I wonder what happened though.
[G1 Android Development] xaueious:
For everyone with their flashes freaking out, which SPL did you guys have? Wonder if that has anything to do with it.

I'll flash my recovery from fastboot next time I need to. 1.6.2 is working fine and I don't really need to switch as I'm still on Donut.