I've searched the forum and Google for over an hour, and I cannot find any information on this issue. I am trying to install attn1's R012 ROM. I previously installed the R008 build a couple of months ago, and I have had no issues. I want to upgrade to the latest build, but I am running into a problem when doing a Nandroid backup. As the title to the post suggests, on the last step of the backup, it seems to freeze at "Generating md5 sum...". I have let it sit for over an hour now, and it is still frozen.
I cannot find any information on the root cause of this problem or the resolution. Could anyone shed some light on this for me? And help is greatly appreciated!
What speed SD card do you have? That would be the only real variable as to why your phone is having issues - there could be a timing issue if you are using a real slow card.
have you done a nandroid backup before with no issues? is this a new problem or has it existed previously?
Thank you both for your replies. The SD card is a Transcend 8GB Class 6, and yes, I have done a Nandroid backup before, prior to installing attn1's R008 ROM. I had no issues with that backup.
Also, to at least use my phone for now, I did a battery pull. I tried running the backup again, with the same result.
if your old backup was created normally, i would recommend reflashing that backup and trying installing the new rom again.
reinstalling your apps may be a pain, but it seems like your best chance at restoring the functionality of your phone. or simply wipe everything and install a new rom.
thats happened to me before, right after i flashed a new kernel! It sucked! i had to wipe
Related
So for the last 5 days I had some very weird problems with my phone. About 2 weeks ago I started with my first Cronos Rom and it worked great. I flashed 1.5 and 1.5.1 without problems and I used it without an ext partition all the time. But then the problems started. When I wiped my whole phone and tried to reinstall 1.5.1 JIT, the phone didnt boot anymore (stuck on the "Android" bootscreen). I wiped again and again, tried 1.5.1 without JIT, 1.5 etc, but I couldt get the phone to work. Nothing worked, so I created an ext partition and tried again. It worked. My phone started and I was able to use it for about a day without problems though I didnt want apps2sd. But then some other weird things happened. 3 Days ago I bought a bigger SD Card, partitioned it, wiped the whole phone and flashed 1.5.1 JIT. The phone started, but after I installed a few apps, I got an error message (installing xxx failed). I found out that theres an "repair ext" function, and it worked, but after I installed some more apps, the problem was back. The second problem was, that after rebooting the phone, more and more apps wouldnt start anymore (FC). The last problem that occured was an FC of the market app. After that, I wiped everything again, tried to flash 1.5.1 JIT, but it happened exactly the same like on the first time. Problems installing apps, FCs, stuck on boot etc.
I am totally down at the moment because I killed my whole weekend trying to get my phone working again. Could anyone please help my with this? I just dont understand what I did wrong. Shouldnt a complete wipe fix almost every problem? And I dont understand why I suddenly cant use my phone without an ext partition. Any Cronos version I try freezes on bootscreen without an ext patition. Is there any way to get my hero working again? Please please help me.
(PS: I also posted this on the Cronos Board.)
I would take out the sd card, wipe system and dalvik cache, and install some custom rom.
well, to make sure it is NOT your phone, did you try another ROM? Eliminate possible problems?
At least try something that is known and stable, like a stock rom, the Taiwain-rooted-repacks (not a rom based on it, but just the taiwan rom rooted) or good ol' MoDaCo 3.2 (based on 1.5 stock).
Til now I just tried the last 2 or 3 Cronos Roms, and as I said, they didnt work, but when I get home from work I'll try the Modaco Rom I used before.
I dont understand what this has to do with the Rom I use. I always wiped the whole phone, dalvik, etc. so shouldnt it just work like the first time I flashed it? No matter what Rom I use?
Another weird thing (could have something to do with this): After I wiped everything and flashed Cronos 1.5.1 JIT, the market still knew what apps I had installed last time. It showed my bought apps AND the apps I was able to install before the latest crash. So does this mean the phone wasnt wiped completely?
The market tracks your purchases and (free) downloads through your google account. So that's normal that the download-list is full.
But it might very well be that you didn't wipe correctly, although I'm curious how you manage to accomplish that. What is your current recovery?
The whole point about trying another ROM is elimination. It doesn't need to make sense, but you need to check things of the list.
There is something weird going on, so trying to solve it logically will only get you so far . Keep trying to narrow down the list of causes. Might well be a bug with Cronos 1.5, or the overclock not working these days because your phone is just a bit hotter than before, who knows.. Like I said: eliminate causes!
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Try another ROM , and if that doesn't work, try without SD card.
tombond said:
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Click to expand...
Click to collapse
Maybe sdcard faulty? What are the logs you get when booting up the phone?
Soooo, I wiped everything again and flashed Modaco 2.8 without an ext partition. It booted correctly, so I wiped the dalvik cache and flashed Cronos 1.5.1 JIT. It also booted (wow, first time it booted without ext since all the problems started to occur) but I instantly got FC's (phone app for example). Now I wiped completely again and flashed 1.5.1 JIT. I hope it boots, as I still dont have an ext partition. As soon as I know something new, I'm gonna tell you.
So now it seems like its working again. I was able to install all the apps I need without a single error and now I'm restoring my settings and contacts. Suddenly it even works without ext again.
I guess there was something very big f*ked up that I couldnt repair by simple wiping the phone. Very weird that just flashing Modaco got it running again. Now I have back my working phone with ultrafast Cronos Rom and without App2SD, perfect. At least till now I hope it keeps working.
Thanks for your help guys, I think I would have smashed the phone to the wall sooner or later. I never thought about flashing Modaco so I'm happy there are people like you.
Thanks again, and thanks to Feeyo for his unbelievable Rom.
PS: Can I uninstall, Facebook and Footprints without destroying everything again?
Yes, just delete both apps using ADB or use a root explorer, search both apps in System/app and delete them.
Or you could use the MoDaCo online kitchen for removing those apps.
I am running CM6 (with no bugs) and when I go to flash a different ROM after going through the splash screen when the phone is about to load and installing last bit, the message "android.process.media..." FC happens. I have looked and looked through XDA for a fix but have yet to find one.
I have rebooted after full wipe, no SD Card, wiping the SD Card etc. all to no avail.
As a note- the only reason I was going to flash a different ROM was to check 4G speeds in SF.
Does anyone know what is causing this?
Maximiano said:
I am running CM6 (with no bugs) and when I go to flash a different ROM after going through the splash screen when the phone is about to load and installing last bit, the message "android.process.media..." FC happens. I have looked and looked through XDA for a fix but have yet to find one.
I have rebooted after full wipe, no SD Card, wiping the SD Card etc. all to no avail.
As a note- the only reason I was going to flash a different ROM was to check 4G speeds in SF.
Does anyone know what is causing this?
Click to expand...
Click to collapse
Not exactly sure why it does this except knowing it doesnt happen when you start your device with the sd card out. I've had the same problem that I was finally able to fix.
Just nandroid backup your phone, wipe everything (Factory wipe/dalvik etc) and nandroid restore.
I tried every other thing imaginable and finally this fixed it as my last resort.
I'm happy I found this out as I was always having to nandroid back to an old backup every other month or so as once this starts FC'ing I'd never been able to make it stop without a full reload of the rom or nandroid restore...
I'm getting huge delays with some push-based apps (e.g. Whatsapp) since the update when I'm on the data connection. When I'm on WiFi everything is fine.
Does anybody else have this issue?
Whatsapp delay
Yes. I'm having the same problem for a month or so. ever since I installed cyanogen 7 on my galaxy ace, no matter what i did, whatsapp messages kept on delaying. I first tried restoring a nandroid backup, didn't work. I then tried reinstalling cyanogenmod, it worked for a bit but it then start failing again so i reinstalled cyanogen and did a nandroid. It didn't work. I thought it could be something the nandroid backup did to the cell, so i reinstalled everything from the beginning: flashed the device to original stock rom then root, cwm, and cyanogen again.
The delay i noticed then was not to take on account 3 to 4 minutes the most.
But now again! i open the app and start recieving messages from hours ago. The thing is i've been using the device during the hours that i should have recieved all those messages. I don't know where can the problem come from. All I know is this didn't happen before having cyanogenmod installed, and know it does.
Does anyone have the problem above? Does anyone know of a possible solution?
Thanks in advance!
I have exactly the same problem and i don't find any solution...
Well I've changed carriers twice since I created this thread and my problem has been solved long ago by itself. Maybe the first carrier's data coverage was weak or something. Well TBH with the first carrier I rarely got 3G, I was on Edge most of the time I recommend that whoever's having this issue should check his connection.
[Solved]
I think i at last found how to solve the problem. I bought an Lg O2x and obviously installed a csustom rom, (MIUI) it all worked fine until I did a nandroid backup in order to try a new rom, which i didn't like. After trying it i restored the nandroid backup, and whatsapp started misfunctioning again. I then installed the rom from the very begining, and configured all step by step and whatsapp didn't fail since then.
Conclusion: The same problem happened in two different devices which only had in common the cwm and a nandroid backup restored, diferent rom, diferent devices, different carriers. So try flashing the device from the start or reinstalling rom from cwm. Remember to wipe data, cache, and dalvik. and remember not to restore any backups at all.
Hope this can help you!!
Hi all. First, forgive me if this has been questioned and answered before, but I face a really BIG BIG problem with my CWM made backups...
Regardless the are created right, and restored, the restored ROM gives me android.core.gapps errors continuously, rendering the phone unusable...
Maybe it's only my phone, I don't know, maybe CWM recoveries are young on my S4 variant and have bugs...
BTW: I own an S4 LTE Advanced (GT-I9506)
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505