Develop Bugs

[Q] TMO SGH-T989 cant wipe data, cant restore backup, cant do ANYTHING

SHG-T989 on TMO. I was running CM 9.0 but wanted to update to 9.1. NOW I CANT DO ANYTHING!!! Here is what I did:
1. Downloaded the CM9.1. 2. did a backup through CWM. 3. wiped data through CWM, "wipe data/factory reset. 4. wiped cache partition through CWM. 5. did a Darkside Super Wipe through "install zip from internal sd card" (last time installing CM9 i got stuck in the boot screen and had to go back using Darkside Super Wipe, reinstall CM9 and it worked fine). 6. Reboot to recovery. 7. installed CM9.1 through "install zip from sdcard". 8. installed gapps through "install zip from sdcard". 9. Reboot.
It came up and was stuck in the CM9 boot screen. So I went back in through CWM and tried to "wipe data/factory reset" and it wont work! Tried to go back to stock through Odin and it wont work! When i try to wipe data, the process starts and completes the "formatting /data, then gets stuck at formatting /cache. Does the same thing if I try to wipe the cache.
Im completely stuck and have no phone.

Which recovery version are you using? It might a corrupted recovery.
Try this recovery TWRP is cwm flashable:
SGH-T989_TWRP_v2.2.2.0.zip - 6.72 MB
Then TDJs super wipe and then install the stock ROM or any other ROM.
http://forum.xda-developers.com/showthread.php?t=1858435
Sent from my SGH-T989 w/AOKP JB Sept-12-12 using XDA app.

any updates to this? i'm having basically the exact same problem, formatting cache or anything to do with that partition freezes up on me.
using cwm 5.0.2.7 did a darkside super wipe, flashed on a JB rom (P.A.Cman), flashed gapps (20121011), wiped cache, wiped dalvik cache, rebooted then got stuck on boot animation. rebooted back into cwm to try and wipe again and reinstall, no luck got stuck on formatting cache.
loaded up my nandroid which went fine, ended up installing twrp instead to see if that would help, rebooted into recovery and was stuck on the "teamwin" blue screen and wouldn't go further multiple times. so, put cwm back on (6.0.1.5) to see if the updated version would work. nope, same thing- can't do anything with the cache partition.
any ideas??
luckily my phone still works fine with the backup i made. running aokp ics build 40, streamline #27 kernel, uvle1 radio. been running that setup since july with no real problems, just wanted to try out JB finally and seems now i can't
any help is appreciated! thanks!
edit: will try the above post^ later tonight, just thought i'd see if i could get some more options to try out. thanks.

wwwwd83 said:
SHG-T989 on TMO. I was running CM 9.0 but wanted to update to 9.1. NOW I CANT DO ANYTHING!!! Here is what I did:
1. Downloaded the CM9.1. 2. did a backup through CWM. 3. wiped data through CWM, "wipe data/factory reset. 4. wiped cache partition through CWM. 5. did a Darkside Super Wipe through "install zip from internal sd card" (last time installing CM9 i got stuck in the boot screen and had to go back using Darkside Super Wipe, reinstall CM9 and it worked fine). 6. Reboot to recovery. 7. installed CM9.1 through "install zip from sdcard". 8. installed gapps through "install zip from sdcard". 9. Reboot.
It came up and was stuck in the CM9 boot screen. So I went back in through CWM and tried to "wipe data/factory reset" and it wont work! Tried to go back to stock through Odin and it wont work! When i try to wipe data, the process starts and completes the "formatting /data, then gets stuck at formatting /cache. Does the same thing if I try to wipe the cache.
Im completely stuck and have no phone.
Click to expand...
Click to collapse
Ok, the wipe scripts in CWM recovery v5 are broken! Got experience there because I got stuck on the PACman ROM boot animation.
So, for factory reset, use Darkside Super Wipe. Install zip from sdcard and choose the wipe. From there, install rom, then gapps, and then use the Darkside Cache Wipe. After that reboot and it should work (hopefully)
However the most important thing is that the wipes don't work in CWM recovery v6! It will do bad things!
So yeah, use super wipe to factory reset. Use cache wipe for cache. But follow the instructions to install the ROM.
Sent from my SAMSUNG-SGH-T989 using xda premium

