Develop Bugs

Problems with cwm after installing paranoid android rom

Ok so I have kind of a strange problem and i dont think its with cwm. I always make nandroid backups before flashing new roms as a precaution but in this case it did no good I recently installed Paranoid Android on my phone to try out Jelly Bean. It is pretty awesome But it is a little buggy with a few of the apps i like to run (rom toolbox and dropbox being the major ones). After restoring all my apps i decided to restore my messaging data. That caused the rom to not boot past the google screen. So I decided to go back to Black Ice AOKP with my backup. Didnt work, gave me the "error while restoring /data!". I also just recently updated to CWM Touch 6.0.0.5. I also tried an earlier backup with the same problem. I decided to use fastboot to flash a different CWM (5.8.*.* touch and regular) and basically has the same issue just a different response (could not find data.img, cache.img, and boot.img). Because i use Titanium backup anyway i decided to just wipe and flash Black Ice but when i do it boots for about 30 seconds and then the phone restarts. I tried this multiple times doing multiple formats to no avail. Just for sh*ts i decided to try to wipe and reinstall Paranoid Android. IT BOOTED!! But the weird thing is is that all my apps were still there including my messaging data that borked the install to begin with :/ Anyway to make a long story short, my phone is now working but im afraid that i can't restore my backup or even install a new rom without issues. It seems that CWM will not properly wipe my phone anymore. I am wondering what this new rom could have installed that would cause these issues? I didnt flash any new radios or bootloaders so i dont think that is an issue. Please help!! lol I would like to go back until this rom gets further development or AOKP goes to JB. Any help is appreciated. Thank you for your time
-Erik

I really don't think the ROM caused your recovery to not work correctly. Have you tried a different recovery, like TWRP?

Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.

shode, ndomeopu
Thanks For The Quick Replies! My Swype Has Decided Too Capitalize Every Word And I'm Not Going Too Fix It Lol.. Anyway I've Tried Changing Modes With Rom ToolboxAnd It Made No Difference. i Will Try With Drop Box. It Seems Like Maybe This New Rom Messed With The Permissions And That's Why i Can't Properly Format? The Thing Is Is That CWM Worked Fine Before Booting This Rom. And i definitely Understand That My Conclusions Don't Make Sense But Neither Does The Problem Lol. i Guess What My Question Is Is Why Do The Previous Versions Off cwm That Worked Before Not Work Now? i Will Give The Other Recovery a Shot And Let You Know But i Prefer cwm Just Because It's What i Know And Had Always Worked... Until Now Of Course. Also i Don't Consider Myself anewbie At Thus Stuff But i Am Definitely No dev Lol. Any Suggestion Is Welcome. Thanks!

jesusice said:
Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.
Click to expand...
Click to collapse
Silly Me For Not Thinking Of Changing The Settings. dropBox Now Works But My Swype Is Still Messed Up

Swype works fine for me at 320 dpi and phone mode. Which is the Gnex's default settings so if an app gives you issues try those settings. I'm not too sure about CWM, it's been a while since I've used it. If you want to try TWRP the easiest way is to just install Goo Manager and go to Flash ROMs and in the additional options select Flash Open Recovery Script.

well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.

Gimmemabrewski said:
well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.
Click to expand...
Click to collapse
/sdcard and /data/media are the same thing. I'm sure there's a better technical explanation but I think it's symlinked or something. So wiping data or factory reset in recovery will not wipe your SD contents. From within the ROM it might.

[Q] Cache Issue When Wiping Using CWM & SuperWipe

I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?

Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.

I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app

whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.

I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).

jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?

I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.

Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.

mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions

VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?

Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.

Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.

EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.

suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!

That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.

screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.

Weird Problem flashing Roms

Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.

You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky

I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.

jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.

jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637

I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped

abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours

playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.

Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway

CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?

You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"

CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.

Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.

A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!

Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?

cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't

So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.

Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).

So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!

cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.

Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?

Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

Problems Flashing and Restoring custom roms

I have had problems flashing and restoring Roms both stk and aosp. By problems I mean getting stuck at boot screen after flash and backups failing at data and if restored without data stuck at boot. The only remedy I have found is a total internal memory wipe. I have tried many wiping techniques none worked long term. Last night when I had these problems again before I did full internal data wipe I used twrp file manager and looked around and notice after factory reset wipe which is suppose to wipe all data but data/media I still had data/app and when I tried to manually erase it failed. even with system mounted I couldn't delete. Maybe someone else having troubles can also check to see if data/app is still there after wipe. I dont know if its recovery related or caused by the aosp sd format. Maybe a combination? I don't think im the only one having these problems so I wanted to start a thread to try to figuer this out. Any help is greatly appriciated.

