Database Develop

Nandroid will not complete backup

I feel that I am running on borrowed time. Every time I upgrade to a new version of cyanogenmod, I do a full Nandroid backup. I've done this several times without any problems.... until now. Here's what is going on.
1) Boot into recovery mode, run Nandroid Backup and it performs backup, adding dots, ENDLESSLY. I allowed it to run for 20 minutes straight and no change.
2) When I boot the phone normally and check the nandroid folder on the SD Card, I find that it started by creating a file and FILLING THE REMAINDER OF MY CARD! (2.2 gig).
3) After running fix_permissions, and FSCK on both the EXT3 and FAT partitions, is get the same result.
4) I went ahead and did the newest cyanogenmod update anyway and the update took without a problem, but the backup issue still is present.
This seems to be similar to this thread. Anyone here with some possible solutions?
EDIT- SOLUTION:
I went into Manage Applications and cleared out all the various caches. I noticed that "Browser" was reporting a very large NEGATIVE size for its data and total size. I'm guessing that that was the problem.
It feels so much better to have a good backup completed.

I know cliq users have that problem if they try to run nand with the phone plugged into USB. Was your phone plugged into USB by any chance?

borodin1 said:
I know cliq users have that problem if they try to run nand with the phone plugged into USB. Was your phone plugged into USB by any chance?
Click to expand...
Click to collapse
Yes. Every time a do anything firmware related, I connect to USB for that redundant power. I'll try without and let you know what I find.
Thanks!

Just tried again without the cable and waited till the screen was completely filled with dots (over 14 minutes) and it was still going. Had to pull the battery to restart it.
BTW... is there a more graceful way to terminate this without pulling the battery?
Did the Cliq users have to do anything after they encountered this problem besides unplugging?
Any log files I should check?

What recovery image are you using? Thought about upgrading it or just reapplying the image?

evilkorn said:
What recovery image are you using? Thought about upgrading it or just reapplying the image?
Click to expand...
Click to collapse
Just updated the recovery to RA-dream-v1.5.2 and it did the same thing. Also tried with a different SD card. No change.

Actually I just found out that the backup doesn't fill the card, it stops at the FAT32 2gb filesize barrier.
EDIT: Additional info: It is the data.img portion of the backup that grows to an insane size.

BART backup ended up failing also.
I've never mounted an .IMG file before. Could someone help me do that perhaps to see what file inside the data.img is exploding?

Try dropping to the console, enter umount /sdcard. Then run nandroid from the console.

