Database Users

wont boot after factory reset. bricked?

I had bionix fusion w/ voodoo and oc kernel. everything worked fine. Saw that froyo is finally out and decided to try it out. yes I disabled voodoo, wiped, and the rom flashed with no problems. It was just laggy and i didnt like it. It was the AOSPish 2.2 rom. I tried booting into recovery-wouldnt go past vibrant screen. thought maybe factory reset would help. it shut off and now wont go past the vibrant/samsung screen.
i've tried recovery and download mode. both get stuck at vibrant screen

ed1380 said:
I had bionix fusion w/ voodoo and oc kernel. everything worked fine. Saw that froyo is finally out and decided to try it out. yes I disabled voodoo, wiped, and the rom flashed with no problems. It was just laggy and i didnt like it. It was the AOSPish 2.2 rom. I tried booting into recovery-wouldnt go past vibrant screen. thought maybe factory reset would help. it shut off and now wont go past the vibrant/samsung screen.
i've tried recovery and download mode. both get stuck at vibrant screen
Click to expand...
Click to collapse
Email me [email protected]
Sent from my GT-I9000 using XDA App

If you are properly entering download.. You won't have a vibrant screen to freeze at.
ed1380 said:
I had bionix fusion w/ voodoo and oc kernel. everything worked fine. Saw that froyo is finally out and decided to try it out. yes I disabled voodoo, wiped, and the rom flashed with no problems. It was just laggy and i didnt like it. It was the AOSPish 2.2 rom. I tried booting into recovery-wouldnt go past vibrant screen. thought maybe factory reset would help. it shut off and now wont go past the vibrant/samsung screen.
i've tried recovery and download mode. both get stuck at vibrant screen
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm able to get into download mode, but sadly I found only one odin file and it'll take 3 hours to download. I'm trying to unbrick with odin

Pretty much what you have to do. Odin is large because its practically replacing your phone.
ed1380 said:
I'm able to get into download mode, but sadly I found only one odin file and it'll take 3 hours to download. I'm trying to unbrick with odin
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App

Vibrant update is out?
Or is he talking about the hacked together custom ROMs?

"hacked together"
?? They are straright from T-Mobile... lets not make them sound bad. I am running Onyx 22 and it is simply amazing.

having the same issues... and ODIN is getting stuck here:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs

Zeno78 said:
having the same issues... and ODIN is getting stuck here:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
Click to expand...
Click to collapse
Try removing your external SD and your SIM card.

all is well thanks guys!

dun bricked myself good this time..

borked up the fascinate whilst trying to update to the devs 2.2.
i know exactly what i did wrong. i was running voodoo5, and i clicked to disable lag fix, but i forgot to restart to let it *actually* disable before trying to load the new stuff. STUPID!
when that happened, it hung on samsung screen, then after battery pull all the phone will do is boot loop.. samsung screen, then goes to robot and screen says says "wiping cache, data, ect.." and then back to samsung screen to reboot and reboot.
i have literally 30 tabs open with articles from here and other forums, nothing seems to be working. here is what i have tried.
1. tried booting back to red cwm and playing with the lagfix (enable and disable again) to see if it would work, no go. i ended up losing red cwm - had to ODIN red back.. i cant get green to flash.
2. tried flashing DL09 both the full package and each individual part via ODIN
3. tried flashing the stocki500system.md5 (from the board) and kernel via ODIN, and nothing.. same boot loop. everything i have flashed via ODIN still gives me a boot loop..
4. tried to connect via ADB but it wont let me access the phone.. NOTE: i just downloaded ADB as a last resort and know nothing about it..
the only thing i can seem to do is get to red cwm. i have several backups in the restore section, but none of them seem to work - either i get a "no file found" even though i can see the file(s), or i get an error after it does load that says ".android_secure.img not found. skipping restore of /sdcard/.android_secure"
any ideas?

Okay follow these steps. Make sure you follow them step by step. Even though you have the lagfix installed this removed it for me.
http://forum.xda-developers.com/showthread.php?t=782204
Place the PIT file where it belongs. Then ODIN the system, kernel, and recovery in that order. Don't restart the process every time. Just ODIN them one after another.

