Related
Hello,
So, I have had a custom flash for some time. I don't use this phone too often and it sat off with a dead battery for about 2 weeks.
I plugged it in and turned it on. It booted into the custom rom for windows just fine. I went to reboot into Android like I normally would and it got stuck at the main boot screen but never displayed the rom / radio red text in the bottom left of the screen.
I've set it sit like that over night with no dice.
I have tried task29, reflashing HSPL, removing HSPL. I can't get anything to complete. It seems like as soon as anything tries to write into the phone's internal RAM is dies. I've tried flashing different radios but nothing takes once the 7 vibes hit.
Any ideas on what this is and any other ways to get around it. I've tried hard-resetting. When it says to press Vol-Up to boot it just gives me 7 vibes and a blank screen.
Where do I go from here?
Cheers,
Ech0
Here is what my boot loader says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Really, no one?
Im having the same problem guys... i have a tmo us hd2 1024... it is stuck at the stick together screen and the r,d,g red letter that appear, are not doing so... oddly enough it can flash roms...
sorry for my bad english...
you must install the latest stock-rom from sd-card.
copy the *.nbh from stockrom to the sd-card and renamed to leoimg.nbh.
just restart your hd2 and follow the text on the screen.
So what exactly is the significance of the 7 vibrations?
I got the same problem. I managed to reflash the phone after MTTY and flashed HSPL, bootloader, radio and ROM. Made hard reset. No luck, it freezes again and again.
I wonder what these 7 vibrations mean? Anybody know?
sorry to re dig up this thread but i have been having the same issues 7 vibrations and it just gets stuck on the boot up splash screen. Does anyone have a solution to this?
I have the same problem with my hd2 original rom... It first went a little warm on the back after heavy using with movie mp3 internet and youtube, it reboots and hang, had to remove the battery and wait to let it cool down....
I think it was a bug, so i downloaded the newest rom software from HTC and updated it... Now when i using it on the same way, movie internet mp3 and youtube it still reboots and hang, But it gives me 7 vibrations and stay in the boot screen,.. or it reboot again and again....
Remove the battery, cool it off and it works ok until.... it gets warm....
Called HTC and they sait that it could be a problem with the motherboard...!!! For now i am waiting for my device.... I send it to HTC for repair.... expect him any day now.... hope they fixed it.....
Just an update on my 2x HD2's.
Both went into repair and came back with "No Fault Found!'
So afterwards i sent it to a different repair centre who agreed with my diagnosis that the motherboard was faulty on both devices.
Subsequently they replaced the motherboard and now the HD2's are working as they should.
It used to lock up at around 33c. now with the replacement motherboard it runs fine even up to 45c! ( i used battclock to monitor device temp!)
Very interesting! I think I should send my HD2 for repair too. Did you use warranty service or paid money for the repair?
Always sent in for warranty!
My phone was bought in Frys. I asked my friend to bring it directly to T-Mobile office, they said "Go to Frys and let they repair it". He came to Frys, they said "It's T-Mobile thing, we can't help, give it to T-Mobile".
Please advise, how to get it repaired?
Call HTC or Tmobile and ask for the closest authorised repair centre. drop your device in directly with the proof if purchase and get it repaired.
T-Mobile declined to get it for repair once again. Friend of mine visited 2 T-Mobile offices and Radioshack shop and was sent to HTC everywhere. Maybe it's local Texas habit...
Will try to send it to HTC service.
Hi guys,
I've been faced exactly the same problem, but also have found (a bit of... strange, let's say... and temporary, somehow) solution. Read below...
I found out that the seven vibration signal indicates motherboard issues. AND - as in most of cases mentioned right here, in this topic - the error wasn't occuring immidiately, but after a few minutes since turning the device on. So what I thought is that the phone was simply overheating, or even if it was not - the temperature indicator wasn't working OK and as a result we were getting this error.
As I found this out after long hours of trying to get things work, here a quick guide how to fix what you probably messed up during your efforts:
1. If you tried to reinstall ROM or any other software using USB cable and things didn't go well - don't worry, it was the same for me. Firstly, we need to clean up. Run the installer on your PC again, then try again, the error will occur, and after it does follow the instructions on the screen UNTIL THE INSTALLER ASKS YOU TO CONTINUE AND INSTALL ANYTHING AGAIN. Don't do it, just pull the cable off the phone.
2. What you need to do now, is to download a new ROM, then copy it onto the microSD card, then rename to "LEOIMG.nbh". Turn the phone on with VOL- pressed down, and then confirm installation with the Power button.
Okay, we have got it all installed and... not working. Probably the white HTC splashscreen and nothing more. And after the reset, 7 vibrations again. Now, the magical trick.
Put your phone into the fridge. Seriously. Take out battery, put it into some plastic bag (so it won't get wet) and put it to the fridge. Wait 20 minutes or so, then turn it on and enjoy temporarily working phone. It was fine for me until I started to use Opera.
Further solution? Well, working on it.
P.S. Sorry for refreshing old topic, but the problem doesn't seem to be solved and I'm trying to push things forward.
Anyone else experiencing the occasional crash/reboot?
The last couple of mornings my phone had woken me up... It's the Samsung boot sound, the phone has crashed and rebooted while I was asleep.
I have had a couple of crash/reboots while using it too...
Nope, no crash or reboot here.
Intratech said:
Nope, no crash or reboot here.
Click to expand...
Click to collapse
same here...
factory reset?
vinokirk said:
factory reset?
Click to expand...
Click to collapse
Thanks for the suggestion.... I have already factory reset once to get rid of the social hub settings...
Maybe it's an app I got installed then...
Nope. Its never crashed on me
Sent from my GT-I9100 using XDA App
mmm_ok said:
Anyone else experiencing the occasional crash/reboot?
The last couple of mornings my phone had woken me up... It's the Samsung boot sound, the phone has crashed and rebooted while I was asleep.
I have had a couple of crash/reboots while using it too...
Click to expand...
Click to collapse
does it reboot while it's on charge ?
Process Of Elimination...
List all the apps you have installed and then the guys here can give a YAY or NAY to those apps causing them the similar issue.
Double Post!!!.
Although it's probably unrelated, the LG Optimus 2x is having significant problems with freezes and reboots, and some users there also pointed out that the Moto Atrix seems to have similar problems too. The obvious commonality is the dual core processor.
As I said, probably unrelated but maybe worth keeping in mind if this becomes more widespread.
What wireless options do you leave on at night? (ie: wifi, gps, bluetooth....)
Some phones can get quite warm while left charging if lots wireless options are left on too.
However, for my Galaxy S 1 I only noticed it getting warm/hot around the top after extensive internet use with the screen on full brightness and either charging at the same time or having just been unplugged from the charger.
In the settings menu -> about phone check what is consuming the battery and it should help to see if there are any rogue applications that won't stop chewing power during the night.
using any latest gameloft games? have heard, that those not-so-legal copies of gl games are crashing devices.
Happened to me when I deleted the unwanted ASEC (or something) files form .android_secure folder in external sd card before uninstalling the apps and the device was connected through usb to pc. Well after two random boots it stopped just thank fully!
it can boot randomly when :
1. GSM signal is weak
2. Simcard is damaged or too old
3. Battery is too hot
4. Some APPS are moved to SD card (it allows you to move it, but actually, apps doesnt like it)
5. External SD card is slow, 4 or below classes, or too small sizes of sd cards (2GB-4GB) or too full of external sd card, ord sd card, or internal memory, etc. (shorly not enough memory
6. RAM!!!!!!, if more then 780mb ....,
7. too many WIDGETS...
8. too long standby
GUYS these are the main reasons, if you have all ok with above list, then you may have problems with OS, then flash and install back, or maybe HARDWARE PROBLEM (ram,cpu etc.)
GOOD LUCK!!!
Hey guys,
It happens to me too. For some reason it reboots, and when I check the battery stats, i see a major vertical drop, then it slowly regenerates the battery, but nowhere near the previous levels. I was on Batista KH3 ROM, now I though I'd try an official KJ3 ROM, but seems it hasn't done the trick. Tried everything from factory reset, to deleting cache and whatnot from recovery, but still no joy. The biggest battery muncher is Display, followed very regularly (unless I abuse some app or game) by Android System (not Android OS, mind you).
Any last words of advice before I send it to it's maker? (Samsung support, don't think about anything else, you crazy guys)
Thanks alot for your patience!
Cheers!!!
My Galaxy S II reboots once a day - in avarage - Hardware or Software problem ?
My Galaxy S II reboots once a day - in avarage - What kind of problem do I have ?
Is it hardware or software ?
Facts:
- Model: GT-I9100
- Android: 2.3.5
- Baseband: I9100XXKI4
- Kernel: 2.6.35.7.I9100XWKI8-CL616395 [email protected] #2
- Build: GINGERBREAD.XWKI8
- Kies has no updates for the phone.
I bought the phone 23th. of november 2011
I installed a 16GB MicroSD card
I installed all the apps that was using at the old phone (Galaxy I9000)
Phone was't able to run 24 hours without reboot.
By reboot I mean: A sound, the little 5 seconds Galaxy-movie, and asks for pincode...
No systematic in the reboot. Not a specific place, not a specific time, not by doing something special.
It never reboots when it is "open". It's always when it is lying on a table, or in my pocket.
==========================
OK. A factory reset. No apps installed, minimum of configuration.
Phone still reboots once or twice a day
=========================
OK. 16GB MicroSD disabled
Phone runs for 60 hours, then reboots, Then it runs for 22 hours and reboots
=========================
Right now: WiFi disabled... It has been running for 14 hours... waiting... Now 41 hours. (16dec,16:12) (not using wifi)
Update by 18dec: After 25hours I forced the tip of a plastic tooth-stick under the battery. After 60 hours I installed all my favorit apps, and it is still running... (88 hours)
Current conclution: Hardware - Bad implementation of battery-connectors...
Update by 3jan2012: Nope... Still not ok. Two reboots around x-mas and yesterday... once again.
I have been talking to Samsung, and they does not (officially) admit that the S II has a reboot-issue. They advice me to go to a repair shop, since the phone is fully updated and that they don't have more advices to give...
========================
More info:
Two colleques has the same phone, and they never reboots.
The one is a lower Android version: 2.3.4
The other is the same except Baseband: I9100NEKI2
If I return it to the shop they will send it to Samsung Repair, and after 10 days I will get it back. Or maybe a new one...
Pls. give me some advice..
Regards in advance
Thorkil
I've never experienced random reboot until now.
I just updated original ROM with 2.3.6 version an reboots hapan 2 a day!
I blame the new version 2.3.6 :/
Update
Hi guys,
It seems that the random reboot issue is gone now. After i went for the KI3 FW, the number of reboots went down at each charge and now they are no longer present. I didn't do anything, but i'm guessing it had something to do with the battery stats.
Hope this helps.
I had this issue the first day I upgraded my ROM. Then it stopped. I'm not sure if it was a random reboot or I accidentally shut it down while in my pocket (I don't use a lock screen). But it happened once, and it hasn't happened again since.
But I did get a weird error yesterday: It couldn't read my SIM card... I had to turn it off and back on to get it working again. Have any of you seen that before?
I've got exactly the same problem.
I recently did a reset to factory settings, but the problem is still there.
Running official 2.3.6 firmware.
I can't really think of a source.
Often it just restarts when it is in my pocket and I'm not using it.
Below you can see a screenshot of the battery stats a short time after the restart.
As you can see suddenly a huge amount of battery life is 'missing'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read about this problem at many forums around the internet.
I hope this is fixed soon, because it is really frustrating.
I'm coming to the Evo 4G LTE (stock, not yet rooted) from the OG Evo (rooted, various ROMs, yada yada). I've held off on rooting, just in case I discovered a hardware issue (light leakage, etc.) and needed to swap out the device. So far I've discovered a definite problem, but I don't know whether it's a hardware or software issue, and I'm hoping someone in this forum can help me down the path of figuring out the cause(s).
Specifically, I'm seeing the following things happen, usually all at the same time, but intermittently:
1. Phone heats up, and battery takes a huge hit
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
3. Wi-Fi drops, as does my mobile data connection, so that I appear to lose all connectivity.
4. My app associations get reset. I usually have my URLs set to open with "Dolphin Browser HD", and mail set to open with "Gmail (Compose)", but after this happens they're back to the stock browser and mail app.
5. Can't enter any text. When I enter a text field/control, the keyboard appears (I use Swype, but switching input methods makes no difference), and I can type/Swype away, but no text ever shows up in the field.
This is happening about once a twice a day, on average, and is obviously driving me nuts. I haven't detected a pattern to when/why it happens. And I've been searching the forums, but I haven't seen anyone else reporting this same set of issues. I'm not sure whether it's my device (hardware/lemon), or maybe just a user app behaving very, very badly - I'm not enough of an Android dev to know where to look for clues...?
Any help very much appreciated. I haven't tried a factory reset, but I'm open to that. Also to rooting the phone, and/or contacting Sprint. I just didn't want to blindly do any of those things before asking the Android experts out there for some guidance.
Thanks!!
If it was me, I'd root and flash a new ROM or at least a rooted stock ROM. If that didn't work I'd unroot and exchange it.
I'd say try a factory reset first, but why not root and have it done as a by-product anyway?
Sent from my EVO using xda premium
I agree
If you dont want to root yet just do a factory reset. What is it going to hurt? If you do a factory reset try to just set the phone up with all stock options to see if your problem is fixed.
roachiepoopoo said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
jpbme said:
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
Click to expand...
Click to collapse
The same is with me BEFORE rooting, and after root and ota from xda
Look I want to thank you for posting this. I am NOT CRAZY. This has happenend to me from day 1, I returned the first EVO LTE (for other reasons) and it is still happening on my second EVO LTE
I finally got to the point that I was going to root my EVO LTE to fix this issue. I was going to root and flash and reset EVERYTHING. well surprise surprise nothing changed.
I have all the same problems you described but I lose my 3G about 15 times a day (especially when on calls) I have full bars but the 3G icon is gone and it states that I am disconnected. I can't figure this out. Everyone I appreciate your quick responses to this mans question but none of them work.
I have update profile and prl more times then I can remember. Flashed, wiped , reset everything. Help Me!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any new info on this topic? My 3G disconnecting is really annoying!!
Rooted, wiped, and switched to MeanROM - phone now works GREAT!
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
roachiepoopoo said:
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
Click to expand...
Click to collapse
NO!
So I flashed the Chameleon Rom, was running it for a while and still had issues. This weekend (during a wedding) I flashed MeanRom. And it is still happening. Does anyone know a real fix for this? :crying:
SilverZero said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
stompkins007 said:
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
Click to expand...
Click to collapse
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
slowfncar said:
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The issue I was having was only specific to the blank notifications... everything else has been pretty solid... BUT, there appears to be a light at the end of the tunnel. Last night I saw ClearnROM DE 1.4 was released, and had to give it a try. This time around I was very careful to do a full factory reset, Wipe of everything except storage cards via TWRP, Ran Superwipe script, and installed the latest CleanROM DE 1.4. The one thing I did differently after install was be very careful of what items I restored via Titanium Backup (making double certain it was only restoring app store apps, and no potential artifacts from previous ROMs.
Since doing this the phone has been solid. Haven't experienced the blank notifications, and the phone seems considerably more responsive than it was (which is nice, because it even seemed fast before doing this). Anyway, if anyone else is experiencing this, I recommend they do the same.
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
I don't buy Sprint's insurance and have had issues getting them to do warranty replacements, most recently with my EVO 3D's phantom screen touch problem (also 1st gen hardware). Sprint told me to ship it back to HTC and be without a phone for however long the warranty repair took. Really?
KatanaMan said:
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
Click to expand...
Click to collapse
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
KatanaMan said:
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
Click to expand...
Click to collapse
RE: SuperSU, it lives on the system partition with the ROM so it's protected from a factory reset since that only clears the data and cache partitions (where your user apps are stored).
Sent from my EVO LTE
Just a thought
You cold try ##786# and enter your MSL code for data connection issues. See here to use CDMA Workshop for those that are not rooted (or use MSL Reader from the market for rooted users). Its worth a try at least, before unrooted users decide to root. Keep in mind this will reset your phone to factory so if your going to reset, might as well do this to reset PLI, PRL and other params...
I've been having the overheating/battery drain issue since about a week after first getting the phone. I've tried Meanrom, Viper Rom, and Clean Rom and still come across the same issue with each one. I do complete wipes/factory resets when flashing the new roms and I'm on the latest firmware. When the phone overheats it's pretty much unresponsive. Today, I watched my battery drain from 15% down to 8% in about 10 minutes. I turned the screen off at 8% and went to turn it back on a few minutes later and found that the battery had completely drained by that time. I have no idea why this is happening.
Same here
I've been having this issue as well. It happened while I was stock, it happened after I rooted, unlocked, went S-Off. And it's still happening under MeanROM. Very frustrating!
Hi guys new member pestering for help here. I've lurked anonymously for a few years getting valuable info re: phone stuff & even managed a ROM upgrade on a crappy old htc following threads here. . this is my goto forum for anything phone related & has been of great help many times. Huge thanks for that!
However, I've come across a problem on my Galaxy S4 that I can't find info about anywhere, so have decided to bite the bullet & register.
Keeping it as brief as possible, my GTi9505 Galaxy phone registered to Virgin Mobile developed what I believe is a fault shortly after an (official) OTA firmware update. Where previously mobile data (not WiFi) was very fast & the 'H' symbol was more or less constant, after the update bandwidth dropped dramatically (as slow as gprs) & only the 'E' symbol lit.
After several very long phone phone calls to Virgin technical department, they eventually fobbed me of by suggesting that the network towers local to my location were being downgraded. . :ahemB$!: They couldn't however explain why my sim in my girlfriends S4 mini was getting 3g from the same location. So, I stopped paying the bill & was cut off.
I decided to try an EE payg 4g sim in the phone & surprisingly, it works fine apart from the same bandwidth limitation. . still locked to 'Edge' regardless of location. WiFi into home router is fast & works normally. ??
I know how to get into service mode & move around so if anyone has any suggestions of settings that I might be able to check/tweak I'd be extremely grateful.
Hope one of you fine people can help
Open your phone dialer, type *#4636#* and check if your phone is locked to edge mode only. Try *#*#4636#*#* if the first command doesn't work.
Hi popthosegaskets thanks for replying. Tried both codes several times to make sure but neither of them work :/
I tried it on a Samsung Note 3 and it works, not sure why it shouldn't work. I'll get back to you about it.
Update: I got so p*ssed off trying to figure out how to fix this issue that I installed CyanogenMod 10 which works fine but still showing 'Edge' icon on mobile data in spite of changing connection settings. I expected something as radical as flashing a new OS would solve the problem but it hasn't.
Kind of weird, maybe it's a hardware issue or some part of the underlying firmware that isn't affected by the OS??
Download "4G LTE Switch" from Play Store and see if it works for you.
OK, installed. 4G LTE Switch & tried every possible option to get LTE mode to stick but it refuses to shift from 'Edge'. Definitely have 3g & 4g coverage but phone setting seems to be welded to Edge for some reason.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit to add: opened up the phone & checked antenna contacts & plugs. All seem to be good.
Hmm... Let me think.
Have you tried flashing another software? Since the problem started after the OTA update maybe it should be fixed with a ROM flash?
popthosegaskets said:
Hmm... Let me think.
Have you tried flashing another software? Since the problem started after the OTA update maybe it should be fixed with a ROM flash?
Click to expand...
Click to collapse
Well as I said I've flashed it with Cyanogenmod, I've tried different modems via Odin, checked the hardware (physically replaced LTE antenna/charge port this morning) have even resorted to playing with EFS Professional! I guess I could try to replace the co-axial wire that connects the antenna to the mainboard but realistically, that probably isn't going to fix it.
BTW.. IMEI is valid (matches label) so I don't think thats corrupted or missing but the root\efs folder is empty. Is that normal?
To be honest I'm not really into this phone stuff, I just want my phone to work properly when I need it to & make a few tweaks sometimes. I updated the software as instructed & now the phone doesn't work properly. The only thing I've done wrong, if anything, is refuse to pay for a phone that stopped working after a legitimate update from Samsung. I read somewhere that it's possible that the mainboard can be damaged when upgrading the firmware, that seems crazy to me.
I think I'll just give this up as a bad idea & go get an S5. I don't need the hassle.
This is finally starting to get some attention.
Just wanted to let others know who have this problem to check these links out for more info and to share your bug reports, findings.
If we're lucky maybe Google will finally admit there's a problem and do something about it.
https://code.google.com/p/android/issues/detail?id=227849
http://www.androidpolice.com/2016/1...toff-problem-and-its-becoming-a-safety-issue/
https://www.reddit.com/r/Nexus6P/comments/5j6qyc/report_your_early_battery_shutdown_issue_directly/
Well.. my 6P is DEAD after the update.. it worked for a day, rebooted and then bootloop. I sent it to two repair services with no result. At this point I can only enter bootloader. Is anyone kind enough to point me to what I can do to bring it back? Burying it seems the only option right now *sadface*
Try the NRT,...Nexus Root Toolkit. Go on YouTube to see how to set up and use it.
Sent from my Pixel XL using XDA-Developers mobile app
Anyone with this issue yet a clean install? I'm not in the mood to do so, so if others have tried without success of be appreciative of the knowledge.
rbrenart said:
Anyone with this issue yet a clean install? I'm not in the mood to do so, so if others have tried without success of be appreciative of the knowledge.
Click to expand...
Click to collapse
Yeah, I've tried a clean install and still have the same problem.
I'm convinced it's a hardware issue.
Thanks for letting me know, just finished a support chat. They seem to think it's a faulty battery and are sending a new (refurbished) device. We'll see what happens.
I had this issue almost daily once I went to 7.0. Even with clean installs if I remember right. I got a refurbished phone over a month ago and it hasn't happened since. Plus my battery life is better or at least as good as when I got my original phone a year ago.
Sent from my Nexus 6P using Tapatalk
maybe Google purposely did this so people with Nexus 6P will upgrade to Pixel :silly:
whoisrikk said:
Well.. my 6P is DEAD after the update.. it worked for a day, rebooted and then bootloop. I sent it to two repair services with no result. At this point I can only enter bootloader. Is anyone kind enough to point me to what I can do to bring it back? Burying it seems the only option right now *sadface*
Click to expand...
Click to collapse
I was having same issue. Until someone referred me to a guide burried deep in the forum. Basically, the procedure involved flashing the stock MM image then booting into the bootloader and flashing custom recovery (TWRP) through bootloader. Then the OP provided link to a TWRP backup that I manually transferred to the twrp backup folder on my phone. Entered recovery and restored my phone through that backup. Only then did it work. Took me about 6 hours after much trial and error. But God bless that person. If I find that guide I will post a link here to exit bootloop!
P.s. Just remembered I had it bookmarked. It worked for me. Give it a try!
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
hashim71 said:
I was having same issue. Until someone referred me to a guide burried deep in the forum. Basically, the procedure involved flashing the stock MM image then booting into the bootloader and flashing custom recovery (TWRP) through bootloader. Then the OP provided link to a TWRP backup that I manually transferred to the twrp backup folder on my phone. Entered recovery and restored my phone through that backup. Only then did it work. Took me about 6 hours after much trial and error. But God bless that person. If I find that guide I will post a link here to exit bootloop!
P.s. Just remembered I had it bookmarked. It worked for me. Give it a try!
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Click to expand...
Click to collapse
My friend..if this works, I'll find you and the op of that post and give you a huge beer.
hashim71 said:
I was having same issue. Until someone referred me to a guide burried deep in the forum. Basically, the procedure involved flashing the stock MM image then booting into the bootloader and flashing custom recovery (TWRP) through bootloader. Then the OP provided link to a TWRP backup that I manually transferred to the twrp backup folder on my phone. Entered recovery and restored my phone through that backup. Only then did it work. Took me about 6 hours after much trial and error. But God bless that person. If I find that guide I will post a link here to exit bootloop!
P.s. Just remembered I had it bookmarked. It worked for me. Give it a try!
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Click to expand...
Click to collapse
That's for recovering from a bootloop? This thread is for the battery shutting down below a certain %.
whoisrikk said:
Well.. my 6P is DEAD after the update.. it worked for a day, rebooted and then bootloop. I sent it to two repair services with no result. At this point I can only enter bootloader. Is anyone kind enough to point me to what I can do to bring it back? Burying it seems the only option right now *sadface*
Click to expand...
Click to collapse
B3501 said:
That's for recovering from a bootloop? This thread is for the battery shutting down below a certain %.
Click to expand...
Click to collapse
That was just an answer to the first comment I saw on the post.. Thought I'd help. But with the battery issue.. My phone seems to die around 5-10℅ battery depending on the day
Sometimes mine dies between 5-15%. Never seen it happening with more juice in it then 15% though. I'm thinking about going back to the online shop where I bought it from.
my does it at 15% automatically.. but sometimes at 35% it shuts off.. then i reboot and its at 30%.. like wth..... I moved on to the V20 (t-mobile had a crazy black friday deal) but I kept the nexus 6p. I really like the phone... does it on both stock rom and custom..
For whatever it's worth I don't have that issue purchase my Nexus 6p 3 months ago at Best Buy
Sent from my Pixel XL using XDA-Developers mobile app
I don't have that issue. And I have the phone since Dec 2015. It only appeared to restart twice while on DP2 (in all realness, it sat at the "enter screen unlock pin").
I highly doubt it's a hardware issue since it started with Nougat. Did anyone of you roll back to MM and see if the problem persists?
wow the google issue site has skyrocket.. it was at 75 replies. two days ago to 455 as of now.. all same issue...
Lets keep this updated with any & all info.
Gotta get Huawei or Google to take responsibility for this.
They have to know that we all can do a Samsung to their bottom lines.
I'm getting my RMA new one tomorrow but today was a mess again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 06:30 PM ---------- Previous post was at 06:01 PM ----------
Puck24 said:
I don't have that issue. And I have the phone since Dec 2015. It only appeared to restart twice while on DP2 (in all realness, it sat at the "enter screen unlock pin").
I highly doubt it's a hardware issue since it started with Nougat. Did anyone of you roll back to MM and see if the problem persists?
Click to expand...
Click to collapse
Yes, it happened on MM too although Im on Nougat now.
I've read about this issue for months and always thought I was one of the lucky ones since I'd never experienced it, until one day a few weeks ago I turned the phone on and launched the camera, with about 15% battery left and was met with the "shutting down..." screen.
Since then it's happened sporadically, with the battery anywhere between 10-25%. And other times I've been able to use the phone right down to the single digits.
But yesterday took the cake. I thought I was in the clear, as I was around 50%, so I went on a trip through the junkyard to look for parts for my car. I hadn't been to a junkyard in many years, so it was a bit of an event, and I looked forward to snapping a few pics of the interesting cars I might see.
Pulled the phone out once and snapped a pic and a snapchat video, and right after I hit the send button in snapchat, the phone powered down. Now it was cold and windy, which may have had something to do with it, but even after putting the phone back in my pocket and warming it up with my hand, I powered it back up and the battery meter read 1%.
Now I'm not usually one to complain, but how can a battery drop from 50% to zero in one second? This has to be a hardware issue, and I don't know whether to wait until I'm near the end of my warranty period to replace it, or do it now and risk the replacement device not showing signs of the same issue until after the warranty expires.
It sucks, but I'm finally a part of this crew.