I was on stock Android and yesterday wanted to go for a custom rom. So went to TWM recovery, took a full backup and then I went in to Wipe and, instead of doing a factory rest, I went on did an Advanced Wipe and Format Data. (I think this has caused all the following problems. ) It cleared all the data on the phone.
Then i used adb push to send the custom rom to /sdcard and tried installing. But the install failed after a few seconds with the following error;
set_perm some changes failed
The last log entry was getting partition information or something.
(However installer log says, formatting system, cache and stuff was successful seconds before the error)
After trying and failing to install few roms, I went on to install the Stock again.
Used adb again to flash the stock. And amazingly it worked. Booting and working without any issues.
But still, when I’m trying to install a custom rom it gets failed in a while. After few trial and errors, I tried restoring my first backup before all this, restore was successful. But when I try to flash a custom rom again I ended up with the same error. Tried with both CWM and TWM.
I tried everything (I hope I’m wrong).
Currently my phone is in working condition with Stock Rom rooted and TWM recovery, kernel_FuguMod_20131015_r1172-4.3
Any idea guys? I hate the idea of having to live with the stock for the rest of my life.
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.
mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.
Hello,
My galaxy nexus suddenly crashed yesterday. I don't know what happened, I only know that I had the xPrivacy installer and "App Ops". It's a rooted phone with TWRP recovery v2.8.6.0 and CyanogenMod 10.2. The only problem I had so far was WhatsApp not displaying any chats and had to restore my chats. I do suspect these two are linked to each other
When I try to boot it normally, it crashes after a couple seconds and gets stuck booting and crashing again until I take out the battery.
After fiddling around for a while, all the errors pointed at the data partition, but it seems like I just can't write anything to the internal SD.
What I've tried to fix it is (not necessarily in this order):
Wiped (Dalvik)Cache
Factory reset via TWRP
Restore a recent nandroid backup via TWRP (this says it failed)
Restore a nandroid backup that I made after a factory reset via TWRP (this says it failed)
Restore a nandroid backup via Nexus Root Toolkit
Create a backup (just to test if I could write, it said it succeeded but after a reboot there was no backup)
Wipe data partition TWRP
Used "fix permissions" on TWRP
Formatting SD via TWRP
Wiped all partitions via TWRP
"Flash Stock + Unroot" on Nexus Root Toolkit (Soft-Bricked/Bootloop mode)
Flashed CM10.2 via TWRP
Flashed CM10.2 via Nexus Rootkit
Flashed stock ROM via ADB
Deleted all data via Windows Explorer
Hard Factory reset via ADB
Everything says it was successful, except when restoring a backup via TWRP and a single time I tried wiping the Data partition. I once got an error message saying a file was opened too many times, but I think that is just because it couldn't read the file.
Besides unlocking, rooting and flashing CM, I haven't done much software wise. I have done some handiwork hardware wise, because when I got this phone from a friend, the pins for reading the SIM card were broken off. This was a couple months ago and I don't think I broke anything.
I hope that I have been clear enough explaining my problem, I sadly cannot give a logcat file.
Thank you in advance
I'm having your issue too. I wrote here some days ago, here it is my post http://forum.xda-developers.com/galaxy-nexus/help/unable-to-reset-strange-behavior-t3116856.
Hope we will find a solution!
Same issue for me.
I tried also with odin and it dosen't work.
I have Cyanogenmod 11 and clockworkmod recovery.
and same thing here, try to install CWM from flashify app... see if you can wipe and install roms with that... i know that CWM is outdated, but most of the times it still gets the job done...
This is so weird. 2 days ago the same thing happened to me, my phone is stuck in a boot loop, and I can't bring it back to stock, since I can't wipe or flash. This is so frustrating.
Dear All,
I have a strange problem.
I was with open beta 8, unlocked bootloader with twrp 3.0.2-28.
By distraction, I accepted the update proposed by OTA (even if I known that it is impossible to update via ota, in my conditions). So it just restarted to twrp.
So I downloaded the full ROM, i pushed it through adb to the op3, and I flashed the full ROM. I got no error after flashing.
BUT, the big problem is that the phone just restart to TWRP. It neither try to boot the system. Every time i restert, It goes to TWRP.
I already tried to wipe again dalvik, cache, data and system, then flash rom again, But it just go to TWRP.
What happened? What can I do? I tried everything :crying:
The big worst coincidence is that I deleted from the PC the TWRP backup, while I usually keep at least 1-2 of them...... and I have never needed in the past. OMG
It's look a joke.
EDIT: I found an OLD backup in my old hardisk. It was of the stock oxygen. So, I restored everything, because I couldn't solve the problem.
I changed to f2fs and i flashed the new open beta 9.
Everything is ok.