Database Develop

[Q] Can this i9000 be recovered?? or is it totally bricked??

Hey all,
I have recently been given a phone by a friend, a SGS i9000. He bought it as is, and being n00b he couldnt describe anything to me about how or why it was like this. As I have a i9000 myself I took a bit of a look at it, I have no idea what firmware,rom,kernel etc is on it. After researching around it seems to be locked in a bootloop, I can not access any recovery menu, if I hold the power + home button I get the screen below (found this button combo somewhere in the forums, attaining to the Samsung anycall, korean?), but when plugged into my computer it comes up saying "windows could not recognize device blah blah". Any hope??? Last resort will be to get a jig, but ive never had to use them before and not sure if it will solve my issue. Any help would be much appreciated.
Thanks
battznz

battznz said:
Hey all,
I have recently been given a phone by a friend, a SGS i9000. He bought it as is, and being n00b he couldnt describe anything to me about how or why it was like this. As I have a i9000 myself I took a bit of a look at it, I have no idea what firmware,rom,kernel etc is on it. After researching around it seems to be locked in a bootloop, I can not access any recovery menu, if I hold the power + home button I get the screen below (found this button combo somewhere in the forums, attaining to the Samsung anycall, korean?), but when plugged into my computer it comes up saying "windows could not recognize device blah blah". Any hope??? Last resort will be to get a jig, but ive never had to use them before and not sure if it will solve my issue. Any help would be much appreciated.
Thanks
battznz
Click to expand...
Click to collapse
Identify what Phone it could be by checking its top corner for a Tucked in TV Antenna ...if you can pull out an Antenna its an M110S, if not it is an i9000 flashed with a wrong ROM. IF its M110S , just use PIT STOP link below to resolve using How to flash guide
The Anycall screen you are getting means it is still in download mode and can be detected by Odin, if not do a battery pull ( follow My Android Solutions, link below)

xsenman said:
Identify what Phone it could be by checking its top corner for a Tucked in TV Antenna ...if you can pull out an Antenna its an M110S, if not it is an i9000 flashed with a wrong ROM. IF its M110S , just use PIT STOP link below to resolve using How to flash guide
The Anycall screen you are getting means it is still in download mode and can be detected by Odin, if not do a battery pull ( follow My Android Solutions, link below)
Click to expand...
Click to collapse
Thanks for your reply.
I have looked to see if there is an antenna, nothing there. Ive tried rebooting the PC, and done a battery pull. Whilst in bootloop ive plugged in the phone, nothing comes up. Whilst in download mode, ive plugged in the phone, device detected but unrecognized. I removed everything......then......
1) Uninstalled all drivers and KIES from my PC > Reboot
2) Went to Android solutions, started with step one, no help.
3) Went onto step 2 (Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable),I checked to see if any pins were bent, and cleaned the contacts using some mini brushes I had. I am using a Samsung USB, same one i use for my i9000, which works 100%. Installed and tried every driver seperately, whilst trying to see if odin would detect anything.
NOTHING :crying:
Tried different ports etc. The only response I get is when ive put the phone into download mode (Home+Power), then all I get when connected to PC is "USB Device not Recognized". Im grateful that I get that, but cant do much else haha.
Can you suggest anything else?? can I even use the jig as a last resort???

Did you remember that you need to reinstall drivers?

monkeywithbanana said:
Did you remember that you need to reinstall drivers?
Click to expand...
Click to collapse
Hey thanks for your reply, if youre referring to the PC, then yes I removed all the drivers that did not work, and lastly reinstalled Samsung KIES. Still no change to the device being recognized by windows.

battznz said:
Can you suggest anything else?? can I even use the jig as a last resort???
Click to expand...
Click to collapse
Nothing wrong with the phone except that its, now loaded with a wrong boot loader, ...try borrow a lap top or PC to connect in download mode, to flash a i9000 rescue or resurrection kit from MY Androids collections link below

xsenman said:
Nothing wrong with the phone except that its, now loaded with a wrong boot loader, ...try borrow a lap top or PC to connect in download mode, to flash a i9000 rescue or resurrection kit from MY Androids collections link below
Click to expand...
Click to collapse
Thanks I will give it a try, will let ya know how I get on.

Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got, when using the heimdall rescue kit:
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
ERROR: Failed to confirm end of file transfer sequence!
IBL+PBL upload failed!
Ending session...
Rebooting device...
Click to expand...
Click to collapse
Please HELP me
What do I do from here??

