Develop Bugs

Bricked? or Soft Brick...

Hi guys,
Was trying to install a ROM last night in CWM Recovery, then I was having some difficulty, after each ROM swipe I was doing the Factory Wipe/Dalvik Cache Wipe/Cache Wipe.
Anyways, I ended up having to try and flash the pre-rooted Stock ROM, I used Odin 3.07 to flash it and in Odin it appeared to work fine, the phone was rebooting and Odin was in "Pass" mode, but the phone never gets beyond the Samsung boot screen.
I then tried to see if I could flash CWM Recovery in Odin and try and get into Recovery mode, it flashed fine in Odin and the device rebooted but still stuck in Samsung boot screen.... but I cannot get into Recovery mode manually, I even tried getting in via the Q3 Toolbox kit, and it says it cannot locate the device :/
So today, last desperate option, I tried flashing the un-rooted stock image for my carrier (Rogers), it seemed to work fine in Odin but it STILL just will not boot back up, still stuck in the Samsung boot screen.
Is this what a brick is? Beyond continually trying to re-flash the stock carrier MD5 via Odin, what can I do? Oddly enough the phone does recognize in the Q3 Toolbox for the Root options, just not for the Reboot into Recovery option. Is there something I can try in the Q3 Toolbox?
/Scared / really concerned
Please help, any help is appreciated.
Once again, I CANNOT get into CWM Recovery.

Sianspheric said:
Hi guys,
Was trying to install a ROM last night in CWM Recovery, then I was having some difficulty, after each ROM swipe I was doing the Factory Wipe/Dalvik Cache Wipe/Cache Wipe.
Anyways, I ended up having to try and flash the pre-rooted Stock ROM, I used Odin 3.07 to flash it and in Odin it appeared to work fine, the phone was rebooting and Odin was in "Pass" mode, but the phone never gets beyond the Samsung boot screen.
I then tried to see if I could flash CWM Recovery in Odin and try and get into Recovery mode, it flashed fine in Odin and the device rebooted but still stuck in Samsung boot screen.... but I cannot get into Recovery mode manually, I even tried getting in via the Q3 Toolbox kit, and it says it cannot locate the device :/
So today, last desperate option, I tried flashing the un-rooted stock image for my carrier (Rogers), it seemed to work fine in Odin but it STILL just will not boot back up, still stuck in the Samsung boot screen.
Is this what a brick is? Beyond continually trying to re-flash the stock carrier MD5 via Odin, what can I do? Oddly enough the phone does recognize in the Q3 Toolbox for the Root options, just not for the Reboot into Recovery option. Is there something I can try in the Q3 Toolbox?
/Scared / really concerned
Please help, any help is appreciated.
Once again, I CANNOT get into CWM Recovery.
Click to expand...
Click to collapse
You're soft bricked, don't panic just yet. A hard brick is when the device is completely unresponsive. So far this sounds fixable.
To get into recovery, are you holding down the volume up + home key for long enough after the Samsung logo appears?
I'd try that again, but if not: Try to Odin CWM again but uncheck "Auto-Reboot" in Odin. After it's done flashing, pull the battery out, put it back in, and use the key combos to get into recovery. Hopefully you have a nandroid backup saved or another rom saved on your sd that you can restore at this point. (Please note that using this method may increase your flash counter, but that can easily be fixed with Triangle Away).
Hope this helps.

If its just hanging at the samsung logo..pull the battery, put it back in, boot into stock recovery ( vol up+home+power) wipe data/factory reset then reboot.
After that just download one f the one click rooted stock rogers roms. Odin it, Then use the S3 toolkit to flash a recovery only.
Should be goo to go from there

I am flashing the pre-rooted stock ROM's via Odin again, and then will try and flash CMW Recovery again but without the Auto-Reboot selected.
I was pretty certain I was holding the keys long enough previously to try and get back into Recovery but it never would actually go into CWM Recovery.
Will let you guys know how it goes, thanks for replying.