m tr4nch said:
any updates to this? i'm having basically the exact same problem, formatting cache or anything to do with that partition freezes up on me.
using cwm 5.0.2.7 did a darkside super wipe, flashed on a JB rom (P.A.Cman), flashed gapps (20121011), wiped cache, wiped dalvik cache, rebooted then got stuck on boot animation. rebooted back into cwm to try and wipe again and reinstall, no luck got stuck on formatting cache.
loaded up my nandroid which went fine, ended up installing twrp instead to see if that would help, rebooted into recovery and was stuck on the "teamwin" blue screen and wouldn't go further multiple times. so, put cwm back on (6.0.1.5) to see if the updated version would work. nope, same thing- can't do anything with the cache partition.
any ideas??
luckily my phone still works fine with the backup i made. running aokp ics build 40, streamline #27 kernel, uvle1 radio. been running that setup since july with no real problems, just wanted to try out JB finally and seems now i can't
any help is appreciated! thanks!
edit: will try the above post^ later tonight, just thought i'd see if i could get some more options to try out. thanks.
Click to expand...
Click to collapse
got it all working again.. ended up odin flashing twrp 2.2 and i was able to boot into it, wipe everything, and install the new rom stuff.

Similar problem, but cannot make zips to work - HELP NEEDED
HI,
I hope you guys can help me. My T989 got stucked in the splash screen when I tried to update to a nightly CM10 ROM. I entered into Recovery MOde (ClockworkMod 6.0.2.7), then tried to use Darkside Super Wipe... but apparently the phone cannot open zip files. When I hit install zip from sdcard and then select one of the zips (I have tried different ones) it says "---Installing: /sdcard/sgh-t989_darkside.supe.wipe.zip"... but it does not move from there. After 3-4 minutes it reboots by itself and gets back to the splash animation, but never goes beyond that point.
I tried to sideload using ADB, but the phone is not recognized by my PC.
As you said, I think that the recovery mode is corrupted... but I cannot install a new version using a zip
Is there another way to reinstall a version of CWM that allows me to install zips so that I can follow the process you suggested (super wipe + installing ROMS)?
Help will be very much appreciated
Thanks for your time,
Enrique
thatdude02 said:
Ok, the wipe scripts in CWM recovery v5 are broken! Got experience there because I got stuck on the PACman ROM boot animation.
So, for factory reset, use Darkside Super Wipe. Install zip from sdcard and choose the wipe. From there, install rom, then gapps, and then use the Darkside Cache Wipe. After that reboot and it should work (hopefully)
However the most important thing is that the wipes don't work in CWM recovery v6! It will do bad things!
So yeah, use super wipe to factory reset. Use cache wipe for cache. But follow the instructions to install the ROM.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse

kikorras said:
HI,
I hope you guys can help me. My T989 got stucked in the splash screen when I tried to update to a nightly CM10 ROM. I entered into Recovery MOde (ClockworkMod 6.0.2.7), then tried to use Darkside Super Wipe... but apparently the phone cannot open zip files. When I hit install zip from sdcard and then select one of the zips (I have tried different ones) it says "---Installing: /sdcard/sgh-t989_darkside.supe.wipe.zip"... but it does not move from there. After 3-4 minutes it reboots by itself and gets back to the splash animation, but never goes beyond that point.
I tried to sideload using ADB, but the phone is not recognized by my PC.
As you said, I think that the recovery mode is corrupted... but I cannot install a new version using a zip
Is there another way to reinstall a version of CWM that allows me to install zips so that I can follow the process you suggested (super wipe + installing ROMS)?
Help will be very much appreciated
Thanks for your time,
Enrique
Click to expand...
Click to collapse
Do NOT use that darkside superwipes with CWM recovery v6.X.X.X. Does bad things.
Use the scripts only for CWM v5.X.X.X.
Anyway, the damage is done and bad things have happened... So maybe check here
http://forum.xda-developers.com/showthread.php?t=1513359
Either that or you can search the forum and Google around and see what you can find. I am in by no means an expert, but depending if you can access the recovery mode or not might be the key here.
I wish you luck, and hope that you don't have a very expensive brick.
Sent from my SAMSUNG-SGH-T989 using xda premium

Use Odin. There is a tutorial on how to revert to stock GB (might be ICS) in the T989 development forum. It should be a sticky in that forum.

Ditto issues.. Thank good for search function. Read.. Read.. Read..
Sent from my SGH-T989 using xda app-developers app

