Related
i bought this Defy+ just a couple of days ago and i was trying to get CM7. I struggled to root it but i achieved it. I wiped and did all the procedure before installing it, but i didn't had enough space on my SD, so i rebooted and booted like a brand new defy, going through the Blur config and everything... So i went to Recovery again, but at this time i forgot to do the wiping - which, i guess, led to a brick.
So i managed to get a .sbf to flash it.. What i didn't realized is that the .sbf was a custom, so i guess this ****ed up my phone even more. And so i went on trying to rescue my phone but this time i couldn't complete the flashing process, i wasn't able to perform a downgrade - i guess. After this, i got a non-rootable .sbf and began the flashing. The process got stuck on some message at 0%, then i disconnected the phone.
When i was able to download a stock firmware, from the .sbf thread, the phone wouldn't reboot when RSD asked, it didn't turn on again. So i tried to re-flash it, same .sbf and now i'm stuck with this situation: the pc is not recognizing my phone, i have a black screen - not even the Bootloader error screen is appearing and i'm here, begging, for someone to help me. is it dead? can i get it back?
HELP, PLZ
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Auris 1.6 vvt-i said:
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Click to expand...
Click to collapse
it doesn't turn on, but i guess it does have battery, i can see the led on when i connect it to the pc
Led is always on when connected to the PC - it means nothing. If it doesn't turn on, then your battery's dead. Find someone who has the same phone and can charge it for you.
I think there is no problem, but you flash older firmware, which is probably due to the 7 bootloader does not go up.
try to be flash with one of these (2.3.6 GB)
http://forum.xda-developers.com/showthread.php?t=966537
begins with the 139-ended, if it is not going to work with the 188-ended
Sorry for bad English
"As of today there is no a full SBF** for the Defy+ (found here).
This full SBF is a new CG Version**, with Android 2.3.6. You wont be able to go back to your Stock Defy+ Rom, but at least you wont kill it if something goes wrong."
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
caiowatanabe said:
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
Click to expand...
Click to collapse
If it gets past the red m and just keeps playing the android animation then simply pull battery hold volume - put battery in and keep volume - held when you get the android and the triangle press volume + and - and wipe all, should boot, unfortunately you've just flashed the un root able sbf and are stuck on moto standard
teamwork makes the dream work
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
caiowatanabe said:
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
Click to expand...
Click to collapse
Feel free to keep an eye on the dev section for the bl7 rooting thread you may get lucky
teamwork makes the dream work
So I wanted to install a new custom ROM and I all ready had one. It wasn't the first time. So, like usual I download the files needed and put them on my phone, boot into recovery and flash them ( but I didn't factory reset or anything because with the ROM I had I didn't need to for it to work I could just fix the not responding errors) Then i go to reboot and I wait. Nothing, nothing at all. Now I try to remove the battery and try again and now none of my buttons do ANYTHING the only sign of life there is, is when I remove the battery and plug my phone to a usb cable and attempt to charge it, all that happens is a red LED comes up. It's probably due to one of the things i installed on my phone that flashes a red LED when battery is low. Please help me with this. My last resort is to give my phone to rogers for them to fix it because I still have a warranty.
Specs: S3 i1747M Rogers
I had aokp jellybean 4.3 as my ROM
I do have a nandroid but its on my phone's sd card
Thank you for your time and I hope we get this to work.
Can you get into recovery mode or download mode?
FoxTrotz said:
Can you get into recovery mode or download mode?
Click to expand...
Click to collapse
No there's litteraly nothing I can do. pressing all the buttons does absolutely nothing. Just stays black and no signs of life
bump. I need help fast with this.
Not sure exactly what you did but I hate to say its sounds hard bricked. Mine was exactly the same, with only the red light coming on for about a minute when cord was plugged in with no battery. I screwed mine up with a file I grabbed without reading properly what it was for and in my haste I installed it. After I rebooted it never came back until I got it back from warranty with a replaced control board. Im guessing they didnt even check the internal memory or they would haven known what a dumbass i was since i voided the warranty doing stuff i had done before that mistake. Glad I had made a nandroid before i pooched it so i didnt lose anything after i got it back.
Yeah after some research I found out I hardbricked it but this isn't the first time and I had a warranty for both( different phones btw )times so I guess I'll just send it out. :c
could just be out of juice, leave it on the charger for around an hour then try and go into download mode.
So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.
Hello,
My S4 Mini I9192 Suddenly died while charging overnight and now no response whatsoever. Only thing I know is that I am in 9008 mode.
QFIL Can see the phone, but i need a firehose programmer and some XML files. Can anyone tell me where I can find those files? Thanks in advance.
kasa ssg said:
Hello,
My S4 Mini I9192 Suddenly died while charging overnight and now no response whatsoever. Only thing I know is that I am in 9008 mode.
QFIL Can see the phone, but i need a firehose programmer and some XML files. Can anyone tell me where I can find those files? Thanks in advance.
Click to expand...
Click to collapse
I read a little about using qfil some time ago, and even if you can find the files I don't think it will work on Samsung phones, though I stopped researching when I read the following link (luckily my phone was not bricked, so I didn't need to), he says QFIL won't work as Samsung do not use the default options (well that was my understanding)
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I think the only option is take it to a repair shop for jtag or new emmc/motherboard, but I could be wrong. (or buy an old phone with cracked screen and use the motherboard from that)
While I was searching the web for files the phone was connected to the pc. It didn't show any signs of life until a battery icon suddenly popped on the screen. I was even able to boot into download mode, but when I went to recovery it said "No Command". Odin recognized the device, I flashed stock, but when i tried to boot it up, It was in a bootloop. I tried flashing many times with no success, still bootloops. Even after the flashing the recovery was in "No Command" mode. Yesterday i tried to flash it for the last time with the same rom, and this time it just booted to the Samsung logo and then turned off. Now I'm back to the 9008 mode. I tried the sdcard method with a debrick.img, no success. Any idea what might be wrong with the phone?
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
kasa ssg said:
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
Click to expand...
Click to collapse
I can't help as I have different model but yakapa40 can as usual, if nobody else has pit for you
https://www.sammobile.com/forum/showthread.php?t=30208
Exact Same Case
kasa ssg said:
While I was searching the web for files the phone was connected to the pc. It didn't show any signs of life until a battery icon suddenly popped on the screen. I was even able to boot into download mode, but when I went to recovery it said "No Command". Odin recognized the device, I flashed stock, but when i tried to boot it up, It was in a bootloop. I tried flashing many times with no success, still bootloops. Even after the flashing the recovery was in "No Command" mode. Yesterday i tried to flash it for the last time with the same rom, and this time it just booted to the Samsung logo and then turned off. Now I'm back to the 9008 mode. I tried the sdcard method with a debrick.img, no success. Any idea what might be wrong with the phone?
Click to expand...
Click to collapse
kasa ssg said:
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
Click to expand...
Click to collapse
Hey, Hi.
So same thing happened with me, I was on Stock Kitkat S4 mini i9192, phone froze while using and never booted up. But then I left it connected to laptop and it vibrated and showed the battery icon and I got every problem same as you, like no command, boot loop, and again phone went into QHS_DLoad mode.
I want to know that how did you manage to get back into the Odin Download mode again because since the last time my phone didn't show any sign of life and I also want to know if you were able to fix it? I have not tried debrick.img yet. Please help to fix my phone :laugh:
geek_hsk said:
Hey, Hi.
So same thing happened with me, I was on Stock Kitkat S4 mini i9192, phone froze while using and never booted up. But then I left it connected to laptop and it vibrated and showed the battery icon and I got every problem same as you, like no command, boot loop, and again phone went into QHS_DLoad mode.
I want to know that how did you manage to get back into the Odin Download mode again because since the last time my phone didn't show any sign of life and I also want to know if you were able to fix it? I have not tried debrick.img yet. Please help to fix my phone :laugh:
Click to expand...
Click to collapse
Well, sorry to disappoint you, but I found out that the flash memory of the phone was dead. After all I've done the phone just turned off, and never turned on again. I also found out that this phone is known for dying memory chips.
Howdy. Does anybody know what happened here and how to fix it???
Claudio4780 said:
Howdy. Does anybody know what happened here and how to fix it???
Click to expand...
Click to collapse
Just press power button when rebootnow is highlighted by using volume buttons.....
HemanthJabalpuri said:
Just press power button when rebootnow is highlighted by using volume buttons.....
Click to expand...
Click to collapse
Thanks, tried it. But it just starts in Recovery Modus or Bootloader Modus
Claudio4780 said:
Thanks, tried it. But it just starts in Recovery Modus or Bootloader Modus
Click to expand...
Click to collapse
Flash TWRP and flash custom rom like you did before.....
And If you want stock rom then flash my stockrom lite in twrp
Thanks a lot for replying
kasa ssg said:
Well, sorry to disappoint you, but I found out that the flash memory of the phone was dead. After all I've done the phone just turned off, and never turned on again. I also found out that this phone is known for dying memory chips.
Click to expand...
Click to collapse
Thank you, I was thinking that once the battery is empty and when you connect it via USB mode, it reboots itself, so maybe that is why you got the second chance with it but when I got the phone turned on, I charged it up to 90 percent and now my battery is not draining. Previously my phone died when it was having around 35% of charge which was drained in 20 days. So I have avery strong reason to believe that its just a corrupt bootloader and I have to flash using pit.
geek_hsk said:
Thank you, I was thinking that once the battery is empty and when you connect it via USB mode, it reboots itself, so maybe that is why you got the second chance with it but when I got the phone turned on, I charged it up to 90 percent and now my battery is not draining. Previously my phone died when it was having around 35% of charge which was drained in 20 days. So I have avery strong reason to believe that its just a corrupt bootloader and I have to flash using pit.
Click to expand...
Click to collapse
I did try flashing with .pit, but to no avail. Actuall, it recalled to me right know, god knows how I managed to flash stock firmware., BUT, everytime the phone started booting, the samsung loading logo would become slowly more and more distorted, until all my screen became pink with white stripes. It was strange.