Attached are the results I get when trying to use odin and trying to flash EZBASE.
I get further in flashing using heimdall. Without trying to sound n00b, can I not flash the bootloader to something that works???

battznz said:
Attached are the results I get when trying to use odin and trying to flash EZBASE.
I get further in flashing using heimdall. Without trying to sound n00b, can I not flash the bootloader to something that works???
Click to expand...
Click to collapse
try ezboot from My Android collections link below

xsenman said:
try ezboot from My Android collections link below
Click to expand...
Click to collapse
Hi, ive tried ezboot, still no luck, I get the same error message in odin. Grrr frustrating, seem to be throwing solutions at it but nothing is cracking it.
Is there a way i can do it through heimdall?? seems to get more done when trying to flash except the error i get above?? perhaps how to do a bootloader flash using heimdall not odin??
Thanks

battznz said:
Hi, ive tried ezboot, still no luck, I get the same error message in odin. Grrr frustrating, seem to be throwing solutions at it but nothing is cracking it.
Is there a way i can do it through heimdall?? seems to get more done when trying to flash except the error i get above?? perhaps how to do a bootloader flash using heimdall not odin??
Thanks
Click to expand...
Click to collapse
I think the solution to your problem has been found, and your phone is actually an M110S Anycall galaxy S..read this thread http://forum.xda-developers.com/showthread.php?t=1888319...so you need to use the M110S repair kit, download from Pit Stop, link below and flash as per guide or like this http://forum.xda-developers.com/showpost.php?p=28174768&postcount=4774

First of all I would like to thank you xsenman, your posts and guides on these forums have been a huge help. Going along with what you said in your last post, I have started downloading the repair kit, then hopefully do an official update for here (Australia).
I just want to add, you may want to add the the following as a solution to a lot of problems (it helped me verify).
I had a look at this thread:
http://forum.xda-developers.com/showpost.php?p=30797809&postcount=1
And about half way through the thread is IMEI check
I entered the IMEI from my phone (an official samsung gti9000), and it came back with a result saying exactly that.
I then entered the IMEI from my friends phone (bought from ebay >:/ go figure), and it came back saying it was M110S but so has it that the internal sticker on my friends phone says model: GT-i9000
If anyone else gets into a confusion like I have, which it is hard to tell if its fake or not. Posting/sticky the imei check will save a lot of time, heart ache and possibly from creating a $200 paper weight.
Once again thank you so much, hopefully this repair kit will work and the phone will be up and running.
:good:

Really (I mean *really*!) bricked my phone. Nothing works.

Hi p970ies,
EDIT: NEW problems, see last pages.
here is my story:
I was on IZS v1.1, when I decided to go into recovery and make a full-wipe for having a "fresh install" again. You know, the phone was laggy, I had to many apps etc. I pressed the on/off-button for 1-2 secs to reboot into recovery, then my phone turned off and restarted but just with a "bright" black screen, the display was on. I thought "something went wrong", pulled the battery out and put it back in again, started, but then same screen again.
A few months ago an easy "unbricking" method (I know, not really unbricking) was to flash Redy2006's touch-recovery and boot into it with his scripts. So I flashed it (I know it's dumb, because of the u-boot and v30 thing, Idk), same result.
After that, I grabbed smartflash and two .bin/.fls packs of 2 roms, went into that special mode (phone off, press vol+, plug in) but there was no "sign" (screen that shows that you are in that mode) like the other day, the screen kept being black, but on.
Nonetheless the flashing worked and the software said everything alright. I started the phone but same result, in addition that there was now this effect: When the battery is put in and/or the phone is charging, the screen changes from being on and off. I can't do anything, no restarting with buttons, no LG screen, nothing but on and off, on and off. Every few seconds.
Thank you, I hope you experts can help me. (Even when I have the phone 2 years now and I was a ROM-junkie since the first day )
Edit: Tried smartflash with another patched v20 ROM. Tried KDZ Updater, just errors. But now the phone seems to boot, but there's nothing on the display, just the 4 softkeys are fading in and out.