skrambled said:
You're soft bricked, don't panic just yet. A hard brick is when the device is completely unresponsive. So far this sounds fixable.
To get into recovery, are you holding down the volume up + home key for long enough after the Samsung logo appears?
I'd try that again, but if not: Try to Odin CWM again but uncheck "Auto-Reboot" in Odin. After it's done flashing, pull the battery out, put it back in, and use the key combos to get into recovery. Hopefully you have a nandroid backup saved or another rom saved on your sd that you can restore at this point. (Please note that using this method may increase your flash counter, but that can easily be fixed with Triangle Away).
Hope this helps.
Click to expand...
Click to collapse
Just tried this.
Flashed the pre-rooted stock ROM, it went to Pass in in Odin, device never booted past the boot screen. Pulled out battery, re-inserted and then flashed CWM Recovery in Odin with Auto-Reboot turned off, that went fine to Pass, pulled battery and did the key combo to enter Recovery. I got the "Booting Recovery" in top left corner in blue for a second, held onto the key combo and nothing, just went back into the same Samsung boot screen and it's stuck there.

Sianspheric said:
Just tried this.
Flashed the pre-rooted stock ROM, it went to Pass in in Odin, device never booted past the boot screen. Pulled out battery, re-inserted and then flashed CWM Recovery in Odin with Auto-Reboot turned off, that went fine to Pass, pulled battery and did the key combo to enter Recovery. I got the "Booting Recovery" in top left corner in blue for a second, held onto the key combo and nothing, just went back into the same Samsung boot screen and it's stuck there.
Click to expand...
Click to collapse
Hmmmm...one more thing to try. Re-download the stock firmware image in the unlikely event that you got a bad/corrupted download (also may want to try the version that doesn't have root injected). Then try again.
I'd say to try a different USB port on your pc, but since Odin is saying Pass that doesn't seem likely. Worth a shot though if the above fails (and also worth trying to Odin from a different computer).
Hang in there, you aren't hard-bricked yet! :fingers-crossed:

It has to rebuild cache everytime you flash, if you are clearing things correctly. This can take up to 10 minutes. Also, when the first samsung logo appears take finger off power button and hold the home and appropriate volume button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

The Q3 Toolbox kit saved me.
I couldn't flash into Recovery (not CWM Recovery, stock Recovery) no matter how long I held the key combo
But I eventually managed to get into Stock Recovery using the Q3 Toolbox.
Thanks for the advice people.
Holy shiiit that was nerve wracking for a while.

Bricked bootlooped s3 after recovery.

ok heres the play by play of what i did to get from a fully functioning s3 to brick.
I used Samsung GS3 toolkit and rooted did full nandroid backup installed CWM recovery 5 something then i went to install the at&t version of cynogenmod10. which seemed to be working fine but i was without the google play store on that rom so i installed from zip and i wasnt happy with how it looked so i decided to go back to my nandriod backup which i did threw recovery. when it was doing the recovery it didnt successfully restore the (system) folder. Then i rebooted and am now stuck in bootloop where it just shows the samsung logo. ive tried going into recovery and it doesnt work. It will flash with the screen saying going into recovery with blue writing on top left. then goto black till i release the buttons then it continues into bootloop. any help would be appreciated right now im installing andriod sdk to view the boot log as it boots up.

curry67 said:
ok heres the play by play of what i did to get from a fully functioning s3 to brick.
I used Samsung GS3 toolkit and rooted did full nandroid backup installed CWM recovery 5 something then i went to install the at&t version of cynogenmod10. which seemed to be working fine but i was without the google play store on that rom so i installed from zip and i wasnt happy with how it looked so i decided to go back to my nandriod backup which i did threw recovery. when it was doing the recovery it didnt successfully restore the (system) folder. Then i rebooted and am now stuck in bootloop where it just shows the samsung logo. ive tried going into recovery and it doesnt work. It will flash with the screen saying going into recovery with blue writing on top left. then goto black till i release the buttons then it continues into bootloop. any help would be appreciated right now im installing andriod sdk to view the boot log as it boots up.
Click to expand...
Click to collapse
If you can't get into recovery your only option is to reflash a stock rom via ODIN. This is assuming you can get into download mode. (Vol Up + Home + Power) Stock images can be found here: http://forum.xda-developers.com/showthread.php?t=1968625
Follow the directions in the post. Once you are done with the flash, go into recovery and factory reset, wipe dalvik and wipe cache. Reboot and you should have a fully functioning s3 again. Albeit a unrooted s3, but a function s3 nonetheless. You will have to re-root, re-install cwm (I recommend looking into TWRP instead, better recovery IMO), and then you can start flashing again. Make sure you make another Nandroid before continuing to flash. =)

