I'd gone from stock to CM 7.1, but the issues there just bugged me too much.
When I *first* got the phone (a month or so ago), I'd used Odin to try to root it and botched something...not sure what. I dug around and found Heimdall, used the collection of files I found here (http://forum.xda-developers.com/showthread.php?t=1026746) and got back to stock. Did the OTA updates, then installed CM 7.1.
Last night, I decided to try out some other ROMs (installed via CW 4.0.1). I downloaded Poolparty, Evil, and OMFGB. They all installed without issue and looked slick, but I found I wasn't getting texts...and when I sent texts, they were blank. I decided to use Heimdall again and revert back to stock.
This morning I tried installing the OTA updates again, but they kept failing. In my poking around, I found that the internal phone storage showed 0kb available.
I tried doing a factory reset, I tried wiping the cache, I tried everything I could think of, including re-flashing via Heimdall...nothing helped, I still had 0kb free space and am unable to install anything.
On a lark I decided to re-install the Evil ROM from CW again, and it went on smooth, but I'm back to square one, where I can't get texts and send blank ones. Looking at the internal phone storage space, however, it shows 1.47 GB free, which is more like what I'd expect.
I've tried using Odin at work today, but it's not seeing my phone. I suspect the cable I've got may be the issue with Odin (which is odd, given that Heimdall works great), so I'll try that again when I get home.
Does anyone have any ideas about:
1.) Why the stock install thinks there's no storage space on the internal storage, and how I can fix that, and
2.) Are there any suggestions as to what radio and modem I should flash for Evil? I saw suggestions elsewhere on the web that the inability to receive texts and sending blank ones was due to not having the correct modem and/or radio.
Odin worked
I was able to update the modem via Odin once I got home. Being the tinkerer I am, I re-flashed back to stock using Heimdall and saw the appropriate amount of internal storage space.
Weird.
hi bigjuan
did you problem of 0kb solved or i do have a solution for that. i too faced this issue earlier
OK so let me start off with, great site. I have read a ton of information.
First: Siyah 4.3.3 (Latest) Kernel which now has been put to AJK v1.48s
ROM; SHOstock3 v2.5.9
PreMod Settings: SGS2 AT&T SGH-i777. Started with GB > AT&T OTA (KIES) 4.0.3 > AT&T OTA WIFI 4.0.4 (caused huge freaking headaches with battery, charging, turn off the phone loop, battery draining, etc.)
Issues:
Original Issue posted in this thread (viewing Single Post) http://forum.xda-developers.com/showpost.php?p=39350619&postcount=18
Creepy offered something to try. That never worked as all I was able to do was download mode or stare at the Samsung Galaxy S2 Splash Screen. Well, I took to his download repository and other links and used his One-Click Recovery to stock GB Rom to make part of my phone usable, using this link here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
While it is Gingerbread at least my phone is usable. I want to try his STOCK ICS method but that mentions the eMMC super-brick bug.
So this is what I have tried so far. I have tried installing Siyah 4.3.3 nomswap for my kernel using Mobil-Odin Lite. That works but it never reboots or actually says finished. What it does do is stay at the wicked purple splash with the yin yang symbol. I left it like that last night until I woke up this morning and it never changed. So I rebooted the phone and the Kernel is on there. I reboot into recovery so that I can install SHOstock3 v2.5.9. That goes off flawlessly except here the last few times it won't reboot when I go to the GO BACK. It sticks and doesn't do anything. Rebooting shows the SHOstock3 Engine Boot Animation. Once it stops it goes to ask me for the encryption password. Well I put in my password (was the same one to the unlock screen) and it reboots and you see the nifty Samsung animation logo and then goes to the Samsung Galaxy S2 Animation Logo and then just stays there. It really pisses me off.
So after all that I finally put a new Kernel on there,AJK 1,48s. Pretty cool it loads up and then reboots. Well AJK shows up after the light-blue bar fills up and then goes black and the 4 touch sensitive row keys are lit up for a bit before going dark but the phone is still on. So I rebooted to recovery (CWM now with the Kernel) fixed tweaks, went to advanced and saw all sorts of options. Tried clearing caches for ROM 2 and restarting,no effect. I removed ROM 2 and went through reboot and nothing. Restored ROM 2 and nothing. Re installed SHOstock3 v2.5.9. Did the same thing after install and not backing out when I hit GO BACK. Rebooted, same scenario that happened before with requiring password. Entering password does the same thing with a reboot and then staying on Samsung Splash Screen. If I Don't enter the password and reboot,same thing happens. So after being irritated and pissed off I ran Creepy's One-Click Fix again and paid attention to the phone and noticed it mentioned not being able to access the AT&T section or partition or something like that. So while part of my phone works under normal circumstances I want to figure out how to remove that encryption part of the phone and get full access (even though full memory and space are shown under Windows 7 and the files on the phone). The password I put on there isn't taking and I don't know if using PC methods for removing encryption (which could take awhile I know) needs to be employed (and if so which methods) or if that part is just screwed and I can't put on any other kernels or custom ROMs. Perhaps tell me where I messed up. Should I try swapping the ROMs from Advanced setting in CWM Recovery? Can I try a different ROM (kernel didn't seem to help)? I have done several factory resets dalvik cache wipes cache wipes formats,etc. and it is still there. I can say that before the whole encryption debacle (even though I was encrypted I did get in my phone after encrypting it) my pin unlock for my SIM wouldn't work and I actually SIM locked my phone. Had to go to AT&T and get a new SIM and was up and running. I put a 4 digit pin lock for the SIM (it let me do it) and when I went to unlock it after a reboot, it wanted an 8 pin for the PUK and wouldn't take what I put. I tried to change the PIN but to no avail. Once that happened I guess it snowballed. Any help is appreciated. I have searched and tried some things that looked to match my issue but none have totally helped. I do have ADB set up on my wife's laptop which I use to restore my phone to GB Stock ROM. I haven't been able to reboot the phone into Bootloader to do any fastboot commands as when I tried to do it the commands just sent the phone into normal reboot (though adb reboot recovery does boot to recovery). I Haven't tried booting to the bootloader using the new Kernel though so I will wait for confirmation or additional information before I try. Thanks guys.
Eagle
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Thank you so much creepy. I will give that a try later and see how it goes. I hope the information I gave actually gives enough info. I know folks usually want enough. Ill post back my findings.
Eagle
quick follow up and what I tried
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
WarEagleUS said:
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
Click to expand...
Click to collapse
Should I try TWRP instead of CWM and if so where should I grab it from?
Status Update
So this is what I have tried so far as of this moment.
I reflashed using your Stock + Root Gingerbread ROM.
Wiped DATA and everything in recovery menu several times.
Used Kernel Wipe and ROM Nuke for extra cleaning power.
Reinstalled the Kernel AJK and SHOstock3 ROM
Haven't installed any themes though I had Johns Blue and Villians Poison Base Theme (I believe that is what it is) on there when this all went down. Should I put them back on there?
Password still pops up. So what it looks like is that unless I stick with the unencrypted portion of the phone, I am screwed with any custom ROMs as the correct password has the phone restart and then stick at the Samsung Galaxy S2 Splash Screen. Apparently I still cannot access that area of the phones memory to wipe it at all no matter what I do. I need to access it somehow. Really driving me crazy and thinking I may need to talk with AT&T(as Samsung told me to earlier this morning lol) and see what they can do.
One thing I do notice is when I use your stock root program it actually removes the encryption or decrypts the section of the phone for the stock ROM to go on the phone which is cool.
Eagle
Any other things to try from anyone is greatly appreciated.
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
WarEagleUS said:
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
Click to expand...
Click to collapse
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
creepyncrawly said:
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
Click to expand...
Click to collapse
Thx bro. yeah I need to run some forensic tools and see if I can mount the whole phone system on my PC and run the tools.
creepyncrawly said:
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
Click to expand...
Click to collapse
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
WarEagleUS said:
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
Click to expand...
Click to collapse
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
creepyncrawly said:
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
Click to expand...
Click to collapse
Yeah I should have used ADB to do that from the get go. I should have used the wife's laptop like I started to instead of my WIN 8 machine has it seems to be finicky with Android SDK (the portion at least needed to run ADB). Linux commands really aren't much different than terminal and I have done both. I was actually trying to get fastboot commands to work but my bootloader wasn't cooperating and for the life of me I couldn't find how to unlock it. I may try restoring that EFS. If nothing else I would love to be able to format that EFS and replace it with my original copy though as you said a damaged EFS may actually cause issues (who knows if it is damaged). I do know that I am fixing to chat with AT&T support. I hope I don't have to drive down to Hoover, AL to the repair facility. I would rather them send me a phone and send this one back. I am on stock 4.0.4 ICS from AT&T and any root that may be on there (though I doubt there is now) I can remove and what not
Thanks for the advice and insight Creepy. I know you tried like hell to get me an answer but in doing research on here with other problems I found out some useful information going forward my friend.
Eagle
Well, looks like I will be getting a special early upgrade and the wife will as well. I will be keeping this phone, however, to mess with this and see if I cannot get this problem fixed. Thanks Creepy so much. I appreciate your research and help more than you know. If possible I would love to keep this thread open for a while just in case I figure this out and fix the issue. It may take me a week or so but I will get back to messing with it again.
A side note. You don't need the whole sdk to get adb. You can download just the files you need from my signature.
Sent from my SGH-I777 using xda premium
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
spiff72 said:
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
Click to expand...
Click to collapse
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
icedventimocha said:
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
Click to expand...
Click to collapse
Thanks...
I actually went through the whole revert to stock with ODIN (but I used the PDA button/file). Was this the wrong approach? It sounds like I ended up at the same point as you...
And of course I couldn't leave it alone last night and unlocked and rooted with Casual last night. So far no issues with recovery data wipes.
I would like to understand what the problem was! Is it hardware, or a flash gone wrong?
hi all its been a while since ive been on the boards because ive been running rooted stock deodexed rom. i havent flashed in a year or so but just recently my settings have stopped.
i continually have been getting this message instantly after ancelling out the message. i cannot get past the select language option. theres no escape.
I couldn't even backup my current rom. so i did a battery pull and rebooted into recovery to flash different roms. I've tried dn3 which was the last rom i had saved to my sd card, and miui7. both yielded the same results of the same message about the settings has stopped. its obvious something has went bad over time. i have done nothing but use it as a phone. no flashing or anything. is there something i need to flash in order to troubleshoot this issue? i do not have the money to obtain a replacement through assurion. also my recovery wouldnt let me restore my 1 backup on my sd card. so is there anything i can do from scratch? any settings zips to flash? Odin? ive searched boards and nothing specific to my device (I605). please help
iflip said:
hi all its been a while since ive been on the boards because ive been running rooted stock deodexed rom. i havent flashed in a year or so but just recently my settings have stopped.
i continually have been getting this message instantly after ancelling out the message. i cannot get past the select language option. theres no escape.
I couldn't even backup my current rom. so i did a battery pull and rebooted into recovery to flash different roms. I've tried dn3 which was the last rom i had saved to my sd card, and miui7. both yielded the same results of the same message about the settings has stopped. its obvious something has went bad over time. i have done nothing but use it as a phone. no flashing or anything. is there something i need to flash in order to troubleshoot this issue? i do not have the money to obtain a replacement through assurion. also my recovery wouldnt let me restore my 1 backup on my sd card. so is there anything i can do from scratch? any settings zips to flash? Odin? ive searched boards and nothing specific to my device (I605). please help
Click to expand...
Click to collapse
I'm assuming you are still on the 4.1.2 bootloader, since you were able to flash miui7 and dn3.
If something has gotten corrupted, you could try Odin'ing the stock recovery back onto the device by following the directions on this thread: http://forum.xda-developers.com/showthread.php?p=53624921
After getting the stock recovery on the device, do a factory reset and wipe cache in the stock recovery. Then you can use ODIN to reinstall CWM/Philz or TWRP (whichever recovery you were using previously). Hopefully you have an old backup you could restore... or you can set up your ROM again from the start after rebooting back into the system.
If worse comes to worst and wiping in the Stock recovery doesn't fix things...sounds like you may have to Odin back to stock 4.1.2, and then reroot with CASUAL and start over again. Droidstyle put together a good guide on how to restore the phone back to stock 4.1.2... you can find his guide here: http://forum.xda-developers.com/showthread.php?p=34891181. I think the 4.1.2 firmware link is down, but you can grab it from Sammobile.com.
You probably know... but don't flash the official Stock 4.3 or 4.4.2 Firmware onto the phone because there's no current bootloader unlock methods for those..... 4.1.2 is the last Android version for our I605's that has a "do it yourself" bootloader unlock method.