Did I do what you wanted?
Booted to recovery, to console, umount /sdcard (wasn't mounted), /sbin/nandroid-mobile.sh -b
It went through and hung on data.img.

PROBLEM SOLVED!!!! Thanks all who helped out.
I went into Manage Applications and cleared out all the various caches. I noticed that "Browser" was reporting a very large NEGATIVE size for its data and total size. I'm guessing that that was the problem.
It feels so much better to have a good backup completed.

Congratulations!
fields_g said:
PROBLEM SOLVED!!!! Thanks all who helped out.
I went into Manage Applications and cleared out all the various caches. I noticed that "Browser" was reporting a very large NEGATIVE size for its data and total size. I'm guessing that that was the problem.
Click to expand...
Click to collapse
Hi,
I had *exactly* the same problem today. While searching for a solution, I tried similar things to solve the the never ending backup problem.
I read your solution a few minutes ago, checked my entries under "Manage Applications" and found the K-9 mail application with a size showing a large negative number. Deleting the cache was not possible, I had to uninstall the whole application.
After that, the nandroid backup works (and I think faster than ever... only about 2 lines of dots on screen).
Thanks for your solution!!!!!
Martin

[Q] Emergency! Cannot restore Nexus One!

Hello out there!
I sure hope someone can help me with this! I have rendered my phone completely useless. I have been working on this thing for the past 7 straight hours.
I upgraded to the 5.08 radio and then the MIUI_Au_1.1.28_R4_N1_EN-signed.zip
Everything was working beautifully until I decided to do a Nandroid restore. I guess I did not truly understand the function of this. After a reboot, I was back at square one.
I rebooted again into the recovery mode and then wiped and reinstalled the new rom. Now the new rom is giving me an error. I cannot get any network connectivity from it. I wipe and reinstall several more times and get the same effect.
This is when I get the idea to format and partition the SDcard from within the recovery menu. This was clearly not the best choice.
I cannot get the phone to restore back to factory anymore. The SDcard is empty. I have even taken it out. When it boots up it still boots into some non-working version of the new MIUI rom. No network connectivity. Where is it storing this? I have wiped everything possible. Played with partitions. I have tried hard resetting in the limited interface and in the Recovery console.
At this point, I cannot work on this any longer. My next idea is to put the micro SD card in another device and put original stock image on it. Is it possible that the new rom installed a kernel and that is what I am seeing? I figure if I can install a different rom from the SD card I might just be ok.
Any input into this mess would be greatly appreciated. Because I still have access to the Recovery console I know this is not the end for my phone.
Someone please tell me they know what is going on!
I would be happy to elaborate any more points regarding this issue.
It seems to me that I am not able to delete something because the new rom keeps coming up. Where is it booting from if I wiped everything?
I am at my witts end!
Thank you so much for your thoughtful responses!
glizitch

If you can enter the recovery mode, you just have to enable the SDCard to browse it from your computer. From there you can push in the sdcard whatever zip you wish. Remember to wipe cache and data.
If you can't enter the recovery mode, go in fastboot and flash it again.

And of course, the ROM is booting from /system partition on internal Flash memory in the device, which you can't wipe without knowing fastboot/adb commands - which obviously isn't the case. Wiping SD card won't do anything, and wiping user data isn't going to help you either.
As already mentioned above, since your recovery is working - get into it, mount the USB-MS, connect to PC, copy a ROM of your choice to the SD card, unmount, flash it, enjoy. I suggest RTFM before doing things.

Gratitude!
Thank you for your replies!
I have been putting off doing this upgrade for some time and have been living with limited functionality on the phone due to the amount of time and research I would have to put in to make sure I cross all my t's and dot all my i's.
I was never able to get the MS-USB toggle to work. Windows XP would not show I had put a new drive in when I used it.
I remedied the situation by getting a microSD to SD adapter so that I could put the new rom on the SD card. I used the original microSD card at first and installed the MIUI again. This caused me the same results of rebooting a few times before it went into the rom. When it got in I had no network connectivity.
I decided I would try this brand new microSD card and put the EvIL rom 1.26 on it instead.
I wiped and installed the Evil rom on the new card and Walla!
I have Evil rom now working with network functionality. There must have been some kind of hidden garbage on the old microSD that was keeping me down.
8 hours into the project, I AM SO HAPPY TO HAVE MY PHONE UP AND RUNNING!!!!
I hope others may find this post useful!
Many Blessings & Thanks!
glizitch

[Q] Galaxy S went nuts

Hi all
My Galaxy S went nuts. Something is very wrong with it. I will try to provide as much details as possible.
Today i was using it as usual, sending messages on facebook, reading email... and suddenly my mail client freaked out and force-closed. This has never happened before (i use K9 mail), so i just restarted it, only to see that there is no more messages in inbox. Trying to "load more" got force close again.
So i thought, OK, **** happens - clear data, uninstall, reinstall. However, when i cleared the data something weird begun to happen. Apps started force closing one by one.
OK, i thought, **** happens - rebooting the phone should help. Only that it didn't help - apps still force closed.
OK, i thought, **** happens - clear data of every app, uninstall and reinstall. I got backups anyway. So i cleared all the data, uninstalled all i had and rebooted. However, apps still force closed, and when i went to app manager - surprise surprise! - all the apps i uninstalled a cluple of minutes ago were still there.
Now this was already kinda freaky, but OK, **** happens - i rebooted into clockwork (i have voodoo lagfix) and wiped the hell out of my phone. Rebooted - but the apps i uninstalled were still there, even after full wipe! Now i escapes me how exactly ANY app (let alone all apps) could survive wipe to factory defaults.
Just to be sure that i'm not dreaming, i rebooted to clockwork once again, wiped everything two times and restored a backup from a month ago. The apps were still there.
I am going to try disabling lagfix as a last resort, but for now i am out of ideas, as this is clearly way out of line with what could be considered normal.
Now to the details of what i have installed - froyo, voodoo lagfix, superuser, busybox blablabla, some common apps like skype, facebook, astro, poweramp player, launcher pro, k9 mail, newsrob, blogaway, easyprofiles, pansi sms, mapdroyd, google shopper, qr droid. That's pretty much it. I have one of the custom battery icon mods that could be found here on boards.
Any ideas about what is wrong and how to make it right?

I cant help you with all the poltergeist sh*t on your phone but if it were mine id copy stuff to pc then full wipe and reflash.
regards

id recommend to flash Eclair 2.1 with partition check than to Froyo so that ud have a "clean" rom to play with
cheers

Problems never walk alone - i would, but my laptop has died a week ago...
However, i think i found the cause - looks like for some reason, some of the partitions (including, apparently, internal sd card and data partition) mount as read only. This could explain all that is happening. Is there a way to correcr this without reflashing?

Burillo said:
Problems never walk alone - i would, but my laptop has died a week ago...
However, i think i found the cause - looks like for some reason, some of the partitions (including, apparently, internal sd card and data partition) mount as read only. This could explain all that is happening. Is there a way to correcr this without reflashing?
Click to expand...
Click to collapse
go into recovery and fix permissions , if that doesnt work then as said before

I have tried all possible solutions - from restoring from backups i made earlier, and down to flashing back to different ROMs - namely JPM, JPC, JM8. With repartitioning and without repartitioning.
Moreover, when i mount the SD card on the PC - i can delete files (well, it looks that way) but then when i reboot and mount again - everything is back to the state it was before.
Now i can't even boot my phone. Sometimes it can't mount stl10, sometimes it can't mount stl11. I went through all the solutions that were mentioned in the threads related to these errors. Also, when i format all the partitions (with voodoo's clockwork) it says everything went OK - i "can" reformat everything including internal SD card, repartition it etc. but then it goes back to what it was, and phone doesn't boot any ROM.
Any ideas? Can this be a hardware problem?
EDIT:
i tried to flash latest stock gingerbread ROM, and after installing a clockwork from here it boots but still doesn't work - starts force closing, can't load anything.
Formatting partitions with clockwork does not induce any errors, nor there are any errors mentioned at boot. however, even unmounting, formatting and mounting internal SD card doesn't affect it.
after flashing stock rom it says it cannot mount /data partition
EDIT 2: still no luck. i can't do anything with SD card. maybe there is some hardcore way with adb that i can try? like manually fscking up partitions so that i force reformat or something like that?