root-injected stock recovery here: http://forum.xda-developers.com/showthread.php?t=1739426

oh ok i found out i wasnt releasing the buttons properly i am now in recovery mode so im guessing the route to go now is to do factory restore im wondering is there a factory image to do that or do i have to download one ive downloading one now from a source on xda

ok so i got the stock firmware and i did factory wipe with catch and dalvik. then i booted into download mode and but in odin 3.07 it isnt being recognized like the box isnt displaying. Im gonna try some different cables and maybe reboot my computer.

curry67 said:
ok so i got the stock firmware and i did factory wipe with catch and dalvik. then i booted into download mode and but in odin 3.07 it isnt being recognized like the box isnt displaying. Im gonna try some different cables and maybe reboot my computer.
Click to expand...
Click to collapse
You may not not need Odin. Load a ROM on a SD card and just flash it. Sounds like you just have a bad flash. A basic soft brick.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

yeah ill give that a go. gotta love havin these canada variants. oh yea would i flash the zip folder the mp5 file came in?

[Q] Help - Cannot do a Factory Reset on my S III - Questions

Hi All,
I just purchased a used Stock S III i747m off Ebay.
I played around with it fine for 20-30 minutes and it worked great.
I then went into settings to do a Factory reset, and the phone powered off and didn't start up again. It flashes the Samsung logo and in top left corner has "Reboot recovery" and then powers off again. I tried for 2 hours (Removing battery, etc) to get it to turn on without luck.
I then found a post that you can hold volume down + home + power to get into download mode. I tried this and it worked. It went into download mode, I then clicked volume down to restart the device, and sure enough, It now boots into Android and works fine. I restarted it a couple times to make sure it worked and it did.
Now I attempted to do a factory reset, and the EXACT same problem happens.
With doing some reading, it appears the Google Recovery is not working properly on this device, which suggests to me it was flashed back to stock by the seller but didn't flash quite right.
I want to use custom Roms on it anyways, but I'm a bit nervous of the device now.
Do you think If I flash TWRP or CWM on it using the Mskip Toolkit, and then flash a custom Rom, it will eliminate this problem? I'm thinking yes as the phone works fine when its on. It just seems to be the Stock Google Recovery is not working.
Thanks!!

bigystyle84 said:
Hi All,
I just purchased a used Stock S III i747m off Ebay.
I played around with it fine for 20-30 minutes and it worked great.
I then went into settings to do a Factory reset, and the phone powered off and didn't start up again. It flashes the Samsung logo and in top left corner has "Reboot recovery" and then powers off again. I tried for 2 hours (Removing battery, etc) to get it to turn on without luck.
I then found a post that you can hold volume down + home + power to get into download mode. I tried this and it worked. It went into download mode, I then clicked volume down to restart the device, and sure enough, It now boots into Android and works fine. I restarted it a couple times to make sure it worked and it did.
Now I attempted to do a factory reset, and the EXACT same problem happens.
With doing some reading, it appears the Google Recovery is not working properly on this device, which suggests to me it was flashed back to stock by the seller but didn't flash quite right.
I want to use custom Roms on it anyways, but I'm a bit nervous of the device now.
Do you think If I flash TWRP or CWM on it using the Mskip Toolkit, and then flash a custom Rom, it will eliminate this problem? I'm thinking yes as the phone works fine when its on. It just seems to be the Stock Google Recovery is not working.
Thanks!!
Click to expand...
Click to collapse
Have you tried the Google recovery? Volume+ power and home button?
I would suggest using Odin and download mode to put a stock rom on to guarantee that it was flashed correctly, than you can go from there. Decide if you wavy to root and install any roms or keep it stock.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
Have you tried the Google recovery? Volume+ power and home button?
I would suggest using Odin and download mode to put a stock rom on to guarantee that it was flashed correctly, than you can go from there. Decide if you wavy to root and install any roms or keep it stock.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes. I should have stated that.
The Google Recovery does not work with Volume Up + Power + Home. It attempts to enter recovery and then phone shuts off.
It has the stock rom on it now, build # and kernel confirmed. Just the Recovery doesn't seem to work.
Odd thing is - I flashed the Stock recovery back on it using Odin a few mins ago. It completed fine and booted into the phone.
I then shut the phone down, and did the volume up + power + home to get into Google Recovery, and sure enough, Phone powers off... Back to the exact same issue. It won't turn on. Just shows "reboot recovery" for a split second in top left and powers off.
I then hold volume down + power + home to enter Download mode, and simply click Volume Down to restart the device, It restarts fine.

