[Q] Hard-Bricked G1 - G1 Q&A, Help & Troubleshooting

[Q] Hard-Bricked G1 - G1 Q&A, Help & Troubleshooting

Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf

Sounds like you need JTAG, and don't take this the wrong way, but flashing firmware isn't the usual way, its the way you brick your phone. If possible always use fast boot to flash firmware or you are asking for a brick.
You can buy the JTAG equipment yourself and the software is free. Or you can see if you can find someone locally to do it. Unless you have a particular sentimental value to this phone it maybe cheaper to buy a new one.... Sorry for bad news
Sent from my Nexus 7 using xda premium

Bricked G1 - Try Again w/ SIM Card IN!
I had the exact symptoms mentioned in this post - tried nearly everything until I finally put back in the SIM card (even through I don't have T-Mobile anymore) - it booted again and registers the AC adapter and/or USB cable. Hope this helps some who are struggling at this level as I did!!
Bapf said:
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Click to expand...
Click to collapse

I don't know if this will work,as I've never encountered a situation such as this, but have you tried bootloader(power button+camera button)?
If you can get it into bootloader, then I have the original rc29 DREAIMG.NBH file(plus, rc29 is the best place to start if you want to root it or install a custom rom).If you get it working and just want stock 1.6, i have those updates as well.
(all said out of hope, I have a g1 and I love it,I'm really glad that someone else shares my enthusiasm!!)
If bootloader works, give me your email and i'll send you the files, good luck!:fingers-crossed:

Nope. It won't even start the bootloader.
Sent from my Nexus 4 using xda app-developers app

Well thats unfortunite, I guess it's just for a soft brick.

Related

New Nexus Not Working

Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!

Sounds like a DOA. Really bad luck.

If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse

If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.

Was it bnib?

mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?

Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.

I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.

Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.

its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.

Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.

You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head

P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?

badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...

padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.

padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.

After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts

[Q] Galaxy S not booting, black screen!

Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan

Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.

thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.

if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces

thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan

You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App

I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike

I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk

[Q] Stuck booting into Download mode

Okay, so as far as I am able to find... This problem is pretty unique...
I'm running Cognition 4.5.3 with no software issues. I have had this problem since Cog 3...
Most people have trouble getting their phone to boot into download mode, but NOT ME!
My phone randomly (I can find absolutely no cause or trigger and I'm not really a novice at Android) will shut itself off. Now normally I would not have an issue with this, but when I go to turn the phone on... it boots straight to download mode, and no key combo or anything will avoid it. So I have been testing this out and I can reboot the phone from the enhanced power menu, I can boot into Recovery from enhanced power menu... But when the phone shuts off or when I shut it down, the ONLY way that I can get it to power on correctly, is to plug the phone in and wait for it to show that the phone is charging. Then I can power it on normally...
Now, this issue arose the same time that my phone began to refuse to be recognised when plugged into a computer via USB... and at times the USB debugging and USB connected notifications will remain in the notification bar until I reboot the phone...
Naturally, my first instinct was to try and restore to stock... But since no computer will recognize my phone (even with fresh drivers installed) I cannot use odin to flash to stock.
So to summarize my problems:
1. My phone will not be recognized by a computer. (USB device not recognized)
2. My phone randomly shuts itself off. (Not a big deal, I can live with that)
3. My phone ONLY boots into download mode unless plugged into the charger (Incredibly frustrating when I am not at home or I don't have my car charger)
4. USB debugging and USB connected notifications stick around until phone is rebooted. (Using enhanced power menu. Again, I can live with this minor annoyance)

have you tried reflashing that rom...or trying another?
it could be the random shutdown issue that some cappys have paired with a failing usb port.
try changing roms.

studacris said:
have you tried reflashing that rom...or trying another?
it could be the random shutdown issue that some cappys have paired with a failing usb port.
try changing roms.
Click to expand...
Click to collapse
Hehe... I tried a different rom for two weeks and had similar and/or more problems...
Reflashing doesn't help either.
I've tried my best to troubleshoot this on my own, so I'm not shutting down your attempt to help. Just letting you know I have tried it.
I hadn't heard about a failing USB port problem... I'll read up on it.
Thanks for your help!

Atleast you dont have to worry about soft bricks if it auto boots into download mode

d34thp1ng said:
Atleast you dont have to worry about soft bricks if it auto boots into download mode
Click to expand...
Click to collapse
Actually I do...because USB still won't interface...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

like i said could be a short or something in the usb port...or somewhere in the hardware. if you experience this problem across different software then it has to be a physical defect someplace. cause if it were software related it would fix once you flashed something different...
you can try for a warranty replacement, that requires a little loose morals. you will have to do something to cause it not to boot, or only boot to the at&t screen otherwise they will have proof of root and/or custom rom and void your warranty. once thats accomplished mention some crap about kies failing and they should replace it.

studacris said:
like i said could be a short or something in the usb port...or somewhere in the hardware. if you experience this problem across different software then it has to be a physical defect someplace. cause if it were software related it would fix once you flashed something different...
you can try for a warranty replacement, that requires a little loose morals. you will have to do something to cause it not to boot, or only boot to the at&t screen otherwise they will have proof of root and/or custom rom and void your warranty. once thats accomplished mention some crap about kies failing and they should replace it.
Click to expand...
Click to collapse
Hmmm... a few months back my original USB/Charging cable broke and for a couple of days I was forced to use a generic MicroUSB cable to charge my phone... Could that have cause a short/damage to the port?
My phone does not have warranty as I bought it refurbished. :'(
(Plus my morals aren't that loose.)

Had a similar issue, eventually determined that it was a short in this usb port and did a warranty return. (Only when plugged in could I turn on, etc.)
If that isn't an option for you, you could try flashing CM. For some reason, the cyanogenmod build won't let the phone charge when off. ( Automatically powers back up once the juice flows.)
I flashed a nightly and somehow, magically, my phone would power back up normally ( but wouldn't turn off, unless plugged in without power. So strange!)
Even more weird? I flashed back to stock and the new powering and rebooting stuck. The short wasn't fixed, my phone simply seemed to reverse the problem.
Plus, you would be using cm.
Sent from my SGH-I897 using XDA App

tbrass said:
Had a similar issue, eventually determined that it was a short in this usb port and did a warranty return. (Only when plugged in could I turn on, etc.)
If that isn't an option for you, you could try flashing CM. For some reason, the cyanogenmod build won't let the phone charge when off. ( Automatically powers back up once the juice flows.)
I flashed a nightly and somehow, magically, my phone would power back up normally ( but wouldn't turn off, unless plugged in without power. So strange!)
Even more weird? I flashed back to stock and the new powering and rebooting stuck. The short wasn't fixed, my phone simply seemed to reverse the problem.
Plus, you would be using cm.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks! You guys have pretty much answered my questions...
I don't want to leave my nice DG Rom though.
Since I have determined that it is a hardware problem... I think I'm just going to live with it for a few more weeks until I can afford to go ahead and buy the newer build of the Cappy... (Might even wait until the SGSII comes out.)

You should be able to get warranty replacement, just make sure the device is in a stock condition when you take it in!

tbrass said:
You should be able to get warranty replacement, just make sure the device is in a stock condition when you take it in!
Click to expand...
Click to collapse
Even though I purchased the device as a refurbished device?
The only problem is that I can't Odin back to stock...

Cease1 said:
Even though I purchased the device as a refurbished device?
The only problem is that I can't Odin back to stock...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=995143&highlight=safely+to+stock
this will get you to stock then look in forums for how to change boot animation change that to stock boot logo and your good to go i did read some were you could do boot img all on phone i belive. i cant find thats up to u

Okay so I called them and let them know what the phone was doing and they tried to send me to samsung to have them repair the phone...

I now hold in my hands a shiny new 1102 build Cappy... Took it to my local device service center and explained the random shutdowns and the booting into download mode and they replaced it no questions asked!
Now to get Cog 5b2 on here.

Nook color will not boot/black screen

my nook color will not boot at all. I formmatted /system and /boot, then it froze. Now I can't boot it up anymore. I was trying to update CM7.
Help please !
Thank you guys.

boot from an SD card. Works every time.

Even backlight doesn'flicker on.
Sorry, but I'll just borrow this thread for my Nook Color nightmare which may be more sinister than anyone else's on this forum.
I've read through Dummies Guide to Fixing 'My Nook Won't Boot' and was unable to come across a post that was able to solve my problem. However, there where three other posters who reported similar symptom as I, and who also were never able to find a solution.
I suspect that my NC, and the three other posters', is truly BRICKED.
Currently my situation is as follows:
- Attempt to power on NC does not yield any response, not even a flicker of the backlight turning on
- Cannot boot from uSD card that had previously successfully booted from in the past (have used it for flashing ROMs to EMMC).
- Attempt to power on while connecting to PC (XP) via USB causes computer to recognise device OMAP3630, but immediately loses it (NC unresponsive as per 1st point).
I had Nookie Froyo 0.6.8 on it for quite some time. And I think I witnessed it die. This is what happened: I turned on the screen using the N button. Everything seemed okay except that it was responding rather sluggishly to my inputs and gestures, and then it just froze (screen still on). I used the power button to try to cycle it but once it turned off that was the end.
I've already followed these suggestions:
- Press power button for 60 seconds.
- Press combination of Power, N, Volume.
- 8 boot attempts (as there is no visible response I press the button for 10 seconds, release it for 5, and then repeat that about nine times)
Hoping that someone could throw some suggestions around before I part with my expensive brick.

It's dead, Jim.
Why not do a warranty replacement?
Rodney

rhester72 said:
It's dead, Jim.
Why not do a warranty replacement?
Rodney
Click to expand...
Click to collapse
My thoughts exactly. Although I don't have extensive android experience, I've got a decent bit of PC time and that sounds like a problem based on faulty hardware rather than improperly installed software.
Sent from my NookColor using XDA Premium App

Other thing is, remember when messing around with flashing roms etc, that your battery is fully charged. Not sure about the nook, but for some phones, they don't charge while in this process and some people have bricked their phones while running out of power doing a flash.
I suspect you might have a battery problem and may not have a charge enough to boot from SD.

I'm in the same boat...
Same thing happened to me. I was fully charged, went to clockwork to boot while trying to update CM7 and now my nook is unresponsive. The only thing I get is the battery too low screen. It has been on its charger for 4 hours. If anyone has any suggestions...

I had the same problem.... wiped the boot and then was unable to boot even with SD card; only got black screen.. Then I decided to hold down the n and the power button at the same time and then after about five seconds I saw my screen flash and I let go of the power button and n buttons. Now the nook is booting fine off of my SD card once again... whew! Won't wipe boot again...

Time to replace this brick
lanje78 said:
If anyone has any suggestions...
Click to expand...
Click to collapse
Well, I've made the decision to exercise the 1 year replacement warranty.
I've been told by B&N customer support that you can simply walk in to a B&N store with the complete package (charger and cable) and they will replace it on the spot. Helps if you take the receipt with you.
For us people who live outside of the US it's a whole different kettle of fish...
UPDATE:
So I sent the NC back to my US seller and had it replaced under the 1 year warranty. I received a refurbished NC, but with the serial number starting with 2010... which I understand indicates a newer version.
I'm still wondering if OCing the NC may have cause the problem on my bricked one... I guess I will find out after I OC it again, which I am certain to do as it improves flash video play...

[Q] A very strange rebooting problem.

Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.

Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.

Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.

Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)

Database Develop

welcome