Database Develop

Firmware flash will not unbrick phone?

I used 2.3.5 JVT (+root) for some weeks perfectly fine on my Galaxy S I9000, though a bit laggy due to too many apps.
Today I rebooted the phone and got stuck in a boot loop. Never had that before.
I went into CWM recovery, wiped cache and did factory reset. Did not resolve a thing.
Then I flashed the whole phone again with the 2.3.5 JVT and it did not help either.
What can I do? The phone goes into download and recovery mode perfectly fine, so guess it's OK. I see Odin has an Option "EFS Clear". Would that help?

I would not tick that option. What happened when you flashed stock JVT with Odin? Bootloop?

Yes I use the stock firmware, that is firmware from sammobile.com (samfirmware.com). No fancy mods.
Tried with and without root. Both give me boot loops.

If you properly used Odin with the 3 files, pit, and repartition ticked, and you get bootloops after that then it goes beyond my experience. Maybe corrupted stock rom download? Download again stock JVS or JVT (change the one that you used before).

ok tried too other firmwares. still bootloops.
then i tried stock 2.3.3 and it went past boot screen. but it said UIDs inconsistent, need to wipe data partition. so i wiped data partition. but still same error.
seems like something strange is going on here. i'm always using 512 pit file and flashing with repartition checked!

that happened to me ,i just plugged in my charger and voodoo lagfix spoke then phone turned on apps were transparent set launcher default went into bootloop tried nandroid restore didnt work .eventually flashed 10.2 resurrection xxjvq worked a treat
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
thers a video on tube by totallydubbedhd or puggerdug shows u how but u probably already know ,hope it helps u

try flashing 2.3.4 XXJVP. this ROM worked for me while I went into a similar bootloop like yours once...while in 2.3.5 XXJVS. Then I reflashed JVS and it worked just fine.

I had similar and had to flash a stock rom to get it to boot. Then just root again...Took a while to figure this out. Very frustrating at the time!

.
OK tried a couple of other roms with no success. I read in another thread that someone had exactly the same problem and had Samsung fix it.
Now I am having a problem wiping my SDcard. The CWM backups are on the SDcard, right? So why can I still select them if I wipe the SDcard in Recovery?

OK, Samsung replaced the motherboard of the phone (warranty).
It's working again now.
So to everybody that is having the same problem, it is a hardware problem, most likely. But you will need to have tried everything else that could fix it beforehand, of course.

cdbee said:
OK, Samsung replaced the motherboard of the phone (warranty).
It's working again now.
So to everybody that is having the same problem, it is a hardware problem, most likely. But you will need to have tried everything else that could fix it beforehand, of course.
Click to expand...
Click to collapse
but warranty doesn't cover rooted/hacked phones lol?

HelloThere1 said:
but warranty doesn't cover rooted/hacked phones lol?
Click to expand...
Click to collapse
Yes, I resetted everything to stock.

[Q] Stuck in bootloop...need help

So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?

GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.

Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.

And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium

korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.

Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate

Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.

Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks

Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse

HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium

... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.

Help! Meday!! Phone Reboots into cwm

Hi All,
I am in desperate need of help.
I have a nexus s. rooted, with cyanogenmod kernel and slimbean rom.
My friend has a galaxy s1 that had unrooted froyo.
A friend of his rooted it, and put gingerbread on it. I wanted to put slimbean on it for him.
I did so.
Except, that his mobile network wouldnt connect.
I googled, and found that this could be because the kernel is not compatible with the rom.
So I downloaded cyanogenmod kernel and flashed.
But this didnt work, because I think the download was corrupted or something.
I tried to re boot into clockwork, but it just got stock on the first loading screen.
Since then I have tried everything and have been googling for hours... I dont know what to do. I have tried so many different things.
Please can some guru help me figure out what to do?
My friend is pissed as hell at me, I told him it will be painless quick and easy. Thats how it was for me and i assumed same for him.
PLEASE!! I need HELP!! :'(
Edit: I reflashed semaphore and it now goes into cwm. But now when I flash the rom and reboot it, it just reboots automatically into cwm again. Anyone know where to go from here?
Thanks in advance,
Zeddicus

