I recently had to get a new Hero due to damage to my original one. After I rooted and did a back-up I installed cm6. After a few days I decided to go back to check for any prl updates since I forgot to check before I flashed. Once my backup was restored I noticed some ... funky-ness ... unlike usual, none of my stuff was in the right place and the Market is missing.
Discounting all this here is my question...I'm still kind of new so excuse me if this sounds really stupid... Would there be any issues in restoring a back-up from my previous hero? I saved them to my computer to keep a back-up of my back-ups.
My wife had a back (nandroid) of Fresh 2.4. When a new PRL came out I read that we can update them from that rom so I flashed back to her nandroid of Fresh and hers updated right away. I decided to take her Fresh nandroid from her sd card and put it on my sd card, it let me flash back to it BUT it would not update PRL. In fact it wouldnt do much of anything! I flashed back to cm6 download Fresh, flashed and updated with no problem. I think something in the build prop or something messes it up when putting it on a diff phone.
Related
Hey guys, new here but I have been lurking for a while.
On Androidforums I have a longer thread detailing what I did, if you want details pm me, I can't post a link yet as I am a noob on this forum.
To make a long story short:
1. I had stock eclair, then rooted with "ryans oclf" and used the lagfix.
2. I decided to try a version of cognition (unhelpfuls kernal). So I backed up my current "rom" using rom managers (which was the stock kernal).
3. Realized that I didn't back anything up so I tried to revert to my backup.
4. relized that I didn't undo the lag fix, and because of this my stock eclair wouldn't restore via rom manger's update.zip file
5. was forced to get cognition running again
6. extraded the files from the .img nandroid bacups from my stock eclair (which is a PITA since the .img files aren't regular mountable .img files - took about an hour of searching)
7. Found the sql databases to restore my text messages and contacts from my stock eclair to this new cognition.
NOW, after a long intro, my question:
The .img files I extracted contained a file named linux.ex2. I assume that this file is where ryans oclf must have been storing the stuff that is causing the restore to fail (it actually completes, but never boots)
Is there any way I can manually repair this nandroid backup? I would like to so that I have a nandroid backup of my stock eclair rom.
BTW, I am pretty good at this kind of thing, but I am not a computer programmer.
I don't have a lot of background info directly related to andorid phones but I am learning quick. I am a Senior in electrical and computer engineering so I do have a light background in programming. luckily I knew enough about sql and command prompts and such to get as far as I did with recovering my contacts/text messages.
If what I want to do is possible I would love to give it a shot. Any help/tips/ideas from you guys would be awesome!
Thanks
-Chad
To me it sounds like your screwed. You did a double bummer.. (backup with LF on, restore a backup with LF ON on your already LF ON rom).
Will see if any other more experienced with backup can help you out, but my answer to you is to go stock and redo sorry.
yeah, well I am willing to try a few different things. I forgot to mention that right before I installed cognition the first time, I did remove the lag fix, I just undid the lagfix before I made the backup.
I have been using cognition for about a week now. I don't really mind it as it seems to work just fine, as It is in fact faster.
Last night after posting my post here I removed the voodoo lag fix and then I made a backup of my current installation of cognition.... So if I have any issues trying to do this I at least have a working/functioning cognition rom.
BTW: I have an unrelated question that is slightly related. If I have to use the odin one click restore at some point, does it clear my internal sd card as well? I see that it says it will clear user data, but doesn't specifically make a clear separation of the internal SD card on the captivate and the 2 gb they setup for the android partition.
A far faster method would be to Odin back to stock, root, then take a nandroid backup right away, then flash back to what ever rom you want. Time consuming, yes, but faster and easier than trying to mod a backup.
OK, when I first started into this stuff, I tried to follow all the guidance that has been given before flashing my first ROM. I did a ROM Manager backup of my ROM the way I got it from AT&T. I did not write down my ID # or anything else. I'm assuming the backup has all the information that came with it. My question is how to re-load that original ROM. I've flashed quite a few ROMs now using the Odin one-click to go back to stock and Master Clear and never had a problem. I'm running P9 right now (w/ no problems) and decided to try something else. After seeing some of the threads on here about your original phone IDs, I wanted to try and recover that info by restoring the original backup. I did that straight from P9, but now I just get locked up on the DG boot screens. I'm going to One Click it again but I'm wondering how I can restore back to my original with the backup that I have. Any guidance would be appreciated.
Thanks
My apolopies if this is already posted somewhere but I can't find it
Your can not restore a 2.1 backup when on a 2.2 rom, if I understand you correctly. In fact I would only restore a backup if you are on the same rom as the backup, and even then you should disable the lag fix prior to restoring
Sent from my SAMSUNG-SGH-I897 using XDA App
Not to sure, I tried going to original with nandroid backup after flashing another rom and soft bricked. I actually got stuck at the AT&T screen which on Perc 9 (that what I was running) was the designgears boot screen. Odin 3 one click saved my sanity. if you can go 2.2 to 2.1 I don't know, but I'm not going to try it again. I just one clicked, master cleared, rooted, flashed Axura 2.5 and have been happy ever since. This was my fault, not Perc 9's, let me say that real clear.
Got it
Thanks. I did have to One Click restore to stock, Master Clear, and then restored my original backup. Now I gotta figure out what information I need off of it before I flash a new ROM. Probably a waste of time since I can't imagine going back to AT&T for anything, but thought I would get it since I was waiting to change to P10 soon.
BigMc71 said:
Thanks. I did have to One Click restore to stock, Master Clear, and then restored my original backup. Now I gotta figure out what information I need off of it before I flash a new ROM. Probably a waste of time since I can't imagine going back to AT&T for anything, but thought I would get it since I was waiting to change to P10 soon.
Click to expand...
Click to collapse
Um.. what information did you want off of it? If you just want your Android ID - there is an app for it on the Market (strangely enough called Android ID) You can then write it down and re-enter it at any time after flashing.
I have not received a text for about 3 days. It started when my sister asked why I hadn't responded to hers. I figured it was just a hiccup on the network. I was able to send her a text fine and make and receive calls fine, but no texts come in. I'm running on CM6.1 and hadn't had any problems with it. I tried uninstalling recent applications, and I even did a factory wipe and re-install of my ROM and mods, as well as all of my apps and I'm still not having any luck. I haven't yet called Sprint, as I'm afraid that they won't know anything or will give me grief for using a non-stock software (perhaps they won't even know); or maybe I'll just stop into the store sometime soon.
Anyway, I've read a few things about this, such as people removing apps and it alleviating the problem. I figured it was just a space issue, like once the phone dips under a certain amount of on-board storage it doesn't download them. I had a similar problem where it wouldn't sync e-mails until I got 2.2 firmware and did App2SD. But my storage isn't really low enough for that to make sense. I tried re-installing the radio that I use to no avail... I just really can't figure this out.
If anyone could give me a leg up on this problem, I'd be really grateful.
Thanks,
Mike
What rom are you running? Is your prl up to date? Current is 60674. Nand, flash a Sense rom, send and receive a few texts, update your profile and prl, then nand restore back to your rom. People have had success with that.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
I'm running the latest Cyanogenmod that is listed for my phone, which is 6.1.0, released about 2 weeks before I started experiencing the problem. I have the PRL file and have it on my SD card. Is there any way to do this without flashing to a different ROM?
I had the same problem. Downloaded Fresh ROM. Did a nandroid, flashed Fresh, updated prl, opened maps for a good GPS lock for safe measure, then just restored my nandroid of Cyanogen. Worked flawlessly, and took 20 minutes. Definately the best fix, and the nandroid restores everything to to the way it was, so it's no headache at all.
I'm downloading the stock RUU and I have Fresh downloaded. Nandroid keeps getting stuck on data... about to just go for it.
Don't flash the stock RUU or you'll have to re root.
Well that's not too hard. But what sucks is when Fresh Sense keeps crashing... then when you go to restore, you get an MD5 mismatch... Yeah, it won't restore my backup because it didn't complete and got stuck. Looks like I'm wiping and re-flashing CM6.... again.
Well, somehow I had a working backup from yesterday, the 24th, at some point. It won't be exactly where I left it... but it'll be close. Hopefully I got all the updates I needed via Fresh. Fingers crossed.
The way I got it to work was to flash a Sense ROM. As soon as the ROM loaded, all the texts came in. Also while on Sense, update your PRL.
Sent from my HERO200 using XDA App
I have been trying for the past 3 days to return my N1 to the stock program. I have unlocked the phone and i was enjoying rooting for the past 8 months. I installed many different builds like Modaco, LeoGingerbread, Rodrigues MIUI, MicroMod Gingerbread and then Cyanogen Mod 7 (build 36), that is when it started to have tons of force close and the programs would stop running.
I always cleared the phone before i installed a new build.
I decided to return the phone back to the original factory settings and start fresh but it is giving me some problems.
I have used many different version of the PASSIMG files on XDA but i always get an issue with an Android program stopping unexpectedly.
At first it was the Settings that did not work, i fixed that.
Now it is the Calendar AND Market who keep force closing.
I have been trying for the past 3 days looking for a solution but i have come to the end of my patience.....
If ANYONE has a solution, i would love to hear from you.
Right now i am just thinking of getting a new phone but i love my Nexus 1
This is the first phone i ever rooted so my knowledge of rooting is limited to the 8 months of installing different builds. I never created a program or modified any.
Thanks
Phone status right now
Canada
Nexus 1
Bell Network
HBOOT: 0.33.0012
Radio: 4.04.00.03_2
Dec 17 2009,13:05:23
Firmware: 2.1 Update1
Baseband: 32.26.0024U_4.04.00.03_2
Kernel version: 2.6.29-01117-g4bc62c2
Build number: EPF30
I am going to take a stab in the dark here...are you by chance using ClockWorkMod recovery? If so did you upgrade to 3.0.0.5? Assuming this is correct you are in the same boat as I was...your not going to like it but if you are first go back to 2.5.1.4 or older. Next you will need to format your entire SD card and repartition it, then do a restore. That should work. Hopefully you have backups of your SD card contents... If a restore doesn't work still then you may need to format and partition again and do a fresh install. I lost a lot of sleep the other night trying to figure out WTF happened. It seems that something it 3.0.0.5 changes the SD-EXT and cannot be repaired without a format. I was mad enough about the whole situation that I have ditched CWM and am now running RA.
Galloway said:
I am going to take a stab in the dark here...are you by chance using ClockWorkMod recovery? If so did you upgrade to 3.0.0.5? Assuming this is correct you are in the same boat as I was...your not going to like it but if you are first go back to 2.5.1.4 or older. Next you will need to format your entire SD card and repartition it, then do a restore. That should work. Hopefully you have backups of your SD card contents... If a restore doesn't work still then you may need to format and partition again and do a fresh install. I lost a lot of sleep the other night trying to figure out WTF happened. It seems that something it 3.0.0.5 changes the SD-EXT and cannot be repaired without a format. I was mad enough about the whole situation that I have ditched CWM and am now running RA.
Click to expand...
Click to collapse
I sis upgrade to the ClockWorkMod 3.0.0.7 and that is when the problem all started.
I downgraded to the 2.5.4 version and i was able to install the CyanogenMod 36 and then it really went all bad.
I was so frustrated that it was not working that i formated (and i did back it up) my SD card. Then i did what i said and i am still having issues.....
Where did you get and how did you install RA? I was used to the CWM and i really liked it until they upgraded to version 3.
Thanks
Look in Developer section.
Take your SD card out, reformat it in Windows, then put it back and repartition for EXT, if you're using old Apps2SD (/A2SD/Apps2EXT).
Wipe everything.
Install any ROM.
Enjoy.
Hey guys, I just have a general question that (seemingly) applies to all Android phones. I'm posting this question in the GS3 mini section because I have a MetroPCS Galaxy Exhibit [SGH-T599N] and I guess that's where we're we've been relegated to, but this question, as I said, could really apply to any phone. My question is this: how can I verify that my NAND backups are not corrupted?
Here's some context: I recently flashed to CM 11. Everything's running great, it's my daily driver, and I love it. It's easily the best, most smooth ROM I've ever used but I recently discovered a need to flash back to the stock ROM backup I was running pre-CM 11. Before I flashed to CM 11 I was running the standard JB stock and incidentally I was also using a different Kik username. After flashing to CM 11 and installing Kik, I decided to make a new username. Now, given that I never logged out of that old username (the one I was using on JB stock), I know that if I were to flash back to that old ROM, I'd boot into a ROM that's logged into that old account. I need to be able to do this because I need to access that old Kik account's chat logs for personal reasons. My problem now is due to two issues: my amazing stupidity and...well, no that's really it.
At the time I was running stock I was running CWM recovery. I made a backup using Rom Manager but like an idiot I backed up to my internal SD card. In order to flash to CM 11 I had to wipe my internal memory, which eventually lead to me losing that backup. My only silver lining is this: I made one backup to external sd about a week before I flashed to CM 11.
Here's where it gets messy: Not knowing that the backup on the external sd was for my stock pre-CM 11 ROM, I stupidly deleted it to free up space and began saving files onto the external sd card. After I had flashed to CM 11 I made about three CM 11 backups. I deleted my pre-CM 11 backup because I mistook it for one of these three CM 11 backups. Upon realizing the height of my stupidity, I just finished recovering these lost folders and files using a data recovery program, but I have no idea whether or not the files have been irreparably corrupted. Is there any way I can verify that this backup is still good to use? I don't want to risk attempting to flash back to my old ROM only to have it wind up bricking my phone. Does anyone know of a good way I can figure this out? Any help is appreciated.
Thanks,
an idiot
adamryanx said:
Hey guys, I just have a general question that (seemingly) applies to all Android phones. I'm posting this question in the GS3 mini section because I have a MetroPCS Galaxy Exhibit [SGH-T599N] and I guess that's where we're we've been relegated to, but this question, as I said, could really apply to any phone. My question is this: how can I verify that my NAND backups are not corrupted?
Here's some context: I recently flashed to CM 11. Everything's running great, it's my daily driver, and I love it. It's easily the best, most smooth ROM I've ever used but I recently discovered a need to flash back to the stock ROM backup I was running pre-CM 11. Before I flashed to CM 11 I was running the standard JB stock and incidentally I was also using a different Kik username. After flashing to CM 11 and installing Kik, I decided to make a new username. Now, given that I never logged out of that old username (the one I was using on JB stock), I know that if I were to flash back to that old ROM, I'd boot into a ROM that's logged into that old account. I need to be able to do this because I need to access that old Kik account's chat logs for personal reasons. My problem now is due to two issues: my amazing stupidity and...well, no that's really it.
At the time I was running stock I was running CWM recovery. I made a backup using Rom Manager but like an idiot I backed up to my internal SD card. In order to flash to CM 11 I had to wipe my internal memory, which eventually lead to me losing that backup. My only silver lining is this: I made one backup to external sd about a week before I flashed to CM 11.
Here's where it gets messy: Not knowing that the backup on the external sd was for my stock pre-CM 11 ROM, I stupidly deleted it to free up space and began saving files onto the external sd card. After I had flashed to CM 11 I made about three CM 11 backups. I deleted my pre-CM 11 backup because I mistook it for one of these three CM 11 backups. Upon realizing the height of my stupidity, I just finished recovering these lost folders and files using a data recovery program, but I have no idea whether or not the files have been irreparably corrupted. Is there any way I can verify that this backup is still good to use? I don't want to risk attempting to flash back to my old ROM only to have it wind up bricking my phone. Does anyone know of a good way I can figure this out? Any help is appreciated.
Thanks,
an idiot
Click to expand...
Click to collapse
if you recovered it immediately after deletion - then it's most likely still good. I don't think there's any way to fully verify backups; but I will say this if you do chose to use that backup and it fails, you should easily be able to flash any rom over again to correct it, or even use odin to go back to stock rom and try again. The only way you truly hard-brick phones is flashing something over usb and it gets disconnected haflway through, or you accidently flash somethign to the wrong partition (if you were using hiemdall), generally speaking for nearly 80% of bricks are sem-bricks and should easily be able to recover from.
Exothermic said:
if you recovered it immediately after deletion - then it's most likely still good. I don't think there's any way to fully verify backups; but I will say this if you do chose to use that backup and it fails, you should easily be able to flash any rom over again to correct it, or even use odin to go back to stock rom and try again. The only way you truly hard-brick phones is flashing something over usb and it gets disconnected haflway through, or you accidently flash somethign to the wrong partition (if you were using hiemdall), generally speaking for nearly 80% of bricks are sem-bricks and should easily be able to recover from.
Click to expand...
Click to collapse
Thanks for your quick reply, Exo. I'm curious, do you think inspecting the .log file would be able to give me an indication about the integrity of the backup? In going through old backups I was able to open the .log file in Notepad and read in plaintext what was written there. If this could be used as an marker of the backup's health, then it seems I may be out of luck as the .log file for this backup seems like nothing but jibberish. I've opened it with Notepad, Notepad++, and I even installed a different third party program that's reads .log files exclusively (called Baretail), all to no avail. I'll try flashing to this backup in the meantime but I'm curious: do you think attempting to read the .log file could be a good way to verify the backup's integrity, or is there something I'm missing here? Thanks for your time.
Adam
First you should make a nandroid of your current ROM (CM I presume) so that if you brick your phone while trying to restore the stock backup, you'll still have the CM backup to restore if something goes wrong and the phone can't boot or says that there's no os installed.