First question: I notice that a fair % of the time when I try to do a restore from CWM, it tells me there's a MD5 mismatch. Is this just a symptom of a bad SD card -- that the backup did not save properly to the card?
Since it's no good to find out the backup is bad when I actually need it, I came up with a work-around, which was to try and immediately restore from the backup immediately after making it. If it gives me an MD5 error, then I make a new backup. Eventually I don't get an MD5 error and the restore works, and in theory it should be restoring the phone to the state it was in just a few minutes earlier -- i.e. nothing is changed.
However, after a successful restore and reboot, I tend to get a slew of FC's at startup from background apps. I'm wondering what I'm doing wrong -- is there some extra step I need to do after a restore using CWM?
Sounds like when you backd up you had some data issues that are being restored too your phone each time you restore. Bite the bullett reflash your rom don't restore. But before you do that try fixing permissions in cwm.
I would clear cache and dalvik before doing the backup...
Sent from my SPH-D700 using XDA App
If you're using SRF, just reflash srf 1.1.1 right over it. It will repair your framework but save your personal data.
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Did not know that. You get a thanks.
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
kennyglass123 said:
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Click to expand...
Click to collapse
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
if you arent properly shutting down you will almost always get FCs on reboot if you have a no journal rom...
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
ummmm
Nerva said:
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
Click to expand...
Click to collapse
that would be not shutting down properly like pulling the power cable out of your comp and turn it back on not goood to do alot wil be ok in light doses
Corrupt data is 100% the cause. The only problem now is trying to determine where the problem came from. It can be from many things, but to be safe, i'd reformat the SD card (backup all ur data first on a computer). And recreate a backup from the rom previously. I use "my backup root" from the market and it works like a charm when switching from rom to rom.
Sent from my SPH-D700 using XDA Premium App
yep
i use the very same thing........... i read that somewhere lol
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
The 4 finger will cause corruption on ROMs without journaling, so yes. There is also a Quick Boot app that boots into recovery, same thing can happen. So for backups and restores, always power down then 3 finger into CWM.
Related
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
algorhythm said:
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
Click to expand...
Click to collapse
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
crawrj said:
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
Click to expand...
Click to collapse
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
algorhythm said:
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
Click to expand...
Click to collapse
Try wiping than flashing Olympus and than restore data only.
The data's part of the backup may not be corrupted.
Sent from my SPH-D700 using XDA App
Now that someone made this thread, I'll take the time and explain my issue, I have an MD5 mismatch for all 3 backups I made in the past. I know how it mismatched as well, I renamed the backups to something that actually made sense,like Eclair, EC05, & EG22, problem is, tried restoring any of them, I get mismatch, also, advanced restore also says MD5 mismatch.
P.S. To whoever made clockwork mod, you need to add the option to override the MD5 Mismatch, and also, why use MD5? Its an outdated form of Checking for the Integrity of files, there are newer methods.
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
counterfeit187 said:
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
Click to expand...
Click to collapse
Seems like that was it. Had 0 space once I booted to a new ROM.
Thanks
it would be nice if there was a way to pick the name of your backup instead of it auto generating by time/date..
I used Titanium Backup to uninstall certain packages (not before backing them up, of course) and it seems that I uninstalled too much... Whenever I start certain applications, the phone immediately blanks - and locks.
I have to press the power button 1-2 times before the screen unlock allows me to seep my finger. And it doesn't always succeed in retaining the screen: too often, it will immediately blank and lock again.
Example of applications that make the phone lock: Titanium Backup.
Example of applications that don't blank the phone: Dialer.
I started restoring some of the packages I uninstalled yesterday with the hope that this will fix the problem. So far I tried restoring:
- hiddenmenus
- sns
- Dialer 2.2.2
-setup wizard
- syncMLsvc
But without much success yet.
Any idea which service or package are responsible for correct behavior of the phone?
UPDATE 2: I gave up and decided to flash the EC07-Nuckin-1 ROM. I repeated the entire procedure detailed here and the phone boots fine, but the problem persists - in addition to the fact that the soft menu buttons now disappeared (replaced by faint color dots - LED-like).
How could this happen? Is it possible that my phone contracted an Android virus? (it appears that the problem started immediately after installing Stay Awake from the Android Market.
OK, this is becoming insane: I did a factory reset, re-installed ec07-clean, and not only the problem persists, the settings, home, back and search buttons no longer work!
Not to mention that my account details (and everything else) are still there, even after the factory reset...
And Market won't even start.
How is this possible?
What do I do to simply start from scratch, wiping out everything and all history (except for the SD card)?
verizonless said:
OK, this is becoming insane: I did a factory reset, re-installed ec07-clean, and not only the problem persists, the settings, home, back and search buttons no longer work!
Not to mention that my account details (and everything else) are still there, even after the factory reset...
How is this possible?
What do I do to simply start from scratch, wiping out everything and all history (except for the SD card)?
Click to expand...
Click to collapse
those softkey mod (led dots) are in the rom, look at what ur downloading/flashing first.
did u clear caches/dalvik??? clear them before u flash ec07clean and after and see buddy.
ciscogee said:
did u clear caches/dalvik??? clear them before u flash ec07clean
Click to expand...
Click to collapse
Of course I did.
ciscogee said:
and after
Click to expand...
Click to collapse
After, too? I didn't know that.
ciscogee said:
and see buddy.
Click to expand...
Click to collapse
Who is buddy?
ciscogee said:
those softkey mod (led dots) are in the rom, look at what ur downloading/flashing first.
Click to expand...
Click to collapse
OK, but they don't respond. Even with your ec07-clean.
Is there a way to do a real factory reset? Start all over again? This problem is driving me nuts.
Thank you ciscogee, you life saver.
Ur buddy lol.
I'm out and about right now. In joshkoss rom thread there is a dl17 stock rom. If u flollow that second post I believe u will achieve 2. 1 stock as in out the box and flash up from there
Sent from my SCH-I400 using xda premium
ciscogee said:
I'm out and about right now. In joshkoss rom thread there is a dl17 stock rom. If u flollow that second post I believe u will achieve 2. 1 stock as in out the box and flash up from there
Click to expand...
Click to collapse
I'm not really interested in 2.1. I just don't understand why a total re-install of ec07clean.zip + ec07.tar + update.zip won't restore everything to "brand new condition". Surely there is a way to tell the phone to "forget all history". But what is it?
In the meanwhile, I managed to make the Settings (leftmost) button work, by manually restoring SDM from Titanium Backup.
Android Market now starts. But the SCREEN OFF problem persists. I am now beginning to believe that Stay Awake actually caused a permanent damage.
verizonless said:
I'm not really interested in 2.1. I just don't understand why a total re-install of ec07clean.zip + ec07.tar + update.zip won't restore everything to "brand new condition". Surely there is a way to tell the phone to "forget all history". But what is it?
In the meanwhile, I managed to make the Settings (leftmost) button work, by manually restoring SDM from Titanium Backup.
Android Market now starts. But the SCREEN OFF problem persists. I am now beginning to believe that Stay Awake actually caused a permanent damage.
Click to expand...
Click to collapse
i understand, but see dl17 is the latest official samsung/verizon release, so what ever you erased will be brought back. the roms that are released here are leaks/hacked so they wouldnt be 100% until tweaked
ciscogee said:
i understand, but see dl17 is the latest official samsung/verizon release, so what ever you erased will be brought back. the roms that are released here are leaks/hacked so they wouldnt be 100% until tweaked
Click to expand...
Click to collapse
I understand that they aren't 100% and I am OK with that. All I want is bring the phone to that pristine state it was right after I upgraded it from DL17 to ec07clean.zip.
Is this possible at all?
I even tried the built in stock recovery 2e to do "factory restore". Didn't help.
Why doesn't it even delete my account information? This is weird.
Wipe all your data. Cache. Dalvik etc.
Sent from my SCH-I400 using xda premium
ciscogee said:
Wipe all your data. Cache. Dalvik etc.
Click to expand...
Click to collapse
I tried this at least 4 times. It doesn't get rid of anything. That's really puzzling.
In the meanwhile, I managed to restore my phone to a usable state (i.e. get rid of the original screen-off problem). Here is how I did it:
Settings > Display Settings > Power saving mode: UNCHECK (was checked)
Settings > Display Settings > Screen timeout: 1 minute (non was selected!)
I bet this was some remanent of that Stay Awake app.
Now, I lost quite a few productivity hours due to this. But at least now I know that this phone will always be mine, because in this particular phone, "Factory data reset" simply doesn't work.
Have you thought about using a different version of clockwork for flashing and wiping? That usually helps or perhaps stock recovery even
Sent from my DROIDX using xda premium
verizonless said:
I tried this at least 4 times. It doesn't get rid of anything. That's really puzzling.
...
But at least now I know that this phone will always be mine, because in this particular phone, "Factory data reset" simply doesn't work.
Click to expand...
Click to collapse
Mystery solved!
It turns out that it is the cyan wipe that doesn't work. The red wipe works.
Here is what I did:
Settings > Privacy > Factory data reset (Erases all data on phone) > Reset phone > Erase everything attempt:
Progressed as expected, then rebooted -- right into Android System recover <2e> (blue!):
Code:
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
___________________________________________
-- Wiping data...
Formatting FOTA:...
FOTA wipe failed.
Formatting DATA:...
Data wipe failed.
Formatting CACHE:...
Cache wipe failed.
Formatting DBDATA:...
Db data wipe failed.
E: Can't mount /dev/block/mmcblk0p3
(No such file or directy)
E: install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy application failed.
As you can see, there were clear error messages, so now I selected "apply sdcard:update.zip" ==> which brought me you into CwM Voodo Lagfix Recovery v2.5.1.x:
Code:
wipe data/factory reset
-- Wiping data...
Formatting DATA:...
Formatting DATADATA:...
Formatting CACHE:...
Formatting SDEXT:...
Formatting SDCARD:/:.android_secure...
Data wipe complete.
wipe cache partition
-- Wiping cache...
Formatting CACHE:...
Cache wipe complete.
Advanced > Wipe Dalvik Cache
Dalvik Cache wiped
Reboot system now
Phone looks now brand new.
Oh wait! I just examined the SD card and it contains all the old stuff. Nothing wiped, nothing formatted. And the Home button doesn't work. And the ticker-feed button reboots the phone... What's going on???
Edit: Looking into what you said
Hi all... tonight I decided to try the Samurai kernel. Unfortunately, it boot-looped on me. No big deal I figured, I did a full nandroid before in ACS's CWM, so I'll just restore. Unortunately, doing so isn't working: all of my apps, data and settings are gone! It basically looks stock (although, interestingly, all the Sprint bloat I had manually removed before still seems to be gone, so the restore worked to a degree)... I've restored backups before and never had a problem so I'm guessing the kernel is somehow the culprit, but I think that got restored from the backup too so I don't know what's going on. I'm stock EI22 by the way.
Can anyone help me? I'm pretty frustrated at the moment.
Thanks,
Frank
Try restoring an older backup. If that works you can attempt an advanced restore data only from your recent backup to see if it was something in your setup.
Sent from my SPH-D700 using XDA App
That was a thought I had too... I tried TWO older backups that I still had, same problem. I also tried a factory reset and then a restore (in theory it shouldn't make any difference to factory wipe first, and sure enough it didn't, but figured it was worth a shot).
My only other thought is maybe if I odin back to stock, root & install recovery and then try the restore again... kind of a shot in the dark, really shouldn't matter, but maybe.
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
DroidApprentice said:
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
Click to expand...
Click to collapse
I was thinking the same thing D. The only other thing I can think of is bad reads from the sd card.
I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.
frostinide said:
I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.
Click to expand...
Click to collapse
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I did not change the partition size at all. The backup before this one worked fine, so it can't be that. I also just did a new backup of today, and restored it. It worked at the first boot and didn't take extra time. I then tried restoring the broken backup again but ONLY data, and again I got a splash screen loop. I doubt multiple reboots will help, but I did try that.
I have an urge to mount the data backup and slowly take out folders until I find out the cause. If not for anything else, just out of my own curiosity.
Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I am facing exactly the same problems...
In same cases i got bootloops when restoring a Backup, in other cases i can boot after restoring but then my data is gone and i am asked to configurate my phone again with the wizard...
I never tried to boot several times if the data comes after some tries...
Btw I also didn't change the partitions...is it possible that it has something 2 do with link2sd?
In that case (@OP) I'm guessing its just a broken backup. This is why I always use Titanium as well. It takes up less space and you can restore it on almost any ROM.
Sent from my NexusHD2
Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.
Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
Marvlesz said:
Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.
Click to expand...
Click to collapse
I use Link2SD, i have ext4....i didn't change anything in the SD Card Layout since first install of the Rom and updated several times without any problem...
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium
Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....
jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.