Related
does anyone know how to do this? i have used superoneclick, AIO captivate tools and OCD. nothing works
i have a rooted captivate running froyo stock
Backup your stuff and flash Cognition. Easiest way. You may want to stay stock, but trust me, it's much better.
Sent from my Desire HD using XDA Premium App
TheBassman369 said:
Backup your stuff and flash Cognition. Easiest way. You may want to stay stock, but trust me, it's much better.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Agreed. Read what cog has in it, it comes with side loading enabled
Sent from my SAMSUNG-SGH-I897 using XDA App
I got it to work through superoneclick even though it failed the 1st 2 times I did it. I restarted the phone did the non market app fix and then restarted again and applanet worked. It is still a little buggy but it works.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I agree with flashing Cog.
However, I am currently trying to see how far I can get with the stock 2.2.
With that said, I used "SuperOneClickv1.7-ShortFuse" to root and allow non-market apps. If it does not work, remember to right click the .exe and run as administrator (if you are on Win7).
i want to keep it stock because of the just incase something happens and i need to use the warranty or insurance i want to get it back to stock in the matter of 2 clicks to backup all the att bloatware and unroot so i can send it in.
i know there is another method to flash back to stock but i dont really understand flashing different roms and kernels and want it to be as simple as possible. if i find a real need to flash a different rom and kernel i will learn more about it. im just not fully educated on much of this stuff.
gephross100 said:
i want to keep it stock because of the just incase something happens and i need to use the warranty or insurance i want to get it back to stock in the matter of 2 clicks to backup all the att bloatware and unroot so i can send it in.
i know there is another method to flash back to stock but i dont really understand flashing different roms and kernels and want it to be as simple as possible. if i find a real need to flash a different rom and kernel i will learn more about it. im just not fully educated on much of this stuff.
Click to expand...
Click to collapse
Seriously, man, getting back to stock is as easy as that. All you have to do is download Odin one click, put your phone in download mode, click start, and bam, you're at stock. If you need me to walk you through flashing ROM's, I can later on today. It's not as hard as you think.
where do i download the rom for cognition
what are the pros and cons to cognition and the known bugs in it
why choose this over other roms? why not flash to 2.3.3?
will i have to re-download all of my apps and settings etc.?
gephross100 said:
where do i download the rom for cognition
what are the pros and cons to cognition and the known bugs in it
why choose this over other roms? why not flash to 2.3.3?
will i have to re-download all of my apps and settings etc.?
Click to expand...
Click to collapse
I'll pm you with details, just download Titanium Backup and sms backup and restore from the market for now.
CM7 Inspire 4G
At this point I've tried every method of flashing, and every version of cwmr. No matter what version or method I use, after about a week, I lose the ability to flash any roms that I havnt already flashed. I also can only restore certain backups due to.an MD5 mismatch. Has anyone else had these issues?
Sent from my LG-P999 using XDA App
hey, unfortunately i cant help you. I havent even been able to flash cm7 once. always boot loop.
md5 sums are giving me mismatch with some the original restore (nandroid) from this post http://forum.xda-developers.com/showthread.php?t=1048274
Yea, a guy In the cm7 thread its going to post a dl that worked for him so ill try that one and let u guys know as far as cm7 goes.
Sent from my LG-P999 using XDA App
I just want to revert to stock so I can get a replacement lol... maybe if you have one I can try :-/ I just deleted mine by accident (read the dates wrong)
mt3g said:
I just want to revert to stock so I can get a replacement lol... maybe if you have one I can try :-/ I just deleted mine by accident (read the dates wrong)
Click to expand...
Click to collapse
Download the stock with root and use one click root to unroot after that use one click recovery and pick stock. Than hard reset your back on tmobile out the box stock
Sent from my LG-P999 using XDA Premium App
crx4xharder said:
At this point I've tried every method of flashing, and every version of cwmr. No matter what version or method I use, after about a week, I lose the ability to flash any roms that I havnt already flashed. I also can only restore certain backups due to.an MD5 mismatch. Has anyone else had these issues?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
No issues like this. I reverted back to other roms more than once and it worked everytime. No mismatch error
Sent from my LG-P999 using XDA Premium App
charlieb620 said:
Download the stock with root and use one click root to unroot after that use one click recovery and pick stock. Than hard reset your back on tmobile out the box stock
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Ya I downloaded it and everything and tried different ways and it wont let restore, just says md5 sums mismatched tried 2 sdcards and downloading them in root of sd card and directly in the CWM/restore folder. still a no go, but I can restore other backups and flsh roms. just not the one i need.
Probably won't get to it till thursday or so, but im going to try and go back to completely stock, reroot, reflash cwr, flash cm7. Otherwise im getting a replacement...
Ps
The dl posted in another thread for me failed as well. I also had an intense the other day where all my partitions were completely wiped. It took 3 hours to finally get nv flash to flash cwr and flash a rom.
Sent from my LG-P999 using XDA App
crx4xharder said:
Probably won't get to it till thursday or so, but im going to try and go back to completely stock, reroot, reflash cwr, flash cm7. Otherwise im getting a replacement...
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I have a feeling im going to return another one thatll make 4
Sent from my LG-P999 using XDA Premium App
My SD was bad! Reformatted in cwr, then in settings SD and storage... dl cm7, and flashed. Just remember to copy ALL the contents of your sdcard cause formatting WILL DELETE EVERYTHING!
Sent from my LG-P999 using XDA App
Ok if anyone is still having problems, id like to mention that I exchanged my 5 year old 2g simcard yesterday for a new one, and bought a new 16gb class 4 sandisk sdcard, and EVERYTHING is working great! so far maybe only 2 or 3 occurrences of data loss, easily corrected with a battery pull. And I borked some lib files trying to get the camcorder to work. So I installed the kanged version update-cm-7.1.0-RC0-G2x-KANG-signed.zip overtop of my build to get the rom to boot again, and now the camcorder works! Maybe only about 15fps but works nonetheless...
Sent from my LG-P999 using XDA App
I was just thinking everyone is bummed about not having a full working cwm to do a full restore. But when u screw up its Odin to the call. right? I just don't see why we need full CWM when we can use Odin if we mess up. As far as getting things back to normal (setting,icons,wallpapers,etc.) U can use advanced restore to put everything back the way it was before the flash but still keep the effects of new kernels and roms. So i ask this why all the fuss? Also maybe someone could elaborate on the mount issue. Is it only when you try to do a full restore Or flash certain Roms? Oh yea and this is a noob asking.
Sent from my SGH-T959V using XDA Premium App
It's mostly a question of convenience. If we get a fully functioning cwm it can be directly booted in to replacing the stock recovery. More importantly it can be incorporated into Rom Manager which makes lots of things easier and more standardized. Things like flashing roms and kernels or restoring backups and making fixes would be much easier and all right there in rom manager/cwm.
As far as Odin/heimdal goes yes that works for installing roms, restoring from soft bricks, etc. but is no substitute for a nandroid backup/restore which is great for reverting to a former configurations fully and easily after trying out new roms, kernels, etc.
There are other reasons it would be great to have a finished cwm but what we have now is not that bad since it can do most of the important things we need.
I am still interested in what I hear that people are restoring full nandroid backups successfully. The official word is that its not unmounting properly during format function in a restore, at least that's what I understand. If full restore is actually working as some are claiming then I'm not sure what is actually left undone.
Sent from my SGH-T959V using XDA Premium App
Harhar321 said:
It's mostly a question of convenience. If we get a fully functioning cwm it can be directly booted in to replacing the stock recovery. More importantly it can be incorporated into Rom Manager which makes lots of things easier and more standardized. Things like flashing roms and kernels or restoring backups and making fixes would be much easier and all right there in rom manager/cwm.
As far as Odin/heimdal goes yes that works for installing roms, restoring from soft bricks, etc. but is no substitute for a nandroid backup/restore which is great for reverting to a former configurations fully and easily after trying out new roms, kernels, etc.
There are other reasons it would be great to have a finished cwm but what we have now is not that bad since it can do most of the important things we need.
I am still interested in what I hear that people are restoring full nandroid backups successfully. The official word is that its not unmounting properly during format function in a restore, at least that's what I understand. If full restore is actually working as some are claiming then I'm not sure what is actually left undone.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
So basically it would take the need for a PC out. Plus make restoring full backup possible (also tried full restore and got mounting error). Thanks for the info. So is it do to lack of devolopment and devs that r device is not so popular or the mounting issue. Thanks again.
Sent from my SGH-T959V using XDA Premium App
Damn you got the mounting error....i thought that worked...wtf
Sent from my SGH-T959V using XDA Premium App
Why am I testing post that your alter to do a full restore...pretty misleading
Sent from my SGH-T959V using XDA Premium App
de1packers said:
Why am I testing post that your alter to do a full restore...pretty misleading
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Just curious..... Have u tried the full restore yet on CWM? If so what where your results??? I have to admit i finally have my 4g running and set up just how i want it and im a little nervous to try it out(i have done a couple advanced restores) for fear me and my old friend odin might end up getting back together a little sooner than i had planned!
Well wait maybe I'm confused..advanced restores are not nandroid restore?...
Sent from my SGH-T959V using XDA Premium App
de1packers said:
Well wait maybe I'm confused..advanced restores are not nandroid restore?...
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Advanced restore lets you restore just not full restore. It gives you the option to restore system,data,ect one at a time. However I have not tried to restore system just data. Like I said before couldn't full restore due to mounting issue. Also I think nandroid backup is just another term for a full backup of basicly the exact state of the phone at the time back up is done. If I'm wrong please feel free to correct me.
Sent from my SGH-T959V using XDA Premium App
Ah so it sounds like there is still a mounting related error after all. And yes you got it about right. A full nandroid restore basically brings your phone back to 100% exactly the state it was in when you backed it up.
Sent from my SGH-T959V using XDA Premium App
Totally clear on that considering I've been in this since the g1 with RAs recovery..that guy was so hardcore with yhe recovery....so what does the state of the phone look like after you do a restore?
Sent from my SGH-T959V using XDA Premium App
You hit the nail on the head....
Sent from my SGH-T959V using XDA Premium App
So wait nandroid backup and restore doesnt work for some people?
Sent from my SGH-T959V using XDA App
So wait nandroid backup and restore doesnt work for some people and for some it does?
Sent from my SGH-T959V using XDA App
Let's clear up the confusion...
As I posted on the Wiki, I have successfully done a Nandroid backup and a Nandroid restore... In both cases the "system" was identified as being backed up (or restored).
I have repeated this several times, the most recent being this morning. But, in an effort to not dispute krylon360, I've posted a targeted question to him in his thread announcing CWM3.0.2.8Beta.
I am hopeful of his response!
I was just wondering cause it works for me all the time and I thought it was working for everybody.
Sent from my SGH-T959V using XDA App
It is....they say it works with bali kernal, you can't use the stock kernal..I've tested and confirmed
Modded gingerbread theme
Whitehawks kd1 deodexed with modded green dialer,modded pull down menu (favorite color is green and favorite football team greenbay packers)
GDofWR420 said:
I was just thinking everyone is bummed about not having a full working cwm to do a full restore. But when u screw up its Odin to the call. right? I just don't see why we need full CWM when we can use Odin if we mess up. As far as getting things back to normal (setting,icons,wallpapers,etc.) U can use advanced restore to put everything back the way it was before the flash but still keep the effects of new kernels and roms. So i ask this why all the fuss? Also maybe someone could elaborate on the mount issue. Is it only when you try to do a full restore Or flash certain Roms? Oh yea and this is a noob asking.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
restore definitely works on cwm.... u all r kinda being wild... there are already threads on this... look at the development thread for clockworkmod... comparing odin to cwm psshhh
Nothing wrong with odin. Nothing wrong with cwm. I have been backing up and restoring with cwm for a while now. Still don't know if it's a true "nandroid" backup but it restores everything but my lock screen wallpaper. Everytime without fail. So good that I have not had to use odin or titanium. I'm even sure I could odin at this point and get all of it back through cwm. Follow the steps for setting it up you should be fine. I'm running whites KD1 and have been since it came out.(**** I might have to Odin now just to check it out) How do you use Odin again?
Have fun
i have to send my infuse in under warranty, so which verison of stock should i use?
i know att will want me to have the most current operating system installed when i send it in.
thanks guys
I would just flash gtg's unbrick and the search updates under settings.
Sent from my SAMSUNG-SGH-I997 using XDA App
After using unbrick, restore to factory once booted so that it will hopefully erase all traces.
Cranky...
shg-i997uckh1
but you might want to flash ke3 and find a bootloader dump from it. if you updated to current bootloaders i believe it has a counter for number of 3rd party firmwares flashed to it. dont want the insurance company to see that. i dont know if this coulter counts cwm flashes or just download mode flashes but it somewhat can distinguish between att official and not atleast on the kernel end.
After the ICS was leaked, it bought some good news and as well some bad news..
Some of our user have just bricked their mobile after performing a wipe data thru recovery..
The cause of error is yet unknown..
Out user vijai has published some of the known causes...
The credit goes to vijai for pointing it out
vijai2011 said:
CAUSES
Symptoms of super brick(caused by emmc bug):
1.Phone gets stuck at splash screen.
2.recovery gets stuck at whenever trying to access corrupted partition.
3.ODIN gets stuck at flashing factoryfs.
4.You can flash kernel but almost nothing else using both ODIN and cwm.
Sent from my GT-N7000 using xda app-developers
Click to expand...
Click to collapse
vijai2011 said:
FIX
No problem....temporary fix to avoid bricking is to avoid using cwm to flash anything,doing wipes in cwm,formatting partitions in cwm,doing factory reset through settings and by typing code in phone,removing large size files from sdcard.
The permanent fix is to disable MMC_CAP_ERASE in kernel while making it.Any kernel dev can do that easily I guess....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This definitely doesn't mean that all galaxy R handset are brick bug or you may encounter such problem..
Only a few have encountered the problem and the cause is yet unknown. This definitely, doesn't stop you from flashing ics..if you want to flash keep these things in mind.
Also, please do not completely rely on brick bug app from play store because the app (imo) is not supported to our device (correct me if i am wrong)
(i am no developer, just heard from my fellow user )
*****NOTE******
This applies to the Stock ROM released by machram and as well to all those ROM which are based/built upon the Stock ROM.
Click to expand...
Click to collapse
SO WHAT DOES IT MEANS TO YOU ?
If you have already flashed ICS, you are requested not to wipe data through CWM/Stock recovery and also do not factory reset the phone till the issue is identified. i.e. Once ICS === No Wipe (till its rectified)
Click to expand...
Click to collapse
Currently there are only two users who have hard bricked their phone after flashing ICS.
As you might be aware by now that the emmc brick bug app is not compatible with our phone.
The most elite developer Entropy512 wants to make it compatible and hence wants some sample..
Entropy512 said:
Can someone who experienced damage and still has their device contact me via PM? One of my contacts wants to collect a few damaged devices.
Click to expand...
Click to collapse
Note: I dnt recommend you to brick your phone
(thanks m.kochan, callmeventus, cooleagle)
A big thanks to entropy for showing interest to our device
Caution:
Here's what to say from a user who bricked his phone
mj.vikram said:
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck..
Click to expand...
Click to collapse
*******UPDATE********
Here is the new fix method
vijai2011 said:
And guys for the guide to safe flash:
Flash a GB kernel,boot into recovery,flash any rom.GB or ICS.Its safe to wipe in gb kernel.But once you flashed ICS you arent safe.If you need to wipe again,you need a GB kernel again.
This was the method we used in Note to wipe when had not got a safe kernel.
Click to expand...
Click to collapse
We have got one lucky user who is enough brave and tested this method
selva.simple said:
To make a conclusion to that, i have tested your method in Galax R buddy. I found that i had a GB kernel in my phone. So why wait till i reach home. Tested now itself. I tested two rounds. One is for getting ICS via CWM flash and the other is for getting ICS via CWM restore.
First Test:
1. Flashed GB kernel
2. Rebooted to Recovery
3. Wipe data
4. Flash ICS by CWM flash i.e., "Install from Zip" method
5. Reboot
Second Test:
First Three points are same. and finally Restored a nandroid backup of ICS i took earlier. Reboot
In both the method i was able to boot the phone and get the ICS ROM and ICS kernel. To add more,
After both boots, I tested the system apps and data apps - mainly Play store, Gmail, Music player, Gallery, Camera for any FC issues. Everything is working perfectly and no issues created apart from existing issues of ICS.
Click to expand...
Click to collapse
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes i do agree..d problem may arise on 1st or on 100th wipe...
Bt the cause is yet unknown...
So imho, all the noobs shldnt do..who knows they get it for the first time...
Sent from my GT-I9103 using Tapatalk 2
Seriously? Removing large size files from sdcard can brick my phone?
Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Dont know...but i have tried deleting large files as 1gb game data...such as max payne and asphalt7
No brick...
Sent from my GT-I9103 using Tapatalk 2
Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
So a little story now.
From where has this infamous brick bug appeared??
Analysis by kernel devs say that MMC_CAP_ERASE command in kernels are present from gb periods.But why hasn't it been causing problems in GB?That's because it was disabled as Google didn't see the need for it.
But in ICS they feel that just removing files causes security problems.so they thought of enabling MMC_CAP_ERASE command which will completely wipe instead of removing.
So why should it need to brick our devices?
That's because,one of the Google engineer said that our mmc uses buggy firmware that initiates wrong process when the kernel receives MMC_CAP_ERASE command.
Actually MMC_CAP_ERASE command and mmc buggy firmware are harmless on its own.But when both are combined the result is super brick.
Sent from my GT-N7000 using xda app-developers app
This is not the worst scenario. In worst case you're gonna get hardbrick with no possibility to turn your device on.
MMC_CAP_ERASE on - wasn't present in every ICS version, at least not for S2 (I know that NOte users had bigger problem with that). All previous 4.0.3 were totally safe. Latest 4.0.4 - unfortunately not. It's not really buggy firmware that causes any problem here. According to Entropy512 (I guess the best xda-expert in that matter) MMC_CAP_ERASE was activated in order to improve writing speed. Hard brick occur if the all three conditions are fulfilled here:
1) You have a faulty (brickable) emmc-chip
2) If MMC_CAP_ERASE command is activated in kernel
3) If you perform wipe/restore nand backup/install roms (wipe-type) where:
a) cwm recovery - very high risk
b) stock recovery - lower risk but still not equal 0.
So faulty emmc chip is a bomb, mmc_cap_erase is a fuse, wiping in cwm - is a trigger or fire!
Not all devices are endangered, only those with brickable emmc-chips. In regard to Note or S2 it's easier because those devices have great dev support and there were thoroughly examined. So there are known some ways to bypass this problem. In case of SGR is much harder. First of all ... we don't know which chips are really sane and which are not.
Fusrodah said:
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
Click to expand...
Click to collapse
Just two as of now so don't panic !
You can use ICS 4.0.4 but till the cause of the bricking is confirmed just don't preform any Wipe data / Wipe Cache / Factory reset operations while on ICS 4.0.4 ROM.
As per mkochan if you want to go back to the stock ROM for giving it to the service center / etc then directly flash GB / 2.3.x ROM without wiping the cache / data using CWM.
m.kochan10 said:
1) To avoid brick = don't wipe, don't do factory reset, do not restore nandbackups.
a) If you wanna to get rid of this fw.version
-> Flash a safe kernel / or best stock rom directly via Odin.
-> Wipe after installation process is done. NOT BEFORE!
2) To recover...one guy from Note section wrote a tutorial for those bricked devices that was able to turn on. He managed to recover it but he had to sacrifice 2-3 gb of internal storage. If device is not bootable then it's a motherboard replacement.
3) Turning off this function in kernel is not easy thing. I don't think this flag can be easily removed. I'm not a kernel guy....so I'm sorry but don't know much more about that. Our devs can take a look, maybe they can find a solution.
4) Bootloaders cannot be flashed via recovery, not via mobile odin either. And FW-odin version is still unavailable so I assume you still have GB ones.
5) About USB jig - Is your DM protocol the same like before? 2.0? (people with 2.1 have never been able to used jig as far as I remember)
Click to expand...
Click to collapse
Okay, we must wait for kernel with disabled MMC_CAP_ERASE. I hope we'll get it. Thanks for the information.
Oh my god
I did factory reset in ics because my keyboard dissappeared. Will my device hard brick?
I cannot understand why Samsung realeses a firmware which should make our mobile dead! What is this function even for?
Sent from my GT-I9103 using xda premium
You can find sort of explanation on the previous page
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Google86 said:
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Click to expand...
Click to collapse
I think app is not working for SGR, both user have used this app and app shown sane chip yet those both guys devices are bricked.
We should contact dev of app to make comp with SGR.
Sent from my CM7.2 powered Galaxy R using Tapatalk 2.
Damn it , I knew this would happen.....
"Friends forever." - Ventus
Guys actually you could check if you have any bad blocks in any partition through gpartrd in adb.Just looking its info.will post when I find some.
Sent from my GT-N7000 using xda app-developers app
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Sorry i have't seen this thread and created new one, so if you think i have created duplicate one please ask Justin to delete it....
mj.vikram said:
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Click to expand...
Click to collapse
Dude i dont have a GB Backup (CWM BACKUP)
and dude, what you gonna do now, how will you get back your phone ???