Develop Bugs

Please help!

Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.

simon211175 said:
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
Click to expand...
Click to collapse
ok mate
right the mcgyver trick works a treat and is surprisingly easy. i wasnt keen on it but it works and is not hard although it is fiddly and if you are anything like me it will take a few attempts to peel back the shielding and expose the wires and then get them in place.
i found the best way to get the wires in place was not put them under the battery as the guide suggests but instead just put the battery in as normal and have the wires in at the very end. you will understand what i mean when you start but i have decided to take a photo and you can see what i mean here
http://sdrv.ms/OPDczX
everything you need for that this section of the recovery is here.
http://forum.xda-developers.com/showthread.php?t=892026
then you need to flash the sbf again. the one you have already flashed is fine and is the one you need so use that. (if for some reason it doesnt work after what i am going to tell you then ask again on here before you choose another).
next follow the guide to un-bricking your phone (linked below). if the phone wont boot and gets stuck after you have flashed the sbf you need to boot into recovery and wipe the data/ cache. reboot and all should be ok.
so follow the guide to the letter but when/ if (the phone wont boot past the moto logo) follow step 8. however you will find that when you press power on/ volume down that instead of motorola recovery you get a droid with an exclamation mark (this is ok so dont panic). to get into stock recovery from this position you need to press and hold down both up and down volume buttons at the same time for about three seconds and viola. then you can wipe and you should (fingers crossed) be good to go. if you dont understand anything then ask but it is relatively straightforward and if you do what i suggest above then you should have a working phone in next to no time.
http://forum.xda-developers.com/showthread.php?t=1828639
good luck

Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.

simon211175 said:
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
Click to expand...
Click to collapse
did you wipe the cache/ data after you flashed the sbf? if you didnt you may want to give it a go before you send it off. it may spring to life once you have done that.

I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.

simon211175 said:
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
Click to expand...
Click to collapse
It looks real bad. You sure the battery didn't die in the flashing process.?
Also try booting into recovery and do a wipe.

It's entirely possible that the battery died during the flash.
I cannot boot in to recovery - the phone doesn't get that far!
I've sent it back to be repaired. hopefully they'll do it under warranty, but if not it's only going to cost around £60 to buy out the remainder of my contract so if the repair costs more I've got that as a backup option.
Thanks for all your help guys.

You can cut an old wall charger but if you can't measure the voltage to know what wire have 5 volts and 0 Volts , and you can hold the wires 5V to plus on akku and 0 to minus and the supply would load..... you can left the batt out of the device...
Wait 10 till 15 min ,for save check if batt getting hot, boot into stock recovery and factory reset your phone
If you can't enter recovery you should be able to enter boatloader
If there is battery low can not program ..load akku.. or ready to program which means .... flash rom with rsd, factory reset , reboot, have fun
i did this two times, flash with low batt one of with not loading batt in dev - i charged with Nokia wall charger cable
If only battery is too empt and briked batt loader.......
If boot loader is briked by bad flashing search Google......
But i mean ciao loved defy
And don't forget : factory reset is always after you changed your rom....
Wiping cache/dalvik cache in only installing new nightly
Sent from my MB526 using xda app-developers app