thank you very much for taking a moment to answer. i did follow that thread, however
i managed to get the stocki500 recovery but the other files (recovery, PIT) are all 404 not found errors.
ive tried that stock md5 and it still boot loops. i actually have that tab open from when i tried that route..
any other ideas and thanks again

Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648

I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.

BSayre18 said:
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
Click to expand...
Click to collapse
downloading now.. thanks for the point to this file.. i hadnt found that one yet

no problem. it should work out good.

mailaliasgar said:
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
Click to expand...
Click to collapse
i soft bricked doing that with a corrupt file before.. however that time i was able to restore using my backup.
this time, every time i try a method, it kicks me back to boot loop. if the file that im downloading now doesnt work, i will have to try and figure out ADB as a last resort..
thanks much for the help!

BSayre18 said:
no problem. it should work out good.
Click to expand...
Click to collapse
problem
thank you for all your help

mrjake1970 said:
problem
thank you for all your help
Click to expand...
Click to collapse
So this worked for you? You just re-rooted as normal?
def

Thank you all for your help. i applied all the info i got here, and one of them worked it finally took the ODIN flash to stock and i recovered into FROYO from there.
seriously thank you all.. its great that the community is so supportive

I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?

Joe T said:
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Click to expand...
Click to collapse
i followed all the hints i got, and i think that the one i got about formatting helped me get out of the boot loop from hell.. it finally took my flash from ODIN, it wouldn't until i did the format(s)..
mind you i am NOT an expert, however from what i read and talked about offline, voodoo is still resident on your phone but disabled (check to see if you have the voodoo file still on your card).. if DL30 is running fine, you are ok..
from what i have read, yes.. the new cwm is required in order to get it to mesh properly with 2.2 leak.. i havent had any issues and i loaded that as well.. from one of the posts i read, if you are a serial flasher, then you need to make sure that not only you download the new cwm zip, but also should have deleted the entire clockworkmod folder from your card for best results..

I love this threadd.... I did the same damn thingg...
Sent from my SCH-I500 using XDA App

You guys are not alone. I'm just glad the peeps that know what's going on have the patience to put up with us.
Sent from my SCH-I500 using XDA App

adrynalyne's di01 odin package covers a multitude of sins.

upsidedownaaron said:
adrynalyne's di01 odin package covers a multitude of sins.
Click to expand...
Click to collapse
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App

godihatework said:
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ABSOLUTELY!! I have those on my computer at all times, adrynalynes d101 brought me back a few times.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate

ODIN DL09 --> reboots to recovery

Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys

dmasjz45 said:
Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys
Click to expand...
Click to collapse
I never used a pit when odining DL09 and it worked fine for me, maybe try it without it...
blazing through on my VZ Droid Charge

