Attempted upgrade from EOS 155 again today prepared from my mistakes of last time...
Upgrade refused to load past log in screen (on main account, funnily enough secondary one I made in 155 worked fine, main one would freeze as soon as I put in pattern)
Anyway short story after factory reset decided I didnt like 4.2, just seemed far too laggy even out of the box nothing installed
So went to restore backup in clockwork mod... get failed to restore /system (backup is definitely OK as used it after last failed upgrade to restore from)
I can flash 155 back on OK and loads up fine, but every time I try to restore that (or any other backup including a brand new one from the clean 155 install) I get failed to restore /system
Have tried formatting /system partition first but dont seem to do anything
Any ideas?
Related
Just curious if anyone else has experienced any of the following:
I was running CM10.0.0, but had that issue where my NFC was unchecked. So i wanted to restore to a TW ROM so i can check on NFC, restore back to CM10, etc.
I did a backup. Tried to restore my old TW (synergy r73), but got an error in CWM 6.0.1.2:
Error while Restoring /System!
Then i got the same message for ALL of my nandroid backups, including the newest one i made of CM10. I did some searching and found tons of folks with the same issues, but no solutions beyond.. format your SDCard properly (which mine is).
That's fail #1.
After being unable to restore, i just flashed CM10 zip again and started over. I did however use that new Titanium feature where it makes a flashable zip of all of your apps a few days back.
But every time i try to flash the zip, the phone resets in the middle of the install. I've never seem CMW crash and reboot.
That's fail #2.
I ended up restoring apps the old fashioned way, but regardless... any ideas?
Thanks,
Mangler
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
papadelogan said:
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
Click to expand...
Click to collapse
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
buhohitr said:
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
Click to expand...
Click to collapse
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
papadelogan said:
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
Click to expand...
Click to collapse
That would be the right way..good luck!
buhohitr said:
That would be the right way..good luck!
Click to expand...
Click to collapse
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
papadelogan said:
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
Click to expand...
Click to collapse
I have high confidence that you will have this issue resolved shortly. It's not your fault, lately, some custom roms did not behave accordingly...
I have z5 regualr, i have carbon rom installed everything fine on older phone works good but the mic. Made a full back up in TWRP 3.1.1.0.
So i got another new phone same exact kind E6653, TWRP 3.1.1.0. I transferred the backup from the original phone and tried restore it. No go. Got an error on data partition, "extractTarFork() process ended with ERROR: 255".. i tried many things and eventually gave up. So i decided i'll do a new install and titanium backup ill transfer all my data and apps. But after formating the phone and installing newest open gapps for amd64 7.1 standard, my programs start automatically closing, market, phone.. and so on. So i did cache and davlik clear.. no good....
I am out of ideas for tonight, anyone want to shed me some light ?
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.
Well, I just did something bad. I have a new Exynos-based S7 (SM-G930W8), which I unlocked, rooted, and installed LOS on. So far, so good.
I then proceeded to root my old S7 (same model), ironically to make it easier to transfer over the application data... Things went so smoothly on the first device I did not take the time to make a backup (so I did not realize that TWRP is not able to mount the /data partition).
I rebooted to Download mode, flashed TWRP twrp-3.5.0_9-0-herolte using Odin 3.13, and rebooted to Recovery. I then followed the same steps I took with the other device (Install of no-verity-opt-encrypt-6.1, and Magisk-v21.4). After rebooting I am greeted by the "Verification failed" / please delete all your personal data screen.
Now, I have made a backup of the /data partition using adb-pull, which of course will be useless if the encryption scheme cannot be restored, or something. I assume the contents are irretrievable, but I'm having difficulty finding solid answers on this since most posts are from people who switching ROMs (and so expected to wipe) or were smart enough to back up before proceeding.
It would be amazing if the original ROM could just be flashed through Odin (including the HOME_CSC archive) and the phone would just pick up where it left off... Or if I could use the fastboot oem disable_dm_verity commands, or just wipe the phone completely, restore to stock, and then restore the previous /data once it's up and running. Again I'm expecting none of this is possible, but I would be really grateful if someone who has some experience with this could chime in. Just going to sit on my hands for now in case further messing around with the phone makes recovery even less likely to succeed.