Tried your suggestion, but Odin won't recognize my phone
Hi there,
Thank you very much for the answer. I actually spent hours trying to find something before I posted my question. Even before posting I found and tried the method using Odin... but my phone is not recognized by Odin. I followed the instructions but on step 4 I actually do not get any "warning" screen... and then the phone is not recognized.
In the meantime, I can get into recovery, but I cannot install any zips. I have tried to complete a factory reset, but the process gets stuck at "Formating /cache..." and then reboots. When I try to install a zip (any zip, the radio, a new ROM, gapps,... any zip really) it gets stuck too.
Any other ideas? I really appreciate your help.
thatdude02 said:
Do NOT use that darkside superwipes with CWM recovery v6.X.X.X. Does bad things.
Use the scripts only for CWM v5.X.X.X.
Anyway, the damage is done and bad things have happened... So maybe check here
http://forum.xda-developers.com/showthread.php?t=1513359
Either that or you can search the forum and Google around and see what you can find. I am in by no means an expert, but depending if you can access the recovery mode or not might be the key here.
I wish you luck, and hope that you don't have a very expensive brick.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse

kikorras said:
Hi there,
Thank you very much for the answer. I actually spent hours trying to find something before I posted my question. Even before posting I found and tried the method using Odin... but my phone is not recognized by Odin. I followed the instructions but on step 4 I actually do not get any "warning" screen... and then the phone is not recognized.
In the meantime, I can get into recovery, but I cannot install any zips. I have tried to complete a factory reset, but the process gets stuck at "Formating /cache..." and then reboots. When I try to install a zip (any zip, the radio, a new ROM, gapps,... any zip really) it gets stuck too.
Any other ideas? I really appreciate your help.
Click to expand...
Click to collapse
The only other possible option I can think is to try and install another recovery....
However!
I have no clue how to do it, and in the end you might just end up making the issue worse.... Like hard brick it.
I might think of something later, but I don't know what else I can do for you. I will search around, but no promises...
Best of luck to you
--edit--
Ok try here possibly
http://forum.xda-developers.com/showthread.php?t=1777970
I have seen a few posts saying that they just install this recovery and then restore a backup.
Ok to be honest, try restoring a backup first and see if anything happens there, and then try this thread.
However like before, this may make the problem worse! Proceed with caution and read and understand everything before attempting.
Hope you can get your phone back to functional!
Sent from my SAMSUNG-SGH-T989 using xda premium

samsung jig
Thanks again for the answer. A couple of days ago I tried to install a functional backup that I had from CWM... but it does not work It runs for a long while, then reboots... but it still freezes on the splash screen (my theory is that the backup is not recovered, as I know for sure that the ROM I backed up did work fine)... I think that CWM is corrupted and not working properly.
Then I tried the solution from the thread you mentioned... but adb cannot find the phone when it is connected
I found somewhere that I can use a samsung jig (microUSB with a resistance) to make the phone enter into download mode, then reinstall CWM using ODIN and then try flashing a stable ROM... What do you guys think?
thatdude02 said:
The only other possible option I can think is to try and install another recovery....
However!
I have no clue how to do it, and in the end you might just end up making the issue worse.... Like hard brick it.
I might think of something later, but I don't know what else I can do for you. I will search around, but no promises...
Best of luck to you
--edit--
Ok try here possibly
http://forum.xda-developers.com/showthread.php?t=1777970
I have seen a few posts saying that they just install this recovery and then restore a backup.
Ok to be honest, try restoring a backup first and see if anything happens there, and then try this thread.
However like before, this may make the problem worse! Proceed with caution and read and understand everything before attempting.
Hope you can get your phone back to functional!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse

kikorras said:
Thanks again for the answer. A couple of days ago I tried to install a functional backup that I had from CWM... but it does not work It runs for a long while, then reboots... but it still freezes on the splash screen (my theory is that the backup is not recovered, as I know for sure that the ROM I backed up did work fine)... I think that CWM is corrupted and not working properly.
Then I tried the solution from the thread you mentioned... but adb cannot find the phone when it is connected
I found somewhere that I can use a samsung jig (microUSB with a resistance) to make the phone enter into download mode, then reinstall CWM using ODIN and then try flashing a stable ROM... What do you guys think?
Click to expand...
Click to collapse
I've heard about the jig method as well, but have no idea on how to go about doing it. Might be worth a shot. I don't think the jig costs that much anyway. I will see if I can find anything later.
Sent from my SAMSUNG-SGH-T989 using xda premium