so, here's my update.
You will recall (see two posts up) that I gave my phone back to T-Mobile on 20th August for a repair. I got my phone back today (+18 days). Here's how it went:
Day 1
Took phone to T-Mobile store. Informed them my battery had a strange lump, which I suspect had fried my phone somewhere. They advised they would send it to the repair centre the following day. No courtesy phones available so I'd be living in the 1980s for a while.
Day 10.
Phone actually arrives a the repair centre. I have no idea where the repair centre is, but I'm guessing really really far away.
Day 15.
Repair centre advise my battery is faulty and to replace would cost me £26.40 for a genuine Motorola battery. Advised repair centre that I told them my battery was broken, and asked why it took them 15 days to repeat that back to me. Also advised them I would rather by my genuine Motorola battery from Amazon for £11.95. Gave them a link in case they want to update their price lists.
Day 17.
Repair started on actual phone.
Repair finished. Yep - the repair took less than 24 hours.
Day 18.
Phone returned to store. it took 24 hours to get there, so I'm assuming the post travels down hill only on the way back.
Picked up phone from store, all set to complain about poor service etc. Noticed brand new battery I hadn't paid for sitting in the returns package. Kept quiet. Left store promptly.
So now I have a working Defy once more (Hurrah).
Obviously I've rooted it already in order to get Titanium Backup to restore all my apps.
Now I have stock 2.2 Blur running on my phone (Boo!), and with only a few months remaining on my contract, I'm not sure if I want to risk loading a new ROM again (I'll reread this once I've loaded a new ROM next week, for sure).

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

In case of emergency!

Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?

Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app

lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.

heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download

Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.

Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!

frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2

Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!

frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2

Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing

Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!

http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?

Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)

ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

S3 won't boot - black screen