bigystyle84 said:
Yes. I should have stated that.
The Google Recovery does not work with Volume Up + Power + Home. It attempts to enter recovery and then phone shuts off.
It has the stock rom on it now, build # and kernel confirmed. Just the Recovery doesn't seem to work.
Odd thing is - I flashed the Stock recovery back on it using Odin a few mins ago. It completed fine and booted into the phone.
I then shut the phone down, and did the volume up + power + home to get into Google Recovery, and sure enough, Phone powers off... Back to the exact same issue. It won't turn on. Just shows "reboot recovery" for a split second in top left and powers off.
I then hold volume down + power + home to enter Download mode, and simply click Volume Down to restart the device, It restarts fine.
Click to expand...
Click to collapse
I suggest you go to the Root without tripping flahs counter thread:
http://forum.xda-developers.com/showthread.php?t=1739426
Flash the stock rooted tar and using the steps given. Then try to get into stock recovery and how it goes. If it doesn't work I suggest you try to install TWRP or CWM. See if that will clear up the problem. Seems like maybe it wasn't a thorough return to stock process by OG owner

hednik said:
I suggest you go to the Root without tripping flahs counter thread:
http://forum.xda-developers.com/showthread.php?t=1739426
Flash the stock rooted tar and using the steps given. Then try to get into stock recovery and how it goes. If it doesn't work I suggest you try to install TWRP or CWM. See if that will clear up the problem. Seems like maybe it wasn't a thorough return to stock process by OG owner
Click to expand...
Click to collapse
Thank You for the help.
I will read the thread over thoroughly. Right away I have a question
I am using a Rogers S III, but the phone has been unlocked by code and I am using it with Telus.
Should I flash the Rogers or Telus files?

bigystyle84 said:
Thank You for the help.
I will read the thread over thoroughly. Right away I have a question
I am using a Rogers S III, but the phone has been unlocked by code and I am using it with Telus.
Should I flash the Rogers or Telus files?
Click to expand...
Click to collapse
Odin flash wont really matter because phone will stay unlocked. Flash for whatever carrier you are using it on.

hednik said:
I suggest you go to the Root without tripping flahs counter thread:
http://forum.xda-developers.com/showthread.php?t=1739426
Flash the stock rooted tar and using the steps given. Then try to get into stock recovery and how it goes. If it doesn't work I suggest you try to install TWRP or CWM. See if that will clear up the problem. Seems like maybe it wasn't a thorough return to stock process by OG owner
Click to expand...
Click to collapse
hednik said:
Odin flash wont really matter because phone will stay unlocked. Flash for whatever carrier you are using it on.
Click to expand...
Click to collapse
Really appreciate the help.
Looks simple enough and I've used Odin on a Note II before.
Only question - I see quite a few people stated they need to wipe data and cache after flashing this to avoid a boot loop. Are they doing this within Google Recovery? Wouldn't wiping data after a this flash erase it? (not cache, but data)
Thanks again, I will give this a go in a couple hours when I'm back home. Hope it resolves my issues.