Tomatengelee said:
Hi p970ies,
here is my story:
I was on IZS v1.1, when I decided to go into recovery and make a full-wipe for having a "fresh install" again. You know, the phone was laggy, I had to many apps etc. I pressed the on/off-button for 1-2 secs to reboot into recovery, then my phone turned off and restarted but just with a "bright" black screen, the display was on. I thought "something went wrong", pulled the battery out and put it back in again, started, but then same screen again.
A few months ago an easy "unbricking" method (I know, not really unbricking) was to flash Redy2006's touch-recovery and boot into it with his scripts. So I flashed it (I know it's dumb, because of the u-boot and v30 thing, Idk), same result.
After that, I grabbed smartflash and two .bin/.fls packs of 2 roms, went into that special mode (phone off, press vol+, plug in) but there was no "sign" (screen that shows that you are in that mode) like the other day, the screen kept being black, but on.
Nonetheless the flashing worked and the software said everything alright. I started the phone but same result, in addition that there was now this effect: When the battery is put in and/or the phone is charging, the screen changes from being on and off. I can't do anything, no restarting with buttons, no LG screen, nothing but on and off, on and off. Every few seconds.
Thank you, I hope you experts can help me. (Even when I have the phone 2 years now and I was a ROM-junkie since the first day )
Edit: Tried smartflash with another patched v20 ROM. Tried KDZ Updater, just errors. But now the phone seems to boot, but there's nothing on the display, just the 4 softkeys are fading in and out.
Click to expand...
Click to collapse
Oh man, its sad to hear that.
I can just think on two situations.
One is a broken screen, but thats pretty obvious.
And the other is a broken boot partition. Its very strange that you cant get into software upgrade mode. You sure you removed SIM, battery and SD, and then plugged it to the cable while holding the volume buttons?
I dont doubt you did it well, just making sure. Anyways AFAIK you should be able to enter that mode unless you got a broken boot partition.
Best of luck, sorry Im not of much help.

Grakel said:
Oh man, its sad to hear that.
I can just think on two situations.
One is a broken screen, but thats pretty obvious.
And the other is a broken boot partition. Its very strange that you cant get into software upgrade mode. You sure you removed SIM, battery and SD, and then plugged it to the cable while holding the volume buttons?
I dont doubt you did it well, just making sure. Anyways AFAIK you should be able to enter that mode unless you got a broken boot partition.
Best of luck, sorry Im not of much help.
Click to expand...
Click to collapse
Hi, thank you for your answer.
Yesterday oder so, I connected my phone without SIM, SD and battery while pressing vol+ to my pc and it showed the S/W-Update "Wait while update is in progress" or something. I was happy because the display isn't broken. But then I flashed again and the display is as black as before...
I thought about a broken bootloader. Do you guys know a way to fix it? Or the boot partition?

Tomatengelee said:
Hi, thank you for your answer.
Yesterday oder so, I connected my phone without SIM, SD and battery while pressing vol+ to my pc and it showed the S/W-Update "Wait while update is in progress" or something. I was happy because the display isn't broken. But then I flashed again and the display is as black as before...
I thought about a broken bootloader. Do you guys know a way to fix it? Or the boot partition?
Click to expand...
Click to collapse
Im pretty sure that if you can see the software update mode, you can unbrick the device.
When you said you reflashed something, do you actually mean that you smartflashed the fls and bin files from a stock v20 rom? AFAIK the bin file carries a bootloader with it so it should get fixed if your problem is the bootloader.
And by the way, while the phone has that black screen and is stuck booting... Are you able to use adb commands? You could try to jump to the recovery with "adb reboot recovery" to see if you got a working recovery.
Best of luck, tell me how it goes

Grakel said:
Im pretty sure that if you can see the software update mode, you can unbrick the device.
When you said you reflashed something, do you actually mean that you smartflashed the fls and bin files from a stock v20 rom? AFAIK the bin file carries a bootloader with it so it should get fixed if your problem is the bootloader.
And by the way, while the phone has that black screen and is stuck booting... Are you able to use adb commands? You could try to jump to the recovery with "adb reboot recovery" to see if you got a working recovery.
Best of luck, tell me how it goes
Click to expand...
Click to collapse
yep, I tried every version (10, 20, 30) in bin/fls and kdz. But I never got the screen to show something again.
And no, I can't use adb commands, sadly. It says "cannot find device" or something like that.

