Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
Related
After installing a ROM and rebooting the phone everything seemed to work fine. The only problem is that it I can not install any programs because it thinks that I have no space available.
Now I did not backup my system... I do have an older backup on my laptop... but I can not install clockwork because there is no space.
please help!
Thanks in Advance!
it might be a problem with the ROM.
ODIN back to stock, then flash that same rom again, if its still there, contact the DEV and tell him, because its their fault.
If it gets fixed with re-flash something went wrong while flashing and that happened.
What ROM did you install? Was it ODEX or DEODEX?
I agree with the above post, if an ODIN doesn't solve the problem, it sounds like a problem with the rom, but a little more info on your situation wouldn't hurt.
Thanks for the input... I hope to resolve this before tomorrow! The ROM was Bionix Fusion
I am new to this and probably should have researched a little more. lol
Ok I have downloaded the ODIN3 v1.00
How do I ODIN back to stock?
I have the Samsung Vibrant,
Having the same issue when running Odin with Eugene_2E_JK2_Froyo ...I ran Odin to fix a brick and didn't know the history of the phone. This is the only tar that will boot the phone all the way up, but I get the 0.00 available space error too. I tried stock and almost get a full boot up, but then goes black before going to main screen... I've tried many different combos including T959UVJFD.tar + s1_odin_20100512 pit , 512 pit + T959UVJI6, T959JL5, etc...
suggestions?
The ROM itself seems nice... I like the changes I've seen. For some reason it does not recognize the space that is available on the SD card as space for Applications. I've read a post somewhere about repartitioning the SD card in ODIN. ROM manager is s pretty much useless without clockwork recovery installed.... can not install it without space available. I tried repartitioning in ODIN but would not do it... is this something that could work? Maybe I am doing something else wrong,... or any other suggestions?
At this point I will be happy to go back to factory settings then start over...
Jayson Simmons said:
The ROM itself seems nice... I like the changes I've seen. For some reason it does not recognize the space that is available on the SD card as space for Applications. I've read a post somewhere about repartitioning the SD card in ODIN. ROM manager is s pretty much useless without clockwork recovery installed.... can not install it without space available. I tried repartitioning in ODIN but would not do it... is this something that could work? Maybe I am doing something else wrong,... or any other suggestions?
At this point I will be happy to go back to factory settings then start over...
Click to expand...
Click to collapse
I agree... This thread would probably get more attention in the development section, but I may be wrong. I will keep trying things and let you know if I come up with something...
Actually now I am having the same problem... Went back to the original using ODIN now when the phone boots up it goes to a blank screen and will not go any further!
Jayson Simmons said:
Actually now I am having the same problem... Went back to the original using ODIN now when the phone boots up it goes to a blank screen and will not go any further!
Click to expand...
Click to collapse
What files did u use to odin back
Sent from my SGH-T959 using XDA App
s1_odin_20100512.pit
T959UVJFD
Okay... YAY!!! I got it working! Here's how!
I want to note that every time I would Flash the phone with ODIN when the phone would reboot it would fail to wipe the data! This was not a fix that I found on purpose but it did work for me:
I flashed the file EUGENE373_SamsungS_Froyo_PDA
Now that file is for the Vibrant i9000. Not mine
So after that I re-tried the original one that I stated above,.... then it worked! I did notice that it did NOT fail to wipe the data!
So relieved!
Jayson Simmons said:
Okay... YAY!!! I got it working! Here's how!
I want to note that every time I would Flash the phone with ODIN when the phone would reboot it would fail to wipe the data! This was not a fix that I found on purpose but it did work for me:
I flashed the file EUGENE373_SamsungS_Froyo_PDA
Now that file is for the Vibrant i9000. Not mine
So after that I re-tried the original one that I stated above,.... then it worked! I did notice that it did NOT fail to wipe the data!
So relieved!
Click to expand...
Click to collapse
Thanks for posting your resolution in the event this happens to someone else down the line. Glad you got it up and running.
Yup that is the true stock firmware... try this, it might help and it might not? when you boot your phone and it loads up, format your internal and external sdcard. (back up first) then reboot.... see if that helps. if not, odin the stock rom again. right now i'm shooting at flies with a BB gun so it is worth a try anyway...... and i'll try and research it for ya......
oops i didnt know you found a way....my bad. glad you got it working!!!!
So is that the way to fix it then? I just want to know if anyone else has tried it with no problem before i do it. Also, will you be able to flash back to stock?
I flashed the files that were included with the ODIN package and i now don't have any memory for applications also is the only way to fix this issue by using ODIN again or has someone found another method?
Did you use OCLF at any time previously?
Sdobron said:
Did you use OCLF at any time previously?
Click to expand...
Click to collapse
I tried voodoo for the first time and couldn't get past the vibrant screen i then used the odin package the tmobile default files and got to the tmobil boot screen but the screen goes black and nothing happens my hard ware keys were on but that's it so then i used eugenes package based off the tmobile leak and that's where i'm at now it works but no application memory available.
so i want to see if i can just use ODIN with the file that is up a couple of posts to get my app memory back
How much available app space are we suppose to have?
So I know the phone has 2GB of app space, but when I totally wipe everything and go back to stock, it says only about 1.7GB.
go to settings, then sd card and phone storage
scroll all the way down to application storage
how much available space is it suppose to have under stock conditions?
Jayson Simmons said:
Okay... YAY!!! I got it working! Here's how!
I want to note that every time I would Flash the phone with ODIN when the phone would reboot it would fail to wipe the data! This was not a fix that I found on purpose but it did work for me:
I flashed the file EUGENE373_SamsungS_Froyo_PDA
Now that file is for the Vibrant i9000. Not mine
So after that I re-tried the original one that I stated above,.... then it worked! I did notice that it did NOT fail to wipe the data!
So relieved!
Click to expand...
Click to collapse
Can you post the EUGENE373_SamsungS_Froyo_PDA file? I flashed Eugene_2E_JK2 Froyo, and then tried flashing the original JFD Stock Rom, but it gave me a black screen after the Galaxy S screen. Also, it didn't wipe the data for me.
has anyone fixed this? i have the same problem im stuck
Ok, I was restoring my phone to stock with odin following these stpes
Disable Voodoo
Odin to eugenes froyo that wont brick
sticks at vibrant screen
tried odining to JFD
odin completes but still hangs at the vibrant screen
I have tried with and with out repartition checked and I am able to enter and exit download mode freely, I have tried 3 differnt versions of odin and 2 different downloads of the pda and pits. Any help would be great.
EDIT, Odin is finishing at the pass stage when the phone attempts to boot Currently flashing the JI6 seeing if it works.
Still not getting anywhere, I have now tried to odin to eugenes froyo, JFD, JI6, all which end the same with out a boot screen, I can get download but no recovery.
From my understanding when you flash eugenes froyo that wont brick the boot animation should change to the international one, mine has not done that so I am starting to wonder if there is an issue with the flashes themself.
How long did you wait after flashing the stock firmware? The first boot usually takes a while after an Odin. Did Odin finish flashing everything to the point that it said restart in blue?
You can find instructions to revert to stock http://forum.xda-developers.com/showthread.php?t=734475
I've gotten myself out of some pretty bad "bricks" with JFD and ODIN... make sure you also use the stock .pit file and you can check repartition, use JFD and should fix you right up.
I have waited for 10-15 minutes after it says restart and then sometimes after it says pass, and I have done to jfd and stock pit.
left phone at boot fell asleep woke up hr or so later still at vibrant screen, still cannot access recovery but can access download mode.
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
iynfynity said:
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
Click to expand...
Click to collapse
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
ionic7 said:
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
Click to expand...
Click to collapse
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
iynfynity said:
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
Click to expand...
Click to collapse
Yes read the first post it says what i have flashed.
Charlie Brown said:
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
Click to expand...
Click to collapse
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
ionic7 said:
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
Click to expand...
Click to collapse
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
ionic7 said:
Yes read the first post it says what i have flashed.
Click to expand...
Click to collapse
try that again.
Sent from my SGH-T959 using XDA App
Im having the same issue with, "Data Wipe Failed" and have 0.00 space in Application storage but my phone reboots into eugenes 2.2 perfectly fine and works, but the application storage seems to be empty still...very frustrating.
cvibe88 said:
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
Click to expand...
Click to collapse
have changed usb cord, port, computer, have flashed jfd ji6 froyo that wont brick, 512 pit,513 pit,and they have not laughed at me in anyway they are sending my new phone now and a g2 to try out soo either way I have something soon. I also was going from axura to stock to a custom rom not from one to the other and I do know how to use odin, I know what I am doing just need help figuring this one out has to be something im missing or its just not gonna work. 50 odins and nothing kinda says it all.
I am in the same boat.. tried ODIN + stock ROM from various sources, nothing seems to work.. am I out of luck ??
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Nerz said:
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Click to expand...
Click to collapse
The one-click downloader is NOT from me, it's a repack of my tar file - and it's starting to sound like the one-click is doing something weird and not flashing the kernel properly.
Use regular old Odin (or Heimdall) to flash the raw tar package.
I'll try it. Though I don't understand how I am in the position I am in from browsing the web on my phone to directly going into a hootloop that neither that odin one click will fix, or any cwm roms won't fix.
Sent from my GT-I9000 using XDA App
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Nerz said:
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so after flashing the odin file from http://forum.xda-developers.com/showthread.php?t=1286432 it is still bootlooping at splash screen.
I'm not sure what my options are right now. I'm pretty sure bootloaders can't be the problem. I can't re-partition from odin because it says it can't open the specified file "(Line: 1828)". Is this because it doesn't have pit file? I don't understand how this problem manifested.
If I need to pull contents from sd card from cwm, will flashing a cwm kernal increment flash counter?
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Have yet to flash a pit file.
Sent from my GT-I9000 using XDA App
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Juq said:
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Click to expand...
Click to collapse
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
hardgrid said:
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
Click to expand...
Click to collapse
Will try to help, but will need more specific information.
The OP of this thread started bootlooping while checking a web page in his browser. So, how did it happen for you? Please give as much exact information as possible. Was it after a flash? Or did it start while you were using the phone? Or how?
Mine was connected to an aftermarket car charger while it happened. I read a post somewhere and a couple ppl it happened to believed the same thing, since it was in my 30 day trail period I sent it back to Sams club and got my replacement today. Since I didn't have a jig at the time, I didn't want to flash a cwm kernel and increase my flash counter so I lost some pics of my kids.
Not sure if it was charger related but I couldn't find a fix and wouldn't really call myself a noob at flashing. Might have some things to learn nut far from a noob.
Sent from my I897 using XDA App
I'm an admitted noob, but my hope is that somebody here will take pity and be able to shed some light on what I've done and how to fix it.
Here is a general high-level list of what I've done:
1. I attempted to root my phone with SuperOneClick (I think 2.3.3)
2. It hung one Step #7 (as I recall) for about 10 minutes.
3. I disconnected USB cable and reset the phone - it wouldn't boot
4. Started researching, discovered Recovery Mode, selected reset to factory.
5. Reset appeared successful, but then phone went into reboot loop.
6. Tried to access Recovery Mode again, but this time it came to different screen, saying "Deleting cryption meta data".
7. Tried flashing several times with odin and stock PDA's suggested in this forum.
8. Same behavior, so flashed CWM 4.0.0.2 (unfortunately it was for I9100)
9. Flashed new CWM 5.0.2.3
10. When I enter Recovery mode now and I select the wipe data/factory reset option, it just goes to a hat icon with a circular arrow and stays there.
Like I said, I'm new here and have already given up hope on recovering any useful data on my phone. I just want to get it working again so I don't have to buy a new one.
Thanks in advance!
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Try to wipe data/factory reset again from this version of CWM Recovery, and then try flashing the one-click downloader return to stock in the "Return to the store or for warranty replacement" thread stickied in general.
Post your results back here and I'll try to keep an eye out to help, but I won't be on the computer every minute.
creepyncrawly said:
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Click to expand...
Click to collapse
This guy is right. The power button is the menu/logo button in that version. The newer version changes that mapping though.
You'll likely need to flash the return to stock image. One of them is already prerooted, too!
Sent from my SAMSUNG-SGH-I777 using xda premium
creepyncrawly said:
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Try to wipe data/factory reset again from this version of CWM Recovery, and then try flashing the one-click downloader return to stock in the "Return to the store or for warranty replacement" thread stickied in general.
Post your results back here and I'll try to keep an eye out to help, but I won't be on the computer every minute.
Click to expand...
Click to collapse
Thanks so much for your quick reply and help. I followed the instructions you outlined and all went as outlined. Upon final reboot I'm back at Stage 6 in my original post. The original Samsung logo is back (which is a relief), but so is the incessant rebooting and upon trying to enter Recover Mode, I get the Deleting cryption meta data message and then more reboot loop.
Looking forward to your next suggestion(s) and a little sleep.
Oh, by the way, the wipe data/factory reset within CWM appeared to run properly but made no apparent change.
digitalsdc said:
Thanks so much for your quick reply and help. I followed the instructions you outlined and all went as outlined. Upon final reboot I'm back at Stage 6 in my original post. The original Samsung logo is back (which is a relief), but so is the incessant rebooting and upon trying to enter Recover Mode, I get the Deleting cryption meta data message and then more reboot loop.
Looking forward to your next suggestion(s) and a little sleep.
Oh, by the way, the wipe data/factory reset within CWM appeared to run properly but made no apparent change.
Click to expand...
Click to collapse
Tried to answer you this morning, but didn't hit the submit button until a few minutes after 8:00. Let me see if I can do it again.
You did a factory reset and then installed the stock firmware. Now try a factory reset again to see if that will clear the bootloop.
If that does not do it, then you may need to replace another part of the system. We need to know exactly what you flashed for the I9100 while you were trying to fix the original problem (point 8 in your list.) So far, you have flashed everything in the stock UCKH7 firmware except the bootloaders and the param.lfs. You may need to flash param.lfs next to see if that will do it. Is there any chance that what you flashed for the I9100 contained bootloaders?
...........
By the way, having Super OneClick hang on step #6 is a known issue, and the solution is posted in the Super OneClick thread OP as well as in the Library sticky thread in the development section of the I777 forum. If you had been better informed, you could have avoided this problem.
creepyncrawly said:
Tried to answer you this morning, but didn't hit the submit button until a few minutes after 8:00. Let me see if I can do it again.
You did a factory reset and then installed the stock firmware. Now try a factory reset again to see if that will clear the bootloop.
If that does not do it, then you may need to replace another part of the system. We need to know exactly what you flashed for the I9100 while you were trying to fix the original problem (point 8 in your list.) So far, you have flashed everything in the stock UCKH7 firmware except the bootloaders and the param.lfs. You may need to flash param.lfs next to see if that will do it. Is there any chance that what you flashed for the I9100 contained bootloaders?
...........
By the way, having Super OneClick hang on step #6 is a known issue, and the solution is posted in the Super OneClick thread OP as well as in the Library sticky thread in the development section of the I777 forum. If you had been better informed, you could have avoided this problem.
Click to expand...
Click to collapse
First, you're a true gentleman (assuming 'creepyncrawly' to be male) for sticking with me on this issue - Thanks!
To address your first point, I could't do a factory reset after this most recent flash because that dialog doesn't exist any longer. All I get is the "Deleting cryption meta data" message when I try to enter recover mode.
As for the I9100 flash, I used CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 first which took me to 4.0.0.2 and then realizing what I'd done, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 which took me to 5.0.2.3, though the I9100 logo still showed during boot.
Thanks again for your help. I will "flash at will" whatever you suggest as at least I feel I'm making progress now.
digitalsdc said:
First, you're a true gentleman (assuming 'creepyncrawly' to be male) for sticking with me on this issue - Thanks!
To address your first point, I could't do a factory reset after this most recent flash because that dialog doesn't exist any longer. All I get is the "Deleting cryption meta data" message when I try to enter recover mode.
As for the I9100 flash, I used CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 first which took me to 4.0.0.2 and then realizing what I'd done, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 which took me to 5.0.2.3, though the I9100 logo still showed during boot.
Thanks again for your help. I will "flash at will" whatever you suggest as at least I feel I'm making progress now.
Click to expand...
Click to collapse
The CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.tar contains only the kernel zImage, so it doesn't flash any of the wrong bootloaders or param.lfs, so no clue there.
However, the message "deleting cryption meta data" seems to be associated with the lfs, so I would suggest that you try flashing just the UCKH7 param.lfs file using Odin3. Go to the Download Repository where you will find the Odin3 flashable tar of the UCKH7 param.lfs.
creepyncrawly said:
The CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.tar contains only the kernel zImage, so it doesn't flash any of the wrong bootloaders or param.lfs, so no clue there.
However, the message "deleting cryption meta data" seems to be associated with the lfs, so I would suggest that you try flashing just the UCKH7 param.lfs file using Odin3. Go to the Download Repository where you will find the Odin3 flashable tar of the UCKH7 param.lfs.
Click to expand...
Click to collapse
I successfully flashed the I777 param.lfs from your download repository. Unfortunately, with the same results. I still get the boot loop and when trying to access recover mode I get "Deleting Cryption Meta Data".
Would you suggest I try flashing the secondary boot loader or .pit files?
digitalsdc said:
I successfully flashed the I777 param.lfs from your download repository. Unfortunately, with the same results. I still get the boot loop and when trying to access recover mode I get "Deleting Cryption Meta Data".
Would you suggest I try flashing the secondary boot loader or .pit files?
Click to expand...
Click to collapse
Well, I had a little extra time tonight so I tried a couple more things after my last post. I went back to the Download Repository and got the secondary boot loader (i777 UCKH7 sbl), flashed with that. No change. Then I got the full set of binaries (I777UCKH7-CL503881-Full), flashed that, and still no change. I think I've tried everything except the .pit and that appears the most risky so I'll await further instruction before trying that.
Am I running out of options at this point?
I had a similiar problem with the deleting meta cache data. I couldn't get it back to working order although I didn't flash pit either. Luckily mine was within 30 days so I gave up and returned for a new one.
Hopefully this deleting meta cache thing can be figured out to see what the cause is. Mine happened from a working rom browsing the web, not from flashing. So I believe it was from aftermarket charger creating some hardware problems to my phone, but not sure what it could have messed up.
If ya can't exchange yours, I hope you figure it out.
Sent from my SAMSUNG-SGH-I777 using XDA App
digitalsdc said:
Well, I had a little extra time tonight so I tried a couple more things after my last post. I went back to the Download Repository and got the secondary boot loader (i777 UCKH7 sbl), flashed with that. No change. Then I got the full set of binaries (I777UCKH7-CL503881-Full), flashed that, and still no change. I think I've tried everything except the .pit and that appears the most risky so I'll await further instruction before trying that.
Am I running out of options at this point?
Click to expand...
Click to collapse
I have always understood that if a phone will boot in any way, or show any sign of life, then it can be recovered. Since you can still get into download mode, you should be able to recover your phone. However, since I am not an Android developer, and I don't really understand the low level workings of the phone, I can't offer any more suggestions myself.
You have flashed the complete I777UCKH7 software package including bootloaders and param.lfs, which also rebuilds the csc, so I don't know what is causing the bootloop.
You need to seek the help of someone more experienced. I have two people on xda in mind who specialize in recovering hard bricked phones, and both have a better understanding of the low level workings of the phone.
Adam Outler is a fantastic hardware level developer who published the unbrickable mod for the Galaxy S series of phones, and is currently moving into the Galaxy S II phones. I have heard that he wants an I777 to work on to try to make the unbrickable mod for our phone. He would probably not charge anything since he is using the phone to learn how to do it, but he might keep the phone for a while.
Connexion2005 of Mobile Tech Videos offers hard brick recovery on the Galaxy S and Galaxy S II series of phones. He also has a very good understanding of the low level functions of the phone.
If it was my phone, I would be contacting these two to see if I could get any guidance about how to recover the phone, probably Adam Outler first. I would try to pm them and I would try to get phone numbers and talk with them in person.
You are not hard bricked. And about the pit, that re-partitions the phone. But I don't have enough experience to know if partitioning could cause the problem you are experiencing.
Good luck moving forward.
Any chance flashing a ROM would do the trick...like Unnamed or SHOstock? Just thinking that maybe he's flashed so many things nothing is playing nice anymore. Just a thought, not necessarily a suggestion. ;-)
Also, how long are you letting it sit in boot loop now? It might be taking a while to rebuild everything...?
Sent from my SAMSUNG-SGH-I777 using XDA App
Nerz said:
I had a similiar problem with the deleting meta cache data. I couldn't get it back to working order although I didn't flash pit either. Luckily mine was within 30 days so I gave up and returned for a new one.
Hopefully this deleting meta cache thing can be figured out to see what the cause is. Mine happened from a working rom browsing the web, not from flashing. So I believe it was from aftermarket charger creating some hardware problems to my phone, but not sure what it could have messed up.
If ya can't exchange yours, I hope you figure it out.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
So, had you rooted and put a custom rom on prior to yours going south, or was it completely stock? What made you think it was related to the aftermarket charger?
Jank4AU said:
Any chance flashing a ROM would do the trick...like Unnamed or SHOstock? Just thinking that maybe he's flashed so many things nothing is playing nice anymore. Just a thought, not necessarily a suggestion. ;-)
Also, how long are you letting it sit in boot loop now? It might be taking a while to rebuild everything...?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Thanks for your thoughts. I had a similar thought last night and so let it sit through the night rebooting. Sure enough, when I checked it (roughly 8 hours) this morning, it was nice and warm, but still rebooting away.
creepyncrawly said:
I have always understood that if a phone will boot in any way, or show any sign of life, then it can be recovered. Since you can still get into download mode, you should be able to recover your phone. However, since I am not an Android developer, and I don't really understand the low level workings of the phone, I can't offer any more suggestions myself.
You have flashed the complete I777UCKH7 software package including bootloaders and param.lfs, which also rebuilds the csc, so I don't know what is causing the bootloop.
You need to seek the help of someone more experienced. I have two people on xda in mind who specialize in recovering hard bricked phones, and both have a better understanding of the low level workings of the phone.
Adam Outler is a fantastic hardware level developer who published the unbrickable mod for the Galaxy S series of phones, and is currently moving into the Galaxy S II phones. I have heard that he wants an I777 to work on to try to make the unbrickable mod for our phone. He would probably not charge anything since he is using the phone to learn how to do it, but he might keep the phone for a while.
Connexion2005 of Mobile Tech Videos offers hard brick recovery on the Galaxy S and Galaxy S II series of phones. He also has a very good understanding of the low level functions of the phone.
If it was my phone, I would be contacting these two to see if I could get any guidance about how to recover the phone, probably Adam Outler first. I would try to pm them and I would try to get phone numbers and talk with them in person.
You are not hard bricked. And about the pit, that re-partitions the phone. But I don't have enough experience to know if partitioning could cause the problem you are experiencing.
Good luck moving forward.
Click to expand...
Click to collapse
Thanks very much for all your help! I'll try to reach out to these other gentlemen as well.
I've seen other people on these forums with the same problem, but unfortunately, every thread seems to end unresolved. I still hold out hope as I really don't want to eat the cost of the phone and start over.
digitalsdc said:
So, had you rooted and put a custom rom on prior to yours going south, or was it completely stock? What made you think it was related to the aftermarket charger?
Click to expand...
Click to collapse
I figured it was the charger because it was connected when it happened. Was driving home from a Christmas vacation, with maps navigation going, stopped at a rest stop surfing the web. Also on another thread that I read that had a similiar problem, they too thought it was the charger.
And no it was not stock, running unnamed at the time, (though I doubt that is the cause). Like yours I think, I could flash from cwm without success. Wasn't until I flashed stock with stock recovery that I got the deleting meta cache or whatever it is.
Sent from my SAMSUNG-SGH-I777 using XDA App
Any luck so far? I think I'm having the same issues. Although I can flash the stock rom, then a CWM .tar file and get into recovery. But no matter what I do, after boot, the phone starts boot looping.
You can see my thread in the Q&A section.
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
hardgrid said:
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
Click to expand...
Click to collapse
THX THX THX THX THX! It worked!
hardgrid said:
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
Click to expand...
Click to collapse
Hi, did anybody tried this solution??? I'm having the same issue, even tried to contact JTAG unbrick service but these guys told me I'm having a emmc chip failure.
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem