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
Related
Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
mrkupochan said:
Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
Click to expand...
Click to collapse
Could you please specify what Rom and version that you flashed?
Sent from the rabbit hole.
Did you install one of the other custom recoveries manually yet? Btw. IMHO TWRP is the best anyways. Did you do a full wipe before installing new ROM? what kernel/version are you on?
I went from using the Android revolution HD 10.0 version with stock kernel, I changed to AllianceROM N7100 XXDMA6 JB V1.0 but didn't find it smooth enough so I swapped back to Revolution, thats when I found twrp had installed.
I've tried flashing the stock recovery and i'm still getting the same issue.
I've since reflashed cwm but this hasn't solved the problem unfortunatley.....No idea what to do
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Martux76 said:
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Click to expand...
Click to collapse
All done, several times, no difference
Have you considered it could be sudden death syndrome?
You should have nothing to worry about in terms of it dying, since you have a very recent base rom (dma6), which include safeguards against it.
When it freezes, have you tried waiting to see if the phone responds after you press the Home Button?
I ask this because I've read reports of people waiting for over 20 minutes for the phone to become responsive again after pressing the home button when in standby.
Another thing: have you ever flashed a full stock rom after DLL7 (including DMA6)? I ask this because DLL7 and later include a new bootloader that *supposedly* helps address the sudden death issue. It doesn't hurt to try anyway.
Sent from my GT-N7100
If ur pc recognises ur phone in download mode seaech the forum for rescue firmware (it comes with pit file) and flash it with odin..u should be sorted then.
Sent from my GT-N7100 using Tapatalk 2
Hi everyone,
I've searched everywhere for a solution so please help!
Basically i've had my note 2 for around 3 months and it keeps freezing (so frustrating).
Surprisingly this happend on stock before i even rooted or anything like that.
I remember installing some game from the app store that started the freezing but i re flashed it on stock and this was ages ago. I went to samsung and they flashed it but they said that they dont know what it is. Without sending my baby away i'd love to get this fixed.
I've tried rooting, unrooting, different roms, clearing all the cashes.. apps to reduce lagg (incase it was something inducing it).
Im really clueless where to go with it..
(Freezes up to 5 times a day)
(On 4.1.2 because of custom rom)
(On Stock rom now trying to fix but still on 4.1.2)
Thanks for all your help in advance!
legendberry said:
Hi everyone,
I've searched everywhere for a solution so please help!
Basically i've had my note 2 for around 3 months and it keeps freezing (so frustrating).
Surprisingly this happend on stock before i even rooted or anything like that.
I remember installing some game from the app store that started the freezing but i re flashed it on stock and this was ages ago. I went to samsung and they flashed it but they said that they dont know what it is. Without sending my baby away i'd love to get this fixed.
I've tried rooting, unrooting, different roms, clearing all the cashes.. apps to reduce lagg (incase it was something inducing it).
Im really clueless where to go with it..
(Freezes up to 5 times a day)
(On 4.1.2 because of custom rom)
(On Stock rom now trying to fix but still on 4.1.2)
Thanks for all your help in advance!
Click to expand...
Click to collapse
try flashing latest stock rom and dont install any apps and play around with it, if it still freezes they you may have a fauilty unit
do you notice the phone heating up at all if so try removing any cases/pouch you may have
brockyneo said:
try flashing latest stock rom and dont install any apps and play around with it, if it still freezes they you may have a fauilty unit
do you notice the phone heating up at all if so try removing any cases/pouch you may have
Click to expand...
Click to collapse
Hi Broky
Its on stock at the moment and i've taken my case of because i thought it might be that before....
When i was in the samsung store it was flashed to the stock and i opened skype after the flash and it froze....
Dont know if this is much help?
Thanks!
Try super wipe script by zoot.
Then flash stock rom.
Don't tell it samsung or google account.
Play around with it like browse or do anything. If it still freezes then I am sorry then brockyneo is correct.
Sent from my GT-N7100 using xda app-developers app
Could be a faulty ram chip. Or flash chip. I don't think check disk works on flash drives. But if it was a hard drive that's be the fix.
Sent from my GN2 using XDA app.
ya it shouldnt freeze if its been flashed back to stock rom,especially through odin as it near bullet proof
maybe try what UtkarshGupta with the superwipe and try again with a stock rom
if not then you maybe looking at a faulty unit :crying:
brockyneo said:
ya it shouldnt freeze if its been flashed back to stock rom,especially through odin as it near bullet proof
maybe try what UtkarshGupta with the superwipe and try again with a stock rom
if not then you maybe looking at a faulty unit :crying:
Click to expand...
Click to collapse
Thanks a lot...
Is this quite a rare case? Im un able to re flash it at the moment but if it wasn't a faulty unit... what else could be the issue?
Thanks again for the help!
legendberry said:
Thanks a lot...
Is this quite a rare case? Im un able to re flash it at the moment but if it wasn't a faulty unit... what else could be the issue?
Thanks again for the help!
Click to expand...
Click to collapse
What firmware do you have? 4.1.1 or 4.1.2? If you are on a safe kernel (latest 4.1.2 for example) you could try "Dummy File Generator" from Playstore. (there are many reports with succesfull fixes on freezes.) Or, better, take a look at this thread, everything you want to know is here: http://forum.xda-developers.com/showthread.php?t=2133401
zetlorf said:
What firmware do you have? 4.1.1 or 4.1.2? If you are on a safe kernel (latest 4.1.2 for example) you could try "Dummy File Generator" from Playstore. (there are many reports with succesfull fixes on freezes.) Or, better, take a look at this thread, everything you want to know is here: http://forum.xda-developers.com/showthread.php?t=2133401
Click to expand...
Click to collapse
Hi,
thanks for responding! Im on 4.1.2 at the moment and il try the dummy file generator.... How does that exactly work?
Thanks again,
legendberry said:
Hi,
thanks for responding! Im on 4.1.2 at the moment and il try the dummy file generator.... How does that exactly work?
Thanks again,
Click to expand...
Click to collapse
Hey legendberry! Did you fix your problem? I'm having the same issue on a stock rom. Resetting and wiping didn't help so I sent mine for repair but it got sent back to me unrepaired and the issue is still there
I have stock note 2, running 2.1 worked flawless since day 1 (was first release in France). Last 2 days been freezing. Have freed up space in internal and external sd. Still happens. Removed some apps, still happens. Reboot, sometimes it works for while then locks up. Very frustrsting as this is business phone.
......
I am in the same situation, because my Note 2 in the last few days has been freezing with maxed out cpu (as reported by the Cool Tool app).
I am now in the process of wiping everything and restoring in the feeble hope to overcome the problem.
Edit: i have wiped everything by formatting with Odin and reloading firmware, then restoring nandroid backup. So far so good, almost 24h without freezing.
Edit2: 2nd day, started freezing again 0
Same problem here, since 2 days my Note 2 freezes all the time, sometimes with 100% cpu load. Sometimes I can use it for a couple of hours, sometimes after reboot it freezes instantly. :S
I did a factory reset (stock 4.1.2), wiped everything but still the same issue...
Very, very frustrating!
To users above: When did you get your Note 2? I've had mine since Oct 10, 2012.
R: Note 2 constant freezing issue
Me too, phone bought in October 2012.
Today I flashed latest Italian firmware, MB2, and started over. No freezes. Even filling sdcard with dummy file generator, which in previous firmware (French MB2) gave several freezes.
Ok.
Then restored nandroid, data partition only, and wiped cache and dalvik. Lots of freezes again, device almost unusable.
So I thought what's the difference? When freshly flashed phone had Touchwiz, while after restore had Go Launcher.
Uninstalled Go Launcher. Bingo.
No freezes anymore so far.
Weird, uh?
I'll report how it behaves in next hours.
Edit: it was go launcher indeed. It's been updated for a reported crashes reboots problem. Now my device is rock steady.
Sent from my GT-N7100 using xda premium
Currently having the same issue. What i had done is cleanwipe and restore to factory setting (4.1.2).
Just the moment i finished setting up, the problem occured.
After root and vold.fstab trick I saw 2 times, that my Ace 2 randomly reboots. Maybe phone reboots many times in one day, I don't know because I use another phone for daily uses. What to do? Factory reset, etc.?
EDIT: I remember, that I tried to flash modified_vold_Ace_2.zip with standard recovery, but without any luck. Later I tried to flash same file with CWM and everything went fine. Maybe my system is corrupted? Any help or advice is very appreciative.
Winudert said:
After root and vold.fstab trick I saw 2 times, that my Ace 2 randomly reboots. Maybe phone reboots many times in one day, I don't know because I use another phone for daily uses. What to do? Factory reset, etc.?
EDIT: I remember, that I tried to flash modified_vold_Ace_2.zip with standard recovery, but without any luck. Later I tried to flash same file with CWM and everything went fine. Maybe my system is corrupted?
Click to expand...
Click to collapse
Reflash system using ODIN , make full factory wipe and watch for results
michal_ag said:
Reflash system using ODIN , make full factory wipe and watch for results
Click to expand...
Click to collapse
I can do that, but where to find files? I have files for Galaxy Tab or S II, but not of Ace 2.
Winudert said:
I can do that, but where to find files? I have files for Galaxy Tab or S II, but not of Ace 2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2118119
:good:
I have 11 android devices and I did not have so much work to root device properly (?). Galaxy Ace 2 still randomly reboots. Maybe I'm doing something wrong? I have latest official stock GB, I'm using this guide - http://forum.xda-developers.com/showthread.php?t=2118119
And why ODIN don't wipe my phone? Just did factory reset after ODIN procedure?
EDIT: I remember I got my Ace 2 at 03-21. Over three days, until yesterday, I have not noticed random reboots, but until yesterday I not tried to root my phone or install CWM or any other stuff. I think root is ok, so my phone maybe reboots because of "vold.fstab" trick or Antsm's kernel I used. Right now my phone is on stock GB and I will use it for few days. We will see.
My Ace 2 reboots when it gets its ram full. even if I clear my ram, it only leaves less than a 100 free to use. I don't know what happens to the other ram so that's why I always experience lag and so to fix it, I restart my phone. It's a bit annoying.
raansu16 said:
My Ace 2 reboots when it gets its ram full. even if I clear my ram, it only leaves less than a 100 free to use. I don't know what happens to the other ram so that's why I always experience lag and so to fix it, I restart my phone. It's a bit annoying.
Click to expand...
Click to collapse
What ROM are you using? Stock? What kernel? You did "vold.fstab" trick? If my phone will reboot two more times in one week (I'm tracking it), I will bring him to service for sure. I did full wipe and installed stock firmware from SamMobile.
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|
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
TALBR said:
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
Click to expand...
Click to collapse
OK... so ODIN is working, eh? That helps the situation. Now...
1) If you can get ADB working, probably.
2) By flashing a pit file through either ODIN or (custom) recovery. (I prefer using recovery as it's safer.)
3) Not completely sure, though it (might) be a hardware issue.
P.S. You should NEVER flash stock ROM unless you have a bricked device. I rather you flash CM11 even if you have a bricked device. I never trust stock ROM.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
TALBR said:
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
Click to expand...
Click to collapse
I had that situation of storage earlier.
u have no choice but to wipe all.
if u still can connect ur device to a pc, i would suggest to copy ur data on ur internal storage to ur pc.
after that, earlier what I did was flash the zoot script from cwm and do a custom mega wipe. of course ur internal storage will be wiped. clean until all the folders nd files.
then reboot back to recovery to flash custom rom again.
if u r not rooted the only way is to factory reset full wipe system data nd cache.
wipe cache only won't solve the problem of internal storage.
to be frank, u jump from 4.3 to 4.4.2, u have to factory reset. too many users try to avoid this because lazy to resetup nd backup. but u have no choice.
Sent from somewhere under the sky, at the corner of this rounded earth.
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Irwenzhao said:
OK... so ODIN is working, eh? That helps the situation. Now...
1) If you can get ADB working, probably.
2) By flashing a pit file through either ODIN or (custom) recovery. (I prefer using recovery as it's safer.)
3) Not completely sure, though it (might) be a hardware issue.
P.S. You should NEVER flash stock ROM unless you have a bricked device. I rather you flash CM11 even if you have a bricked device. I never trust stock ROM.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
not all ppl like Cm / aosp.
and stock rom is not bad. it is just most ppl don't like to do a clean flash.
without stock rom, u can't use the full feature of spen, and it defeat the purpose of having spen.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
I had that situation of storage earlier.
u have no choice but to wipe all.
if u still can connect ur device to a pc, i would suggest to copy ur data on ur internal storage to ur pc.
after that, earlier what I did was flash the zoot script from cwm and do a custom mega wipe. of course ur internal storage will be wiped. clean until all the folders nd files.
then reboot back to recovery to flash custom rom again.
if u r not rooted the only way is to factory reset full wipe system data nd cache.
wipe cache only won't solve the problem of internal storage.
to be frank, u jump from 4.3 to 4.4.2, u have to factory reset. too many users try to avoid this because lazy to resetup nd backup. but u have no choice.
Sent from somewhere under the sky, at the corner of this rounded earth.
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
not all ppl like Cm / aosp.
and stock rom is not bad. it is just most ppl don't like to do a clean flash.
without stock rom, u can't use the full feature of spen, and it defeat the purpose of having spen.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Or Ditto N3, stock ROM has loads of bugs (kitkat)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Irwenzhao said:
Or Ditto N3, stock ROM has loads of bugs (kitkat)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
I agree that DN3 is great rom.
I also agree that sometimes official firmware also have bugs.
but, I don't agree that custom rom will free of bugs that official have it.
certain bugs will still remain.
don't forget, custom rom is build on Samsung stock base with some enhancement to feel better in smoothness, functions, battery life, as well as user interface.
Sent from somewhere under the sky, at the corner of this rounded earth.
Not sure why there's an asop vs tw debate going on here... anyway, assuming the op's history is accurate, this sounds like hardware failure