I made a Backup in my old rom (miui 12.5) with the idea of restoring ONLY application data in the rom that I would install later (Pixel Experience A13). When I installed the rom I started it normally, went into recovery mode to restore the backup, and I didn't know which partitions to select. I selected Data(exclude...whatever) and boot once it was done I just rebooted to the system and it stayed at the google logo. Flash a zip (I don't know what it's for, I just know it's necessary to use the rom in the first place) and reboot the system again and this time it started fine....I found the miui launcher and more applications they were installed (logically if the back up was from miui I was going to find that) so I decided to delete them, but when I connect to the internet something very curious happens, the phone after 10-20 seconds turns completely black. I restart it and nothing, absolutely nothing, loads the google logo and launches me into what I think is the system, but with a completely black screen. Help please, I can use the rom normally but I really need that app data
Have you tried to do a factory reset? That will probably return the device to a working state (erase the data partition). If you included data partition in your backup, you should be able to extract /data/app folder, reboot and then extract /data/data folder and fix permissions onto your phone from TWRP
Related
So, just messing around after i wiped my phone to install a different ROM, I did a backup of my wiped phone. If their is nothing on the phone, what is it actually backing up? It was like 365mb file, and I was to scared to run it after the fact (because I just know one of these times I'm going to push the limits and screw my phone up with my curious thoughts).
It's backing up the /system directory (mostly) along with the bootloader and clockworkmod recovery. The "wipe" option simply deletes everything on your cache and data partitions. You use it when:
~ You want to switch from (example) a rom to a different kind of rom, say virtuitous to cyanogenmod
~ You want to start from scratch again
Clockworkmod wouldn't let you delete your system partition without installing a new rom... this would be a bad idea
You can restore and boot off of that recovery you just made. It'll boot up with the "touch the android to begin" and google account setup wizard.
Sent from my T-Mobile G2 running Cyanogenmod.
ibemad1 said:
It's backing up the /system directory (mostly) along with the bootloader and clockworkmod recovery. The "wipe" option simply deletes everything on your cache and data partitions. You use it when:
~ You want to switch from (example) a rom to a different kind of rom, say virtuitous to cyanogenmod
~ You want to start from scratch again
Clockworkmod wouldn't let you delete your system partition without installing a new rom... this would be a bad idea
You can restore and boot off of that recovery you just made. It'll boot up with the "touch the android to begin" and google account setup wizard.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
Ok, so What ROM will be running though? Would it be the one that I had before the wipe?
***IT HAPPENED A SECOND TIME. THIS TIME I WAS ABLE TO FIX IT BY CLEARING CACHE/DALVIK CACHE AND FLASHING A NEWER VERSION OF THE THE SAME ROM***
Hi guys,
I recently bought a Desire and loaded LeeDroid on a week later. Everything's been fine, until today, when I shut-down my phone and went to turn it back on, and it froze at the Telstra (telco who I bought it from) splash screen.
Here's what I did:
- Power + Vol- + trackball, which resulted in it restarting and freezing at the same point (15 minutes wait)
- Pulled battery and booted into recovery
- NAND Backup using AmonRA
- Restored original (pre-LeeDroid) NAND backup, and rebooted, which resulted in phone freezing at the same point
- Shut down, removed SD Card, wiped using AmonRA, restored original (pre-LeeDroid) NAND backup, which enabled it to boot properly
- Restarted and flashed Leedroid Rom from ZIP, which worked fine.
- Restored today's NAND backup, which of course brought everything back to square one.
Can anyone tell me if it's possible to access any of the contacts/SMS/etc? I was planning to back-up tonight as I'd put a whole heap of stuff in today, so of course this arvo was when it had to die. That and there's some stuff I'd really like to have that I'm not sure the relevant apps have stored on the SD.
And how can I ensure a clean restore? Run Telstra's RUU, then install LeeDroid as per instructions?
(EDIT) I notice that the NAND backups consist of a bunch of .img files. I imagine that data.img might have what I'm looking for in it. I've tried searching for a way to explore the contents, but I'm still trying to get unyaffs running...
Reflash or wipe cache and dalvik cache and reflash.
Sent from CM7
So you're suggesting I do the following?
- Restore freezing NAND backup
- Wipe Cache + Dalvik Cache
- Reflash LeeDroid from zip
Are the contacts all google contacts? If so you can recover those that way.
When you signed in for the first time after flashing the rom, while linking your google account, did you check "backup this phone to google servers"? If so, that should restore things if you wipe all and reflash the rom.
I used this option for the first time, and my wallpaper, shortcuts, alarm settings and SMS all restored after 5 minutes or so.
Unfortunately not. I didn't make the same mistake this time though >_>
Even so, I'm still hoping I might be able to pull some of the stuff out of the NAND backup.
Do you know if it's possible to fake/bypass the md5? If I can swap the data.img from the busted backup to a working one (the one before I put all my contacts in etc) then I should be able to access something.
Unfortunately that brings up an error, and I imagine the checksum is what's doing it.
Hey guys, got a strange problem here. I'm running MIUI-XJ 2.3.30 A2SD.
Had 8 apps to update via Google Play and 31mb internal left (over 600mb on sd-ext, too). In the middle of updating the apps I've got a Google Play crash followed by few other fc's, phone said my internal memory is too low to operate and such - so I tried the most obvious fix, which is of course rebooting the phone.
That was a mistake, apparently. Phone will not boot anymore - goes through the bootscreen and gets stuck on the yellow MIUI splash. It's not a bootloop, the phone just freezes and the only thing I can do is battery removal. Tried booting it up with no sd card as well, nothing seems to help though.
Is there anything I can do except full wipe via recovery? I had some important sms and spent quite a bit of time customizing the desktop, I'm not to keen on doing that again.
Is it possible to delete some apps via adb or something like that? Or is there a point in trying to install the rom again on top of my system?
Thanks in advance, help really appreciated!
Try clearing dalvik cache and cache from recovery and then boot. Thereafter clear some space or change your a2sd scheme.
Thanks for the answer! Makes me feel silly I did not think of that myself lol, sounds like an obvious solution.
Problem is, it still does not seem to help though - wiped /cache and dalvik-cache on data, sd-ext and system - still nothing, same problem persists. Stuck at MIUI bootanimation.
Any other ideas? I'm really kind of desperate to recover the data.
- Take a nandroid backup first. So you can start over if need be.
Some things to try
- Only flash ROM and see if it helps.
- Wipe data. Flash ROM fresh. Install Titanium Backup. With TB locate nandroid on sdcard and try to extract your data. Maybe restoring the launcher and messaging will do the trick. Not sure . Try. You can always start over.
- Fix permissions in recovery
There's an app called AROMA Filemanager that can be started from recovery and allows you to modify all phone partitions, all you need is to mount them before starting the app. Here it is:
http://forum.xda-developers.com/showthread.php?p=25911276
Tried flashing the ROM again on top of my system - no effect whatsoever, still gets stuck at bootanimation. Also, tried the permission fix as well as the RMD recovery "apk uid mismatches" fix. Still nothing.
Going to give the AROMA a try, having some problems right now though - using RMD recovery, no touch support. Trying to flash 4ext touch from fastboot somehow!
Thank you. Will keep you updated.
UPDATE//
Managed to get the AROMA up and running, deleted few apps from /data/apps, nothing to delete from /system really. /cache is cleared, so are all 3 dalvik-cache folders.
System still does not want to start.
Any ideas what might have happened? Seems like I'm running out of options and will have to do a clear install, after all.
You probably damaged some important system files so tho phone can't load system. The best solution is to restore some nand backup if you have, or to do a full wipe and start from scratch.
Sent from my HTC Desire using Flashes and Thunders
If that was the case, reflashing the ROM on top of my current system should fix the problem, while it didn't - right? Also, I find it hard to believe that "important system files" could have been damaged during routine Google Play apps update...
Than a full wipe and fresh install is inevitable...
Sent from my HTC Desire using Flashes and Thunders
My phone is stuck on the boot screen (it's rooted and i have clockwork mod) and normally when this happens, i would just factory reset and it would work just fine but all my photos would be wiped. This time I have really important photos that I didn't back up so I was wondering how I could back it up. Unfortunately I didn't have debugging mode enabled so it doesn't show up when i plug the phone into my laptop
What can I do to backup my photos?
a factory reset/data wipe(NOT the one that wipes the ENTIRE /data partition, I use twrp I can't remember what they call it in cwm) might allow your device to boot by erasing userdata/settings/installed apps and such, BUT it leaves /data/media intact which is a link to /sdcard where all your photos are stored.
a factory img restore WILL WIPE ALL /data, so don't do THAT yet.
if you have any rom zips on device you can TRY booting recovery and install it and then try to see if it boots.
recently I got stuck at boot and had to reflash my commotio zip in order to boot device.
TL;DR of the problem: Can't mount the User Data Partition in TWRP, so I can't wipe it or do anything to it. Stock Recovery and Fastboot mode can't see it or mount it either, it's like it doesn't exists at all.
Is there any way to restore the default partitions?
How I created this mess: I tried to remove the encryption and failed (TWRP recovery and then wiping the data and userdata partition), so I tried flashing it using a Stock rom from another site (I'm not sure if I can link it since it's an external site so I'll just put the file name XT1710-06_ALBUS_ATTMX_8.0.0_OPSS27.76-12-25-15-2-4_cid50_subsidy-IUSMXLA_regulatory-DEFAULT_CFC.xml.zip) but the sparsechunk 6 (everything else was successful) failed to flash and I've been stuck on bootloop (it turns on, tries to load the OS and sort of manages but then it restarts itself) since then but now it's like the userdata partition doesn't even exists, it can't be mounted, can't be wiped, can't be restored (from TWRP) nor factory restored (STOCK RECOVERY).
So I am here asking any of you if there's a way to restore the partitions, specially since I don't really know if there's a way or the sizes/formats.
Also I've read about a blankflash but I'm not sure about the results I've found using google (it scares me to screw this even more). Could this fix my situation?
Please let me know if more data is needed (also how to get it so I can post it).