i have been tinkering with my phone and now i am certain that the root of the problem is that the internal SD card went into read-only mode - and it doesn't get fixed with any sort of permission fixing, repartitioning or flashing ROMs. i've searched some more on this topic (now that i know what the problem is) and found that on one was ever able to successfully fix this problem. i just hope that the samsung guys fix it for free because it doesn't look like a user problem...

thankssssss

Samsung accepted it on warranty, and they agreed it is a hardware problem.
What is alarming is that this is not the first time (as i said i found a bunch of threads with similar problems), and apparently it can also happen on galaxy tab (i seem to remember stumling upon a similar thread in tab section, and IIRC galaxy tab has hardware similar to SGS). This means that it can easily happen again.
So whoever is reading this thread - save yourself some time, don't bother fiddling around with odin and go straight to samsung customer service, they'll fix it for free provided you bought your phone less than 2 years prior.

.... okay nvm

[Q] Freaky i9000M problems - any idea why/what/who???

Hey guys, I need some advice please. Have had a number of odd happenings with my i9000 in the last 24hrs and not sure if some of them are the fault of the phone, or my fault! Apologies up front too for the long post – didn’t know how to put it all more succinctly!
First things first – it’s a Galaxy i9000M Bell vibrant. Came as Éclair 2.1, upgraded recently via Kies to Froyo 2.2, Build UGKC1. Then rooted with SuperOneClick, successfully without drama. Can get into recovery and download modes no problem via 3-button method.
Bit of background info – int SD 16GB, inserted 16GB ext SD. Before any upgrade to the phone had some issues where some photos taken with camera on the phone would show up in gallery as a corrupted/damaged icon. Pretty sure this occurred on default int SD so changed save location to ext SD but same deal now and then. Formatted ext SD – still happened from time to time. Actually replaced ext SD (exchanged at shop with brand new one), but same thing happened again. Figured I’d learn to live with it as only happened now and then.
So, phone rooted last week. Had been doing reading on ROMs/kernels before trying to flash anything. Only root-type things I’d done were to get TiB (and do full backup), Root Explorer, Terminal Emulator and Wireless Tether. Y’day I noticed after taking a few pics that one of the ‘corrupt’ icons that had previously been in place of an older photo, was now in the spot of one of the pics I had just taken (and strangely, the older, apparently corrupted photo was now fine).
I tried to delete a few of the photos but the phone just got stuck trying to delete. Had to force close it with task manager. Same deal if I tried 1 or many photos. Did this a number of times but no joy. Eventually just took ext SD out, put it into PC and deleted them that way, then put back into phone. Now it took AGES to complete the media scan on ext SD – like 5-10 mins! This happened a couple of times if I tried to do anything with the SD eg. save a file to it. So reformatted the SD card (on PC) but same prob when put back in phone.
Figured it might finally be time to try a new kernel in hope it may fix this bug. Had speedmod all ready to go (but hadn't been brave enough yet to try my first flash) so flashed K13E-500Hz via Odin. It worked fine, but “media scanning” problem was still there. Figured I might as well go the whole hog so factory reset the phone via recovery 3e. Did this ok, and “media scanning” was no longer a prob when I put the ext SD card in, just took a couple of seconds – hooray!
Restored apps + system using TiB which also appeared at first to work fine. Put a few pics and ringtones on the ext SD and all seemed fine. Then some app icons disappeared from the Applications pages. They appeared ‘crossed out’ in TiB and when I went to restore them again the phone spazzed out saying (sorry can’t recall exact wording) there was not enough memory and to delete some things to try to fix this. A red SD-like icon appeared in the top bar. I tried rebooting the phone via recovery 3e and it went into a cycle of vibrating, flashing up the turn-on screen/display then shutting off, but vibrating occasionally and lighting the soft touch keys but nothing else. This did this for about 5 mins and in order to try to save battery/stop the whole process I ended up factory resetting yet again via recovery.
Today it works 'ok'. Have not braved putting an ext SD in yet! Got Tib off the market but have also not dared to try to restore any thing yet. Oddly, in TiB it shows “System ROM” as almost fully taken up ie. Full green bar (289MB, only 6.06MB free) – this can’t be right can it?
Internal, DB data and SD card all show as ~99% free.
Deleted Dalvik cache in case that was the RAM problem but it didn’t do anything much (freed up about 6MB only).
So, my questions!
1. is this all because of the ‘corrupt/damaged’ issues before I’d done anything to my phone?
1b) How do I find out what RAM is available and what is using it all up? RAM manager is showing 197MB/339MB used but is this what the 'memory' problem would be? Clearing memory doesn't seem to do anything.
2. I never installed any kind of lagfix (knowingly anyway) – could this be a reason - have seen lots of threads/posts about disabling lagfix before flashing roms or kernels
3. I thought factory reset would wipe everything – but it obviously kept the int SD info ok (I’d copied Tib backup to ext SD and also to dropbox just in case) –should I maybe reformat the int SD and factory reset again?
4. If the issue is the phone itself (with prior corrupt file problem) – would it be worth flashing back to stock kernel and unrooting phone to try to bring back and get fixed/replaced under warranty?
Thanks in advance for any help anyone can offer!!!!!!

