I did and man my phone is messed up. It got stock (going on 15 min) atthat little droid animation with the wireball rolling around in the android belly. Not sure how to fix it.
robstunner said:
I did and man my phone is messed up. It got stock (going on 15 min) atthat little droid animation with the wireball rolling around in the android belly. Not sure how to fix it.
Click to expand...
Click to collapse
I just pressed the power and volume up/down then it loaded to the bootloader. Once there i wiped cache and data. Then waited a bit while it was wiping data, then held down the power and it restarted. Hopefully that helps.
Ugh, im getting pissed. Second phone same thing. I factory reset from the settings menu. 100% stock. Every time i restart the damn phone it stuck attempting for format data for >15 mintues before i get pissed. If i choose bt tools or factory, it loads the phone just fine, but when i reset, back to the same problem.
EDIT: 8th time around it took just over 13 minutes and the phone reset.
robstunner said:
Ugh, im getting pissed. Second phone same thing. I factory reset from the settings menu. 100% stock. Every time i restart the damn phone it stuck attempting for format data for >15 mintues before i get pissed. If i choose bt tools or factory, it loads the phone just fine, but when i reset, back to the same problem.
EDIT: 8th time around it took just over 13 minutes and the phone reset.
Click to expand...
Click to collapse
Did it actually reset itself though? Clearly there's something wrong with the stock recovery. I can wipe cache fine, but do a data wipe, or factory reset, and it hangs... though I never let it go more than 5 minutes. I had used the fxz files previously, so I'm glad to hear it's not those and apparently a problem with the actual recovery img that came with the phone.
It also does seem to actually wipe data... something just must be getting stuck not allowing it to move forward when it's done.
jntdroid said:
Did it actually reset itself though? Clearly there's something wrong with the stock recovery. I can wipe cache fine, but do a data wipe, or factory reset, and it hangs... though I never let it go more than 5 minutes. I had used the fxz files previously, so I'm glad to hear it's not those and apparently a problem with the actual recovery img that came with the phone.
It also does seem to actually wipe data... something just must be getting stuck not allowing it to move forward when it's done.
Click to expand...
Click to collapse
Nothing wrong with it, it takes ages to erase, wait like 20 mins and it will eventually come back. It happened to me too.
nkd said:
Nothing wrong with it, it takes ages to erase, wait like 20 mins and it will eventually come back. It happened to me too.
Click to expand...
Click to collapse
Well at least that's good to know - but that seems way off timewise, regardless. I know there's more internal storage than most devices, but still...
Yep, it just takes a massively long time. Sorry for the pre teen freak out.
Sent from my DROID RAZR HD using Tapatalk 2
Yup apparently it just takes a little bit. All good on my end.
boot with android guy screen
Did anyone that had this problem have a progress bar the whole time? I bought a used Razr maxx hd online and it was factory reset. I tried to boot and got the same issue (android guy with geometry spinning forever) did a hard reset (power + volume down) same thing. Finally got into recovery menu (power + volume up + volume down) and any option i chose would reboot and finally load. But after activating the phone and having all my apps loaded I decided to test a reboot on the phone. Sadly it got stuck again and after using the same method to boot, I had lost everything. Hope there's a fix for this, not sure I can do a swap since I bought this used.
heeroyuyzero said:
Did anyone that had this problem have a progress bar the whole time? I bought a used Razr maxx hd online and it was factory reset. I tried to boot and got the same issue (android guy with geometry spinning forever) did a hard reset (power + volume down) same thing. Finally got into recovery menu (power + volume up + volume down) and any option i chose would reboot and finally load. But after activating the phone and having all my apps loaded I decided to test a reboot on the phone. Sadly it got stuck again and after using the same method to boot, I had lost everything. Hope there's a fix for this, not sure I can do a swap since I bought this used.
Click to expand...
Click to collapse
Yea, just let the android guy spin, and go back to in 20 minutes. If still spinning, 10 more minutes. It should be good after that. If not, return that thing!
robstunner said:
Yea, just let the android guy spin, and go back to in 20 minutes. If still spinning, 10 more minutes. It should be good after that. If not, return that thing!
Click to expand...
Click to collapse
I let it run a long time, finally rebooted but erased everything again. Then I tried installing the new update. Again hung on android guy long long time, reboot finally and again had to setup the phone and update didnt even install.
Related
I went to use my 300 today after not touching it for a couple weeks (been busy with my new evo 4g lte) and it was stuck on the asus boot screen. Tried rebooting a number of times with various button combos, long pressing the power button and all and it will not pass this screen.
I had the latest firmware installed prior to this issue.
Anyone have any suggestions?
Did you try cold booting? To do this, power off your tf. While holding the vol down button, then press and hold the power button. You will see white text at the top. Let go of the buttons and it should boot to a screenasking if u want to wipe data. Dont presss anything and let it timeout and reboot.
cavsoldier19d said:
Did you try cold booting? To do this, power off your tf. While holding the vol down button, then press and hold the power button. You will see white text at the top. Let go of the buttons and it should boot to a screenasking if u want to wipe data. Dont presss anything and let it timeout and reboot.
Click to expand...
Click to collapse
I did indeed try that, still did nothing
Right now I have it sitting unplugged waiting for it to run out of power.
Well thats not good. You could download and play a movie on it to help expedite the battery discharge. If after that and it still doesn't work, consider doing a wipe/factory reset as a last ditch effort. After that, you are looking at a store return or warranty repair. If this was the 101, you would have utilities to fix that but we dont have such things for the 300 yet. Good luck my friend.
cavsoldier19d said:
Well thats not good. You could download and play a movie on it to help expedite the battery discharge. If after that and it still doesn't work, consider doing a wipe/factory reset as a last ditch effort. After that, you are looking at a store return or warranty repair. If this was the 101, you would have utilities to fix that but we dont have such things for the 300 yet. Good luck my friend.
Click to expand...
Click to collapse
If I could play a movie I wouldn't be in this situation
It's weird because The only people I've seen with issues like this were rooted or trying to flash roms.
Lol yea you are right on that. Ive seen this happen with unrooted 101s before. For whatever ryme or reason something in the system gets borked and prevents it from booting properly.
Try to do a factory reset, it should solve the problem
nooktablet said:
Try to do a factory reset, it should solve the problem
Click to expand...
Click to collapse
As in wipe data from the cold boot menu?
Was hoping against that as this wasn't really something I brought on myself through flashing and tinkering.
If this happens again I'll be doing an rma I'd say. Either way I have plenty of time for other suggestions, just hoping someone has some!
Tried wiping data and still stuck, just tried resetting with a paper clip and still no go as well. I'm assuming it's bricked at this point.
Brandito said:
Tried wiping data and still stuck, just tried resetting with a paper clip and still no go as well. I'm assuming it's bricked at this point.
Click to expand...
Click to collapse
Yeah, I'd return it. Without root or unlock, it would be impossible to modify anything even if we knew exactly what was wrong with it.
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.
Last night, my nexus 5 suddenly rebooted itself. When it restarted it was in a boot loop. but not a boot loop that i can get out of.
It just keeps going round and round almost as if the power button is stuck. however the power button is not stuck.
i cant get into recovery to clear the cache as when i boot into the bootloader it just automatically restarts again, i can move one option up or down and that is to shut down or reboot into bootloader, but not the second move that would take me to recovery.
i have now taken the back off, and unplugged the battery in the vain hope that it clears through whatever is causing the issue but im not convinced it will make any difference.
Please advise. i'm completely housebound and cannot walk due to having a knee operation, and completely dependent on my mobile if i have an emergency.
i've tried Kwoggers out of the box fix from his 2.1.2 toolkit but this didnt work as the phone wont stay in one place long enough for it to get a fix.
spasypaddy said:
Last night, my nexus 5 suddenly rebooted itself. When it restarted it was in a boot loop. but not a boot loop that i can get out of.
It just keeps going round and round almost as if the power button is stuck. however the power button is not stuck.
i cant get into recovery to clear the cache as when i boot into the bootloader it just automatically restarts again, i can move one option up or down and that is to shut down or reboot into bootloader, but not the second move that would take me to recovery.
i have now taken the back off, and unplugged the battery in the vain hope that it clears through whatever is causing the issue but im not convinced it will make any difference.
Please advise. i'm completely housebound and cannot walk due to having a knee operation, and completely dependent on my mobile if i have an emergency.
i've tried Kwoggers out of the box fix from his 2.1.2 toolkit but this didnt work as the phone wont stay in one place long enough for it to get a fix.
Click to expand...
Click to collapse
If it reboots, even in bootloader, then it's either a broken power button or a broken motherboard.
Lethargy said:
If it reboots, even in bootloader, then it's either a broken power button or a broken motherboard.
Click to expand...
Click to collapse
thanks for replying, but why would this happen all of a sudden?
the phone was on, it hadn't been rebooted for a few days. It hadn't been dropped. but suddenly it went into a boot loop.
spasypaddy said:
thanks for replying, but why would this happen all of a sudden?
the phone was on, it hadn't been rebooted for a few days. It hadn't been dropped. but suddenly it went into a boot loop.
Click to expand...
Click to collapse
Not exactly sure, it's happened to a couple of people. Another reason could be a defective battery. What happens if you plug in the charger and attempt to boot?
Lethargy said:
Not exactly sure, it's happened to a couple of people. Another reason could be a defective battery. What happens if you plug in the charger and attempt to boot?
Click to expand...
Click to collapse
same. just boot loops.
the reason i dont think its the power button is it just stops doing it and just switches off.
when its plugged in it just reboots around the white google logo, constantly. without being plugged in it goes to the 4 balls and reoots
spasypaddy said:
same. just boot loops.
sometimes it gets to the 4 balls converging, sometimes it just reboots around the google logo.
Click to expand...
Click to collapse
Afraid there's not much you can do other than RMA, then.
Lethargy said:
Afraid there's not much you can do other than RMA, then.
Click to expand...
Click to collapse
thanks, i just rang google and they are sending me some troubleshooting via email and then it will get replaced.
will google mind that ive opened the back up?
spasypaddy said:
thanks, i just rang google and they are sending me some troubleshooting via email and then it will get replaced.
will google mind that ive opened the back up?
Click to expand...
Click to collapse
I'm not sure, I think it voids the warranty :/
hmm
i'll just have to risk it if their troubleshooting doesnt work
I wanted to clear the system cache because my phone was acting laggy and the battery was running down very fast even with little use. I attempted to boot into recovery by holding the volume+, home and power buttons. The phone rebooted and did a factory reset instead of booting to recovery. I tried a second time with the same result. I have booted to revcovery using the same method before. It's a good thing I didn't have anything important on my phone that wasn't backed up because I would have been screwed. I was able to boot to recovery using ADB command at a terminal on my PC and clear the cache but since the phone was factory reset twice it probably didn't matter. One positive is that the phone is running smoothly and the battery life is back to normal (which isn't saying much). And I'll probably will be selling it soon anyway since I ordered a S7 Edge. So anyway has anyone else ever experience that?
That's an unpleasant surprise! Luckily I haven't had that happen to me during the many times I've cleared the cache.
I had the same thing happen, but lost a lot of stuff I really needed. Really frustrating way to figure that one out.
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).
follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...
Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????
My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?