Well, this is a loaded question, and I've seen it in various other phones' Q&A sections, but nothing comes up that specifically matches this phone.
Has anyone else identified any application(s) that cause the GS3 to spontaneously reboot - to the point if insanity?
I'm already on "Mike's 2nd Galaxy S3" and VerizonWireless was very helpful yesterday (??) and showed me how to do a safe mode start. I haven't seen that posted, so here's the trick: press and hold the power button until the "Samsung" logo appears, then press and hold the volume down button and quickly release the power button. After cogitating for a few minutes, the phone will come up in 'virgin mode', with "SAFE MODE" displayed at the bottom left corner. So I'm told it loads only factory-original programs in that mode, fair enough.
It still rebooted after about five minutes while we were checking things out. So, friendly S-O-a-B had me do a factory reset. :cyclops: That's cool, I have everything backed up with CWM and TiB and screen-shots of the layout, so it was actually trivial to get everything back. Never-the-less, before I could get through the cycle of updating my phone using the Google Market - er - "Play Store" - it rebooted yet again, this time while I was trying to answer the psuedo-random "Customer Satisfaction Survey" phone-call that you get when you have called tech support - sometimes. Call dropped, I felt the little twitch it gives when it warm boots into the quick-load vector and just said "F it!" and called him back and have yet another ("Mike's 3rd Galaxy S3") coming overnight on Monday. I've had squirrelly phones that were "new models" do weird things before, so no big whoop. Maybe "Door #3" will be better. I know #2 worked better until about a week ago than the original unit.
Just in case anyone wonders: flashing the original factory recovery mode forsaking the OC'd core gives no joy...
OK, I'm calmer, back to the original question: has anyone identified any common APK that makes the SGS3 go spastic? I'm thinking - in my case - since I got a reboot in the 'virginal safe mode' boot it's not going to help, but - just checking.
ratledge said:
Well, this is a loaded question, and I've seen it in various other phones' Q&A sections, but nothing comes up that specifically matches this phone.
Has anyone else identified any application(s) that cause the GS3 to spontaneously reboot - to the point if insanity?
I'm already on "Mike's 2nd Galaxy S3" and VerizonWireless was very helpful yesterday (??) and showed me how to do a safe mode start. I haven't seen that posted, so here's the trick: press and hold the power button until the "Samsung" logo appears, then press and hold the volume down button and quickly release the power button. After cogitating for a few minutes, the phone will come up in 'virgin mode', with "SAFE MODE" displayed at the bottom left corner. So I'm told it loads only factory-original programs in that mode, fair enough.
It still rebooted after about five minutes while we were checking things out. So, friendly S-O-a-B had me do a factory reset. :cyclops: That's cool, I have everything backed up with CWM and TiB and screen-shots of the layout, so it was actually trivial to get everything back. Never-the-less, before I could get through the cycle of updating my phone using the Google Market - er - "Play Store" - it rebooted yet again, this time while I was trying to answer the psuedo-random "Customer Satisfaction Survey" phone-call that you get when you have called tech support - sometimes. Call dropped, I felt the little twitch it gives when it warm boots into the quick-load vector and just said "F it!" and called him back and have yet another ("Mike's 3rd Galaxy S3") coming overnight on Monday. I've had squirrelly phones that were "new models" do weird things before, so no big whoop. Maybe "Door #3" will be better. I know #2 worked better until about a week ago than the original unit.
Just in case anyone wonders: flashing the original factory recovery mode forsaking the OC'd core gives no joy...
OK, I'm calmer, back to the original question: has anyone identified any common APK that makes the SGS3 go spastic? I'm thinking - in my case - since I got a reboot in the 'virginal safe mode' boot it's not going to help, but - just checking.
Click to expand...
Click to collapse
Reflash the stock rom via PDA slot in odin, then wipe/data factory reset in stock recovery!
droidstyle said:
Reflash the stock rom via PDA slot in odin, then wipe/data factory reset in stock recovery!
Click to expand...
Click to collapse
Unfortunately I tried that before I called. I'm using "Route66", but - basically stock ROM + root and the Invisiblek OC to 1.89GHz. I tried backing down the OC to 1.80, then 1.75, and finally just undoing it, flashing it back to CWM 6.0.1, but no joy there, either.
ratledge said:
Unfortunately I tried that before I called. I'm using "Route66", but - basically stock ROM + root and the Invisiblek OC to 1.89GHz. I tried backing down the OC to 1.80, then 1.75, and finally just undoing it, flashing it back to CWM 6.0.1, but no joy there, either.
Click to expand...
Click to collapse
does it reboot at the stock clock speed(1.5)? Also, you went back to the stock kernel and it still reboots?
droidstyle said:
does it reboot at the stock clock speed(1.5)? Also, you went back to the stock kernel and it still reboots?
Click to expand...
Click to collapse
Yep, yep, yep... Sure enough, I can flash the stock recovery and it still reboots, doesn't matter what I have in the RECOVERY.IMG
I've already done the factory reset and reprovisioned my phone twice, also. Fortunately unit #3 will be arriving tomorrow shortly after noon (I live so far out in the weeds that even priority overnight usually gets there around 12:30 or 1)...
Ya I would flash that back to one hundred percent stock. That's really the only way your gonna find out if your phone is truly busted or not.
Sent from my SCH-I535 using xda premium
tapatalk keeps force closing on my and once caused a random reboot . My screen goes black and unresponsive for like 30 seconds then says tapatalk stopped responding or something like that. When it rebooted it also went black and unresponsive for like a minute I was about to pull the battery then it booted back up. Not sure if your having a similar issue there are my $.02
Sent from my SCH-I535 using Tapatalk 2
Mark930 said:
tapatalk keeps force closing on my and once caused a random reboot . My screen goes black and unresponsive for like 30 seconds then says tapatalk stopped responding or something like that. When it rebooted it also went black and unresponsive for like a minute I was about to pull the battery then it booted back up. Not sure if your having a similar issue there are my $.02
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't have it installed. I do have the XDA app installed, but while I'm working (like right now), I'm not able to use my cell on the network. :angel:
The thing is the new (2nd) one has about 75% of the crap I had on the original one, and I've slowly whittled that down to about 50%, trying to eliminate anything I thought might be questionable. I've not heard one person P&M about any problems running the "Route66" SYSTEM.IMG for root, or I'd go ahead and flash it back, too. Of course - "within the next 5 days" after receiving the 3rd unit, I'll certainly do that to unit #2, and remove all traces of ever having been anywhere but a factory original image, so they don't pop my plastic for $500 or so. I already did that once when I returned the first one.
Related
Hello All,
I promise I've done 2 days of research before and while doing this.
I have a Samsung Galaxy S on ATT using ATT network. I tried to put Cognition on it 2.3b7 and something was wrong with the battery life, so I decided to start over and flash it again. In the meantime DG released 2.3b8.
I rooted it Mac (i'm on a mac), got superuser permission, did the whole clockwork thing. Then I decided to flash it using Odin3 1 click downloader back to ATT software. Well then I got phone...!...computer error. I couldn't do the 3 button combo to get it download mode. I made the 301k Jig, that worked and got me in to download mode. I used Odin3 again, got it back to ATT software but I think it was still custom.
The whole ODIN process was actually way more indepth because it wouldn't work, or the USB software wasn't installed correctly, my phone kept being a *****. But I got it to work eventually.
My phone would also say Samsung I9000 (it's a i897, idk if its the same) instead of just the ATT start up. I went through the rooting process a few times on the Mac and no super user app would show up. So I did it on a PC and it worked. Then I went through the standard process of installing Cognition. I backed it up using clockwork, then clicked install rom and selected the .zip file in the SD card.
It started working. Then after about 30 minutes, it just wouldn't turn on anymore. I've taken out the battery, it's fully charged and all that. It still just won't turn on. It's all black...
What happen, has it happen to anyone and how do I fix it?
It's seriously a paper wieght right now.
dnguyen527 said:
What happen, has it happen to anyone and how do I fix it?
Click to expand...
Click to collapse
Exact same thing happened to me - except I have a genuine i9000.
ROM Flasher - selected ROM - booted into clockworkmod, which started flashing the ROM, it proceeded for about 10 minutes, displayed lots of activity on the screen, then the screen went black... and has remained black ever since.
The phone won't turn on, won't go into download mode, won't go into reset mode. I have a jog on order, but I don't think that will do much. I thought that maybe the battery had drained (it didn't - tried it in a different phone).
The phone is just dead, and an equal paperweight.
Are there any options left, or do I just need to send it back to Samsung?
background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*
Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk
Did you try booting into recovery mode instead of odin?
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
if u can boot into cwm flash darkside
OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?
Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...
I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe
Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727
The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
UPDATE 12/23/2013:
1. I was able to get into Recovery by quickly pressing reboot and reboot into recovery. From here I could get into Download Mode.
2. I first cleared my Dalvik & Cache and reflashed JellyBeans v19, then cleared Dalvik & Cache again. This did no solve any problems.
3. Next I flashed the Stock VRBMF1 Firmware through Odin, which also did not solve any problems.
4. Now I am downloading Root66 and following Hero's guide to unbricking a soft-bricked device.
usatf1290 said:
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
Click to expand...
Click to collapse
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the response!
I would try to flash stock packages through Odin, but i cant get to download mode. Usb debugging is enabled.
Ill probably send it Verizon when i get back to the states, but I was wondering if i could do anything in the mean time.
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.
Hello,
I recently changed the LCD of a S6 edge. I installed it and turned it on and it booted up fine. I went to make sure everything was working. While I was playing music it would restart. I thought it was odd, so i was waited til it came back on and started using other apps. Same thing..restart. So, i booted to safe mode. Same thing...restart.
So, I tried factory resetting. After that, it would just get stuck in a endless restart loop cycle.
I have also tried reinstalling the OS using Odin. I ran Odin and it said everything passed. The phone restarts and goes to installing updates.
It gets to 32% every time then it says "erasing". After a few seconds of displaying "erasing" it just starts its endless reboot cycle again.
**EDIT: I should add that it never restarts when it's in the download manger.** So, that makes me think its a OS issue.
*EDIT#2: This is a good video. I did all of this. Got to the 9 minute mark and where his comes on, mine restarts again.
Any help?
Thank you!
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
3mel said:
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
Click to expand...
Click to collapse
Hi,
thank you for your reply. I learned about all of this last night lol. so, i'm not exactly sure what you mean. I bought the LCD+frame from Ebay. It stated it was pulled from a working unit.
Could a bad battery cause all these issues? I notice when i power down (only way I can power down is if I Hold POWER+VOL DOWN and select power down) that the LED light stays on.
Hello, could someone delete this thread. I have posted a more detailed thread on this issue.
if it says it's an LCD screen it's not an original part. my point was that some people have had issues booting up roms because of screens.
that was something that was fixed in custom roms though so if you can't another solution a custom rom that works with 3rd party LCD displays might be an option to consider.