zeddicus0 said:
Edit: I reflashed semaphore and it now goes into cwm. But now when I flash the rom and reboot it, it just reboots automatically into cwm again. Anyone know where to go from here?
Thanks in advance,
Zeddicus
Click to expand...
Click to collapse
It appears to be a bootloop. That means flashing messed with boot partition and you have to reflash boot. Is this phone i9000 or i9001?
Search for similar topics like: http://forum.xda-developers.com/showthread.php?t=1590747
If you can get to CWM or download mode nothing bad happend - you can repair everything, however it would be wise if you had backup of previous, working ROM

Calm down its fixable first you try to fix it without Odin by
- flashing slim bean again don't forget full wipe flash i9000.zip twice the first time it will reboot half way through at least it did for me
-then pull out the battery and boot into cwm
- flash both slim bean files
- this should get the phone starting again after that to get network working flash this file in cwm http://www.mediafire.com/?fbgxblhbip7bkuv it should get network running credit goes to pwneman for that
Let me know how it goes
Sent from my GT-I9000

First of all, thank u guys very much for helping me.
right now i am having an even bigger problem.
all of a sudden sometime between my flashing, i started getting this error when trying to mount the external card from cwm
unable to write to ums lunfile (no such file or directory)
so cant flash anything from phone now...
its an i9000

