[Q] Hard Bricked? - Samsung Infuse 4G

Well, I was running the 2/10/2012 build of CM7 for about a week and a half, everything was silky smooth except for a few little hiccups until last night. My phone shut off and started boot looping. (SAMSUNG screen.... Off.... repeat). i figured it'd be fine, and just put it into download mode and i'd be fine. But no, it was different. As soon as i put the battery in, it instantly starts boot looping. no matter what i've tried it won't go... the only way i could get it into DL mode was using a custom jig i made with some resistors but even then, it shut off after about 3 seconds and then continued the boot loop routine. Seems like this thing is done for. i called AT&T and they're sending a new one, but do you guys think they'll find i had a custom rom on it? i took it to the store but naturally i knew more then the "helpful" sales rep. No one there could figure it out so i think ill be fine. Any thoughts??

devilsxcrunner15 said:
Well, I was running the 2/10/2012 build of CM7 for about a week and a half, everything was silky smooth except for a few little hiccups until last night. My phone shut off and started boot looping. (SAMSUNG screen.... Off.... repeat). i figured it'd be fine, and just put it into download mode and i'd be fine. But no, it was different. As soon as i put the battery in, it instantly starts boot looping. no matter what i've tried it won't go... the only way i could get it into DL mode was using a custom jig i made with some resistors but even then, it shut off after about 3 seconds and then continued the boot loop routine. Seems like this thing is done for. i called AT&T and they're sending a new one, but do you guys think they'll find i had a custom rom on it? i took it to the store but naturally i knew more then the "helpful" sales rep. No one there could figure it out so i think ill be fine. Any thoughts??
Click to expand...
Click to collapse
Runner,
Sounds like similar to a few other user.
Something to do with the power button stuck or bad board.
Search user garen21. Read his thread..a few pages back. Gl

thanks man, ill give it a look. It's really out of no where that this happened.

Related

Phone wont stay shut off?

Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Wolf_2 said:
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Click to expand...
Click to collapse
Lol that is funny, what apps did you update?
I also have a problem with charging the phone and not sleeping, i was starting to think that it was just finaly getting worst
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Wolf_2 said:
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Click to expand...
Click to collapse
I dunno, I already did that and it did nothing, but I guess its worth a shot for you...
And I dont have any of those apps
If I find something I'll post here
/me shrugs
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Edit: What version of Clock Work Mod recovery do you have installed and which rom were you running? Trying to go through the variables with this issue.
Wolf_2 said:
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Click to expand...
Click to collapse
Yeah it is odd, could be coincidence, could be related, dunno, I dont see how it could be an ATT update when nearly all the roms here have that function disabled. Then again maybe you know something I don't
What did you do to get it to turn off finally? I dunno if I wanna try now that you said it wouldn't turn back on.
Also, what rom where you on when it started, I was on CM nightly #121 or maybe #120 I forget
I just happened to come across this in the general section
http://forum.xda-developers.com/showthread.php?t=1145495
no fix though
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Wolf_2 said:
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Click to expand...
Click to collapse
Could this have something to do with partitioning the SD card? I think i remember reading that clockwork bricked some phones, is that true?
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: I changed the time and date back to automatic and it is working like it should again. Did you get yours working again or is it still having problems?
Wolf_2 said:
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: Did you get yours working again or is it still having problems?
Click to expand...
Click to collapse
This worked for me also.
im still having this phone wont shut off issue as well. i have set it to the same date as u and turned off auto and it still just reboots when trying to turn it off
Try leaving automatic off for a whole day. Then see if it is still having this problem. Also replied to pm but try this first to see if it gets past it and works..
willdo thanks a bunch
BAleR said:
Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
Click to expand...
Click to collapse
I had that problem, but it was the car app. I had to disable it in the settings.
seems this keeps happening more and more to people. i still have yet to solve my issue
well i retried setting the date on the phone but this time i chose 1/1/2011 and now the phone stays off when i turn it off which is nice but now i have to deal with having the wrong date

Emancipation boot loop