Read your hole post its really long. Can't answer to all questions. But did you try to put your phone as massage storage to your pc and mark everything thats on int sd and just erease it. When turn your phone off, put it in download mode and flash a stock rom (with 3 files) from samfirmware.com with repartition enabled? Maybe that works. Good luck! Before i forgot ext 4 is the better filesystem. Rfs getting laggy after a while cause its not the correct filesystem for sgs. Thats why ext4 is the main format on sgs2.
Sent from my GT-I9000 using XDA App

hey thanks for the reply.
i know it was a super-long post, apologies again.
didn't try deleting the ext SD whilst connected via usb. got fed up with the phone not being able to delete & freezing when i tried that way so just took SD out and deleted them with card plugged directly into laptop.
as it happens, since 2nd factory reset, i've been cautious about what i do. no ext SD yet (though might try that tomorrow). didn't do full restore of missing apps and system files as i did the first time. so far have only restored about 6apps via TiB and wifi locations. Phone working ok...for now.
next steps:
1. try taking loads of photos to see if 'corrupt'-style icons occur again with int SD only;
2. maybe try an ext SD again after reformatting it and see how the media scanning goes and how it goes having music/vid/pic files on it etc;
3. gonna look more into the speedmod kernel ie. the tweaks which i think i need to access via recovery mode.
not quite ready to try and flash a custom rom with that little scare!
...but would like to try a custom rom at some point when i feel more educated about all this