Bdadd34 said:
I have had problems flashing and restoring Roms both stk and aosp. By problems I mean getting stuck at boot screen after flash and backups failing at data and if restored without data stuck at boot. The only remedy I have found is a total internal memory wipe. I have tried many wiping techniques none worked long term. Last night when I had these problems again before I did full internal data wipe I used twrp file manager and looked around and notice after factory reset wipe which is suppose to wipe all data but data/media I still had data/app and when I tried to manually erase it failed. even with system mounted I couldn't delete. Maybe someone else having troubles can also check to see if data/app is still there after wipe. I dont know if its recovery related or caused by the aosp sd format. Maybe a combination? I don't think im the only one having these problems so I wanted to start a thread to try to figuer this out. Any help is greatly appriciated.
Click to expand...
Click to collapse
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now

spleef said:
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now
Click to expand...
Click to collapse
I'm going to try deleting data/app before booting to recovery when I flash from now on to see if it helps. I think something to do with the size of that folder is corrupting data in recovery as it seems to happen only when I run a rom for a few days adding apps. If I flash right away it works fine.
spleef..If you can check data/ folder from twrp before wiping internal data...I wonder if the data/app is from backup or previous rom as I believe it is being corrupted to not be wipable.

spleef said:
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now
Click to expand...
Click to collapse
Bdadd34 said:
I'm going to try deleting data/app before booting to recovery when I flash from now on to see if it helps. I think something to do with the size of that folder is corrupting data in recovery as it seems to happen only when I run a rom for a few days adding apps. If I flash right away it works fine.
Click to expand...
Click to collapse
I'm seeing this happen to a lot of people and I don't understand why. I've been flashing all the ROMS and restoring from backups for months now with no issues. Maybe I just got a lucky phone.
Maybe this will help many of you.
In TWRP 2.5.0.0
Click Wipe
Swipe to Factory Reset
Back button to the Wipe menu
Advanced Wipe
Tick all 4--
Dalvik
System
Data
cache
Back to main TWRP menu and restore/install
Like I said, I've had no issues doing it this way. May the Force be with you.

engine95 said:
I'm seeing this happen to a lot of people and I don't understand why. I've been flashing all the ROMS and restoring from backups for months now with no issues. Maybe I just got a lucky phone.
Maybe this will help many of you.
In TWRP 2.5.0.0
Click Wipe
Swipe to Factory Reset
Back button to the Wipe menu
Advanced Wipe
Tick all 4--
Dalvik
System
Data
cache
Back to main TWRP menu and restore/install
Like I said, I've had no issues doing it this way. May the Force be with you.
Click to expand...
Click to collapse
thanks for the advice but I have wiped every which way including rebooting recovery after wipe before installing..no luck
I think it started from initially wiping internal memory and reloading data from pc backup to get rid of the aosp stuff on the sd card..
My advice to anyone else who wants the sd card back to stock is to leave it alone.

normally i have no problems going back and forth.... want to hear something even weirder.... restored my aokp and it booted into lifeless.... now either i restored lifeless again...which us possible big fingers and always in a hurry... or something very funny going on in my recovery i am on the older version 2.4.4 i think it is haven't updated it yet cause of all the issues people are having and the different wipe area... just seems weird top me but guess its time to do it and at least see if it will help
Sent from my LG-LS970 using xda premium

OK this is crazy...deleted data/app with ROM manager root browser..then entered recovery wiped everything in advanced wipe..system..both caches and data..then rebooted recovery checked data\ there was nothing but \media and a config XML file..then flashed a STK custom ROM...got stuck at lg boot logo. Got back to recovery went to filemanager and there it was data\app with all the apps had had installed in my aosp ROM. Loaded aosp backup and all is fine....but I deleted data\app with root browser and in recovery and still there.. :banghead:
Sent from my LG-LS970 using xda premium

Bdadd34 said:
OK this is crazy...deleted data/app with ROM manager root browser..then entered recovery wiped everything in advanced wipe..system..both caches and data..then rebooted recovery checked data\ there was nothing but \media and a config XML file..then flashed a STK custom ROM...got stuck at lg boot logo. Got back to recovery went to filemanager and there it was data\app with all the apps had had installed in my aosp ROM. Loaded aosp backup and all is fine....but I deleted data\app with root browser and in recovery and still there.. :banghead:
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
I usually wipe all data by all data I mean including data/media then I have no problems. Keep in mind this erases sdcard so you need to have rom on computer and adb push it to the sdcard to flash
Sent from my LG-LS970 using xda app-developers app

I think I will start from scratch with lgnpst and leave the internal memory alone this time and see if that was the cause.
update: Im back to stk going to root then unlock with freegee..Any advice for using freegee it soft bricked me last time and I had to flash tinybin

Well since I went back to unrooted and locked and started from scratch..tried using free gee then flashed tinybins all has gone well..no flashing problems anymore..I think messing with the internal memory is what caused my problems. Been almost a week and I have flashed between several roms and restored from backup many times.
Sent from my LG-LS970 using xda premium

