I need to reload a stock G928PVPU2BPC3 tar with no wipe. I failed to make a backup after loading TWRP. Can anyone give me advice before loosing my data. My phone is just rebooting from the Sprint splash screen. The only tar I found with "no wipe", is for stock G928PVPU2AOI6. Any help will be appreciated.
The no wipe might work its a 50/50 if not you will have to do a full wipe. You can flash TWRP and trying to figure out how to get the mount setup to work to mount your internal data but that hasn't worked in awhile. You can also try stock recovery mount. If you can get a working cwn that would work for mounting for sure.
I notice that deleting some of the system apps that you could in lollipop can cause a boot loop and or freezing of the device.
Related
Long story short, I've spend the better part of 2 days trying to get my phone to working order.
I tried to flash the stock 4.0.4 rom into my phone. After I did that, the radio stopped working so i wanted to go back to my previous All-star-v7 rom that i had backup in the external sdcard.
When I was installing 4.0.4 i had to switch from CWM to TWRP to get it to install. I switched back to CWM using ODIN but now when i try to wipe the phone so i can restore a backup, it hangs up on wiping /cache and if i try to restore it hangs up on restoring cache....
What do i do? I had used the infamous super wipe and cache wipe to get the phone into 4.0.4 I think i messed up something because of using those...
update: Strangely, I can restore a backup of 2.3.6 and even though it hangs on restoring /cache. I restart the phone and it boots up to it. I also find that google play is unable to update any of my apps, it looks like it's because of the corrupted /cache. how would i fix it?
update2: i used odin to flash into TWRP 2.6.3.1 and did a cache wipe and it's stuck at "unable to open '/cache/recovery/.version'. anyone know how to fix that?
Here's the short and sweet of it. I am on an i747, running TWRP 2.4.4.0, and PACMAN ROM current nightly. Then I updated to 4.6.3.0 TWRP. Recently my phone lost power ( I forgot to charge it). Then it would boot. I tried to do a restore in TWRP and it would fail at data. I tried flashing a ROM, fail at running updater. I tried to restore, again it would fail at data. Nothing would install or restore. Finally, in desparation, I formatted data. Then, after all of internal was wiped, I could restore from a backup.
Problem fixed right? No.
If I reboot, shutdown, crash, lose power, or in anyway power cycle, the phone fails to boot until I completely format data and do restore. WTF is going on? I'm currently trying to downgrade TWRP to see if TWRP is the issue but I doubt it is.
EDIT: 16:23 The problem is in DATA. I used TWRP backup to restore JUST system and boot and it didn't fix the issue. Something is messing up stuff somewhere in /Data. When attempting to restore data, I sometimes get an error about data/lost+found but I can't reproduce the error right now
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.
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
Hey guys, could one of you please tell me how to do a complete wipe?
I'm having so many problems with TWRP at the moment, and so I want to nuke the partitions in hope that it'll fix it. I've tried using the fastboot format commands for system, data & cache. I've also tried to wipe the recovery, but it gives me the error "Formatting is not supported for filesystem with type ' ' ". So for that I just use format erase and flash the recovery again.
The only other partitions I know of are the boot and bootloader, but I don't want to touch them if at all possible.
The problem I'm having and why I want to wipe sotrage is that if I install sultan's LinageOS (haven't tested with other ROMs yet), TWRP ****s the bed and will make the device undetectable from ADB, (while TWRP is still running though), and if I then try to go into TWRP again, it'll hang, crash, and somehow make the ROM think its just been freshly installed again (data partition corruption?), and it'll do that every time I reboot from then on. The only way to fix this is to wipe the phone as I mentioned earlier, but it will always get stuck again when I re-flash the ROM.
Also, another unusual thing is that when I boot the phone, it has the old boot splash from my previous ROM when loading recovery or for the first few seconds when loading a ROM. So that might be having an effect on the problems I'm having, and what makes me believe that wiping will help.
Any help would be greatly appreciated. (Sorry if it's a bit incoherent)
TL;DR: Flash TWRP, load TWRP, flash ROM, flash Gapps, load ROM, restart, load TWRP, TWRP hangs, crashes, and breaks ROM. ROM will keep being broken until full wipe. Also weird thing where I have old boot splash from old ROM.
Edit: Ended up bricking my phone, and using the unbrick tool to fix that. It seems that it was what I was looking for, where it wiped the phone completely. I'll have to see if that actually fixes my problem.
TWRP 3.1.xx is having this problem, believe the fix is to use the blue_spark 3.1.xx version or the nethunter 3.0.4-1 version, both found here on the forums somewhere