Tomatengelee said:
yep, I tried every version (10, 20, 30) in bin/fls and kdz. But I never got the screen to show something again.
And no, I can't use adb commands, sadly. It says "cannot find device" or something like that.
Click to expand...
Click to collapse
Huhmmm... Quite strange.
You can try to open up device manager, look for the phone (will probably have no drivers and the icon will have a yellow triangle) and force installing adb drivers. After that you are supposed to use adb even in middle of a boot.
I'd say that your best chance is to get to your recovery, so you can wipe everything (even formatting system) and start from scratch...
Anyways Im no expert at all... Just trying to help.

Grakel said:
Huhmmm... Quite strange.
You can try to open up device manager, look for the phone (will probably have no drivers and the icon will have a yellow triangle) and force installing adb drivers. After that you are supposed to use adb even in middle of a boot.
I'd say that your best chance is to get to your recovery, so you can wipe everything (even formatting system) and start from scratch...
Anyways Im no expert at all... Just trying to help.
Click to expand...
Click to collapse
Sometimes ADB works, but it says "device offline". When I flashed PRE-IZS fls/bin from the spanish forum, and then V30B bin/fls, something really weird happens: The phone is on, the wake-button works well - it turns on and turns off the display and the softkeys. But the screen doesn't show anything - just black.

Hello there!
Did You try out the B2C tool provided by LG? And there is one other tool provided by LG. Just try these oit. If they dont work, then try claiming it under warranty. They might replace the motherboard.
P.S: If You have the money, sell this piece of **** and get a Sony or Samsung. Cheers!
Sent from my LG-P970 using xda app-developers app

rokr05 said:
Hello there!
Did You try out the B2C tool provided by LG? And there is one other tool provided by LG. Just try these oit. If they dont work, then try claiming it under warranty. They might replace the motherboard.
P.S: If You have the money, sell this piece of **** and get a Sony or Samsung. Cheers!
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to buy a Nexus 4, but I have to convince my parents
Oh and yes, phone is older than 2 years and in Germany we only have 2 years of warranty I think.

Tomatengelee said:
Sometimes ADB works, but it says "device offline". When I flashed PRE-IZS fls/bin from the spanish forum, and then V30B bin/fls, something really weird happens: The phone is on, the wake-button works well - it turns on and turns off the display and the softkeys. But the screen doesn't show anything - just black.
Click to expand...
Click to collapse
An easy, possible fix for The Device offline is to use the latest ADB. Just use the attached zip anywhere and use ADB, its the latest version from the android SDK, but just the files required for ADB. My nexus 4 had the same problem, but Solved it by updating ADB.

ykumar00 said:
An easy, possible fix for The Device offline is to use the latest ADB. Just use the attached zip anywhere and use ADB, its the latest version from the android SDK, but just the files required for ADB. My nexus 4 had the same problem, but Solved it by updating ADB.
Click to expand...
Click to collapse
damn it says "error: device not found" when in S/W or bootloop... or device offline in bootloop
any ideas?

did you try patched bins ? (for being able to boot into recovery right after the flash process, maybe you just need right wipes)
#700th post yay...

Ilko said:
did you try patched bins ? (for being able to boot into recovery right after the flash process, maybe you just need right wipes)
#700th post yay...
Click to expand...
Click to collapse
Yes, I did, but Smartflash works "less" than the KDZ-Updater. Actually the phone beeped today while it was on (with some kdz flashed) :silly:
Is it possible to convert patched bin/fls files to kdz?

I don't know, probably not... what I can say is that kdzu doesn't perform full wipes since it's intended to update the system and keep datas at the same time. You probably need wipes...

Ilko said:
I don't know, probably not... what I can say is that kdzu doesn't perform full wipes since it's intended to update the system and keep datas at the same time. You probably need wipes...
Click to expand...
Click to collapse
Oh ok... But with KDZ-Updater, it's possible to turn the phone off and on (screens is "on" but shows the color black while the softkeys are on too).
I'll try again with Smartflash... Do you know another version of it or a good tutorial? Maybe I've done the wrong method or something...

there are several tuts in this forum. smartflash is the quickest and safest way to restore / unbrick as it erases everything in the internal memory

Ilko said:
there are several tuts in this forum. smartflash is the quickest and safest way to restore / unbrick as it erases everything in the internal memory
Click to expand...
Click to collapse
I know, but it never works. That problem is so weird! :silly:
Man, nothing works... After smartflashing display flashing off and on again, after kdz display on, softkeys flashing