Running Emancipation A1 for weeks now. Love it. Runs smooth, support is top notch. All of a sudden, I'm stuck at the Samsung logo boot loop. I can't even get into CWM recovery mode to wipe and reflash. Didn't download or change any settings.
Downloading necessary files to go back to stock. In the meantime, if anybody has any suggestions, I'm all ears. Going to be a long night I guess.
If you used a crt on mod, the last 5-10 pages on the main Eman thread may address this problem.
Thanks. No, I didn't install the CRT on mod that was provided. Very strange, because the rom has been running flawless for quite some time. I'm downloading the Heimdall one click file now.
A little nervous at this point. Yes, I've flashed a few Rom's, and flashed a few modems, but never had any problems.
Holding volume up and down Anne pore won't get you to recovery?
If that's the case, you might need to get into download mode and start from scratch via heimdal or Odin
Yeah, can't get into recovery holding up/down volume buttons. I downloaded heimdall, and went back to stock. Not I'm experiencing same problem. Phone continuously rebooting. Can't connect or even get into download mode. Also tried a different USB cord, just to make sure. No difference.
Yikes.
Well this pretty much sucks. I think I went back to stock. The phone booted up briefly enough for me to go into settings and see that it was running a stock version of the software. What it was I can't remember. Probably 2.3.6 just like the post says it will revert to. However, I cannot do anything when I power on now. The phone is stuck in at the Samsung logo and will just flash and flash and flash. Can't get into recovery or download mode. Nothing.
Lavman72 said:
Well this pretty much sucks. I think I went back to stock. The phone booted up briefly enough for me to go into settings and see that it was running a stock version of the software. What it was I can't remember. Probably 2.3.6 just like the post says it will revert to. However, I cannot do anything when I power on now. The phone is stuck in at the Samsung logo and will just flash and flash and flash. Can't get into recovery or download mode. Nothing.
Click to expand...
Click to collapse
is the battery charged?
do you have a jig to force a download mode?
may have to go back thru th q/a thread for similar problems...there's quite a few
If its doing that, it could be a hardware issue. Might need to take it in if you are still under warrantee.
qkster said:
is the battery charged?
do you have a jig to force a download mode?
may have to go back thru th q/a thread for similar problems...there's quite a few
Click to expand...
Click to collapse
battery charged. in fact I have a couple batteries charged, just in case.
not sure what you mean by whether I have a jig to force a download mode.
I'll search through the threads. I'm pretty fed up at this point. Also tired, which isn't helping.
NunHugger said:
If its doing that, it could be a hardware issue. Might need to take it in if you are still under warrantee.
Click to expand...
Click to collapse
I got the Infuse the first weekend it came out, which I think was last May. So I think I'm technically under the 1 year warranty. I also have the Insurance on it. Not sure if that will help.
Well, this didn't have a very happy ending. After playing around with the phone last night trying to revert back to Stock, the phone suddenly stopped working. Wouldn't turn on at all. Tried different batteries, different USB cords, nothing. Replacement on it's way from AT&T free of charge (since I was still under warranty). Refurbished no doubt.
Lavman72 said:
Well, this didn't have a very happy ending. After playing around with the phone last night trying to revert back to Stock, the phone suddenly stopped working. Wouldn't turn on at all. Tried different batteries, different USB cords, nothing. Replacement on it's way from AT&T free of charge (since I was still under warranty). Refurbished no doubt.
Click to expand...
Click to collapse
The ending sounds happy to me. This issue could have happened out of your warrantee...that would have been sad. Hope your are back up and running soon.
Yes, it's bittersweet. Because I really had the phone functioning well and looking the way I wanted. But like you said, it was under warranty, so I can't be all that upset. Just trying to make it through the 4-5 days without having a phone.

[Q] Help - dead N8010

Hi All,
I'm hoping somebody can help me here. I have an N8010 which is stuck on a constant reboot cycle.
It displays the "Samsung Galaxy Note 10.1" Logo and then blanks the screen. After a couple of seconds, then it redisplays the same logo.
It first did this on Thursday after being in use for about 30 Mins. The Tablet just hung and rebooted. It got stuck in this loop until somehow I managed to turn it off. After about an hour, it started up and worked OK, but I didn't try prolonged use.
This morning, it did the same thing, hung (Editing contacts) and rebooted. This time it started back up, but almost immediately id hung again and now it's stuck in the Reboot/Logo loop. I cannot even turn it off - It's just displaying the Logo.
I can press and hold Power/Vol Down to invoke Odin. Selecting Restart Phone just returns me to the loop.
Earlier I could press and hold Power /Vol up to invoke the Reboot/Reset screen and I have done a factory reset.
Oddly - Now I can no longer use the Power/Vol up combination to get to the reboot/reset screen, but I have managed to use it to turn of the tablet.
Occasionally there are a number of corrupted pixels flashing on the screen.
I am assuming that there is some sort of dry joint/bad connection that is warming up and causing these issues.
This Note has not been flashed with any software at all - It's stock.
Anyone seen anything like this before or should I just return it
Thanks in Advance
Steve
Return it, don't try to flash anything to it.
Sent from my GT-N8010 using Tapatalk HD
If it is under warranty and you are on your stock market rom then give it to a service center
samir_a said:
If it is under warranty and you are on your stock market rom then give it to a service center
Click to expand...
Click to collapse
Did you try to root it or flash another rom? If not just send it to service.
gpgalanis said:
Did you try to root it or flash another rom? If not just send it to service.
Click to expand...
Click to collapse
Thanks guys - No didn't try to root or flash at all. I'm waiting for the JB update to see if I need to.
It's working perfectly right now, While it was rebooting endlessly, I managed to get the battery display to appear - It seemed to be completely discharged. (85% a few minutes before) . So I connected it to the charger.
After 35 mins, the charge was showing 92% and it booted and has been running happily ever since.
Exactly what it did on Thursday - showed empty and then charged after about 30 mins.
I think I'll take it back and see if they'll swap it for one with the 3G. Hope that they don't have to send it away, it's gonna be my Christmas present
Steve
Good luck! Since you didn't flash a custom rom or anything, there's no reason you should have to deal with that stress.. Just return it and demand an exchange or something. If you got it at a store, they'd probably be happy to exchange it. If you got it online, it'd be a little harder and more delayed, but still doable! Good luck again!
Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....
ultramag69 said:
Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....
Click to expand...
Click to collapse
I thought that I should let you guys know the outcome.
I was not soured at all, I took it back to the store, and was told that they would have to return it
So while I was there I bought a N8000
Jelly Beaned it, rooted etc This thing rocks

Random restarts

Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/

[Q] Acatel 4060a "Ideal" Stuck at Boot Logo

My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Silicon Knight said:
My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Click to expand...
Click to collapse
I'm assuming you used Kingroot to root it? It's a common issue for Kingroot to cause a bootloop.
Typically, this is fixed by re-flashing the stock firmware but you have to get it to connect to PC to do it, and that's only if the stock firmware is even available.
Sent from my SM-S903VL using Tapatalk

Categories

Resources