Develop Bugs

[Q] incredible keeps on rebooting?

I have a co-worker with Droid incredible and every time she turns the device on, it is stuck at the white HTC screen. Once in awhile, she'll be able to see the lock screen, but then the device will reboot again. I tried going into the recovery by pressing vol. down + power, but when I choose recovery, it gets stuck at the white screen again.
She does not have an insurance on the phone, is there a possible fix to this problem?
Thank you in advance.

Is it rooted or what? What did she or you do before this happened? Try to flash a rom or diff kernel?
Sent from my ADR6300 using XDA App

cheols46 said:
I have a co-worker with Droid incredible and every time she turns the device on, it is stuck at the white HTC screen. Once in awhile, she'll be able to see the lock screen, but then the device will reboot again. I tried going into the recovery by pressing vol. down + power, but when I choose recovery, it gets stuck at the white screen again.
She does not have an insurance on the phone, is there a possible fix to this problem?
Thank you in advance.
Click to expand...
Click to collapse
Download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename that file PB31IMG.zip, put that on the root of the SD card, boot the phone into bootloader mode by pressing vol - & power. Let the update run its course, and she will go back to a TOTAL stock 2.2.
EDIT: She will lose all her texts, have to re-download all her apps, and set her homescreens up again, but I don't think you have any other option if it keeps getting stuck at the white HTC screen.

If it's stock already or if rooted and the PB31IMG from the above post doesn't work, she simply needs to do a warranty exchange. We are, after all, still within the warranty period.

najaboy said:
If it's stock already or if rooted and the PB31IMG from the above post doesn't work, she simply needs to do a warranty exchange. We are, after all, still within the warranty period.
Click to expand...
Click to collapse
How would that not work? Its the stock rom, signed. I myself have done this before. Why go exchange it and get a crappy refurb (most likely SLCD )that, more likely than not, has problems? Why not fix the problem and keep the one that she has?
If they didn't want to do that they could go to shipped-roms.com and download the RUU from there and flash it back to stock that way also.

g00s3y said:
How would that not work? Its the stock rom, signed. I myself have done this before. Why go exchange it and get a crappy refurb (most likely SLCD )that, more likely than not, has problems? Why not fix the problem and keep the one that she has?
If they didn't want to do that they could go to shipped-roms.com and download the RUU from there and flash it back to stock that way also.
Click to expand...
Click to collapse
It ain't gonna work if it's a hardware failure, which seems a bit too common with the first run of Incredibles. No software is going to fix a problem with the SoC, which is why I said if the RUU doesn't work, she needs to do a warranty exchange.

The phone is completely stock.
She had to cut the line off and use company phone for about a month or two due to her personal problems. Now she's trying to get back on line with Verizon, but it's keep on rebooting itself so there's noway put it back on again..
Does Verizon/HTC do warranty on the phone even though she's not on the Verizon with the Incredible?

cheols46 said:
The phone is completely stock.
She had to cut the line off and use company phone for about a month or two due to her personal problems. Now she's trying to get back on line with Verizon, but it's keep on rebooting itself so there's noway put it back on again..
Does Verizon/HTC do warranty on the phone even though she's not on the Verizon with the Incredible?
Click to expand...
Click to collapse
I doubt they do, but you could just put it back on the plan, and take it into a verizon 30mins later. Tell them you hit *228 & #2 to update the prl and your phone rebooted and keeps doing so.

Thanks. If everything fails, I'll just go ahead and do that..

There's another version of recovery that lets you wipe the phone - you can search if I'm wrong, but I'm pretty sure that instead of pwr<->vol down it was pwr<->touchball. There, you'll be able to wipe the phone.
I had a similar problem with a phone that I just sent back for warranty repairs. The upside was I did get past the white splash screen. The downside was a few days later, the phone finally kicked the bucket and wouldn't power at all.

This fixed my issue. I was able to retreive my pictures after everyone else was saying to forget about it including HTC and Verizon.. I think this is a pearl as so many Incredible users have posted the constant reboot issue. Thank you Thank you Thank you!!