Hey folks,
I was trying to flash a custom kernel (Phenomenal Extreme 4.0) from Clockworkmod on a rooted stock 4.1.2 rom and kernel. I placed the zips on my sd card, then flashed, but it was unsuccessful. Then, when I rebooted from CWM's main menu, the phone went dead. Nothing worked, no buttons, no nothing. Any combination I tried failed, from a simple reboot, to reboot into recovery, to a reboot into download mode. Took battery out, and placed it back in, still nothing.
I'd appreciate any help you can give me! If there's anything like a factory cable, that is still better than nothing. I think I bricked it, and no warranty (Samsung's 3 month is quite short). When I plug the phone in, the laptop responds with a sound but it's not the usual sound when you dock the device. A balloon says that device driver installation failed. Then nothing happens. In any case, I rooted it and there's a flash counter of 1 on it, even if I'm running stock everything. Again, I appreciate any help!

seokhun said:
Hey folks,
I was trying to flash a custom kernel (Phenomenal Extreme 4.0) from Clockworkmod on a rooted stock 4.1.2 rom and kernel. I placed the zips on my sd card, then flashed, but it was unsuccessful. Then, when I rebooted from CWM's main menu, the phone went dead. Nothing worked, no buttons, no nothing. Any combination I tried failed, from a simple reboot, to reboot into recovery, to a reboot into download mode. Took battery out, and placed it back in, still nothing.
I'd appreciate any help you can give me! If there's anything like a factory cable, that is still better than nothing. I think I bricked it, and no warranty (Samsung's 3 month is quite short). When I plug the phone in, the laptop responds with a sound but it's not the usual sound when you dock the device. A balloon says that device driver installation failed. Then nothing happens. In any case, I rooted it and there's a flash counter of 1 on it, even if I'm running stock everything. Again, I appreciate any help!
Click to expand...
Click to collapse
What forum did you find that kernel? Hopefully it was made for d2tmo.
+Bound for Valhalla!

I just checked, it wasn't. It's actually made for the international version -- my fault. Oh crap, I'm totally screwed, aren't I? *rolling eyes and a long sigh*
http://forum.xda-developers.com/showthread.php?t=1917234 My question is, it failed regardless, and why would it die AFTER I reboot the phone? It should've died right when I tried to install it through CWM.

seokhun said:
I just checked, it wasn't. It's actually made for the international version -- my fault. Oh crap, I'm totally screwed, aren't I? *rolling eyes and a long sigh*
http://forum.xda-developers.com/showthread.php?t=1917234 My question is, it failed regardless, and why would it die AFTER I reboot the phone? It should've died right when I tried to install it through CWM.
Click to expand...
Click to collapse
Google jtag repair.

That's an expensive paper weight.
|When Emotion Goes Up, Logic Goes Down|

I made a Nandroid before messing around.
Once I do the JTAG repair, can I restore using that Nandroid after re-rooting and flashing CWM? The guy who will be doing the JTAG said that it's dangerous because there's a risk of bricking involved.

I would just restore things individually, personally. I don't know what you had on there, but is there anything that you can't restore some other way ?

That happened to me when i flash wromg kernel. And I had a panic attack...but I somehow manage to go into recovery mod....if you can go into recovery mod...have no fear back up is there lol
Just wipe everything and restore your backup.
Sent from my SGH-T999 using xda premium

Send it back
Sent from my SGH-T999 using xda premium

seshaz said:
Send it back
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hopefully you can get odin to recognise it...

tdotdot said:
Hopefully you can get odin to recognise it...
Click to expand...
Click to collapse
I had the same problem when I first got my S3. I flashed a file that was for my S2 not realizing and the phone responded the same way or didnt respond at all. Im not saying this will work but you can try. Do the proper button combo to get into download. It wont show anything on your scrren but the phone could still be in download mode. Go ahead and try connecting it to your computer and see if odin will recognize it. Make sure you have your drivers installed and dont forget to push volume up to get all the way into download mode. It worked for me once before and I hope to never have to try it again. If you have already tried this then your out of luck and will have to jtag.

JTAG is no scam. It is a VERY reliable source! Go for it.
Sent from my Galaxy Nexus using xda premium

Never mind, warranty exchange. I don't want to send my phone to strangers, even if it's legitimate. Still $45-$60 on the credit card.
I have a question though, as long as the phone is under warranty, I can exchange for a replacement an unlimited number of times, right?

Warranty Exchange!
seokhun said:
Never mind, warranty exchange. I don't want to send my phone to strangers, even if it's legitimate. Still $45-$60 on the credit card.
I have a question though, as long as the phone is under warranty, I can exchange for a replacement an unlimited number of times, right?
Click to expand...
Click to collapse
Yes you can...I did it with my S2 until I got one that did'nt have any signs of being refurbished. It looked brand new! I have even told them that something was wrong with the phone (hardware issue) when there was nothing wrong just because the one year warranty was about to run out and it had a few cosmedic blemishes..I have given them a lot of money in the past 9 years so I do'nt feel too bad... I did it with my Vibrant as well.

[Q] I need help. My s3 i747M shows zero signs of life.

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.

Sudden death of n2 n7100

I have been using my n2 for 1 year. but, I found my note 2 not turning on two days back. I just kept it fully charged and the next morning its not turning on. It was first stuck on the boot logo. then, I pulled the battery out and try to factory reset from stock recovery. but, I couldn't enter. then I tried installing the stock rom via odin. but, no luck. my android version was 4.1. can anyone tell me where is the problem and how I can solve?
oh one thing, now its not even turning on. just going to download mode. if I connect it to charger a battery icon shows up with a refresh circle on middle.

Sorry for hear that, mine have died on Sunday night u_u after flashing Agni kernel but I don't think the fault was for the kernel, the days before flashing it was already showing an erratic behavior like freezing and rebooting by it self. I thought it was because an undervolt or something like that (some custom roms do it) so i tried changing the kernel =( to see how it will die.
I took my phone to an external service center on yesterday morning (It doesn't have warranty anymore), and there they used Riffbox and Jtag to trying come back to life :laugh: and it worked for a couple of hours. They told me it had the bootloader bricked. I have my doubts because I have not even touched the bootloader just once when I rooted it after bought It (if it was touched after it, should be on an update or custom rom flashing, I don't know).
But last night was died again, so I started to search on web and I found this SDS, all the stuff described are the same that my phone suffered (but It was on 4.3 Ditto Note 3 soooo I though it was already solved since 4.1.2).
Is very sad but now I'm going back to the Service Center to tell them what I found. Maybe they will need to change the emmc or the motherboard =S I hope it doesn't cost a lot.u_u
Whatever, maybe yours one can have the bootloader broken, because yours turn on into download, mine doesn't turn on to recovery/samsung logo/download. Perhaps you can have luck and a chip solution just trying to flash another bootloader with odin and if you can get back working your Android, don't forget to download the "emmc check" app from playstore. It will give you any clue about this, if it says your emmc is vulnerable you will need to do the same as me changing emmc or motherboard but if you have luck and says it is not a bad batch you will no have problems again just flashing a good bootloader.

Service Center in Slovenija
badtzo said:
Sorry for hear that, mine have died on Sunday night u_u after flashing Agni kernel but I don't think the fault was for the kernel, the days before flashing it was already showing an erratic behavior like freezing and rebooting by it self. I thought it was because an undervolt or something like that (some custom roms do it) so i tried changing the kernel =( to see how it will die.
I took my phone to an external service center on yesterday morning (It doesn't have warranty anymore), and there they used Riffbox and Jtag to trying come back to life :laugh: and it worked for a couple of hours. They told me it had the bootloader bricked. I have my doubts because I have not even touched the bootloader just once when I rooted it after bought It (if it was touched after it, should be on an update or custom rom flashing, I don't know).
But last night was died again, so I started to search on web and I found this SDS, all the stuff described are the same that my phone suffered (but It was on 4.3 Ditto Note 3 soooo I though it was already solved since 4.1.2).
Is very sad but now I'm going back to the Service Center to tell them what I found. Maybe they will need to change the emmc or the motherboard =S I hope it doesn't cost a lot.u_u
Whatever, maybe yours one can have the bootloader broken, because yours turn on into download, mine doesn't turn on to recovery/samsung logo/download. Perhaps you can have luck and a chip solution just trying to flash another bootloader with odin and if you can get back working your Android, don't forget to download the "emmc check" app from playstore. It will give you any clue about this, if it says your emmc is vulnerable you will need to do the same as me changing emmc or motherboard but if you have luck and says it is not a bad batch you will no have problems again just flashing a good bootloader.
Click to expand...
Click to collapse
Service Center in my country told me, that i have modified the software and that there is no warranty to it even if it was SDS, for which they know...
New motherboard and that's it...:crying:

U should have done factory reset by stock recovery and bring binary count to 0 by that. I had same problm. Went to service centre there they told to replace motherboard which was almost costing very high. Luckily I had made everything on phone normal before going to service centre so I had done all in warranty《free》
Sent from my GT-N7100 using XDA Premium 4 mobile app

starlut said:
I have been using my n2 for 1 year. but, I found my note 2 not turning on two days back. I just kept it fully charged and the next morning its not turning on. It was first stuck on the boot logo. then, I pulled the battery out and try to factory reset from stock recovery. but, I couldn't enter. then I tried installing the stock rom via odin. but, no luck. my android version was 4.1. can anyone tell me where is the problem and how I can solve?
oh one thing, now its not even turning on. just going to download mode. if I connect it to charger a battery icon shows up with a refresh circle on middle.
Click to expand...
Click to collapse
if you can go into download mode try flashing a stock rom via ODIN and report back. If it says NO PIT PARTITION in ODIN then you need to flash the pit file and then a stock rom .

zeeshanonlyme said:
if you can go into download mode try flashing a stock rom via ODIN and report back. If it says NO PIT PARTITION in ODIN then you need to flash the pit file and then a stock rom .
Click to expand...
Click to collapse
i tried to flash the stock rom. its not flashing the kernel. and, I don't know whats wrong with it.
I don't have warranty and I am stuck in it.

aNtRx said:
Service Center in my country told me, that i have modified the software and that there is no warranty to it even if it was SDS, for which they know...
New motherboard and that's it...:crying:
Click to expand...
Click to collapse
Sorry to hear that, but they told you nonsense. If it's really SDS they have to repair for free. Ask a friend in your country who is envolved in legal things, a lawyer best.
One in general: As long as one can start eg. download mode, it is no SDS, mostly a software prob.