bigystyle84 said:
Really appreciate the help.
Looks simple enough and I've used Odin on a Note II before.
Only question - I see quite a few people stated they need to wipe data and cache after flashing this to avoid a boot loop. Are they doing this within Google Recovery? Wouldn't wiping data after a this flash erase it? (not cache, but data)
Thanks again, I will give this a go in a couple hours when I'm back home. Hope it resolves my issues.
Click to expand...
Click to collapse
You will just do a factory reset in stock recovery to get it back to out of the box stock to remove any possible conflicts. This is especially helpful if you are going from a 4.1 ROM back to a 4.0 stock ROM. Wiping data means removing everything in your /data folder. You can find the /data folder using a root file explorer like root explorer or es file explorer and see what you have stored in there or might want to backup on an ext SC card. I.E. pictures, videos. It will make the phone as if no one has ever used it before and a clean slate.

hednik said:
You will just do a factory reset in stock recovery to get it back to out of the box stock to remove any possible conflicts. This is especially helpful if you are going from a 4.1 ROM back to a 4.0 stock ROM. Wiping data means removing everything in your /data folder. You can find the /data folder using a root file explorer like root explorer or es file explorer and see what you have stored in there or might want to backup on an ext SC card. I.E. pictures, videos. It will make the phone as if no one has ever used it before and a clean slate.
Click to expand...
Click to collapse
Awesome.
It makes sense. I guess I never truly knew what Factory reset means within Recovery. (I've flashed tons of Roms before on other phones but always did Factory Reset before flashing a rom, so I was thinking it an erasing tool)
Thanks. Will report back in a few hours once I get home and attempt this.

I have a feeling the recovery is messed up. The one selling phone took out non stock recovery, but didn't flash stock recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium

I just wanted to report back that flashing using the non trip thread above fixed my issues. Everything is back to working including the stock recovery. Thank you so much!

[Q] Galaxy S3 doesn't boot

I have Galaxy S3 on which I have CyanogenMod. I was on vacation in Poland last summer and I got there my Rogers Galaxy S3 phone unlocked and polish language CyanogenMod ver 10.0 was installed . It worked fine since. Recently, I installed few game for my grandson. Right after I found that it took longer time to boot a phone. Then I started to get a message after rebooting, "System process didn't start" with option to click "Wait" or "OK". When I clicked OK phone was slowly booting and finally was fully operational. Every new reboot took longer and longer with the same message, "system process didn't start" click "wait" or "ok".
Finally it stopped to boot. When I power on a phone it starts booting and get to same message as before. I click "wait" and nothing happen, or I click "ok" and still nothing happen. Then phone reboots itself and keep doing it.... Doesn't boot anymore to application.
What I can try to do to fix it? I am pretty new to this "rooting" "Odin'...etc so if you have an advice please communicate it as simply ans possible.
Any help appreciated
Thank you

Boot into recovery and flash a newversion or same version of CM 10 or CM10.1 (Either one is good or you could pick a whole new ROM up to you). Make sure you follow the instruction of the ROMs thread for how to install. To get to recovery you hold the volume up + home button + power untill it boots to recovery and from there follow ROM instructions.

polanki55 said:
I have Galaxy S3 on which I have CyanogenMod. I was on vacation in Poland last summer and I got there my Rogers Galaxy S3 phone unlocked and polish language CyanogenMod ver 10.0 was installed . It worked fine since. Recently, I installed few game for my grandson. Right after I found that it took longer time to boot a phone. Then I started to get a message after rebooting, "System process didn't start" with option to click "Wait" or "OK". When I clicked OK phone was slowly booting and finally was fully operational. Every new reboot took longer and longer with the same message, "system process didn't start" click "wait" or "ok".
Finally it stopped to boot. When I power on a phone it starts booting and get to same message as before. I click "wait" and nothing happen, or I click "ok" and still nothing happen. Then phone reboots itself and keep doing it.... Doesn't boot anymore to application.
What I can try to do to fix it? I am pretty new to this "rooting" "Odin'...etc so if you have an advice please communicate it as simply ans possible.
Any help appreciated
Thank you
Click to expand...
Click to collapse
Before you install any ROM be sure to do a factory/reset, wipe dalvik cache, wipe cache partition and format system, and don't worry about doing everything twice, especially if you are coming from a TW ROM and going to a CM type ROM. If you don't start off with a clean slate you may have some "ghosts" left over.

andy442 said:
Before you install any ROM be sure to do a factory/reset, wipe dalvik cache, wipe cache partition and format system, and don't worry about doing everything twice, especially if you are coming from a TW ROM and going to a CM type ROM. If you don't start off with a clean slate you may have some "ghosts" left over.
Click to expand...
Click to collapse
er
How I can do factory reset if I can't boot to anything except a download mode? Do I need to install new ROM first and then do factory reset or there is other way to get to factory reset option without loading new ROM?

polanki55 said:
er
How I can do factory reset if I can't boot to anything except a download mode? Do I need to install new ROM first and then do factory reset or there is other way to get to factory reset option without loading new ROM?
Click to expand...
Click to collapse
If you can't into recovery and download mode is your only option, use odin to flash stock ROM on your phone.
Sent from my SAMSUNG-SGH-I747 using xda premium

polanki55 said:
er
How I can do factory reset if I can't boot to anything except a download mode? Do I need to install new ROM first and then do factory reset or there is other way to get to factory reset option without loading new ROM?
Click to expand...
Click to collapse
You can factory reset from recovery.

Pbwizkid said:
You can factory reset from recovery.
Click to expand...
Click to collapse
He said he can't get into recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium

Possible Fix
1. Go here - > http://forum.xda-developers.com/showthread.php?t=1968625 -> install the correct stock firmware for your carrier
2. Go here -> http://forum.xda-developers.com/showthread.php?t=1722686 -> download ODIN.. and READ THE INSTRUCTIONS!!!
3. Use ODIN to put the STOCK ROM back onto your phone. It takes a little while to do it.. and first boot can take a while as well.
4. Go here -> http://autoroot.chainfire.eu/#odin -> download the correct version of CF autoroot for your phone
5. Use ODIN to install CF auto root the same way you installed the STOCK ROM
6. Go to the google play store and download ROM manager
7 - In ROM manager Installed CWM recovery
8-> enjoy a rooted phone and flash custom roms if you like!

[Q] Fixboot.tar Install/backscreen on reboot

I have a Samsung Galaxy S3 SGH-I747 (AT&T) that I updated OTA to 4.1.1 a while back. I just decided to root the phone using Odin3 V3.04 and clockworkmod.tar. I tried using clockworkmod at first but couldn't get the phone to go into CWM recovery mode. It just went into stock recovery instead. Reading further, I was told that I need to flash fixboot.tar first, then clockworkmod.tar, then flash CWM_SuperUser_3.0.7.zip file in recovery mode. When I used odin to flash fixboot.tar and rebooted, it boots the Galaxy S3 logo, at&t chime, then goes black with Amber light. It will not boot fully. I then used Odin to flash clockworkmod.tar, rebooted and it also went to blackscreen.I was then able to go into recovery mode and flash the Superuser zip file and reboot but I'm still getting the black screen. What did the fixboot.tar file do to my phone?? Can I reverse this without flashing a whole new rom? I have search the forum for severalhours now with no luck. Any help would be great.

where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates

xBeerdroiDx said:
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
Click to expand...
Click to collapse
I got it from this link - http://rootgalaxys3iii.com/root-at-t-galaxy-s3/
I am aware of the process you mentioned, but it would not work. It just kept going into standard recovery mode instead of custom recovery so I could never root from there. Thats when I came across this link and thought I needed to flash fixboot.tar first as it states. It did work! I was able to flash clockworkmod.tar and then root the phone, but what good does that do now that my phone is hosed at the blackscreen...There were two sites that said to use this fixboot method. I should have known better...
I just read your thred. Looks like my problem was letting the phone reboot. Is there any way to reverse the fixboot.tar I used? Maybe there is a 4.1.1 boot.tar that can put things back as they were?

via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.

xBeerdroiDx said:
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.

OpusxXx said:
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
Click to expand...
Click to collapse
Well, since I got no response, I did what you said and deleted everything. I still have the same problem. Phone boots to Samsung logo, does jingle and geos to blackscreen with blue light.
Back to my original question. I used the fixboot.tar and it jacked my phone where it only boots to blackscreen with blue light. Is there a fix for this???