I was experimenting with the xposed framework and got stuck in a boot loop after restarting for a second time to install some more modules. The safe mode booting didn't work and neither did the included restore zip file for getting out of it. I tried to restore from the backup on the phone, but it already had the xposed framework in it and it got into a boot loop too!
I tried to adb sideload the backups that I made, and that didn't work either.
I keep backups, made from CWM Recovery, and I pull these to my computer using a WiFi file explorer. (I don't have enough storage to keep two alternative backups so I always have the second stored on my computer)
Anyway, I cant seem to get the restore file that I uploaded to my computer (a restore image) to reload on to my phone and restore. I have attempted to transfer it back to the phone into the folder it came from, but the file wont flash as a zip and it doesn't show up to be restored if I select the restore feature. (BTW-The restores have plenty of SD room to restore on, that isn't the issue)
I realize that the WiFI File Explorer that I use may be zipping the files, so shouldn't I be able to "install zip" in CWM recovery and it restores the image? (apparently not, can you explain why, and what I can do?)
Can I get access to the mnt/shell/emulated/clockworkmod/backup/ to put the file there to be restored again?
Or,.. How do I put the restore file on my phone (in the correct place) to be restored again?
Is my problem being caused by where I am pulling/pushing the file from(mnt/shell/emulated/clockworkmod/backup/)?
What am I missing/doing wrong?
Nexus 4
CM11 installer version xnpq08q
Rooted Unlocked
CWM Recovery
Related
I see this being discussed in many places but none of the solutions seems to work for me. Here's what I did.
1. Create update.zip (containing installed apps+data) with TB
2. factory wipe and flashed ROM (happens to be Wicked v8)
3. waited 5 minutes then rebooted
4. installed TB and its pro key from from Play Store
5. granted TB SU
6. went to recovery and tried to flash update.zip created in step 1.
7. FAILED!!!
What am I doing wrong here? For some reason, I'm experiencing a lot of problems with TB and TWRP (2.4.4.0). TB can't even extract frrom TWRP's nandroid backups.
When I did it, I did not install TB because it was included in the update.zip itself. I just flashed it directly after the ROM and it was fine. You might have some other problem going on, but perhaps it's that simple.
I found then problem. It's because TWRP's zip routine is compiled with 32bit switches so, any update . zip that's over 2gb will not work.
Sent from my Frosty Jellybean fingers.
my update.zip didn't fail but once cm 12.1 booted i didn't see any traces of it anywhere. any advice?
Hey quick question,
so I make a backup of my system for flashing. Then I move the backup onto a folder to my computer same with my titanium backup folder. So when I wipe and flash a new rom, I have all of my files for my system backup and my titanium backup on my phone. After I restore all of my apps after flashing the new rom, can I move the backup files and leave them on the computer as well as the system backup to save space? Is there anyway that I can still restore the system if it gets stuck in a bootloop - (besides flashing a new stock one)?
basically I want to store the system backup and the titanium backup on my computer so they are safe and because they take up about 4 gb of space on my phone.
I tried to be clear but let me know if I should further explain
Thanks
I wouldn't backup system apps with titanium, because they can vary from rom to rom. As long as you properly wipe your phone before flashing, you shouldn't get bootloops(can still happen). If you get a bootloop, try pulling the battery 1st. If your phone still bootloops, you have to use download mode and ODIN to flash stock ROM.
sent from somewhere
right which I have done before. I just want to know that if my phone does get stuck somewhere (has happened before, and I had to flash a stock rom and lost everything - lost backup) Would I be able to move my system restore and titanium backup files from my computer to my phone to be able to recover?
Basically store backups on computer, then if something happens, be able to transfer them back to phone
Thanks for the help
Generally it's good to leave backups someplace where they won't get easily corrupted or lost. Since the S3 has a microsd slot, sure, keep them on your computer and move them over if necessary.
My SOP is to keep the current backup on the microsd, and store the backups on my computer. Then if I need to reflash/nandroid back, they're there, and if my microsd is corrupted I have a known good backup.
b11aze said:
right which I have done before. I just want to know that if my phone does get stuck somewhere (has happened before, and I had to flash a stock rom and lost everything - lost backup) Would I be able to move my system restore and titanium backup files from my computer to my phone to be able to recover?
Basically store backups on computer, then if something happens, be able to transfer them back to phone
Thanks for the help
Click to expand...
Click to collapse
As long as you can get into your custom recovery after anything happens, backups will work. Make sure to backup system, data, and boot. If not and you have to flash using ODIN, like starting from scratch, you may have issues such as md5 mismatches.
sent from somewhere
ok I was just looking to see if it was possible or not to transfer backups from computer to phone if the phone cant turn on ie. stuck in download mode or recovery mode.
Hi,
I am running Carbon Mod Nightly Rom, I was looking at the Volume Blaster Mod (http://forum.xda-developers.com/showthread.php?t=2563209) to raise the volume up on the external speaker. I edited the file system/etc/snd_soc_msm/snd_soc_msm_2x. Somehow I screwed the file up after editing. After I edited it and rebooted, it gets stuck at the Carbon Logo and doesn't go any further :crying:. I have a nandroid backup, but I didnt backup until after I edited the file (before reboot). So I'm wondering can I or how do I replace the edited file (snd_soc_msm_2x) with the original file. I have the original file on the SD card in the phone. I went into the TWRP Recovery and into file manager, but I could not locate the location of the edited file from within there (system/etc/snd_soc_msm/snd_soc_msm_2x). Can someone please help me restore this one file so that my phone will boot up or tell me how would be the best way of getting my phone up and working again ASAP. Oh, I have tried exploring the backup created with Nandroid Backup Manager, well I found the file thats corrupted and opened it with File manager, select all- then delete, then pasted the contents from the working file, and then try to save, and I get an error "Operation Failed". So any help would be greatly appreciated.!!
Thanks in Advance
If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.
DocHoliday77 said:
If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.
Click to expand...
Click to collapse
Dirty Flash? I'm new to all this, so I need some help with the slang. I can explore the contents of the Nandroid backup, are there anyway possible to delete a file in the Nandroid backup and replace it with another file?? If I can do that, then I can replace the corrupted file and then restore from backup. I just dont want to reflash the clean ROM and then have to manually restore all my apps, sms and photos...
If I flash the backup Rom that has the corruted file, and before reboot, can I use the file manager to pull the clean file from the external card and replace the one that corrupted in the root folder. If I can do this, then it should boot normally. Otherwise if I boot with the corrupted file it gets hung after it processes all the apps. (Gets hung on Starting Apps).
I figured it out!!! What I did was I went into recovery, and selected the recovery nandroid backup file that was corrupted. Instead of restoring all the available options, I unchecked System. So it restored everything but the system data. The system data already installed was from the newly installed rom that was working, so by leaving the system unchecked it didnt install the corrupted system from backup! I hope I explained this where you can understand it.
Thanks for all the help DocHoliday77!! I'm just glad that worked and I dont have to manually install everything back over!!
:victory:
The strangest thing happened on my wifi Nexus 7 2013. I'm running Android 5.0 (Lollipop), unlocked and rooted (using Nexus Root Toolkit), with TWRP.
TWRP was working just fine until yesterday. afternoon. I ran a backup around noon and everything was fine. I could access and manage the backup folder under 'TWRP' from Root Explorer, ES File Explorer, and my computer (through USB cable). Copying, etc., all was working fine.
Then, later in the afternoon, I did another build and things are different. The backup completed just fine, but after rebooting I can't see the backup folder from my computer or Root Explorer, so I can't copy it to my computer or a OTG flash drive. I see it in ES File Explorer, but its icon has a big question mark and when I tap it to open the folder, I get an "Open As" dialog. I can't remove the folder (is it still a folder?), or rather the removal doesn't 'stick'; in other words, the folder keeps coming back. The only way I can remove the backup is from the File Manager within TWRP itself. All backups after the one I did yesterday afternoon now behave that same way now. They're taking up a lot of unusable space like this.
It's the strangest thing. I actually ended up going back to stock and root again, just to see if that makes a difference. But what's really odd now is the TWRP folder itself now has the question mark. So this behavior persists even with completely starting fresh.
Does anyone have any idea what's going on here? I *believe*, but I'm not entirely sure, that TWRP was updated from 2.8.0.x to 2.8.1 between these backups. Could it have something to do with that? How do I copy the backup folder to my computer or a flash drive for safekeeping outside of my Nexus?
Thanks!
Ron
I'm having this same issue right now. I need to restore from a backup but I am unable to access the twrp folder as it is corrupted or something. Reflashed stock 5.0 and the issue persists. Nexus 5 though.
Okay I fixed the issue, this is what I did.
- Wiped everything in twrp
- Flashed factory 4.4.4 image
- Flashed previous version of twrp
- The folder was now normal, so I added my old backup to it
- Restored from backup and all is good.
If I had to guess, it looks like a lollipop issue. I also had problems with recovery changing back to stock when lollipop was installed. I'm sticking to my perfect 4.4.4 setup or now.
I just replaced TWRP with ClockworkMod recovery, and I'm seeing the exact same thing there! The ClockworkMod folder has a big question mark and is essentially inaccessible. I wonder if this is a Lollipop issue.
--Ron
I *think* I resolved the problem (thanks to this post in the Nexus 5 forum):
Open a terminal emulator application and enter the following two-line command (press enter after each line):
Code:
su
restorecon -FR /data/media/0
After doing that and rebooting, the TWRP and ClockworkMod folders seem normal again and I can access them, and the backups in them, as normal.
--Ron
I think it is a lollipop issue. It doesn't seem to like custom recovery. My folder stopped working after trying to transfer a backup to it from my computer. I also had to flash twrp twice or more because it would keep reverting to stock recovery after reboot.
I put TWRP on it and can boot to recovery. However, it fails flashing the Cyanogenmod zip because (it says) you need to wipe the device due to an incompatible device layout. So I tried that and naturally it wiped the zip off the /sdcard. Then I mounted the sdcard from TWRP but I couldn't write to it from my computer. (I could see the now-empty drive.) So I said what the heck and rebooted the system and had a like-new device.
I had backed that up before I did anything. So transferred another copy of the cyanogemod zip to the tablet, rebooted to TWRP and tried to install it again. Still no luck. I then transferred my backup to my tablet and restored the backup so I'm back where I started.
Is there another way I haven't thought of?
I put 12 on my n5110 before I found slim rom 4.4.4. Had no trouble with the install of either one. Have you tried putting the cm zip on the external sd card and installing from that using twrp? I also think you can use either Odin or adb but as I recall the methodology will be different. Lots of people with a lot more experience here maybe someone else has some suggestions as well.
Regards
Expat