USB Debugging not accessible

Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?

Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.

CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate

Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release

xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?

Try wiping data and cache again in recovery

xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.

BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.

xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help

aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?

xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery

it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?

It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4

actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.

BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide

BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated

[Q] problem with flashing rooted JB stock rom

Hi,
I got the rooted, deodexed, and debloated version of the latest stock rom.
After I flashed it, I keep getting the error messages "unfotunately the process ... has stopped unexpectedly". I used CWM to flash this rom multiple times. I also wiped data/factory, cache, and dalvik cache. I saw some others are reporting the same error.
I was wondering if there is a solution for this out there.
Thanks

Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.

gc84245 said:
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
Click to expand...
Click to collapse
No I didn't try the infamous superwipe. I will do it. What is cache wipe, is it same as the option in CWM recovery mode?

I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.

gc84245 said:
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
Click to expand...
Click to collapse
Ok, BTW, I moved from Juggernaut 5.0 to JB Stock using ODIN and it worked fine. It's the rooted version of the JB Stock that gives me these errors. In fact, the main reason that I tried rooted version is because it supposedly doesn't have bloadware either.

Well using odin removes more than flashing a zip, for example it replaces your recovery. I'm not an expert and don't know much about the details, but that's probably why it worked using odin.

An odd situation please help?

Okay so to start off I had RSL14 Hyperdrive installed on the rom, ended up trying a new one and when going to wipe data, cache, dalvik, system as usual i ran into an odd error. I am using TWRP recovery and when going to wipe data, the phone just restarted, so i rebooted into recovery and tried again same thing.....which was odd. So i reinstalled twrp and then tried again same thing. Then I decided to install CWM 6.0.1.2 and it wipes data and everything fine, but when going to wipe cache, dalvik, or data it sometimes states E: unknown volume for path {/sd-ext}. On top of that everyonce in a while it says E: unable to format unsafe partition?
Please help its causing me problems and I am a flashaholic.
Regards,
Sean

sean82007 said:
Okay so to start off I had RSL14 Hyperdrive installed on the rom, ended up trying a new one and when going to wipe data, cache, dalvik, system as usual i ran into an odd error. I am using TWRP recovery and when going to wipe data, the phone just restarted, so i rebooted into recovery and tried again same thing.....which was odd. So i reinstalled twrp and then tried again same thing. Then I decided to install CWM 6.0.1.2 and it wipes data and everything fine, but when going to wipe cache, dalvik, or data it sometimes states E: unknown volume for path {/sd-ext}. On top of that everyonce in a while it says E: unable to format unsafe partition?
Please help its causing me problems and I am a flashaholic.
Regards,
Sean
Click to expand...
Click to collapse
Unsafe partition usually means your internal partitions got corrupted somehow.
I would suggest to flash a stock ROM via ODIN or ADB. You could try MSkips toolbox if your comfortable using it-http://forum.xda-developers.com/showthread.php?t=1703488
message brought to you by my GalaxyS3

So....
joeyhdownsouth said:
Unsafe partition usually means your internal partitions got corrupted somehow.
I would suggest to flash a stock ROM via ODIN or ADB. You could try MSkips toolbox if your comfortable using it-http://forum.xda-developers.com/showthread.php?t=1703488
message brought to you by my GalaxyS3
Click to expand...
Click to collapse
If I flash the stock recovery via odin will this fix the partition? I'd really hate to have to do that but reflashed both recoveries a couple different times and like the rom im currently on but if it must be then I guess I have no choice.

sean82007 said:
If I flash the stock recovery via odin will this fix the partition? I'd really hate to have to do that but reflashed both recoveries a couple different times and like the rom im currently on but if it must be then I guess I have no choice.
Click to expand...
Click to collapse
I think you need to flash both of them over.
message brought to you by my GalaxyS3

Make a backup, ODIN back to stock rooted, then reflash recovery and restore

CNexus said:
Make a backup, ODIN back to stock rooted, then reflash recovery and restore
Click to expand...
Click to collapse
I was gonna tell him that, but I figured with all the issues he was having, it was better to start from scratch.
message brought to you by my GalaxyS3

[Q] "gapps stopped" loop after CWM restore

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.