ADB side service is not active while in S/W mode. The only chance to access to recovery is to boot normally, and access to the device via ADB. The problems are : device needs to pass initial boot process for being able to be detected by ADB (even if you don't see the desktop it's ok), and USB debug must be enabled by default...
so, if you can't pass initial boot process, no chance to use ADB, and, if it passes, usb debug must be enabled or device will remain offline...

Ilko said:
ADB side service is not active while in S/W mode. The only chance to access to recovery is to boot normally, and access to the device via ADB. The problems are : device needs to pass initial boot process for being able to be detected by ADB (even if you don't see the desktop it's ok), and USB debug must be enabled by default...
so, if you can't pass initial boot process, no chance to use ADB, and, if it passes, usb debug must be enabled or device will remain offline...
Click to expand...
Click to collapse
Is there a chance to enable it manually?

the only chance is to flash a ROM which have it enabled by default for the most of them.
mine died because of the new twrp 2.6. It has definitively corrupted the boot partition as even smartflash can't ends its process. I had to buy another device...

bricked....

Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.

re: not bricked
cronos1388 said:
Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.
Click to expand...
Click to collapse
Your phone is NOT bricked. If it was the screen would not even go on.
Have you tried going into recovery mode (VolumeUP/VolDown/PowerButton)
and once in Recovery Mode do a factory reset or Data Reset forgot what the
exact wording is in the stock recovery.
If you flashed twrp recovery it's ok too, just select "factory reset".
After doing that the phone should no longer display anything about Kies.
If you get to the twrp recovery screen you should be able to flash a stock
rooted rom without any issues.
If all you get is the stock recovery screen then you should be able to odin
flash the official Samsung Note 4 kitkat 4.4.4 NJ7 firmware which you may
need to download the firmware from http://SamMobile.com if you don't
already have it. (be sure you have the correct firmware for the Note 4 N910T).
Be 100% sure that the phone is FULLY POWERED DOWN before going
into Download Mode to avoid odin errors and issues.
Good luck!

Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.

cronos1388 said:
Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.
Click to expand...
Click to collapse
Can you check for the file with md5 before you flash from your phone? I forgot where to dig for this info.
All I I have done before is on my cook rom file, I just open it with WinRAR and test for error. If no error, then its good.

On my Home PC I have a program that will put a check mark next to a file if it matches the md5. I also have Winrar at home.
I was just using the default Windows zip program and I have had problems with that and installers/roms in the past.
The only other things I did different were I removed the SD card and installed the drivers before plugging my phone in instead of letting Windows download them automatically.
I also removed the battery after I left work so it was out of the phone for a couple of hours.
The final thing I did was calm down lol after the initial shock of seeing a softbricked screen on my brand new phone.
I'm all rooted now with TWRP and running Hyperdrive so it's all smooth sailing from this point forward.

You should check md5 on phone once you done transferred to phone from PC
BAD ASS NOTE 4

[Q] Completely dead N7000. Hardbrick I think.

Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi

It is exactly this: just another bricked Note thread.

ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi

Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?

If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.

I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.

nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?

I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.

froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?

AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.

Part of the "hardware" is your battery...

S6 Active Bricked? Need Help

My wife's AT&T S6 Active was plugged in and just sitting idle. Out of nowhere, it turned off. When she turned it back on, it booted to the Samsung boot screen and got stuck. It will not get past that. She never tried to root / flash or anything... just normal use.
I've tried booting into recovery mode but it won't. The only thing I can get it to do is to boot into download mode... and if I select reboot, it just hangs on the Samsung load screen again.
She took it to the AT&T store and they were unable to do anything with it. She has probably 1500+ pictures/videos on here that we would love to recover. Plugging it into a PC with or without Kies does not detect anything.
Can anything be done here?

I have a International S6 but i think the proceed for your model is the same.
Try to flash Firmware in Odin. You can get into download mode and think you have a high chance. Look at the forum for more instruction.
Im sorry for my bad english but i come from Germany. Isn't good enough?

Sorry, I don't have an answer, but I have the same issue. Random boot loop and cannot get to recovery. Happened after the latest software update. Tried flashing with Odin with download mode but it didn't fix anything.
If you find an answer to this please let me know, and I'll do the same.

ghostdeadeye said:
Sorry, I don't have an answer, but I have the same issue. Random boot loop and cannot get to recovery. Happened after the latest software update. Tried flashing with Odin with download mode but it didn't fix anything.
If you find an answer to this please let me know, and I'll do the same.
Click to expand...
Click to collapse
Same issue here...well basically..ever figure it out?