dmasjz45 said:
Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys
Click to expand...
Click to collapse
I had this happen to me the other day, you likely downloaded the wrong DL09 odin files. This is the DL09 you want (I bet it's several dozen megs larger than the one you have, if you did the same thing as me).
Flash that with the re-partition PIT and then you should be good.

Not sure what the issue was, but heimdall fixed it, thanks, will go back and odin DL09 now

KitsuneKnight said:
I had this happen to me the other day, you likely downloaded the wrong DL09 odin files. This is the DL09 you want (I bet it's several dozen megs larger than the one you have, if you did the same thing as me).
Flash that with the re-partition PIT and then you should be good.
Click to expand...
Click to collapse
Yes you're right, the DL09.tar.md5 I had is about 308 megs.......Weird....Thanks!!!!

help(resolved)

Hey I just seriously screwed my self over bassicly I tried to get miui to boot from the samsung fascinate however when I installed it in cmr it spassed out then powered of then went to the bootloader and I get a red error message saying can't mount data or something so then I tried to reinstall Eco 3 Odin using Odin and it worked it booted but it says I have zero data on my phone and I can't install anything. I also tried the oneclick soft unbricker but it fails saying adb divers are not installed when they are. I'm doing this on my phones browser witch is the only thing that seems to be working right now I also tried a band restore but I got the same data error message.

Have you tried restoring to DL17 and then re-upgrading to 2.2?

And how about a good old odin flash?
In worst case, I would ask imnuts for the full odin package, or use a fascinate full odin package to get you off your feet, then reflash the modem, and recovery, then wipe In recovery cyan cwm... Then flash ec03
Sent from my SCH-I400 using XDA Premium App

wait wait, is this on a Continuum or Fascinate?

Nuckin said:
wait wait, is this on a Continuum or Fascinate?
Click to expand...
Click to collapse
He is on a Continuum, but you can use a fascinate Odin package to reformat partitions if they get messed up, then just reflash recovery and start fresh if you can get in then... That wasn't a really good thing though to suggest to a newcomer necessarily, so thank you for pointing that out

okay heres what happened firts i wanted to see if i could get the miui rom for the samsung fascinate to boot on the continuum there pretty much the same phone minus the ticker and screen size so i went into clockwork mod and wiped everything then went to install zip from sd card and clicked on the miui rom witch was the process we always used on the hero. then after i clicked on it, it started to install then my screen started shacking and my phone turned off. when i turned it back on it when to the bootloader and a red error message poped up saying
e:cant mount /dev/blockstill(invalid argument
and when i go to recovery it says the same thing when i try to wipe/restore nand it says the same thing. so at that point i powered off and went to download mode and reinstalled eco3 odin using pda mode on odin and it worked then it rebooted and i got to the set up screen and i got 2 force closes daily brefeing and something else i went ahead and skipped all that stuff and it loaded fine after that. however now for some reason it says i have zero system memory so i cant install any apps or save data however it does recognize my sd card but i cant install to sd card. so bassicly the phone functions just no internal memory. at this point i honestly dont know what to do everything on the hero was simple and straight forward and we never ran into these kind of problems. ive also tried to restore my nands and reinstall clockwork mod but still no dice. what i need to do now i guess is get the necessary files to go completely stock and see if that helps. and if someone could point me in the direction to those files i would really aprechiate it. oh and i tried the one click unbricker it sayed success but didnt really do anything.
oh and i know trying to install miui was stupid but i was just wanting to see if it would boot lol.

Download the PIT file in the Development forum, as well as the DL17 Odin package from the FAQ of the EC03 post I made. Flash the DL17 in PDA, with the PIT, and re-partition selected. After that, you should be back on DL17, and can do whatever you want from there.

huzzza!!!
thank god that worked thank yall so much i still cant believe that just happened but restoring the stock odin image worked and all is well. so i guess tommorow i can reroot and restore my nand.
once again thank yall for the help.

Stuck on boot after installing custom roms

hello to everyone.
to make it quick and simple, I have an ATT Samsung s4 i337, i had CleanRom 1.0 installed via twrp 2.5.0.2 since scott released it. but its been a while so i tried installing a different more updated rom today, and i went with SHOsock... i factory reset my phone, installed it, it booted just fine. then i tried to reboot my phone and it got stuck on the samsung boot logo. tried to reflash it wiping dalvic and factory reseting,worked again, but every time i reset it, it stays stuck. i tried flasing Aplha Infamous s4 rom, same thing. tried flashing a custom rom and ktoonsez kernel nothing.
tried to recover from my nandroid back up and nothing happens.
then i read that it might be twrp. so i insalled OUDHS CWM tried flashing. samething.
so im basically stuck.
PLEASE if anyone has any idea or solution i'd appreciate it.
update!
i have found the only possible solution that i may know of as today. the only thing you can do if your phone is stuck on boot after trying to flash different roms, is to flash the stock ATT UCUAMDB or UCUAMDL firmware via ODIN.
you will lose your custom recovery but at least you can use your phone again.

If you've got everything backed up, perhaps use oudhs or even cwm and completely wipe everything. System, data and all. Then reflash your loki'd ROM, kernel, etc. See if that gets you straightened out.

So if you do a clean flash, it's boots fine the first time. But if you reboot it hangs at the logo? And a nandroid won't restore properly. I think you might have some hardware memory issues. But let's see if anyone else has any ideas.

xBeerdroiDx said:
If you've got everything backed up, perhaps use oudhs or even cwm and completely wipe everything. System, data and all. Then reflash your loki'd ROM, kernel, etc. See if that gets you straightened out.
Click to expand...
Click to collapse
i try wiping data through recovery but it gives me an error. system/data not available(found)

I guess you can give formatting everything a shot. Did you unmount anything by accident?
Sent from my GT-S7560M using xda app-developers app

xBeerdroiDx said:
If you've got everything backed up, perhaps use oudhs or even cwm and completely wipe everything. System, data and all. Then reflash your loki'd ROM, kernel, etc. See if that gets you straightened out.
Click to expand...
Click to collapse
OP the post I quoted will more than likely fix your issue. Please try it and let us know!

agent929 said:
OP the post I quoted will more than likely fix your issue. Please try it and let us know!
Click to expand...
Click to collapse
i have tried that with custom roms loki-ed already, loki-ing after, flashing kernels, everything.
the only solution i was able to find is to download the stock ATT UCUAMDB firmware, and using ODIN to flash it. after that it boots fine. i did lose everything though, my custom recovery and root. at least its not looping on boot...gonna flash MDL now.

rickymh19 said:
i have tried that with custom roms loki-ed already, loki-ing after, flashing kernels, everything.
the only solution i was able to find is to download the stock ATT UCUAMDB firmware, and using ODIN to flash it. after that it boots fine. i did lose everything though, my custom recovery and root. at least its not looping on boot...gonna flash MDL now.
Click to expand...
Click to collapse
You do know if you don't hurry and flash a custom rom since you went back to Factory AT&T and is not rooted your phone is gonna upgrade on it's own to MF3 and if that happens you won't be able to flash custom Roms just thought i let you know!

I've got almost this same exact problem, but for me it only boot loops every now and then. When it does boot loop, sometimes, battery pulls will work, but most of the time, I have to go into TWRP and do a factory Reset to even get it to boot.
I am running CM10.2-20130908-Nightly-jflteatt with cronic kernel installed. It has been doing this since I got the phone and rooted it a few days ago (Thankfully, the phone came loaded with MDL instead of MF3 from what I have been reading).
Since mine only does it randomly, would you recommend to install something else and try to see what happens? Or go the route of doing a ODIN flash with no SimCard and WiFi access to keep the phone from updating? Or just leave it like it is?
P.S. None of this stuff is new to me, I flashed so much stuff on my SGS3 that I got a hang of it, but can't find the issue for these boot loops. I thought it had something to do with Google Apps because it would boot all day, everyday fine without Google Apps installed (tried it all day today). I would randomly restart it to see what it did, and it booted fine, no problems.

firepong said:
I've got almost this same exact problem, but for me it only boot loops every now and then. When it does boot loop, sometimes, battery pulls will work, but most of the time, I have to go into TWRP and do a factory Reset to even get it to boot.
I am running CM10.2-20130908-Nightly-jflteatt with cronic kernel installed. It has been doing this since I got the phone and rooted it a few days ago (Thankfully, the phone came loaded with MDL instead of MF3 from what I have been reading).
Since mine only does it randomly, would you recommend to install something else and try to see what happens? Or go the route of doing a ODIN flash with no SimCard and WiFi access to keep the phone from updating? Or just leave it like it is?
P.S. None of this stuff is new to me, I flashed so much stuff on my SGS3 that I got a hang of it, but can't find the issue for these boot loops. I thought it had something to do with Google Apps because it would boot all day, everyday fine without Google Apps installed (tried it all day today). I would randomly restart it to see what it did, and it booted fine, no problems.
Click to expand...
Click to collapse
I'd try a different rom. It sounds like it boot loops on reboot? And not random reboots?

jd1639 said:
I'd try a different rom. It sounds like it boot loops on reboot? And not random reboots?
Click to expand...
Click to collapse
Yeah, its not random reboots. Have yet to have that problem yet. It just gets stuck at the Samsung logo when I need to restart the phone every now and then for whatever reason. After it gets past the Samsung logo, I have yet to have it get locked on the custom Rom boot screen.

firepong said:
Yeah, its not random reboots. Have yet to have that problem yet. It just gets stuck at the Samsung logo when I need to restart the phone every now and then for whatever reason. After it gets past the Samsung logo, I have yet to have it get locked on the custom Rom boot screen.
Click to expand...
Click to collapse
Ok, here's something new after installing a new Rom (This is doing a complete Install. Cleared System, Data and Wiped all Cache). On boot now, it still get stuck every now and then on the Galaxy S4 screen, but when I pull the Battery and re-insert it, it somehow resets my phone back to Default for that Rom. For example, on Slim Bean, with Gapps installed, it will make me go through the whole process of setting of Gmail again as well as make me redownload all my apps again. It's like the stuff isn't sticking after reboots.
Has this ever happened to anyone?
EDIT* Like I said, if nothing is suggested, after the stock ODIN files are downloaded and I try a few more things out, I'll just do a stock flash and redo my Root then see what happens with a Custom Rom then.

This is a kernel issue period, you need to find a loki kernel and flash that....and if that one doesn't work try another...

rickymh19 said:
i try wiping data through recovery but it gives me an error. system/data not available(found)
Click to expand...
Click to collapse
I just had this problem last night. Then went to restore ROM and it failed when trying to restore data. I was in the process of testing new ROMs. I have had problems previously even flashing Odin MDL with stock s4 cable. Also have the random boot loop issue. Could it be a hardware memory issue?

rickymh19 said:
hello to everyone.
to make it quick and simple, I have an ATT Samsung s4 i337, i had CleanRom 1.0 installed via twrp 2.5.0.2 since scott released it. but its been a while so i tried installing a different more updated rom today, and i went with SHOsock... i factory reset my phone, installed it, it booted just fine. then i tried to reboot my phone and it got stuck on the samsung boot logo. tried to reflash it wiping dalvic and factory reseting,worked again, but every time i reset it, it stays stuck. i tried flasing Aplha Infamous s4 rom, same thing. tried flashing a custom rom and ktoonsez kernel nothing.
tried to recover from my nandroid back up and nothing happens.
then i read that it might be twrp. so i insalled OUDHS CWM tried flashing. samething.
so im basically stuck.
PLEASE if anyone has any idea or solution i'd appreciate it.
update!
i have found the only possible solution that i may know of as today. the only thing you can do if your phone is stuck on boot after trying to flash different roms, is to flash the stock ATT UCUAMDB or UCUAMDL firmware via ODIN.
you will lose your custom recovery but at least you can use your phone again.
Click to expand...
Click to collapse
Hey!, I saw this post when searching for answers to the same issue I have right now. I have tried to flash I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar but Odin is getting a Failed results. I tried flashing back again to NB1 rootable rom from other threads here, then Tried flashing back to stock rom AMDB, still no luck. Could you tell me how did you managed to go back to AMDB?.. Thanks so much..

jobpvill said:
Hey!, I saw this post when searching for answers to the same issue I have right now. I have tried to flash I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar but Odin is getting a Failed results. I tried flashing back again to NB1 rootable rom from other threads here, then Tried flashing back to stock rom AMDB, still no luck. Could you tell me how did you managed to go back to AMDB?.. Thanks so much..
Click to expand...
Click to collapse
What is the error in Odin? What bootloader is currently on the phone?

audit13 said:
What is the error in Odin? What bootloader is currently on the phone?
Click to expand...
Click to collapse
thanks so much for responding.. I really dunno what to do with this phone.. Ever since I patched custom rom it started to hanged after restarting. The initial start is fine, but after I restart the phone It only reached the welcome screen. The only way I can get in is to do a factory reset. zzz
Bootloader: I337UCUFNB1 (that's what I saw using CPU Z)
Below is the error just now again.. ( I tried to flash it again.. )
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Odin will not flash the rom because the rom being flashed has an older bootloader than the rom on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.

audit13 said:
Odin will not flash the rom because the rom being flashed has an older bootloader than the rom on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.
Click to expand...
Click to collapse
Anything else I can do to put this At&T s4 back to that stock rom?.. so that I can use it again?. Please help :'(

This may help : http://forum.xda-developers.com/showthread.php?t=2616221