STUCK on welcome screen & Dying batteries - Galaxy Note II Q&A, Help & Troubleshooting

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

Related

Power on issue

Hi , I'm using a custom rom (Revolution 9.3) and have a strange issue.
I normally turn my phone off on a night to put it on charge. When the phone is fully charged it now turns itself back on. Is this normal and is there a way to stop it doing it. I have not had this problem either with the official rom or with other phones i have had with custom roms installed.
The other issue is when i wake the phone in the morning it has the "people" app open.To get rid of this i have to press the home button which crashes Sence .Once Sence reloads all is fine all day .Apart from this im very impressed with the Rom so dont really want to change it.
These are minor issues and not the end of the world but i would like to know if there is a cure. I'm fairly experienced in flashing roms but have been unable to locate any reference to this on this site. I have had to post on here as i havent the 10 posts to allow me to put in the developers section for this ROM. Thanks
I think it's clockworkmod recovery that turns the phone on when nearly charged.
Martintxx said:
Hi , I'm using a custom rom (Revolution 9.3) and have a strange issue.
I normally turn my phone off on a night to put it on charge. When the phone is fully charged it now turns itself back on. Is this normal and is there a way to stop it doing it. I have not had this problem either with the official rom or with other phones i have had with custom roms installed.
The other issue is when i wake the phone in the morning it has the "people" app open.To get rid of this i have to press the home button which crashes Sence .Once Sence reloads all is fine all day .Apart from this im very impressed with the Rom so dont really want to change it.
These are minor issues and not the end of the world but i would like to know if there is a cure. I'm fairly experienced in flashing roms but have been unable to locate any reference to this on this site. I have had to post on here as i havent the 10 posts to allow me to put in the developers section for this ROM. Thanks
Click to expand...
Click to collapse
did u perform full wipe, erased cache and dalvik cache before flashing ROM
vivek_bhoj said:
did u perform full wipe, erased cache and dalvik cache before flashing ROM
Click to expand...
Click to collapse
Yes did full wipe with super wipe as per instructions .Also did a cache wipe and dalvik cache wipe before and after install.
Thanks for the info about clockwork - it hasn't had this effect on previous phones plus when i flashed back to stock rom but still with clockwork recovery it doesn't turn on when it reaches full charge. Presuming it is clockwork is there a way to stop it ?
Open to any more suggestions though.
It's one of those things that is bugging the hell out of me but i can live with it for the extra functionality the rom gives me and the better battery life.
Little worried that the extra on time it is giving me will have a long term effect on battery life and also dont want the phone going off with text at two in the morning.

[Q] Note II dying, Please help!

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

[Q] Tmobile Samsung Galaxy S3 bricked after install of LiquidSmooth

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|

[Q] note 2 warming up fast

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

Best ROM for S4 Mini?

Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.

Categories

Resources