Another rebooting SLCD Incredible
Hi guys,
Just wanted to let you all know that this week, my wife's SLCD Droid Incredible started randomly rebooting. I had her on the Virtuous stock-based ROM and the SLCD ClockworkMod Recovery, and she had a TON of crap apps (pregnancy, game, live wallpaper, etc.)
I was able to back up the phone if I left the back cover off, but everything I did was time/heat sensitive. I wiped the phone and when setting it backup, got the bootloops after downloading only five or six market apps, not running any of them.
Last night I went back to stock (S-ON, Stock November PB31IMG.zip bootloader update). Again, after getting back to complete stock, it locked up after a few market apps were downloaded.
I called Verizon this morning from MY AMOLED Incredible, and they first had me describe the issues in detail (30 minutes), then try and repeat the issue (20 seconds after opening Google maps and starting a navigation session *quick heat*). She transfered me to "Level 2 Support", then he wanted to walk me through resetting to factory defaults on the phone via the SD card and storage settings. I noticed he wanted me to wipe the Internal storage, so I told him I needed to first backup the DCIM folder full of personal pics and videos to my SD card. He waited patiently while I backed them up (20 minutes). When finished, he had me wipe the phone+EMMC. I left the cover off so we could get through the initial setup, the put it back on after setting it up. He had me do *228 option 1, after the phone rebooted he wanted me to try and do "normal tasks" like downloading apps to get the phone to repeat the issue, if possible. I simply opened up Google Maps, started navigation and 1 second later, the phone went into bootloops. He promptly set up an "in-warranty" replacement to be overnighted to my house.
I do not have any monthly insurance on my phones, so I thought it was great deal that Verizon can issue an advance warranty replacement with return shipping, overnight, no less. Most companies would tell a customer to contact HTC directly. I am sure that is what Alltel used to do. I don't think VZW did it because we have corporate discount, I think this is standard service they provide for all their customers.
For any of you having this issue, here's what I recommend:
**If your phone is continually rebooting, pull your battery and let it sit out of the phone so they can cool for at least 20 minutes... Alternatively, you could probably put your battery in the freezer for 10-20 minutes and get a little extra "cold time" out of the phone before it bootloops**
1. Sync your apps with an app service like Appbrain to easily retrieve the list of apps you had.
2. Backup your call history and bookmarks using an app or two from the market. I have used free ones before, they should be easy to find.
3. Back up your Internal Storage and SD card to your computer (and preferably to a backed up location on your PC)
4. Revert to S-ON, and Stock ROM, if you are not already on one.
5. Set up only the basic functions on your phone (don't download any apps), then test that it is a heat issue by simply opening up Google maps and navigating anywhere.
6. Call Verizon and wait PATIENTLY on the phone as they walk you through their hoops. Expect this to take an hour or three. Just do as they say, as they have to make sure you indeed have a defective phone.
7. Profit.
Hope it helps,
jakewill

6. Call Verizon and wait PATIENTLY on the phone as they walk you through their hoops. Expect this to take an hour or three. Just do as they say, as they have to make sure you indeed have a defective device
jakewill
Click to expand...
Click to collapse
Ditto I have always had a pleasant outcome talking to the phone reps. Remember they are just doing their job and they are probably doing this exact same long process all day..
Wish I could say the store reps we're just as good but it's pretty hit and miss.
Sent from my ADR6300 using XDA Premium App

[Q] Please help, Arc S has mind of it's own...

Hi everyone,
I got my Arc S a week ago and I love it. Or at least I did until about 24 hours ago. It started with multiple digits coming up for each touch of the pad to enter my screen unlock code, this was followed by having to touch icons multiple times to get apps/games/widgets to load up. This morning all hell broke loose; I went to use Navigation which loaded fine but after 5 minutes it decided to go back to the home screen. Tapped the icon, it loaded, it cancelled. And again. And again. Then it started freezing for short periods, now it is completely pot luck as to what happens when I press home or back buttons. It is unuseable. There is no pattern to it's actions, and I cannot find a way to cure it, can anyone help???
And yes, I have turned it off and on again! :-s

Reflash
Sent via CM7-FXP45

Cheers XperienceD, I will do; was kind of wondering if it was a known problem or not, as reflashing will sort it, but is it likely to re-occur again?

ExperienceD looking for short answer record!
If you have only had it a week it may be worth doing a factory reset as you won't have too much data to lose.
Settings - privacy - factory reset.
This will wipe everything, but as it may be an app that has done this it is wise to do so

double post

Steelspike said:
Cheers XperienceD, I will do; was kind of wondering if it was a known problem or not, as reflashing will sort it, but is it likely to re-occur again?
Click to expand...
Click to collapse
It could just be a glitch but reflashing should show whether it is or it isn't, and if it is you know to get it replaced.

Reboot Loop NEW FINDINGS

Hey guys, my gnex has just been stricken (for the second time) by the boot loop. Managed to fix it last time with a flash of the google image, but this time it isnt working.
Same as usual, mine features the greyed out wifi toggle as well, and reboots every time the screen goes off (which makes sense that I've been noticing it go off every 2 minutes).
I have found that the device will not reboot if it is plugged in and set in the dev options to "stay awake" while charging. This seems to keep it running, same if I set the time-out to longer. My theory has to do with the distribution of power...I think that something is telling the phone it doesn't have enough power to function.
Like everyone else I've done endless factory resets, flashed the goog image and such and such to no avail. Currently stock but I left my bootloader unlocked atm. I can still boot into recov and everything and even flash other roms.
Has anyone else noticed this, or could someone who is also having the problem confirm the screen thing?
I think last time I posted I was on winmo, missed this forum.

Bump? Anyone else having this issue?

Just send it in for warranty. I sent mine in and Samsung exchanged the phone

I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?

My Nexus has been stuck on "Turning WiFi on.." since I've had it. It would also constantly boot loop itself whenever the screen went off. I flashed the new AOKP build to avoid this issue, however, the WiFi still does not work If I'm ever on stock again, I'll give stay awake a shot.
I live in the U.S. with the GSM GNex, so warranty is out of the question unfortunately.

Fixed the loop by flashing aopk again with franco's kernel. Brilliant but my Wifi is still messed up. I flashed a new baseband XXKL1 and no improvements. I'm gonna just wait it out for a bit because I've seen some threads elsewhere where that has actually worked, but who knows. I'll probably cave and send it out soon.

RogerPodacter said:
I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?
Click to expand...
Click to collapse
Yes and no. It happened twice and the second time I fixed it by going FROM stock to AOPK with included kernel. Now it happened on THAT setup so I went back to stock and no dice. Its a very weird problem....

I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.

mastergrifis said:
I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.
Click to expand...
Click to collapse
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.

ShatteredAxe said:
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.
Click to expand...
Click to collapse
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating

mastergrifis said:
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating
Click to expand...
Click to collapse
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!

ShatteredAxe said:
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!
Click to expand...
Click to collapse
I have a Desire Z by my side, but of course I want my Gnex back as new. The only thing that scares me is the warranty. I'm not sure if it's still valid. I mean, apparently there's no sign of root/bootloaderunlocked, but how can I explain that suddenly my phone has started rebooting itself without any reasons?

Yeah, only option is to just try and see what happens.

Galaxy Nexus freeze after unlock **UNROOTED** troubleshooting

Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance

You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.

Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.

slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme

Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again

slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem

Lenovo P2 display black after recovering from a bootloop

Hey guys.
I am posting this particular issue because while I could find something similar to this issue (recovering from a bootloop for this very device), I couldn't find much in case your screen remained black afterwards.
I know why the bootloop took place (or at least I'm almost sure I know why):
-Via dr.fone, I chose the root option. This is a naïve move, as I know that one-click rooting options basically never work. Well, I know this now at least. However, the root never happened, as my device didn't even have OEM activated (there are some issues happening in this regard with lenovo). The program just couldn't continue, telling me that my phone wasn't registered in the data base or something like that. I was honestly just messing around because I didn't have OEM access, just wanted to see what error would pop up.
-The bootloop happened the day after, about 16 hours later. It also happened randomly, while the phone was idle without being connected to the PC. The screen was black, but I knew it was bootlooped because it would vibrate consistently every 10 seconds or so.
-If I pressed the Up+down+power buttons simultaneously, the blue LED in the top right corner would light up and a very long vibration would happen. There's a thread on this issue already, and adding a new firmware solved this.
-I tried to solve this by using ADB to add the stock firmware again. The bootloop stopped after this and the phone would charge. It didn't while bootlooping.
-I tried to factory reset and nothing happened. Except that my USB debugging option is now turned off, which makes things harder because I can't find a way to turn it on without having access to my phone.
I was wondering if there'd be a solution for this very situation. It's also worth noting that my screen is basically shattered, but I don't think it's an LCD issue because these two things happened at the same time. I find it too much of a coincidence.
Do you guys know what could be going on? I also wiped the cache data, even though my phone was factory reset just to give it a shot.
I very much appreciate your attention.
PS: this is literally only the display and the touch screen. Even the fingerprint sensor works.

Did you unlocked bootloader before root ?

Shreyash01 said:
Did you unlocked bootloader before root ?
Click to expand...
Click to collapse
No, the root didn't even take place. I tried to unlock the bootloader, but the Lenovo servers are down for that. So my bootloader is not unlocked.

I think that is the reason..
Your bootloader is not unlocked. You must have to ask someone before doing..
I think costumer care is the only option.