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
Related
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
ZBoater said:
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only thing I would've suggested would be flashing the signed ruu.
You could try reverting to the pre-OTA firmware, but I'm not sure you'll be able to use ADB if you're stuck bootlooping. Check out the "NOT FOR ROOT USERS" section.
ZBoater said:
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
RIP poor TB
How long did you wait for the screen to clear?
Just curious because I know usually when I do any type of update or rom change, etc, since you normally wipe the data and cache, the boot up can take quite a long time on the initial boot up.
I know some people report as long as 10 minutes or so to get past the screen. I don't think mine ever took that long, but there have been times I think it's stuck and then a minute or so later, it gets past it.
Just my two cents.
This has happened to a few people already after the update. I don't know what is in this update but HTC screwed up majorly.
Sounds a lot like what happend to mine, but mine was rooted.
See here...http://forum.xda-developers.com/showthread.php?t=1090531
LOL, I welcome the breaks when I can't find my phone for the day.
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
will9512 said:
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
Click to expand...
Click to collapse
What would that accomplish?
Yeah your lucky you got a guy to order your phone because I wouldn't have because even the new ones are rebooting, when you get it I would suggest postponing the update if it comes without the Mr1 update, as far as your wives phone yeah I would check out the forum uptop on going back to old software other than I have had a few people come into the store with same problem and couldn't do anything( mainly because I have no access to anything), but ship a replacement, oh and one suggestion is if you don't want your wife to borrow your phone your local store does have emergency stock Android loaners that you use until you get your replacement in, and then you just send your phone and the loaner back in the FedEx box so if you really need a phone you can do that.
Sent from my ADR6400L using Tapatalk
I believe your random reboots are due to the new radio which is tied into the OTA. If you apply the OTA again your still going to have random reboots. I ever used the newer radios and have never had a random reboot.
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.
Hi
I have a problem with my Galaxy S2 where it's in a constant reboot loop and the only way to stop it is by taking the battery out.
I'm sure that if I do a factory reset it'll go back to normal.
The problem is, I can't back anything up because as soon as the phone boots up it restarts.
Is there ANY other way to back up my photos and videos etc?
I have NOT rooted the phone
Cannot find any solutions online
I'm currently having this problem too. A couple of days ago it kept rebooting in a loop. I took the battery out and left it for a while, then let it charge. It seemed okay afterwards. Now today it keeps rebooting, and the past couple of days it has refused to charge the battery because apparently the battery was "too hot or too cold" (don't quote me on that) so I'm very confused. Just now though the battery was about half-charged and it still went into the reboot loop.
Something else you should know is that like the OP it has the stock OS on. It isn't rooted or modified. I don't want to factory reset it because I have spent so much time customising it (with apps) and it would be a pain in the ass if the problem still existed afterwards. One thing I must ask the OP is, did you recently get a 64GB MicroSDXC card for your S2? I ask this because I did a couple of weeks ago and it's been working fantastically and was said to work fine with the S2, but I'd like to explore any possible reason this reboot loop is happening.
Thanks.
Edit: To confirm I deleted the cache and this didn't help. I don't want to hard reset...
I've just done a factory reset - I hadn't realised that it only affects my apps and not my files.
The phone is ok now.
So I've been v customizing friends and families S3's today even an old LG Revolution, And I finally got around to doing my dad's and was using going to use odin to just flash the stock image of JB 4.1.2 and then boom lol
Anyways, it said Successful and all that good stuff, unplugged it, and then restarted it but instead it just shut off. And it wont turn back on, But it still makes the notification sound on my laptop for when a device is plugged/unplugged from the USB, and it started installing the Android device drivers as well, so something in that phone still has to be alive.
Please tell me I can fix thi. When I show up at his his house later with a broken S3, he's gonna be so pissed, and I just got a new Note 3 and I really dont wanna have to give it to him as a replacement.
Just read this in a thread if ound on here while doing a search - And if it doesn't work you can force it into downoad mode by holding down the power. volume down and power key without the battery and then putting in a micro usb cord plugged into the computer. Then put in the battery. -
when i did that, the notification LED lit up RED, but I think i did something wrong after that. So I am thinikin this is fixable if I can just get into stock recovery and format/reset system and cache.
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
BackSeatSuicide said:
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
Click to expand...
Click to collapse
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
BackSeatSuicide said:
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
Click to expand...
Click to collapse
Have seen that happen when battery too low and messing with SD Card and recovery. Remove battery and sd card a few minutes. Replace battery only and plug into charger for at least 30 minutes. Unplug and Try to boot. If it boots. Power off and replace sim card. Reboot. Worth a shot.
I will try that
Sent Using My Galaxy Note 3
Yea that didn't work.
Sent Using My Galaxy Note 3
This morning I wanted to use my SGS6 and it randomly rebooted. I thought I was a one time thing. I just update evernote and trello in the play store. It then happened again. I though maybe it was due to these updated apps so I deleted them. No result. Next step was clearing the cache in the recovery. Done, without any result.
I cursed a bit because the only thing left was a factory reset. When I wanted to backup my photos and so on, I got a error promoted on the computer that I couldn't read anything. Keep in mind that the reboots still happens every 2-5 minutes. Even when the battery was charged at the full 100%.
Now here is where I really missed the micro-SD. I had to move everything to google drive/dropbox. While the files were uploading, the reboots kept happening. I was busy for about an hour before everything was safe.
I then contacted Samsung. They asked if I could go to a Samsung Experience Store (I live in the Netherlands) but I wasn't able to go there so the service Representative told me I had to sent it for repair. Tomorrow the device will be picked up at my home. I'll will keep you posted about what Samsung does for me.
Does anybody else encountered these problems? Did the problems got solved ?
NOTED: I haven't rooted, I haven't installed the toggle fix yet because I didn't use those toggles, my device was bought less then a month ago on the 23th of may. No damages of the screen/back, it was in PERFECT condition