Related
Hi,
I've the following problem with my Gio. First, it didn't want to start. When I plugged it the charger, a symbol of the battery appeared on the screen with a yellow triangle, indicating that the temperature is too cold. And it wasn't cold. But I could start up the phone...until I removed the charger. My phone fell out directly.
I had a rooted version of the original firmware, so I tried to connect my phone to Kies. Didn't work. So I flashed a clean rom, 2.3.5 with Odin. My phone is working again, but I still have to connect it to the charger before I can start my phone. If I don't to it, a empty battery appears on the screen. But when the phone is started, I can remove it from the charger and it will still work. But now and than the phone falls out after a while.
At the moment, my phone isn't connected to the charger, but it still thinks that the charger is connected... Picture is attached.
Does anybody here had this problem too? Or do you people know a solution? The problem is, within 2 weeks I go to Sweden for 4 months, so I can't bring in my phone for repair...
Thanks in advance!
Anyone? Or any suggestions? I even can't read the battery gauge, also not in the settings menu. The graph is like a rollercoaster
Maybe you can go to recovery mode and do a wipe, maybe theres a problem with some files.. did you had root and modified something??
I think if you flash another stock rom, fresh, with a factory reset and sd card format, it may fix the problem.. but I havent seen this in xda before, so going to repair centre is good to, but you must be on stock rom and no root or unrooted
Sent from my GT-S5660 using xda premium
maybe you should try to do factory reset before flashing it again
Go to recovery and wipe battery stats and flash a rom with the usual dalvik and data wipes and see if that changes anything.Otherwise idk I never seen or heard anything like this
Sent from my LG-P350 using XDA premium
voetbalremco said:
Maybe you can go to recovery mode and do a wipe, maybe theres a problem with some files.. did you had root and modified something??
I think if you flash another stock rom, fresh, with a factory reset and sd card format, it may fix the problem.. but I havent seen this in xda before, so going to repair centre is good to, but you must be on stock rom and no root or unrooted
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
He can be rooted and on custom rom but then he cant use warranty.
Sent from my LG-P350 using XDA premium
I had this problem too about a month ago. You don't need to take it to repair center, install cwm (look in the gio big thread for help and dl), go to advanced menu, and wipe battery stats. If that doesnt help, do a wipe data/factory reset.
Btw, i had this too when it was about -15 celsius and i was outside. The Gio doesnt like cold :S
Sent from my GT-S5660
Thanks for the comments! I will try to wipe the battery stats. I'll keep you posted!
hsrars-d said:
I had this problem too about a month ago. You don't need to take it to repair center, install cwm (look in the gio big thread for help and dl), go to advanced menu, and wipe battery stats. If that doesnt help, do a wipe data/factory reset.
Btw, i had this too when it was about -15 celsius and i was outside. The Gio doesnt like cold :S
Sent from my GT-S5660
Click to expand...
Click to collapse
I installed CyangenMod 7.1, an did a wipe data. I also wiped the battery stats. No results. So I think that it is a hardware problem, with the battery... So I will bring my phone to a service center, no other option I think. And flash a stock firmware
Yeah that's probably the best thing to do.Good luck
Sent from my LG-P350 using XDA premium
http://www.danasoft.com/ sig/****yeah287168.jpg
Sorry for the dig guys but I'm facing a problem. I was running Gio Pro 1.4 on my phone with A2SD and I noticed the battery was draining fast and I saw the key lights were on even with the key lock so I shut the phone down. When I tried to start it again the phone didn't do anything. I took the battery off, tried downloading, recovery, ram dump mode and only the last one worked but after some time it stopped working also. I tried a friend's battery and nothing. I got home and connected the phone to the charger and everything was normal. I could start the phone, enter recovery, etc. Without the charger the phone was the same, didn't start. I tried a hard reset and nothing so I tried to flash to clockworkmod recovery and to cyanogen rom. The installation went good but I still had that problem. Then I tried to wipe the battery stats, dalvik cache, etc and still the same. I then tried to flash the clockworkmod recovery with odin and the same. I then flashed with an original firmware with every file (incluiding modem) and the phone was working good and I could start without the charger. Now I installed the cyanogen and cwm recovery again and the problem reappeared. Help please?
EDIT: Guys, reflashed with cyanogen and it is now working...Weird..
Just a little bump since the problem came back...
Already flashed to and ICS Rom, back to official rom and the problem's still there, even with the official rom. Any help guys? My battery's in good condition, already wiped everything...I can't find the solution...
EDIT: Sometimes it boots, sometimes it doens't...
the13thing said:
Just a little bump since the problem came back...
Already flashed to and ICS Rom, back to official rom and the problem's still there, even with the official rom. Any help guys? My battery's in good condition, already wiped everything...I can't find the solution...
EDIT: Sometimes it boots, sometimes it doens't...
Click to expand...
Click to collapse
what official rom do you use? try to avoid using KS2/KS5 baseband. they have bug when turning on the phone.
Ks5 doesnt
Sent from my GT-S5660 using xda premium
I fixed it mine
I had the same problem for several months now.. Yersteday i've got a new micro SD card, bigger, and i decided to reinstall to the latest stock ROM 2.3.6, i wiped data, cache partition, Dalvik Cache and Battery Stats and now my Gio is booting like a charm, whithout being connected to the cargher or USB cable. My guess is that the card was defective...
danyrolux said:
I had the same problem for several months now.. Yersteday i've got a new micro SD card, bigger, and i decided to reinstall to the latest stock ROM 2.3.6, i wiped data, cache partition, Dalvik Cache and Battery Stats and now my Gio is booting like a charm, whithout being connected to the cargher or USB cable. My guess is that the card was defective...
Click to expand...
Click to collapse
Hmmm maybe but I doubt that the card would cause such a problem...
Sent from my Optimus Me using xda premium
Back to the original problem of the yellow triangle and not charging. I googled over and over to find a solution, I came across some askme website that had over 30 people say that DROPPING the Samsung Gio from 2 feet will fix it. I decided NOT to do that but slam the phone slightly hard on a desk. It totally fixes this icon (remove the sim and micro sd before slamming it semi hard).
People were dropping it from 2 feet, but I found slamming it (not hard!) fixes it right away. Now the yellow charging icon is gone and my Samsung Gio GT-S5660!
yuprules said:
Back to the original problem of the yellow triangle and not charging. I googled over and over to find a solution, I came across some askme website that had over 30 people say that DROPPING the Samsung Gio from 2 feet will fix it. I decided NOT to do that but slam the phone slightly hard on a desk. It totally fixes this icon (remove the sim and micro sd before slamming it semi hard).
People were dropping it from 2 feet, but I found slamming it (not hard!) fixes it right away. Now the yellow charging icon is gone and my Samsung Gio GT-S5660!
Click to expand...
Click to collapse
This is rather interesting. It could point to a hardware problem. Anyway I also wouldn't recommended dropping it from 2 ft
Sent from my LG-P350 using xda premium
Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.
Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App
Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened
Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.
Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?
Ok so I so I have suffered from authentication errors and ridiculously poor WiFi range since I rooted my phone. Or most probably since I flashed a custom Rom (omega) for the first time..
Now, after endless research and lots of trial and error (or as I say, terror) I have finally found a solution. Although this is NOT and ideal solution, it solved my problem. Not being able to use WiFi at work when I'm only around 7 meters from the server is an absolute no no for me! Especially twinned with the frustration of 30 attempts to authenticate and still having 70 odd % signal and yet no connectivity.
So here goes..
For me.. disabling power saving mode via *#0011# did NOT work.
Nor did flashing back to stock without root.
Flashing cm9 did NOT work.
Flashing stock did Not work. And full cwm wipe didn't work either. And all other combinations.
So by hard work, research into other threads, Lots of terror and pure luck. I fixed my problem.
Apologies if this does not work for you.. but if u Have simular problems to me. I'm sure it will work. So follow these steps
1. back up via android. Copy backup to pc if u try this and it doesn't work u cant go back to before. Also backup and apps or pics music etc to pc.
2. Download latest stock Rom with root
http://forum.xda-developers.com/showthread.php?t=1704185
Thanks to wanam!
3. full Wipe, wipe cache partition, wipe dalvik cache. Flash latest wanam stock Rom. And repeat the wiping in recovery again. Full, cache and dalvik. Fix permissions.
4. Now reboot. And test if u still have the problem. As I did still. If not... yay you!
5. Do a hard reset. Yes a factory reset. NOT a full wipe via recovery. A reset via settings/backup and wipe/factory personal data reset. WARNING by doing this you will lose all app settings. All android backups and all data on internal storage. I believe this will also leave your ext sd contents unusable so ALWAYS backup to pc!
6. Repeat steps 3 and 4 again. This made my WiFi range and connectivity problems
Disappear! Although I still had authentication errors
7.Then repeat step 5 and see your outcome. It's seems for me atleast, that a double wipe was necessary. I'm not sure about you guys.
I hope this works for you all!
Thank me if it did or If I've helped in anyway!
Happy to answer questions! Noob or not.
Thanks to JJE and d4seeker for there effort in trying to help me!
Sent from my GT-I9300 using xda app-developers app
Sent from my GT-I9300 using xda app-developers app
Thanks for the info!
slking1989 said:
3. full Wipe, wipe cache partition, wipe dalvik cache. Flash latest wanam stock Rom. And repeat the wiping in recovery again. Full, cache and dalvik. Fix permissions.
Click to expand...
Click to collapse
I'm fairly sure you can skip the second wiping here and go straight to factory reset, correct?
Yeah most probably. But I thought I'd just share with you exactly how I fixed this problem.
Let me know how you get/got on with it.
Sent from my GT-I9300 using xda app-developers app
Does anyone know why this happens?
Sent from my GT-I9300 using xda app-developers app
Congratulations !
But then , you rooted or stay unroot ?
Best regards
Stay rooted
Sent from my GT-I9300 using xda app-developers app
Did this work for u mate?
Sent from my GT-I9300 using xda app-developers app
slking1989 said:
Did this work for u mate?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I put a stock Rom and rooted. Since then I got WiFi problems.then I flashed again the Stock Rom but I didn't root and it seems to work fine. Once after I've read your post I'm thinking about getting root again but maybe I'll wait to see if I have now OTA upgrades or I haven't (i wouldn't like to loss them .
Ok so I still have authentication errors. But only very few. And it's not affecting me. Seems strange that I am stock and I've reset. Must be faulty hardware. Surely. It's much better than before. Very usable. But still occasional errors. Someone must know more about this...
Sent from my GT-I9300 using xda app-developers app
Hi,
I also got problems similar to yours, I believe.
I always flashed ROMs from sam mobile. Since the 1st one after the original, I was bound to use the #*0011# workaround.
I believe after I flashed CM11 recently wifi didnt behave ok anymore.
Then I wiped everything a lot of times (not as you suggested though), installed a lot of ROMs,
but wifi only connects within a certain range from the router.
There are a lot of glitches to that, as you may have noticed as well. For instance, the 1st time
you associate to a network, usually it connects straight away. After that, it's a nightmare.
But one thing that made me believe this is a rom/kernel/root issue, is this: you try and fail to
connect. Go to the service screen via #*0011#. The wifi module/process don't know the tech term,
is unable to show the bssid or even the ssid, although any play app can. That is very very odd.
Also, in this scenario sometimes when you can connect, #*0011# info is weird, like rssi -200,
speed -1Mbps, did you see those numbers too?
All in all, I don't think your solution is far fetched, it could really be needed multiple wipes and all.
I'm still trying another regions ROMs, like 4.3 Switzerland, and I plan to downgrade until something better happens.
Thing is, I already flashed the -original- ROM, which was ICS, but wifi was not ok. That is what
put me on defcon 1... lol...
Well, good luck for us...
cheers,
Xezi
slking1989 said:
Ok so I so I have suffered from authentication errors and ridiculously poor WiFi range since I rooted my phone. Or most probably since I flashed a custom Rom (omega) for the first time..
Now, after endless research and lots of trial and error (or as I say, terror) I have finally found a solution. Although this is NOT and ideal solution, it solved my problem. Not being able to use WiFi at work when I'm only around 7 meters from the server is an absolute no no for me! Especially twinned with the frustration of 30 attempts to authenticate and still having 70 odd % signal and yet no connectivity.
So here goes..
For me.. disabling power saving mode via *#0011# did NOT work.
Nor did flashing back to stock without root.
Flashing cm9 did NOT work.
Flashing stock did Not work. And full cwm wipe didn't work either. And all other combinations.
So by hard work, research into other threads, Lots of terror and pure luck. I fixed my problem.
Apologies if this does not work for you.. but if u Have simular problems to me. I'm sure it will work. So follow these steps
1. back up via android. Copy backup to pc if u try this and it doesn't work u cant go back to before. Also backup and apps or pics music etc to pc.
2. Download latest stock Rom with root
http://forum.xda-developers.com/showthread.php?t=1704185
Thanks to wanam!
3. full Wipe, wipe cache partition, wipe dalvik cache. Flash latest wanam stock Rom. And repeat the wiping in recovery again. Full, cache and dalvik. Fix permissions.
4. Now reboot. And test if u still have the problem. As I did still. If not... yay you!
5. Do a hard reset. Yes a factory reset. NOT a full wipe via recovery. A reset via settings/backup and wipe/factory personal data reset. WARNING by doing this you will lose all app settings. All android backups and all data on internal storage. I believe this will also leave your ext sd contents unusable so ALWAYS backup to pc!
6. Repeat steps 3 and 4 again. This made my WiFi range and connectivity problems
Disappear! Although I still had authentication errors
7.Then repeat step 5 and see your outcome. It's seems for me atleast, that a double wipe was necessary. I'm not sure about you guys.
I hope this works for you all!
Thank me if it did or If I've helped in anyway!
Happy to answer questions! Noob or not.
Thanks to JJE and d4seeker for there effort in trying to help me!
Sent from my GT-I9300 using xda app-developers app
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hey guys,
So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.
Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.
Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)
I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.
Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.
Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.
Thanks so much for any and all help.
OneIdiotInATree said:
Hey guys,
So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.
Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.
Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)
I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.
Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.
Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.
Thanks so much for any and all help.
Click to expand...
Click to collapse
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
Sent from my SGH-T999 using xda app-developers app
monkeypaws said:
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It auto-wiped to upgrade to 4.2.2, so if there is a way to downgrade it to get it to work, I'd love to know. At the moment all I can access is the Clockwork Mod boot list from the vol+pow+home route. Did a battery pull and entered recovery. Still nothing. If I try to boot without going through the vol+pow+home method, it just vibrates and then nothing.
Update recovery.
Wipe everything except sd cards.
Install rom.
Install Gapps.
Factory reset.
Done.
Aerowinder said:
Update recovery.
Wipe everything except sd cards.
Install rom.
Install Gapps.
Factory reset.
Done.
Click to expand...
Click to collapse
I formatted everything from that vol+pow+home menu.
Gapps? Is that something I should install from SD?
Sorry, I'm just a bit overwhelmed by something I thought would be easy...
OneIdiotInATree said:
I formatted everything from that vol+pow+home menu.
Gapps? Is that something I should install from SD?
Sorry, I'm just a bit overwhelmed by something I thought would be easy...
Click to expand...
Click to collapse
Gapps are Google apps that are required to flash after flashing an aosp ROM. They are usually included as a separate download in the first post of the wrong you are downloading. Make sure you download the right gapps. There shod be a setti ng in cwm to turn on USB connection when connected to comp. So you can load the gapps to your SD card. Then re wipe phone through recovery, reflash the rom , the in the same menu reflash gapps. Then reboot. It should then load properly . Otherwise. If you can access download mode, restore stock rom with Odin, reroot and try again from step one.
Sent from my SGH-T999 using xda app-developers app
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
Sent from my SGH-T999 using xda app-developers app
SamsungGui said:
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?
At this point, I just want to restore to the original loadout, but I've been unable to do that too.
By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
OneIdiotInATree said:
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?
At this point, I just want to restore to the original loadout, but I've been unable to do that too.
By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
Click to expand...
Click to collapse
Make sure you have the ROM of choice and compatible Google apps on your SD card.
Now do the following
1. Pull battery out of phone
2. Put battery into phone
3. Boot into recovery (volume +, home button, power button)
4. Wipe cache
5. Wipe dalvik cache
6. Wipe data/factory reset
7. Install ROM
8. Install gapps (Google apps)
9. Wipe cache
10. Wipe dalvik cache
11. Reboot phone
Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
707BeastMode707 said:
Make sure you have the ROM of choice and compatible Google apps on your SD card.
Now do the following
1. Pull battery out of phone
2. Put battery into phone
3. Boot into recovery (volume +, home button, power button)
4. Wipe cache
5. Wipe dalvik cache
6. Wipe data/factory reset
7. Install ROM
8. Install gapps (Google apps)
9. Wipe cache
10. Wipe dalvik cache
11. Reboot phone
Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
Click to expand...
Click to collapse
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
Okay follow this to get to stock and make sure it can at least do that. http://forum.xda-developers.com/showthread.php?t=2136921
Sent from my SGH-T999 using xda app-developers app
OneIdiotInATree said:
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
Click to expand...
Click to collapse
Are you sure you have a T-Mobile phone?
monkeypaws said:
Okay follow this to get to stock and make sure it can at least do that. http://forum.xda-developers.com/showthread.php?t=2136921
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the set of instructions, but I am unable to either start it (power button), put it in cwm (pwr+up+home) or download mode as mentioned (pwr+down+home). I don't get a vibration; I don't get anything. Is this totally bricked now? Since the device isn't on, I can't do anything with Odin or the SD card.
What country do you live in, and how did you acquire your phone? Looks like you maybe have the intl version.
I would say try to get into download mode with the physical bottons if that dint work try a jig u can get on ebay like 5 bucks they are always handy.if u can get in to dl mode odin a root66.tar then install recovery.if that dobt worj u prib install liquid rom but fir diff device abd hard brixk u f that case hope u have insurance ti replace they will never know u rooted ir have it jtaged
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
lojak29 said:
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
Click to expand...
Click to collapse
it honestly sounds like he has he international version not the US variant. so i think thats the mistake not the phone
lojak29 said:
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
Click to expand...
Click to collapse
99% of the bricking is user error...the reason for the increase in "bricked" topics is cause by the amount of users of the T999...its the most heavily used phone by a wide margin now.
Ive far from an expert but have been flashing since the G1 days and have experience with many phones...in my opinion the t999 is darn near unbrickable unless you didnt follow the directions or use a reputable developer when selecting a rom...
To the OP:
What is the actual model of your phone ? you came with an issue and have not really posted much about the specifics of your phone...
sounds like your phone is not partitioned correctly which probably happened by not following the correct directions
there is so much more info needed to diagnose your issue its silly...
Ive been using wicked roms from day one on the t999 and I dont remember seeing anyone hardbrick a phone yet and there are thousands of users using wicked roms...
---------- Post added at 10:58 AM ---------- Previous post was at 10:16 AM ----------
Also...was your phone charged when you last tried to flash something? long ago my phone died while flashing ( lessoned learned) ...
pull the battery for awhile...put it back in and try to charge it...
then try to odin back to stock after its charged...
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).
I also wonder if this phone is actually an International version instead of the T-Mobile one.
OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
Pennycake said:
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).
I also wonder if this phone is actually an International version instead of the T-Mobile one.
OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
Click to expand...
Click to collapse
OP just has to remove the battery cover and battery and bam! There's a label with Sammy's logo along with device model and other info about the phone.
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
hey, ive been feeling that my phone is getting warmer throughout the past week and ive just been ignoring it, however i decided to checkout what numbers its reaching....55 degrees c...indoors...browser app running only ,using mobile data ONLY...wtf is this? is it a battery deffect?
OmarKnows said:
hey, ive been feeling that my phone is getting warmer throughout the past week and ive just been ignoring it, however i decided to checkout what numbers its reaching....55 degrees c...indoors...browser app running only ,using mobile data ONLY...wtf is this? is it a battery deffect?
Click to expand...
Click to collapse
1. Upper portion or Lower portion?
2. Stock ROM or Custom ROM?
3. 4.3 or 4.4 based?
4. Battery drain or not?
5. ROM flashing history?
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
1. Upper portion or Lower portion?
2. Stock ROM or Custom ROM?
3. 4.3 or 4.4 based?
4. Battery drain or not?
5. ROM flashing history?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
1.upper portion
2.custom rom (paranoid android v 4.6 beta 2)
3. 4.4 based
4.not really but kinda, usually lasts around 10 hours of average use
5.started out stock rom, flashed latest phoenix, cyanogenmod, dn3, and paranoid android
OmarKnows said:
1.upper portion
2.custom rom (paranoid android v 4.6 beta 2)
3. 4.4 based
4.not really but kinda, usually lasts around 10 hours of average use
5.started out stock rom, flashed latest phoenix, cyanogenmod, dn3, and paranoid android
Click to expand...
Click to collapse
Clearly CPU overheating is the issue. I too had overheating issue. I too did flash several ROMs. But, it all started with DN3 ROM. After that no matter what I flashed my CPU would heat up quickly.
Issue is closely related to kernel. It happens due to migration from one ROM to another. In most cases the wipes and installs are clear. But sometimes things go wrong unexpectedly.
You can try some solutions:
1. Stop indexing service with Titanium and check.
If warm again,
2. Power down the phone, remove SD card and wait for device to cool down. Restart and check.
Still not then
3. U will have to flash stock recovery on your device and do a wipe/ factory reset from the menu. (Of course u will lose all the data on internal SD card). Check for at least 2 battery recycles.
If not then,
4. Backup everthing EFS, CONTACTS,etc and flash stock rom via pc odin. When phone reboots and reaches language screen. Power it down, go to recovery and do a wipe/ factory reset.
This should surely solve your overheating problem.
If not, it might be a hardware issue.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Clearly CPU overheating is the issue. I too had overheating issue. I too did flash several ROMs. But, it all started with DN3 ROM. After that no matter what I flashed my CPU would heat up quickly.
Issue is closely related to kernel. It happens due to migration from one ROM to another. In most cases the wipes and installs are clear. But sometimes things go wrong unexpectedly.
You can try some solutions:
1. Stop indexing service with Titanium and check.
If warm again,
2. Power down the phone, remove SD card and wait for device to cool down. Restart and check.
Still not then
3. U will have to flash stock recovery on your device and do a wipe/ factory reset from the menu. (Of course u will lose all the data on internal SD card). Check for at least 2 battery recycles.
If not then,
4. Backup everthing EFS, CONTACTS,etc and flash stock rom via pc odin. When phone reboots and reaches language screen. Power it down, go to recovery and do a wipe/ factory reset.
This should surely solve your overheating problem.
If not, it might be a hardware issue.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
well this hasnt started from dn3, it was in the middle of cm 11 and well i already flashed stocked rom and re-rooted and everything a few days ago for other reasons, still over heating, could it be the battery is faulty?
also how exactly do i stop indexing service ?
OmarKnows said:
also how exactly do i stop indexing service ?
Click to expand...
Click to collapse
U have to wipe/factory reset the phone after clean install using stock recovery.
Sent from my GT-N7100 using Tapatalk
Sorry for late reply
So im trying this now, flashing stock rom at this very moment, then ill power down at language screen and factory reset via stock recovery, really hope it works.
ps:sorry for late reply, ive had alot of studying todo recently