Related
I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
From what you said...yes....I guess its time to plead ignorance and get another replacement
Sent from my nightly EVO
So what went wrong ? I've done this same method about 6 other times with my previous phone and friends phones with absolutely no problems. Any insight so this doesn't happen again ? I'm on my way through traffic to a sprint store to pick up another one and want to root it but not brick this guy too.
My guess would be that it was either interrupted or a bad install...I really couldn't tell you though
Sent from my nightly EVO
tayden812 said:
I'm hoping I did not brick this thing because I literally just got it replaced because of screen issues and a blown speaker and broken usb port. Anyway, got the replacement home and wasted no time to use unrevoked 3 on it. Worked great. installed Fresh Evo Rom 4, installed perfect. Tested - working fine. Then I tried installing the Radio, Wimax, NV, and PRI updates. Radio and Wimax installed correctly. Went to install the NV and PRI updates and it just said installation aborted ( I was driving to pick up dinner for the family so I just let it run for a few minutes then checked on it). I then decided to just restart and start putting in my contacts and stuff. It restarted to a screen with a box and what looks like a droid jumping out of it. Removed the battery and tried again after a minute or so, same thing. Tried the VOL - and Power method to boot into Hboot, same screen. Removed my SD card per some instructions on here , same screen. Replaced the battery with another one I had per some people getting the same issue here , same thing. Frustrated I ate dinner and came back to it. Now it wont turn on at all. No charging LED light at all. Tried both batteries, one red and one black, no go. Doesnt boot at all and doesnt look like its charging. Am I royally f*kt ? Anyone have any ideas for me to try ?
Click to expand...
Click to collapse
Whenever you flash a radio, NV, or PRI or something like that, when you first flash it, it then tells you that you need to reboot to complete the installation. When it reboots, you will see that odd screen, which will either be an arrow facing down with a phone, an arrow with a box, or some kind of a droid guy with a box or something. That is very important to not pull the battery during that phase (it's when it's actually writing the radio, or pri, or whatever), otherwise a brick is the result, 99% of the time. Never pull the battery during any kind of a radio flash whatsoever. As far as why it told you that the installation was aborted, I've got no idea on that one. Maybe the file you were trying to flash was corrupted, or something to that nature.
If you're sure the battery is charged up, yet you get no LED light when the phone is powered down and plugged in, the phone won't boot to the bootloader, and seems completely unresponsive, then you are most likely indeed bricked. Sorry for the bad news. Don't pull the battery during any kind of a flash, especially a radio, pri, wimax, hboot, recovery flash etc. Battery pull during flashing of important things = bad idea.
EDIT: after thinking about it for a few minutes, after you updated your radio and wimax (which you said updated successfully), did you complete the installation by rebooting? After you flashed the radio, did you reboot, and see the black screen with an arrow coming out of a box, or something like that (that screen varies based upon your hboot version or recovery version)? If not, and you just tried flashing all of them, one after the other, without rebooting inbetween each one...then that may be why the installation of the pri aborted. Then when you went to reboot, it tried to finish the installation of the radio and wimax (which if you didnt reboot initially after selecting to flash, those installations would not have been complete, so as soon as you tried to reboot, it'd have tried to finish writing the radio image, which appears to be where you pulled the battery out)
If I remember right, that screen is part of the radio update. After it flashes, when you reboot you will see that screen. You're supposed to wait until it finishes and it should send you back to the recovery screen. After that you can reboot into the rom.
I'm scratching my head though because you said the installation aborted. Maybe part of it flashed successfully but the rest didn't?
EDIT: Didn't see that the radio flashed successfully. If you can still get to that screen, letting it run it's course should eventually solve the problem.
EDIT 2: K2buckley beat me to the punch. At least I know I was right and not giving you wrong info. Sometimes it takes pulling the battery 20 or so times to actually brick the phone, so hopefully you can still recover.
My Evo + xda Premium App = This post.
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
tayden812 said:
Thanx for the quick responses. After the radio and wimax update it went back to the install from zip screen in clockwork. From there I ran the other update. I let it sit on that installation aborted screen as I was driving. I ran in , grabbed dinner, came back within 5 minutes and it was still on that screen. Thats when I figured I'd just put contacts and stuff after I remove the battery. Still didnt work. If I indeed "bricked" this phone, is there any way ANYONE can fix it ? HTC or otherwise ? BTW - I already bought a new phone. Just scared to root and stuff now. I mainly want root to put in ROMS that have better battery life. Although now I have 3 batteries for it because of this brick lol.
Click to expand...
Click to collapse
Unfortunately, if its bricked there's nothing that can be done. Since it doesn't turn on, sprint wont be able to tell it was rooted. Just be sure your SD card is "clean", and take it to sprint. See what they say about it. I'd just tell them it wont turn on. Still under 1 yr warranty...
Sent from my PC36100 using XDA App
Great idea. Never even crossed my mind to take it back. I know if they know its rooted they wont touch it which is why I was hesitant to take it back. I'm gonna try that tomorrow, thanks.
BTW - Any suggestions as to a ROM and kernel for absolutely the best battery life without sacrificing any of the Evo's stock options ?
Again, thanks for all the help guys.
On both Blazer (w/ rogue and Lost Kernel) and Calks 2.0 (only tried rogue) whenever I reboot my phone nine times out of ten, it hangs on the lockscreen with a random date and random time flashing back and forth between no signal and the regular status bar symbols. It is unresponsive to touch and repeats the process of the keys lighting up, screen comes on for about 4 seconds, keys turn off, screen turns off. Repeat... If I hit the power button, the pop up shows up but I can't touch anything so I end up having to do a battery pull and reflash the rom. I've re-downloaded both roms to rule out a bad copy. I over-wipe every time I flash a new rom formatting system, wiping data, cache, and dalvik, and then flashing Calk's format all.
I messed with it last night and it seems pretty random but more often than not, it happens. If I try to restore a nandroid I had made recently, it does the same thing. In other words, there were multiple instances where I flashed the rom, got it set up, booted to recovery to make a back up, and then it wouldn't boot back up NOR could I get my back up to boot up.
What in the hell could be causing this??? Please and 1000 thank you's!!!!
First of all, sorry to tell you I don't have the answer.
I have this exact same issue and have tried almost everything you have tried, (I didnt have a back up since I just got this phone not too long ago).
My issue started at work when my battery died really fast in the middle of the day after being fully charged. The phone got hot and I just pulled the battery to stop it. Then I came home and am having this exact same issues.
I've spent the last few hours working on resolving this without success. Hopefully someone out there knows how to resolve this issue.
Edit: I am on Rogue recovery 1.10 (cmw v 5.6.2.7) and on Blazer ROM [11/26/11] [v1.2]
Might be the rom since we are both on Blazer...Im gonna try another. Hmm we are on the same recovery too!
Thanks!
Why not flash back to stock and start over?
Sent from the future.
FIXED!!
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.
VegasEvo4G said:
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.
Click to expand...
Click to collapse
Yes this has been an ongoing issue and posted in a few places. Also remember that when Go Launcher updates this may happen to you again. You can always use adb and push a launcher over to your phone incase you find yourself stuck like this again. Or delete launchers so there is only 1 choice
I finally got rid of this loop. I was able to flash a rom via the recovery menu in clockworkmod, since for some strange reason it won't recognize my sd card now.
Playya, so if I wanted to push a recovery on my phone (I have clockworkmod v. 4.015 installed but it won't recognize the sd card no matter what I do to it), can I do this from Root Explorer? ADB? What commands would I use? I am on Linux and am looking for a guide. Thanks.
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
EVoorhees said:
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
Click to expand...
Click to collapse
yea that problem happens when some one flashed venom ROM or other sense based roms....check out my antivenom super wipe thread ....as for solution there really isnt one...buuut a good way to stop it from happening...everytime you do a backup or flash superwipe...every now and then just for the proventitive maintenance i super wipe aleast onces ever few weeks...doing that i havent had ANY death lag since the dawn of it
EVoorhees said:
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
Click to expand...
Click to collapse
Try connecting your phone to your PC, mounting as disk drive so the PC reads the card and not your phone. If the lag goes away then it could be something with the SD card maybe. Don't unroot yet before researching. Be sure you are checking md5 before flashing to ensure a good download. If you narrow down to a SD issue, remove any files you need, and wipe and reformat the card.
Sent from my Incredible 2 using xda app-developers app
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.
OK guys, long read but I really need some advice. Device is op3 running 3.2.8, magisk, phh superuser and exposed. Issue started while I was reading in news app, screen froze the the phone reboots. 1st time this has happened since I got the phone in June. Didn't think much if it. So I go back to reading in same app and after 5 min it happens again. Now I'm suspecting an issue. So I try one more time with same result. I figure an app update or something must be the problem so I reboot to TWRP(latest official version) and restore my last backup from the previous day. I boot up the phone and decide to just try some browsing. About 5 mins in, it freezes again, but doesn't reboot. I have to hold power to get it to reboot. So now I boot into twrp and decide to try a clean flash, I go to factory reset and I got error message can't mount system or cache. This worries me so I try rebooting to recovery to try again and it will not boot into recovery or system now all I get is fastboot. I have to work the next day so I just put device away and go to bed. The next morning I check the phone and it boots into system no problem. About halfway through work the phone starts all over again with same issue freezing and rebooting until only fastboot works. So I try unbrick tool, everything says OK I boot up and immediately freezes and after a couple boots I can again only get to fastboot. So I start RMA and send device off, when I get it back, the paper says they reloaded the OS. I think well its probably not fixed but I'll try it. I go through process of setting everything up as it was before and it worked fine. Until the fourth day, I'm installing an app and it freezes and reboots. Then exact same story as before, the longer I mess with it the less functional it gets, if I let it sit overnight it will work a while the next day. I have tried all the different twrp versions as well as stock recovery, I have tried other ROMs also, everything ends with same result. So I resubmitted the RMA and now I am waiting to get it back again, but I'm afraid all they are doing is reinstalling the OS again. So anyone experience anything like this before or have any suggestions/ideas what is happening. Thanks for reading and for any help provided.
budbay said:
OK guys, long read but I really need some advice. Device is op3 running 3.2.8, magisk, phh superuser and exposed. Issue started while I was reading in news app, screen froze the the phone reboots. 1st time this has happened since I got the phone in June. Didn't think much if it. So I go back to reading in same app and after 5 min it happens again. Now I'm suspecting an issue. So I try one more time with same result. I figure an app update or something must be the problem so I reboot to TWRP(latest official version) and restore my last backup from the previous day. I boot up the phone and decide to just try some browsing. About 5 mins in, it freezes again, but doesn't reboot. I have to hold power to get it to reboot. So now I boot into twrp and decide to try a clean flash, I go to factory reset and I got error message can't mount system or cache. This worries me so I try rebooting to recovery to try again and it will not boot into recovery or system now all I get is fastboot. I have to work the next day so I just put device away and go to bed. The next morning I check the phone and it boots into system no problem. About halfway through work the phone starts all over again with same issue freezing and rebooting until only fastboot works. So I try unbrick tool, everything says OK I boot up and immediately freezes and after a couple boots I can again only get to fastboot. So I start RMA and send device off, when I get it back, the paper says they reloaded the OS. I think well its probably not fixed but I'll try it. I go through process of setting everything up as it was before and it worked fine. Until the fourth day, I'm installing an app and it freezes and reboots. Then exact same story as before, the longer I mess with it the less functional it gets, if I let it sit overnight it will work a while the next day. I have tried all the different twrp versions as well as stock recovery, I have tried other ROMs also, everything ends with same result. So I resubmitted the RMA and now I am waiting to get it back again, but I'm afraid all they are doing is reinstalling the OS again. So anyone experience anything like this before or have any suggestions/ideas what is happening. Thanks for reading and for any help provided.
Click to expand...
Click to collapse
"I'm installing an app and it freezes and reboots"... What app were you installing, specifically?
I put my trust in XDA devs more than OnePlus devs, so... I suggest you flash FreedomOS. It's based on OxygenOS, but... tinkered by a very cool French guy . Oh, flash ElementalX kernel, too. Always better than stock. You never know
Formhault said:
"I'm installing an app and it freezes and reboots"... What app were you installing, specifically?
I put my trust in XDA devs more than OnePlus devs, so... I suggest you flash FreedomOS. It's based on OxygenOS, but... tinkered by a very cool French guy . Oh, flash ElementalX kernel, too. Always better than stock. You never know
Click to expand...
Click to collapse
Thanks for the reply! The last time that it froze, i was installing firefox from playstore. One of the ROMs I tried was freedom with elemental. It seems no matter what ROM I would flash, device would only work so long before freezing up, the main thing that seemed to matter was how long I waited before booting again, the longer I waited the longer I could use it before freezing up again.
budbay said:
Thanks for the reply! The last time that it froze, i was installing firefox from playstore. One of the ROMs I tried was freedom with elemental. It seems no matter what ROM I would flash, device would only work so long before freezing up, the main thing that seemed to matter was how long I waited before booting again, the longer I waited the longer I could use it before freezing up again.
Click to expand...
Click to collapse
Interesting...
Okay, this may sound weird, but try using the phone without the SIM card in it for a while, see if it freezes up. Or, get the SIM card replaced (if you can). Back when I had the HTC EVO 3D, the phone would lock up at times. Wasn't ROM related, as I experimented heavily with it and... eventually, it turned out to be the SIM card's fault. The guy at the store said he experienced that several times with other customers, but it's an extremely rare occurance. Some bad pin or God knows what. That was 4 years ago (actually, 5. Jesus! ).
Sounds hard to believe, I know. But you never know
Still, I believe there may be something wrong with your device's hardware. Try RMA'ing it again - if you dare going through the process again and risk having to deal with OnePlus' extremely lacking customer service several times a day, like I did .
PS: I see you're new here. You should know that there's a "thanks" button next to each post, which you can press so you don't post a single "Thanks!" every time. For the future, you know.
Formhault said:
Interesting...
Okay, this may sound weird, but try using the phone without the SIM card in it for a while, see if it freezes up. Or, get the SIM card replaced (if you can). Back when I had the HTC EVO 3D, the phone would lock up at times. Wasn't ROM related, as I experimented heavily with it and... eventually, it turned out to be the SIM card's fault. The guy at the store said he experienced that several times with other customers, but it's an extremely rare occurance. Some bad pin or God knows what. That was 4 years ago (actually, 5. Jesus! ).
Sounds hard to believe, I know. But you never know
Still, I believe there may be something wrong with your device's hardware. Try RMA'ing it again - if you dare going through the process again and risk having to deal with OnePlus' extremely lacking customer service several times a day, like I did .
PS: I see you're new here. You should know that there's a "thanks" button next to each post, which you can press so you don't post a single "Thanks!" every time. For the future, you know.
Click to expand...
Click to collapse
Good to know, I actually considered the sim. I've been using it since my HTC onex. Might try that when I get device back, however it is working in my opo as we speak. You mentioned you've going through rma before. Any advice on how to get them to take a different action other than continuing to reload the os?
budbay said:
Good to know, I actually considered the sim. I've been using it since my HTC onex. Might try that when I get device back, however it is working in my opo as we speak. You mentioned you've going through rma before. Any advice on how to get them to take a different action other than continuing to reload the os?
Click to expand...
Click to collapse
No idea, honestly. The RMA I did was for a replacement, since it was within 14 days of purchase, so I got to choose to get a replacement. Should have chosen the refund, wait another month and get the 3T... had I known it was going to be released. Oh well.
In your case... I guess you can do another RMA and hope for a better intervention. Perhaps explain to them... more thoroughly? Or just go with the flow - they'll reload the OS, you'll report the same issue again... Maybe they replace it, I don't know.
Interesting that they did the OS reloading IN SERVICE. Usually, this procedure is done via remote control... So they don't have to pay for shipping when such a thing can be done via a remote session, you know... Weird.