zeddicus0 said:
First of all, thank u guys very much for helping me.
right now i am having an even bigger problem.
all of a sudden sometime between my flashing, i started getting this error when trying to mount the external card from cwm
unable to write to ums lunfile (no such file or directory)
so cant flash anything from phone now...
its an i9000
Click to expand...
Click to collapse
Try to format your sdcard in fat32 filesystem (through Windows/CWM or any other various ways if this won't work)
Also try other sdcard...
If formatting card doesn't fix the problem try to reflash CWM via Odin in Download mode.

ok i did a hard reset and left batt out for a good few min and got the sdcard back again.
i followed the steps u said latrop and it didnt fix it... still booted back into cwm...
since i now have the sdcard back i am making a backup zip file of it just in case lol

@divibyzero
i followed that post but it didnt fix the problem

OK you will have to flash with Odin I'll get back to you with instructions
Sent from my GT-I9000
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
OK follow the in this website and use the new sourceforge mirror http://www.darkyrom.com/index.php?threads/odin-darkyrom-10-2-resurrection-gti9000.4272/
Make sure you have the Samsung drivers installed http://forum.xda-developers.com/showthread.php?t=961959/ then once that's done phone should start up if it does follow my previous instructions
Sent from my Awesome GT-I9000 using Slim Bean

Wait, before you odin flash:
Let me get this straight, your rom .zip is on your external sd card? it has to be in your internal sd card.
From the recovery main menu, go to mounts & storage. From there, plug in your phone to your computer and select "Mount internal USB storage."
You'll be able to then copy the rom file into your internal sd card. While you're at it, I'd recommend X-Bean, as it's currently faster and more stable than SlimBean. Then, unmount your phone and return to the recovery menu and select install zip and choose the file you've just copied.
Please let me know how it goes.

@kngroo
thats what i did.. ive flashed tons of roms and kernels before on my nexus s...
its this galaxy s 1 that isnt working for some reason... it was meant to be a quick and painless proceedure which has turned into a nightmare
gonna probably have to format the sdcard now :*(

Hi All,
I wanna give a SERIOUS thank you to latrop.
This guy is a freaking legend. He just sat with me for almost 2 hours helping me sort out the phone. We did almost everything you can think of and then some... But ultimately it was latrops great experience and knowledge that helped save my ass here...
Phone is running full on slimbean rom with great reception etc.
Latrop... you are a legend!!!

Just wipe/factory reset and wipe cache
its work for me and maybe it would work with you too

[Q] unable to install stock rom

After Rooting n using safe kernel, I was on RocketRom V3 and last week i updated to Ultimate Rom 5.1 JB and phone was working awasome, and then i tried to install awasome Beats throught CWM but i was not able to install it. then i again tried to install photo sphere through CWM but again same problem, when i select zip from SDCARd, after selecting nothing happens, so i thought CWM is corrupted and then i tried to restore the backup (rocketrom v3) but same thing happened, unable to even restore the backup so i was sure there's problem with CWM.
So i decided to to flash stock rom via PC ODIN and i installed stock rom N7000XXLPT, build number IML74K.XXLPY , android ver. 4.0.3.
after flashing, phone got stuck on samsung screen so i rebooted into recovery and wiped data factory n cache (i knw i was not supposed to do this but thr was no other option) and after wiping phone booted normally but i got many errors... unfortunately settings has stopped, unfortunately file manager has stopped, unfortunately software update has stopped has stopped etc etc.....
then i tried to install another stock rom (latest november) but now i m not even able to flash rom through PC ODin, FAIL... FAIL error with tht red color ...
So what could be done to get back to normal stock rom ?? Plzzz Help

is it stuck on factoryfs ?
if so, theres a big chance that doing the wipe caused the brickbug and only re-partition will fix it and bring it back to life.
before doing that, try to flash stock GB and see if it boots, if so, boot into recovery and do the wipes there, stock GB kernels are safe from the brickbug.

azzledazzle said:
is it stuck on factoryfs ?
if so, theres a big chance that doing the wipe caused the brickbug and only re-partition will fix it and bring it back to life.
before doing that, try to flash stock GB and see if it boots, if so, boot into recovery and do the wipes there, stock GB kernels are safe from the brickbug.
Click to expand...
Click to collapse
YEs, it stuck on factoryfs and the FAIL msg appears with REd background.
phone boots with many FCs and i mnot able to see any SDCARD, so its EMMC brick bug,
i guess i ll need to use PIT file method to revive from a MMC_CAP_ERASE brick

nitinbarve said:
YEs, it stuck on factoryfs and the FAIL msg appears with REd background.
phone boots with many FCs and i mnot able to see any SDCARD, so its EMMC brick bug,
i guess i ll need to use PIT file method to revive from a MMC_CAP_ERASE brick
Click to expand...
Click to collapse
Confirmed. Apologies. Notes once you repartition, there's a chance you won't be able to run full Roms with a larger file size due to damaged sections, you'll likely face fc's and freezes. After repartition look to cm based Roms as they take up less space and should work ok.
Sent from my GT-N7000 using xda premium

help please needed

my sons sg i9000 was rooted with a custom rom but then started playing up, now when i've wiped it and tried put new rom on it, all it does it force crash everything that was existing on his phone, so it looks like it is not wiping the phone anymore for some reason, i've tried flashing rom by odin but still the same effect, is there anything out there that totally wipes the phone for sure and then will allow me to put phone back to stock and then reroot.
many thanks if anyone can help as i am totally stuck now and my son is without his phone.:fingers-crossed:

If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?

rodman01 said:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
Click to expand...
Click to collapse
thank you for the advise i will try and see what i can do

still having trouble with the phone, every time i reflash stock rom with odin it keeps starting up but then i have a lot of force close box popping up saying about all his old apps and and setting force closing and then when it get to the start up wizard it says it has forced closed and then can not go any further, this is why i cant understand why when i wipe all data and system it is not wiping it for some reason,im waiting on a download recovery for it but if anyone can understand what i mean and no a fix i will be most grateful as i have spent many hours now searching through xda for a answer and can not find any.:fingers-crossed::fingers-crossed:

Could you give us some more information? What device do you have? And which ROMs did you try to flash? Which stock and which custom ROMS? And when do have the problems? After reboot from flashed stock rom or after flashing the custom rom? I think the stock rom you try to flash does not fit to your device?

i have tried the stock rom from samfirmware and my device is a galaxy s i9000, the custom rom was a old gingerbread rom, the problem comes when i have flashed the new stock rom with odin, it flashes with odin not a problem but then when it boots up and starts to go through the first 6 or 7 steps of the phones steps, ie ( keyboard use, packed data settings, wifi on or off and so on) it keeps popping up little dialog boxes saying sorry google play is not working force close and goes through a whole load of stuff saying the same thing for them all, hope this helps a little but is hard to describe

I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...

rodman01 said:
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
Click to expand...
Click to collapse
ok thank you i will try that,

thank you for all the help today but think the phone is knackered nothing will work anymore on it nothing will boot up properly :crying:

no problem and you welcome...better would have been if my proposals had worked...but perhaps you are right and there is a hardware defect or something else...perhaps even a fluid defect....or it is only stressed for today and tomorrow all is fine again ! So head up, and don't give up.

Hope you flashed Stock GB ROM with pit file and Re-partition ticked