PLEASE HELP!!!
CWM used to restore backed up ROMs, no problem. In the last 3 or so months, restores fail, without fail, while restoring data. I flashed a TWRP recovery and tried backing up/restoring through TWRP. Same problem. System and Boot restore fine, but Data always fails.
This was never a problem until around the beginning of November 2013. Does anybody know how to fix this? I've tried the wiping SD card method, backing up to internal memory, etc. etc. with no luck.
Thanks,
Turnip29
Other Recovery
turnip29 said:
PLEASE HELP!!!
CWM used to restore backed up ROMs, no problem. In the last 3 or so months, restores fail, without fail, while restoring data. I flashed a TWRP recovery and tried backing up/restoring through TWRP. Same problem. System and Boot restore fine, but Data always fails.
This was never a problem until around the beginning of November 2013. Does anybody know how to fix this? I've tried the wiping SD card method, backing up to internal memory, etc. etc. with no luck.
Thanks,
Turnip29
Click to expand...
Click to collapse
I had the same problem, installed another Recovery: and that solved the problem: http://forum.xda-developers.com/attachment.php?attachmentid=2464887&d=1387533161
turnip29 said:
PLEASE HELP!!!
CWM used to restore backed up ROMs, no problem. In the last 3 or so months, restores fail, without fail, while restoring data. I flashed a TWRP recovery and tried backing up/restoring through TWRP. Same problem. System and Boot restore fine, but Data always fails.
This was never a problem until around the beginning of November 2013. Does anybody know how to fix this? I've tried the wiping SD card method, backing up to internal memory, etc. etc. with no luck.
Thanks,
Turnip29
Click to expand...
Click to collapse
I've had this problem before. I am sorry, but if that particular backup is corrupted for whatever reason, then it's unrecoverable. The post above is your best option, flash a working recovery. I hope you didn't have any precious files saved to the device itself, but most of your photos and other media was probably stored on your SD Card which should be fine (unless you specifically wiped it).
Sometimes it's best to just start over anyway.
Related
I accidentally did a factory reset while in Safe mode. My first time ever getting into Safe mode and I have no idea how I got in there, only realized after the wipe. Thus, I lost all my pictures, videos etc... I made a Nandroid backup before the wipe so that got deleted as well. I have another Nandroid backup on my SD card that I have been trying to copy to the phone's internal memory but I keep getting errors.
First error on CWM was the annoying MD5 mismatch - I think I was able to fix that with the terminal emulator and the Notepad++ and MD5 calculator. Then the next error was, 'error restoring boot image.' I made this Nandroid backup with Semaphore 2.7.4 and still is my kernel now.
I believe this Nandroid recovery is corrupted. Is there any chance of recovering it? I've tried PhotoRec and Recuva already and they didn't work for me. PhotoRec gave me weird filenames and Recuva didn't find the stuff I was looking for. I still have this untouched backup on my SD and everything else on the SD works by the way.
Zytorious said:
I believe this Nandroid recovery is corrupted. Is there any chance of recovering it?
Click to expand...
Click to collapse
Have you tried to flash your semaphore kernel + recovery via Odin/Heimdall, so you have a clean recovery?
Cheers
EDIT: If this isn't working for you, you are always able to flash a stock samsung rom and then get back to your current rom + recovery.
If this does not work, i would guess your backup is corrupted. Had this by myself in the past... corrupted backups
Hello!
Before I want to go on to CWM I want to tell you what happened before.
Yesterday I flashed TWRP recovery which resulted in a really bad situation. I was stuck in recovery. If I pressed reboot it went straigt to recovery again, even if I pulled out the battery. So flashed the stock firmware via the KDZ flashing method and everything worked again.
Then I rooted again, installed CWM, installed CM, installed all my apps (TB backup on PC was quite old),....
So all in all it was a big amount of work and it took me a few hours.
Then everything was working again as it should and I updated all my TB backups and then I wanted to make a Nandroid backup so that I wouldnt have to do all that flashing and installing again.
So I went to recovery--> backup and restore --> backup
But it didnt finish. It always stopped with this error: Error while meaking a backup image of /system!
So i thought maybe I should install everything again, which i did. (I had already made a TB backup of all my apps, so i thought this woulb be done fast)
Well, went to recovery again, did a factory reset, wiped dalvik cache and even formated /system. Then I installed the latest CM + GAPPS and rebooted.
And the first thing i recognized was that the screen popped where it says "android is upgrading". And I wondered even more when I realized that all my apps where stille there. So obviously the factory reset and also format /system didnt work properly.
If I format /system and dont install any ROM then the device doesnt boot (which i guess is the normal behaviour). But what I want to say is that the format works there but if I flash CM afterwards all my apps are still there (despite the fact that i also did a factory reset).
All in all the phone does work normal now, but I'm not able to make a Nandroid backup and I'm really wondering why.
(I also reflashed CWM recovery but that didnt change anything)
I would be glad if s1 could help me.
PS: Could the solution be to flash stock again via KDZ and then do everything from the beginning?
Never heard of anything like this before.
Did you flash the recovery as a .IMG or through Rom manager (I would suggest to flash it with Rom manager).
Try this and report back (maybe your recovery image is damaged or smth.)
Sent from my LG-P880
I have no idea what caused this crazy behavoiur of CWM, but I started over again with flashing kdz and now everything is fine
Maybe your SD card is full. Try deleting a few files from your SD and then do the backup.
Sent from my GT-I9070 using xda premium
I dont have any external sd card and on phone memory there were more than 10GB free space
Is it possible to retrieve data from a soft bricked phone (failed to mount /system (invalid argument))?
I was so absent minded that I actually copied out a TB backup from 2013 (I probably saved it into another folder) into my computer instead of the latest copy. I am hoping to be able to retrieve my latest TB backup copy from the internal SD.
Before disaster happened, was already rooted with custom rom on JB 4.3.
What happened:
Tried to update from 4.3 to 4.4 through Odin but halfway got stuck at boot.img.
Unplugged and tried to reset but phone was stuck in the screen - firmware upgrade encountered an issue... ......
Flashed a kernel found in this forum to get it out of that screen.
Managed to get into recovery (android recovery instead of CWM) and there was an error with mounting /system, /data and some others which I can't recall.
So I tried flashing 4.4 again and finally after multiple attempts including changing ports and cables was the flash was successful.
Then I rooted and tried to restore my backups which was when I realised that I have the old backup files instead.
Couldn't find my latest backup anywhere which is why I'm here.
Any advice would be very much appreciated.
Thanks all for viewing.
netty88 said:
Is it possible to retrieve data from a soft bricked phone (failed to mount /system (invalid argument))?
I was so absent minded that I actually copied out a TB backup from 2013 (I probably saved it into another folder) into my computer instead of the latest copy. I am hoping to be able to retrieve my latest TB backup copy from the internal SD.
Before disaster happened, was already rooted with custom rom on JB 4.3.
What happened:
Tried to update from 4.3 to 4.4 through Odin but halfway got stuck at boot.img.
Unplugged and tried to reset but phone was stuck in the screen - firmware upgrade encountered an issue... ......
Flashed a kernel found in this forum to get it out of that screen.
Managed to get into recovery (android recovery instead of CWM) and there was an error with mounting /system, /data and some others which I can't recall.
So I tried flashing 4.4 again and finally after multiple attempts including changing ports and cables was the flash was successful.
Then I rooted and tried to restore my backups which was when I realised that I have the old backup files instead.
Couldn't find my latest backup anywhere which is why I'm here.
Any advice would be very much appreciated.
Thanks all for viewing.
Click to expand...
Click to collapse
I'm not quite sure what you are trying to say, your phone is able to boot but you can't find backups that were stored on your internal SD before flashing 4.4? Have you tried looking for them with Total Commander? (Or any other file manager with root access).
ArkThompson said:
I'm not quite sure what you are trying to say, your phone is able to boot but you can't find backups that were stored on your internal SD before flashing 4.4? Have you tried looking for them with Total Commander? (Or any other file manager with root access).
Click to expand...
Click to collapse
It was soft bricked for awhile and then I managed to flash a rom successfully so afterwards it was able to boot. Actually it seems like my entire phone was wiped because I couldn't find traces of anything with a file manager.
netty88 said:
It was soft bricked for awhile and then I managed to flash a rom successfully so afterwards it was able to boot. Actually it seems like my entire phone was wiped because I couldn't find traces of anything with a file manager.
Click to expand...
Click to collapse
Is /data/media/0 empty?
ArkThompson said:
Is /data/media/0 empty?
Click to expand...
Click to collapse
Yup, empty. I meant that it was all there before I flashed 4.4 but I saved the wrong backups and after flashing I couldn't find them anymore.
netty88 said:
Yup, empty. I meant that it was all there before I flashed 4.4 but I saved the wrong backups and after flashing I couldn't find them anymore.
Click to expand...
Click to collapse
Odin probably formats the main partitions when it flashes a ROM. I had something similar happen after flashing 4.3 to recover from a softbrick. Did you ever make a nandroid backup or did you only use TB? Also, if you lost your contacts you could check whether they were also saved onto your sim card.
ArkThompson said:
Odin probably formats the main partitions when it flashes a ROM. I had something similar happen after flashing 4.3 to recover from a softbrick. Did you ever make a nandroid backup or did you only use TB? Also, if you lost your contacts you could check whether they were also saved onto your sim card.
Click to expand...
Click to collapse
Nandroid is the one that is saved as update.zip?
netty88 said:
Nandroid is the one that is saved as update.zip?
Click to expand...
Click to collapse
No, you make them using a custom recovery and they are a series of .tar, .img or .win files.
ArkThompson said:
No, you make them using a custom recovery and they are a series of .tar, .img or .win files.
Click to expand...
Click to collapse
I did make a nandroid backup but it couldn't be found after the soft brick recovered
netty88 said:
I did make a nandroid backup but it couldn't be found after the soft brick recovered
Click to expand...
Click to collapse
If you don't have any backups on your external SD then you might be out of luck unfortunately.
ArkThompson said:
If you don't have any backups on your external SD then you might be out of luck unfortunately.
Click to expand...
Click to collapse
I did suspect that... Just wanted to be sure. But thanks so much for your help
I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.
The situation is a little complicated, so I'll explain step by step. I appreciate any help, idea what what caused this or if I can do anything to fix. Please, write if you have even a little clue.
- The top speaker (earpiece) was faulty. I wanted to change it.
- I damaged signal antenna port on motherboard while changing the speaker.
- Anyway, phone was working in all this process. Just no signal.
- After, removing motherboard for a second time, phone didn't boot up.
- I flashed a custom rom via TWRP. (phone was already unlocked.). Didn't boot.
- I flashed MIUI via TWRP. Didn't boot.
- I flashed MIUI via Xiaomi Flash Tool. Didn't boot.
- I am able to enter fastboot and recovery.
- It's charging, without problem.
- It doesn't stuck on kernel phase (It passes the MI screen).
- It stuck on boot screen. I have waited really long times, more than 30 minutes.
Do you think, I f***ed up the motherboard? Why it doesn't boot? Please, share if you have any idea.
@baggord
If the motherboard was dead, you'd not be able to turn on your phone.
Sounds like software to me at the moment.
Some ideas:
Are you on the latest twrp version (3.2.3-0)?
Did you try reflashing latest twrp via fastboot (not from within twrp)
and then wiped all partitions (including mounting and also wiping vendor) following a formatting of the data partition (where you need to type "yes") following a reboot to recovery?
Did you try restoring the efs partition from a backup where everything worked?
Would also rather try a stable custom ROM to test.
Hi,
If nothing worked, follow the instruction of this video. It worked for me after dropping my phone in water.
Sorry for my poor English?
Phil_Smith said:
@baggord
If the motherboard was dead, you'd not be able to turn on your phone.
Sounds like software to me at the moment.
Some ideas:
Are you on the latest twrp version (3.2.3-0)?
Did you try reflashing latest twrp via fastboot (not from within twrp)
and then wiped all partitions (including mounting and also wiping vendor) following a formatting of the data partition (where you need to type "yes") following a reboot to recovery?
Did you try restoring the efs partition from a backup where everything worked?
Would also rather try a stable custom ROM to test.
Click to expand...
Click to collapse
I tried flashing twrp via fastboot. I've also tried stable custom rom and stock rom.
I'll try to format all partitions then re flash a rom. I don't have an efs partition backup. Can I backup in this situation or do you think it's already gone?
Thanks for the reply!
Kabula2000 said:
Hi,
If nothing worked, follow the instruction of this video. It worked for me after dropping my phone in water.
Sorry for my poor English?
Click to expand...
Click to collapse
Hi, thanks for the reply. I'll check it out.
baggord said:
I don't have an efs partition backup. Can I backup in this situation or do you think it's already gone?
Click to expand...
Click to collapse
An old efs backup could have been of use, as sometimes important things like the imei get lost and you would only be able to restore it via this partition.
Next time better make an efs backup right away and store it at a safe external place in case you one day might need it.
In this scenario it's too late.
If it's faulty you only backup something that doesn't help you later.
Might still be that your problem has another source.
Then, if we found out a solution and everything is working well again, of course you could make that backup.
Please tell us if the wiping and formatting changed anything.
Good luck!
Phil_Smith said:
An old efs backup could have been of use, as sometimes important things like the imei get lost and you would only be able to restore it via this partition.
Next time better make an efs backup right away and store it at a safe external place in case you one day might need it.
In this scenario it's too late.
If it's faulty you only backup something that doesn't help you later.
Might still be that your problem has another source.
Then, if we found out a solution and everything is working well again, of course you could make that backup.
Please tell us if the wiping and formatting changed anything.
Good luck!
Click to expand...
Click to collapse
I am out of my home town, currently. I will inform you when I get back to town.
Thanks for the replies.
@Phil_Smith
I talked to my brother since I'm out of town.
He wiped all partitions including vendor.
Reboot into recovery. (format data returned error, before reboot)
Then format data. (worked fine)
Reboot into recovery.
Flashed a custom rom.
It boot up!
Thanks.
IMEI stays by the way. Now we need to fix the antenna somehow. Phone is still alive, at least. Thanks again!
baggord said:
@Phil_Smith
I talked to my brother since I'm out of town.
He wiped all partitions including vendor.
Reboot into recovery. (format data returned error, before reboot)
Then format data. (worked fine)
Reboot into recovery.
Flashed a custom rom.
It boot up!
Thanks.
IMEI stays by the way. Now we need to fix the antenna somehow. Phone is still alive, at least. Thanks again!
Click to expand...
Click to collapse
Nice, glad that you're good again!