I had not seen this thread before or I would have chimed in by now. My issues don't go back to the 28th; only over the last week. My issue goes like this: I built and flash my own Beanstalk 1.561 ROM, and had no real functionality issues. I played with it for a day or two before realizing I hadn't backed it up. Did that, and at reboot, got a loop. WTF? I immediately thought it was the ROM, so I wiped Factory, dalvik and cache, and ran one of my older back ups. No problem. Flashed a new build of JellyBeer, updated everything, and backed it up. Restart and loop. Now I'm REALLY pissed. Restored my original stock back up; no prob. Okay, now I'm more confused than angry. Go to update my recovery(already running TWRP 2.5, but wanted a fresh install) Install of fresh recovery fails. I forget what the fail was for though, I was spitting nails at this point. Soooooo, really long story a little shorter, I downloaded and reinstalled TWRP 2.5, no problems. Dumped all of my 'standard' flashing files(Banks Gapps, Smoocha kernel, newer ROM downloads, etc), and redownloaded everything. Installed a fresh download of Beanstalk 1.561(build 7/07; original problem was on build 7/05), updated it, and performed a back up. SAME ISSUE. I think you can imagine the string of curses I want to put here. So, for me all back ups older than last week work fine. ANY BACK UP MADE EVEN TODAY FROM ONE OF MY OLDER BACK UPS RESTORES AND BOOTS FINE. But, any back up made form any of my newer builds(7/01 to now) flakes out. I haven't had the time to try other ROMs, and to be honest, I haven't tried to run anyone else's work since trying to install Vectus a few weeks ago. Does anyone have any info, advise, similar experience? This is driving me nuts, so anything would be great. PM me if you want to

BMP7777 said:
I had not seen this thread before or I would have chimed in by now. My issues don't go back to the 28th; only over the last week. My issue goes like this: I built and flash my own Beanstalk 1.561 ROM, and had no real functionality issues. I played with it for a day or two before realizing I hadn't backed it up. Did that, and at reboot, got a loop. WTF? I immediately thought it was the ROM, so I wiped Factory, dalvik and cache, and ran one of my older back ups. No problem. Flashed a new build of JellyBeer, updated everything, and backed it up. Restart and loop. Now I'm REALLY pissed. Restored my original stock back up; no prob. Okay, now I'm more confused than angry. Go to update my recovery(already running TWRP 2.5, but wanted a fresh install) Install of fresh recovery fails. I forget what the fail was for though, I was spitting nails at this point. Soooooo, really long story a little shorter, I downloaded and reinstalled TWRP 2.5, no problems. Dumped all of my 'standard' flashing files(Banks Gapps, Smoocha kernel, newer ROM downloads, etc), and redownloaded everything. Installed a fresh download of Beanstalk 1.561(build 7/07; original problem was on build 7/05), updated it, and performed a back up. SAME ISSUE. I think you can imagine the string of curses I want to put here. So, for me all back ups older than last week work fine. ANY BACK UP MADE EVEN TODAY FROM ONE OF MY OLDER BACK UPS RESTORES AND BOOTS FINE. But, any back up made form any of my newer builds(7/01 to now) flakes out. I haven't had the time to try other ROMs, and to be honest, I haven't tried to run anyone else's work since trying to install Vectus a few weeks ago. Does anyone have any info, advise, similar experience? This is driving me nuts, so anything would be great. PM me if you want to
Click to expand...
Click to collapse
Correct me if I'm wrong, but from some of your posts, i never hear you mention wiping /system. That could be some of the problem. Even restoring should have /system wipes.
Also on your backups are there at least 7 files in each? You might have ticked a button and aren't backing up /boot
Sent from my LG-LS970 using xda premium

engine95 said:
Correct me if I'm wrong, but from some of your posts, i never hear you mention wiping /system. That could be some of the problem. Even restoring should have /system wipes.
Also on your backups are there at least 7 files in each? You might have ticked a button and aren't backing up /boot
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Thanks for the response. I'll check into that advice and post what happened.
Checking on my one back up that I haven't deleted before anything else.This is what I have:
boot.emmc.win
boot.emmc.win.md5
data.ext4.win
data.ext4.win.md5
efs1.emmc.win
efs1.emmc.win.md5
efs2.emmc.win
efs2.emmc.win.md5
efs3.emmc.win
efs3.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
It looks right to me, but honestly, I never looked that closely at the files. Looks the same as the other backups.....

BMP7777 said:
It looks right to me, but honestly, I never looked that closely at the files. Looks the same as the other backups.....
Click to expand...
Click to collapse
Compared it to mine and it is. You just have the efs also. Maybe try formating /system then restore.
Also maybe try backing up without efs.
Just more options to try.
Sent from my LG-LS970 using xda premium
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Also, have you tried a flashable TWRP?
Sent from my LG-LS970 using xda premium

I have had this problem and I thought it was just my ROM, I have been making changes to different apks and then flashing and if it bootloops I restore previous working version. Several times however the restores work and then bootloop or they fail in recovery. When this happens I wipe cache, dalvik, system, internal memory, data, factory reset. Then I go into download mode and LGPNST and flash original stock unrooted, then root then flash teeny bins, then I'm ok. It's a pain, thought it was just from me tinkering with things. Anyway that gets me working again, then I can reflash the ROM.

Update: More recently when I've had this happen I just format data and then push what I'm trying to flash into /data/media. Much easier.
Sent from my LG-LS970 using xda app-developers app