Related
Hi,
I had a problem with my NDT miui nand buil recently, it was sticking on boot animation, so I made a backup via cwm, I saved the backup folder on my pc. Now I want to restore that backup. I tried all the usual methods for it, I did tas29, flashed new clk, and tried backup, still stuck on boot animation, I flashed my last rom and then tried to restore the backup, again stuck on boot animation. I did everything for it, but doesn't works for me. It does the restore process as usual, but I wan't to boot, my phone stuck in boot animation. So I beg you to help me with one of these alternatives, please.
-I only want to restore my contacts, call logs and sms. Anyway to restore them only? there are some .img files in backup folder, which one are these files stored?
-Is there anyway I can extract backups files on my pc and get my contacts,sms,... in it?
-If none of above works, is there anyway to install cwm on pc android emulator, and then restore my backup in it, and again get my contacts,sms there?
I will really be thankful of your helps
behnam2016 said:
Hi,
I had a problem with my NDT miui nand buil recently, it was sticking on boot animation, so I made a backup via cwm, I saved the backup folder on my pc. Now I want to restore that backup. I tried all the usual methods for it, I did tas29, flashed new clk, and tried backup, still stuck on boot animation, I flashed my last rom and then tried to restore the backup, again stuck on boot animation. I did everything for it, but doesn't works for me. It does the restore process as usual, but I wan't to boot, my phone stuck in boot animation. So I beg you to help me with one of these alternatives, please.
-I only want to restore my contacts, call logs and sms. Anyway to restore them only? there are some .img files in backup folder, which one are these files stored?
-Is there anyway I can extract backups files on my pc and get my contacts,sms,... in it?
-If none of above works, is there anyway to install cwm on pc android emulator, and then restore my backup in it, and again get my contacts,sms there?
I will really be thankful of your helps
Click to expand...
Click to collapse
Are you using the correct partition size? Too small a partition normally causes the phone to hang at the bootanimation. If you have used the correct partition size and it still doesn't boot, try simply increasing it to account for any bad blocks you may have.
It's also possible that your backup is corrupted somehow, it happened to me once. If this is the case, try flashing the same ROM and then restoring the data partition in CWM.
When you rename backup file do not use spaces (exp. icsromv3)
Sent from my E15i using xda premium
2010matej said:
When you rename backup file do not use spaces (exp. icsromv3)
Sent from my E15i using xda premium
Click to expand...
Click to collapse
I don't think that's the problem because if the ROM gets up to the bootanimation (after a Task29) then it's clearly been [somewhat] flashed correctly so it's probably down to the backup itself, or of course an error somewhere on his part.
behnam2016 said:
... it was sticking on boot animation, so I made a backup via cwm, ...
Click to expand...
Click to collapse
Come on guys, this is common sense. If he made the backup with the rom ALREADY not booting up, no matter what he does, it'll always stick to the boot animation.
The back-up saves your ROM at its current state, not the one it was working at before. Backups should only be done when your ROM is actually fully functioning, not when it is broken. So unfortunately, you have to do what Nigel Suggested. Make a clean install of that ROM and then only restore the data partition.
You may be able to do the emulator thingy, but I'm not sure, you can give it a shot though.
For extracting something from your backup see appextractor or nandroid browser
Marvlesz said:
Come on guys, this is common sense. If he made the backup with the rom ALREADY not booting up, no matter what he does, it'll always stick to the boot animation.
The back-up saves your ROM at its current state, not the one it was working at before. Backups should only be done when your ROM is actually fully functioning, not when it is broken. So unfortunately, you have to do what Nigel Suggested. Make a clean install of that ROM and then only restore the data partition.
You may be able to do the emulator thingy, but I'm not sure, you can give it a shot though.
Click to expand...
Click to collapse
Whoops, I should have read the OP more carefully
@OP Yeah, just fresh install then restore the data partition. I still don't understand why the other ROM isn't working though unless it's your fault somwhere
Hey guys,
I recently encrypted my phone for my work e-mails (the Exchange server required it). I made a complete Nandroid backup and also entire Titanium backup before encrypting, just in case something went wrong. But the encryption went beautifully.
However, I've noticed that I cannot mount /sdcard or flash anything from recovery. I can't update my Franco kernel or CM nightlies... It's a bit annoying because I want to keep flashing! lol.
My phone asks for my password everytime I reboot (in order to decrypt sdmount and mount the ROM), so I'm assuming this is the reason I can't mount it in CWM recovery.
Anyone know of a bypass or fix for this?
I don't really feel like restoring nandroid backup or doing a factory reset everytime I want to flash a new nightly, it just doesn't make any sense (besides I haven't even tried to see if I can restore from nandroid or factory resetting, they might not even work because it can't mount /sdcard?...)
I've searched around the forums for some complex solutions such as using ADB or Odin but I'm not interested in that.
Thank you!
UPDATED:
Ok guys so basically restoring from nandroid did not work because of the sdcard mount error.
I did a factory reset, erased all data and format system. But I couldn't format sdcard or even user data as it didn't have access... Basically the phone got bricked from then on and I had to completely restore back to stock bootloader/recovery/stock rom with adb/fastboot. Instructions are found here:
http://forums.androidcentral.com/nex...e-restore.html
Hopefully this will come to use to someone else. I've heard that TWRP does not have this sdcard mount problem with encryption as does CWM, so that's what I installed this second time around.
Why don't you just transfer the files regularly without entering recovery mode?
The recovery doesn't allow mounting to the PC. It just doesn't work.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Why don't you just transfer the files regularly without entering recovery mode?
The recovery doesn't allow mounting to the PC. It just doesn't work.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I've never mounted to PC in recovery. My files are backed up on my computer and nandroid as well.
My issue here is that I can't regularly flash new nightlies (and thus mount internal /sdcard to do so) following the phone encryption.
Since my internal /sdcard path is encrypted with a password, CWM recovery can't bypass this and it gives me the error "cannot mount /sdcard".
bump?
Any help would be highly appreciated!
Is this a lacking feature in CWM Recovery? Have the developers looked in it? Or is there already a fix for this without doing an entire factory reset?
Daily bump.
Anyone there? (echo...)
Ok guys so basically restoring from nandroid did not work because of the sdcard mount error.
I did a factory reset, erased all data and format system. But I couldn't format sdcard or even user data as it didn't have access... Basically the phone got bricked from then on and I had to restore back to stock using this:
http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
Hopefully this will come to use to someone else. I've heard that TWRP does not have this sdcard mount problem with encryption as does CWM, so that's what I installed this second time around.
If you want to recover the data from SD card, you do not use the SD card.
You can try to recover the data from the card with some specific software.
I will try to fin one I used before.
It will take few minutes... do not use the card.
cyrus_e said:
Basically the phone got bricked from then on and I had to completely restore back to stock bootloader/recovery/stock rom with adb/fastboot. Instructions are found here: ...
Click to expand...
Click to collapse
Many thanks, this link helped me restoring my Nexus 4. I enabled "encrypted storage" and wanted to root the phone and almost bricked it.
It's also possible to flash the stock recovery with odin, then do a real factory data reset and be able to install a custom rom, after (or before) which you can reinstall a custom recovery.
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.
I ended up just flashing the stock google image and that at least gave me a working phone back.
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)
Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk
mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info