Just look at the search function on xda or google. There enough guides about flashing. Know how you feel. The first time i flashing it was very scary for me. Got a heartbeat like a technosong. If you want i can write you a guide for every step. Trust me it is easier as it sounds. Just pm me and i will help you out.
Sent from my GT-I9000 using XDA App

TWRP - Long backup to External SD

I searched the forums as well as the site, I didn't see a similar post. If this is answered elsewhere, please delete my post.
I just crossed hour 12 of a TWRP backup to external SD. Unlocked bootloader, S-OFF Running 4.4.2 Rooted stock. After 12 hours of a backup, I'm wondering if this is still within the realm of normal, or if there is a way to stop the process. A few looks around the site, sounds as though restarting the phone or letting it die during the backup may cause it to Soft brick/ boot loop.
Brief backstory: I tried to do a backup to my external sd in preparation for flashing to MM this weekend. The backup has been running now for over 12 hours.
Help? Thoughts? Suggestions?

Tecchief said:
I searched the forums as well as the site, I didn't see a similar post. If this is answered elsewhere, please delete my post.
I just crossed hour 12 of a TWRP backup to external SD. Unlocked bootloader, S-OFF Running 4.4.2 Rooted stock. After 12 hours of a backup, I'm wondering if this is still within the realm of normal, or if there is a way to stop the process. A few looks around the site, sounds as though restarting the phone or letting it die during the backup may cause it to Soft brick/ boot loop.
Brief backstory: I tried to do a backup to my external sd in preparation for flashing to MM this weekend. The backup has been running now for over 12 hours.
Help? Thoughts? Suggestions?
Click to expand...
Click to collapse
I always make full backup with TWRP to external SD (approx. 8 GB backup) with no problems. And it doesn't take more than 10-15 mins for sure (I have class 10 SD so speed might vary).
Possible causes: corrupt SD card(try reformatting on PC) , especially if backup works fine on internal memory.
About stopping backup while in progress, I once did hard reset (vol up+power) nothing happened except corrupt backup which I deleted. But I would NOT recommend this as it can harm the SD card.
PS if you fixed the problem post an update incase someone searches for similar problem.

Vcek said:
I always make full backup with TWRP to external SD (approx. 8 GB backup) with no problems. And it doesn't take more than 10-15 mins for sure (I have class 10 SD so speed might vary).
Possible causes: corrupt SD card(try reformatting on PC) , especially if backup works fine on internal memory.
About stopping backup while in progress, I once did hard reset (vol up+power) nothing happened except corrupt backup which I deleted. But I would NOT recommend this as it can harm the SD card.
PS if you fixed the problem post an update incase someone searches for similar problem.
Click to expand...
Click to collapse
Thanks for the reply. I was able to fix with a power off (power button + up arrow) followed by rebooting into recovery.
Since then I've cleared some space internally and properly backed up my stuff.