Develop Bugs

[Q] Chainfire 3D brick :(

Hello guys, i need serious help with my Samsung Galaxy S3, I just rooted today, and everything was working fine.
I decided to download chainfire 3d, thought i'd enable some unstable games to run, but quite the opposite my phone is now BRICKED.
I tried re-flashing my rom with ODIN, but to no help, the phone remains bricked.
I read some tutorials how to flash using the 'transfer to sd card from PC' rom. But there is another problem..
My pc doens't recognize my phone completely(icon doesn't show in My computer - winows 732bit).
Now im stuck at the Samsung logo, with no other options but hope someone here can help.. ..
Ps; I tried cleaning the cache and dalvik cache from CW mode. Anything else im missing out??..

When you Odin did you wipe data / factory reset after or before? Usually when you Odin and didn't wipe data in recovery mode you will get stuck at the Samsung boot up. So try going back to recovery and do a factory reset /wipe data and see if it boots up pass samsung logo.

teambestyrandy said:
When you Odin did you wipe data / factory reset after or before? Usually when you Odin and didn't wipe data in recovery mode you will get stuck at the Samsung boot up. So try going back to recovery and do a factory reset /wipe data and see if it boots up pass samsung logo.
Click to expand...
Click to collapse
In fact i dont even know if I'm doing it correctly, i only flash one file, the one i ROOTED with. its in the PDA location. I will try to wipe before and after..
Edit: I used ODIN and then i wiped data/factory reset from CW, and still stuck at the boot logo
I also got this error on my PC, MTP USB device did not install correctly. I downloaded the drivers from the official t-mobile support page, so i don't think its the Pc's fault. .
Any ideas?

knight26 said:
In fact i dont even know if I'm doing it correctly, i only flash one file, the one i ROOTED with. its in the PDA location. I will try to wipe before and after..
Click to expand...
Click to collapse
Try wiping data and see if it works. I it should pass the Samsung logo boot up.

teambestyrandy said:
Try wiping data and see if it works. I it should pass the Samsung logo boot up.
Click to expand...
Click to collapse
Doesn't work.
Should i try to format my /data, /sdcard, etc, from the CW menu?.
Is there a risk in doing that?, I dont mind losing my data as long i get the phone back running.
EDIT: I flashed Odin, and it seems to be working now, I'm only left to wait for the phone to pass the bootloop.
what I had forgotten was to flash the stock firmware after i do the CW mode. Lets hope for best, I'll edit this post if it works.
EDIT 2: IT WORKS!. I'd post links to the stock firmwares, but not sure if that is allowed on the site. Anyway just google galaxy s3 stock firmware download.
writing this response to the other people in need of the same help

[Q] CM10 m2 Encryption Issue

Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?

fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app

[Q] Friend did a bad file flash, Hard bricked phone

Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.

Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.

Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...

This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!

topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.

Help possibly?
Can you get it into download mode and just use Odin to flash it?

Note 2 softbricked, TWRP recovery says (system/data/EFS/usb/data etc...) cant mount!

Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.

the9kill said:
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
Click to expand...
Click to collapse
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
P.s If anyone is interested in looking for this phones Stock ROM I found it here:
samsung-updates.com/device/?id=GT-N7100 (Select the one for your country/region)

the9kill said:
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
Click to expand...
Click to collapse
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers

the9kill said:
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
Click to expand...
Click to collapse
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi again,
Yes, I can fully appreciate why you would say that, from what I see ODIN is very straight forward and unless you do something totally (silly), like jiggle the cable or do something midway it should not hardbrick. Therefore it makes sense you suggesting the cable is faulty, but it seemed to copy over 32GB of data seemlessly in one go. Although i will change the cable as a precaution as there is a slight cut.
When I say hardbricked, I mean hardbricked as in no recovery and no download mode, and no display whatsoever no matter what you do.
[UPDATE] Okay, the strangest thing happened. After a whole day of charging the phone, sometimes trying it on for luck, hoping something would happen. I went to the doctors and came back, and oddly enough the screen had life!!! Yes, this gets bizarre, I repeat a clearly hardbricked phone resurrected back to life with a screen showing ("A firmware upgrade encountered an error, please retry with kies") or something like that, so overjoyed with this sign of life I carefully put it into download mode and its now waiting.... But before I try Odin again, I think I will take a leaf from Ceomavericks suggestion and get a brand new cable from another samsung phone and use that this time.
By the way Ceomaverick, last time i just tried to flash to stock rom using AP, and kept autorebook and Ftime checked.
This time I am seeing on a thread to do the following, please advise (given that my TWRP doesnt mount anything at all).
It says do this: from: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
Open ODIN, and check Re-Partition, Nand Erase All, Auto Reboot and F. Reset Time. Uncheck all other boxes. Click the PIT button and select the PIT file appropriate for your device (16GB or 32GB). Click the PDA file and choose the Stock Rom you downloaded. Press start and wait.
File Type: rar PIT_t03g_0907_16GB.rar - [Click for QR Code] (899 Bytes, 84 views)
File Type: zip BOOTLOADER_N7100.zip - [Click for QR Code] (1.03 MB, 75 views)
click start.
If everything goes well, the process should succeed and the phone should reboot. Don't wait for the phone to boot into android. Immediatly boot into recovery, factory reset the phone and wipe cache. Reboot to Android.
Now, if everything worked well, your phone should boot into Android. And then sort out the sleep of death issue.
I think I will wait for some feedback before doing this and just enjoy that my phone is mysteriously back in download mode, perhaps a hardware issue......
Another thread reading http://www.theandroidsoul.com/unbrick-restore-samsung-galaxy-note-2-gt-n7100/
Cheers

UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)

the9kill said:
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
Click to expand...
Click to collapse
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life

the9kill said:
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
Click to expand...
Click to collapse
If the firmware from other region fails, then find pit file for 16gb to flash. If that too fails, I think your phone needs hardware repair.
Sent from my GT-N7100 using Tapatalk

Please help me find Kernel for S3 T999

I`ve finally managed to mess up my kernel after flashing numerous roms on my galaxy s3 T999. The problem is that my device has bootlooped and I can`t enter recovery mode (due to messed up kernel) and I don`t know where to find a Kernel which can be flashed with Odin.
Can someone please share a link to any kernel for s3 T-999 (it must be in .Tar form please) so that I can fix my phone. Thanks in advance.

I suggest flashing the latest stock ROM via Odin to solve the bootloop issue.

audit13 said:
I suggest flashing the latest stock ROM via Odin to solve the bootloop issue.
Click to expand...
Click to collapse
Thanks for trying to help. The problem is that I can`t find any other S3 rom (in Tar form so that it can be flashed with Odin) other than T999UVUEOH1 (Jelly Bean 4.3). It bootloops over & over no matter how many times I flash it (I think it`s because I cannot wipe cache due to no recovery).

You used ROMs from sammobile.com or updato.com?

audit13 said:
You used ROMs from sammobile.com or updato.com?
Click to expand...
Click to collapse
I tried one ROM from sammobile and another from androidfilehost (uploaded by a developer). Neither of them work because Odin gets stuck at Setup connection. I saw a video in which a guy fixed it by cleaning cache & delvik cache. This is the main issue because my kernel is messed up and I can`t clean cache because the phone just won`t go into recovery mode (neither custom recovery nor stock recovery).

Ashaz93 said:
Thanks for trying to help. The problem is that I can`t find any other S3 rom (in Tar form so that it can be flashed with Odin) other than T999UVUEOH1 (Jelly Bean 4.3). It bootloops over & over no matter how many times I flash it (I think it`s because I cannot wipe cache due to no recovery).
Click to expand...
Click to collapse
Ashaz93 said:
I tried one ROM from sammobile and another from androidfilehost (uploaded by a developer). Neither of them work because Odin gets stuck at Setup connection. I saw a video in which a guy fixed it by cleaning cache & delvik cache. This is the main issue because my kernel is messed up and I can`t clean cache because the phone just won`t go into recovery mode (neither custom recovery nor stock recovery).
Click to expand...
Click to collapse
Flashing the stock 4.3 rom was or wasn't successful?

audit13 said:
Flashing the stock 4.3 rom was or wasn't successful?
Click to expand...
Click to collapse
It was successful every time i`ve done it in the past but it was a mistake to flash it via odin after knowing the recovery is messed up and disappears a few minutes after flashing (doesn`t matter which one I flash, I`ve tried multiple recoveries but they all behave the same due to problems with kernel). I believe that is what caused it to bootloop. I then went on to flash stock 4.3 several times but it bootloops on the samsung logo every time. Now finally i`ve encountered a new error which doesn`t lets odin to flash ROMs or Recovery. It remains stuck at SetupConnection the entire time.
BTW This phone is a 5 year old device and is not my primary device (Ever since I got the LG g5) but still it`s very dear to me so I started this thread. I don`t use it as much as I used to before but I still want to keep it alive (as long as it doesn`t dies on it`s own).
I need to find a way to clean cache from PC. I don`t think there`s any other way to save a phone in this kind of situation.

Try this: open Odin, uncheck everything except F reset time, flash. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use key combination to get into stock recovery, factory wipe, reboot.
If this still doesn't work, the phone's internal memory chip may be defective.

audit13 said:
Try this: open Odin, uncheck everything except F reset time, flash. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use key combination to get into stock recovery, factory wipe, reboot.
If this still doesn't work, the phone's internal memory chip may be defective.
Click to expand...
Click to collapse
IT WORKED!!! :victory:
Unchecking everything except F reset time did the trick. How did you come with that ? You saved the day with that man. Thank you so much for showing up and taking the time trying to help me. I would not have been able to fix it without your help.
You should make an instructional thread for people facing this issue with Odin on any phone. I`m pretty sure it will help a lot of people who are stuck at SetupConnection when trying to flash ROMs. Thanks a lot for helping me out. I`d give you 500 if I had more accounts
Take care of yourself and keep up the good work audit13. :good:

Glad you got it working. We're here to help and learn from each other.
I learned the "uncheck" trick years ago when I started flashing the galaxy s2.