My tablet was working great until I let my 8-year old son play on it this morning. He then handed it back to me a little while later and said it didn't work. When you try to boot it up, it goes to a black screen and says Boot Verified Failed...
I am also unable to get into recovery, I get Recovery Verified Failed...
I was running Flex Rom RC 3.1 with CWM....
Anyone have any ideas?
No idea, very sorry to hear it.
Without knowing what might have happened to it. It seems hard to say. Could he have bounced it off something.
No he is usually very good with things. It ticks me off though, I had surgery today and i'll be on my back for a few days. I was looking forward to using it.
These lost I had the same problem and I could not solve and no help here
took her back to mediamrkt and the warranty and they took care of all the 15 days had a new free of charge
Well I contacted Acer Support, I told them that it happened during an update. They allowed me to RMA it back to them. I shipped it last Wednesday and I just got it back today. They replaced the motherboard and all is well again!
Related
Hi all,
Ever since flashing the last CM stable, I've been experiencing terrible boot loops.
Yesterday was the worst, no matter what I did, the phone would either get stuck at the white screen, or get to the CM loading screen and then reboot.
Tried wiping and reflashing, and experienced the same things.
Wiped and reflashed with Fresh 3.4, and it was working for a while. Then, all of a sudden, the phone couldn't pick up Sprint service and started the hands-free activation mode. Low and behold, it goes back into a boot loop.
Now, I'm sitting here on a frozen white screen again.
The funny thing is, the phone will randomly reboot sometimes during a wipe or a flash using Clockwork.
Any ideas? I see a few similar posts but none describing the same issue with Sense based (not CM) roms.
Thanks
So I just tried the following and I am frozen at the white screen:
- wipe data/cache/dalvik twice
- flash Fresh 3.2 (sense based rom)
Tried doing a Nandroid restore. Seemed to be going OK for a while until the phone just rebooted during the restore. WTF? Is this a problem with the SD card?
Was finally able to do a nandroid restore to an older CM. Formatted the SD card. Going to re-flash to another ROM now.
Menotti said:
Was finally able to do a nandroid restore to an older CM. Formatted the SD card. Going to re-flash to another ROM now.
Click to expand...
Click to collapse
Back into a reboot loop after full wipe and new ROM flash. What gives?
Best way to start over?
Damn phone is freezing just trying to go into Recovery :/
Phone reboots when trying to flash something in Recovery. Jeez...
can anyone offer an advice? i'm drowning here...
Flashed RA recovery. Thing still randomly reboots when wiping or flashing ROMs. Ugh.
It's rebooting while in recovery?!?! Wow man, it sounds like your hardware is messed up. I've never heard of a phone rebooting while in recovery. You may need to get a replacement
Yes, I had this problem. The processor was overheating. The phone was replaced. Hopefully you can unroot so you can get yours replaced. I had trouble unrooting because it kept rebooting during the process, took a good 3-4 hours.
Leukay said:
It's rebooting while in recovery?!?! Wow man, it sounds like your hardware is messed up. I've never heard of a phone rebooting while in recovery. You may need to get a replacement
Click to expand...
Click to collapse
Yeah it reboots while in recovery. Like, I'll be doing a wipe and the phone will reboot.
So far I've tried a number of RUUs and stock PC36IMG from flashboot all with the same result - the device will get into the OS and then just reboot. This will loop 3 or 4 times and then get frozen at the white screen.
Misty Blue said:
Yes, I had this problem. The processor was overheating. The phone was replaced. Hopefully you can unroot so you can get yours replaced. I had trouble unrooting because it kept rebooting during the process, took a good 3-4 hours.
Click to expand...
Click to collapse
Ah weird. If I am S-ON I'm good to go? Sounds like I need a manufacturer's replacement if I don't have the insurance, right?
I went to sprint for my replacement. I called HTC first, but they were going to charge me, which I am not ok with doing while the phone is still under warranty. At sprint, they asked me to replicate the reboot and when I did, they ordered the replacement on the spot. My problem had gotten to the point that I knew how to make it happen on the spot, though. You may have to do some quick talking if you can't reproduce the problem right away. But, you should be able to get a free replacement.
ETA: I don't have the insurance. As long as your phone is under a year, which it is, sprint has to honor the manufacturer 1 year warranty.
Misty Blue said:
I went to sprint for my replacement. I called HTC first, but they were going to charge me, which I am not ok with doing while the phone is still under warranty. At sprint, they asked me to replicate the reboot and when I did, they ordered the replacement on the spot. My problem had gotten to the point that I knew how to make it happen on the spot, though. You may have to do some quick talking if you can't reproduce the problem right away. But, you should be able to get a free replacement.
ETA: I don't have the insurance. As long as your phone is under a year, which it is, sprint has to honor the manufacturer 1 year warranty.
Click to expand...
Click to collapse
K, I'm going to try to walk in and do that.
I called one of the repair centers and they said they'd only be able to look at it, but would triage back to HTC for warranty repair.
Called HTC, they're talking 2-4 weeks for repair.
You think if I walk in one of the Sprint places and repro, they will replace on the spot? Sounds like they don't do that.
I called sprint and made an appointment. You must not tell then you rooted at any point or they will not honor the warranty. If at all possible, don't mention going into recovery. Try to reproduce the problem some other way. They will not charge you and they will either give you the replacement if they have it or order it and it will arrive the next day.
Misty Blue said:
I called sprint and made an appointment. You must not tell then you rooted at any point or they will not honor the warranty. If at all possible, don't mention going into recovery. Try to reproduce the problem some other way. They will not charge you and they will either give you the replacement if they have it or order it and it will arrive the next day.
Click to expand...
Click to collapse
Thanks, I will try this tomorrow.
I had it in a semi working state today, got back S-OFF and .76 HBOOT. Had CM 6.1 running for hours. Went to check it a lil while ago, just messing around in the UI and the thing reboots. Reboot loop begins at that point. Doesn't make a lot of sense to me, sounding more and more like hardware.
Menotti said:
Thanks, I will try this tomorrow.
I had it in a semi working state today, got back S-OFF and .76 HBOOT. Had CM 6.1 running for hours. Went to check it a lil while ago, just messing around in the UI and the thing reboots. Reboot loop begins at that point. Doesn't make a lot of sense to me, sounding more and more like hardware.
Click to expand...
Click to collapse
Did an RUU to the latest for craps and giggles. This makes S-ON and HBOOT .97. Same issue, get to OS, random reboot, the reboot loop.
This is easily producible and now that I am in S-ON and no recovery installed, I should hopefully be able to replace it. Definitely hardware, possibly CPU overheat from what I've read earlier.
I'm afraid my sprint store may force me to go direct to the manufacturer since this would be a manufacturer warranty repair. they told me over the phone (sprint corp) that this is the policy. I'll walk in and try.
Menotti said:
Did an RUU to the latest for craps and giggles. This makes S-ON and HBOOT .97. Same issue, get to OS, random reboot, the reboot loop.
This is easily producible and now that I am in S-ON and no recovery installed, I should hopefully be able to replace it. Definitely hardware, possibly CPU overheat from what I've read earlier.
I'm afraid my sprint store may force me to go direct to the manufacturer since this would be a manufacturer warranty repair. they told me over the phone (sprint corp) that this is the policy. I'll walk in and try.
Click to expand...
Click to collapse
So I went to the Sprint store today. I pretty easily reproduced the issue.
My options were to go through HTC for manufacturer's warranty, or have it replaced on the spot. Problem is that Sprint charges a $35 "replacement fee" for the convenience. I felt my time (3-4 weeks through HTC) was worth more than the fee, so I paid it and was on my way.
That's interesting. I did not have to pay for my replacement and I did not have to go through HTC who did try to make me pay.
Can anybody help me out with this? I've already searched but haven't found a clear cut answer on what to do.
For a while, I've had random events that cause my HTC Evo (running the latest stable release of CM7) cause my phone to suddenly show the "HTC Evo 4G" white screen, then go black and vibrate 5 times while having the green LED on, which never lets me do anything until I pull the battery out and start it up again. It used to only happen when I did specific things, like whenever I tried using Google Goggles at the store (and had to go through all the trouble of disassembling my 3 layer protective case just to pull the battery again). It even happened again yesterday when I was trying to use Goggles on a specific item, but it has happened before in other events since then, like when I was browsing my phone's running applications menu, or even one time when I was simply browsing the internet on it.
I've been taking steps to try and fix it, but I think it's been getting worse. I tried downloading CM7 and Google Apps again to flash on the phone to see if it fixed anything. I tried doing this again, but clearing the data and cache this time. I tried flashing the latest CM Recovery (since I stayed with 2.5.x.x for as long as I could remember), and I'm pretty sure it's gotten worse. There's points where I get to the CM7 boot animation and the phone then does the white screen and five vibrates again, and just a moment ago when I was sure I finally solved it after clearing data and cache, while filling out my Google account info, it happened again and I was greeted once again by that horrendous white screen and the five vibrates.
Now I don't know what to do. I still have S-OFF, but I have no plans to unroot. Can anybody think of suggestions? I've already tried Googling and haven't gotten anything useful enough to help me so far.
EDIT: I guessed it would help if I was a bit more specific. This started happening about two or three weeks ago after I tried using Goggles for the first time in ages. Since then, I've had this issue coming back over and over. It also puzzles me how Goggles usually works completely fine when I'm at home but causes the phone to go black and vibrates 5 times whenever I'm at a store.
Also, right now, I re-downloaded CM7 and Gapps from the CM mirrors instead of simply reusing the ones that ClockworkMod had saved for me already. I hope this somehow makes a difference.
Also, last edit, if I manage to solve this somehow, I'm going to definitely post the answer to what I did in case anybody else out there is having the same issue.
EDIT 2: Welp, re-downloading CM7 and flashing again didn't do anything to fix the problem. I'm going to try another ROM to see if the problem persists. I really want to stay with CM7, though.
Did you wipe everything? Cache and so on ect....?
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
SirSigma said:
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
Click to expand...
Click to collapse
Why would you lose root "for ever"?
Just curious ....
Sent From The Tree House Out Back!
I had the same exact issue with my Evo over the past 2 weeks. But I never use Goggles and run MIUI pretty much exclusively. I was never able to fix it and it just got worse. I unrooted and still have the same problems.
I notice it happens on 3g data, I can't remember when it happened on wifi.
I am selling mine back to Sprint tmrw and using my upgrade to get the Nexus S for$50. Then hoping the Evo 3D comes out within 30 days.
Sent from my PC36100 using XDA Premium App
I took it back to Sprint today, and after being treated like a second class citizen for rooting over and over, they managed to somehow fix the random reboots, but have initiated the OTA update for me. Now I'm sitting here with it and it's asking if I should install it now or later.
I'm hesitant because I tried to unroot earlier, and since then, the technician at Sprint said that it wasn't really unrooted or something (I remembered using unrevoked forever last year when I rooted). I'm scared that maybe I'll lose my chance at being able to root again if I accept the update or not. I'm also scared if I won't be able to get full root from here.
EDIT: SON OF A *****. I can't believe this. I applied the OTA update like a good boy and everything, and then the phone starts boot looping randomly again. This is the last straw. I'm going to go back to Sprint tomorrow and be more in-your-face about this problem. I'm through letting them treat me like **** just because I rooted my phone once.
I have a similar problem.....
My problem is random. My phone will go into constant reboot mode until I pull the battery out for 10 minutes. Just pulling the battery and putting it back does not help.
I also noticed that I am losing GPS signal occasionally. It is random too. The GPS will come on and work for about 5 minutes then just lock up. I have to reboot to get it working again and there is no rhyme or reason as to when it will stick (or wont) or how long it will last. It may work for 3 days and then not work a lick for 3 days.
The local Sprint store replaced the back red portion of my phone (the part with the camera lens and kickstand) stating it was an GPS antenna problem. I got 30 secs outside the store and tried the GPS....same problem. I went back into the store and showed them and they tried to convince me I needed AGPS on as well. AGPS always worked but is not as accurate as the satellite GPS. The repair shop refused to do more or order a replacement. I just got scammed out of $35.00 cause nothing is fixed.
I got so pissed, I called Sprint. They were terrific. They refunded the $35.00 the repair center charged me of the repair (the rip-off repair) and agreed to send a replacement phone. Awaiting arrival of the replacement but they are back ordered...so, maybe, I'll get a new phone instead of a refurb.
Long story short...I don't know what is causing your reboots. Mine could not be solved by software changes. My phone was rock solid until around a month ago. Then the GPS dropouts and reboots became more frequent until they became unlivable. I think you have a bad device and would seek replacement.
I had the same problem with mine about a month ago. It happened once about a month before that and then a month ago started happening a lot. I finally narrowed it down to how "hot" it was (body temperature in this case). So basically any time that I was in the car it happened. I was able to unroot (you have to make sure you to s-off on) and put a stock rom on it, and take it in with it happening. They took it for an hour and said they had not seen any issues. I finally convinced them and the replaced it with a refurb. I'm okay as long as it works, but it makes me wonder what happened. When I first got it I used fresh for about a week and then went to CM and was on it the rest of the time. I used an SBC kernel starting around the same time and am thinking maybe that had something to do with it... Just as a precaution I'm staying away from SBC kernels.
If I were you I would just go to the store and get a replacement if you can otherwise if it's like mine you won't be able to count on it working...
Good luck
Hello,
I have a HTC Desire S-OFF for a week. I don't think that AlphaRev has something to do with it because I rebooted it at least 6 times since the operation.
The problem began yesterday when it fell from about 2 Ft and the battery went out of the phone. For the first 10 minutes, my screen was looking like a starchart. After that, I removed the battery and now when I try to boot it up, the screen remains black. I can confirm that my phone has booted up because the below buttons are lighten up (when I press on power button) and there is the green LED telling probably that I've got emails. There isn't any scratches or crack on the screen.
I don't know that to do. From where could the problem come?
Thanks in advance.
Vascer
Hello. It's probably a problem from the motherboard, maybe a short circuit or something. If you don't have any esthetic problems maybe you could try and get it to the guarantee and get it repaired for free.
I would be less probably to be a soft problem, since Bricked Screen only comes after flashing some .zip files incompatible.
truy to put your phone in fastboot power+back wait 30 second and then instal the ruu and your phone is back to normal
@UsManyDead. There are just minor scratches on the aluminium chassis but nothing that let me think that I've broken the screen. I'll send it back according to warrenty.
@en_mih. Thanks for you answer. Now they aren't supposed to see that i've rooted and S-OFF my phone?
Thanks for your answers.
nop your waranty is available good luck , wait for the message when you breng your phone home
Good, I'm going to send it to the support by mail. I will get it in ten days according to the technical support I've called this morning. I will call tomorrow because they forgot to give me the adress. Or I will rather ask one of their technicians to pick it up at my home, it is easier.
I will reply again when I will get it back.
Many Thanks.
good luck man
I finally got it back today, their tracking website told it was ready for a bit more than 2 weeks. I had to call the support 3 or 4 times before getting my telephone back (today).
The telephone is working again, they updated and replaced a component. Best news: the warranty worked so many thanks to both of you.
Virgile
Last week I have rooted my LG G3 so I can install Cyanogenmod 13 on it, bcs after some time I felt my phone got slow and the battery life was not that great. I installed it and it got really better. I tried to get a more stock feel so I installed Xposed and the module Android N-ify to get some Android N look to it. Like always, it said my phone can get into a boot loop, but I knew how to fix it. So, one morning I woke up and saw my phone in the reboot screen and didn't care a lot about it. Later I woke up to get ready to go to my lectures, but the LG logo was still there on my screen. It would then get black and the logo reapears. I thought it got into a bootloop and reflashed CM, but still. I wiped the whole system, reinstalled it again, nothing. Flashed stock Firmware to it, still the same. I brought the phone to the workshop where I work and a coworker took care of it, saying he installed the softwer anew and it really looked like it was fixed. I got home, plugged it into the charger and when I got back it was like before, restarting... It didn't look like it was software based so I searched the forums and saw that a lot of similar problems were solved with buying a new battery. I did the same but it got even worse... Before I could actually sometimes get pass the bootloop but WiFi, Bluetooth and the other connectivities wouldn't work, now it just keeps bootlooping. A friend of me, who works at a repair service, said I should buy a new "power flex" for the phone and install it. I bought it, but I am not sure if it will fix it. It should arrive sometime next week, but I wanted still to ask here if somebody has somekind of idea that could help me. And yes, I tried also to put a piece of paper between the battery and the simtray, but didn't help me... Would the problem be solved if installed the power flex? And did this happen bcs I rooted my phone?
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
This sounds really similar to what I had happen after a while with my first Pixel XL. I tried to document everything HERE.
Wiping dalvik cache through TWRP seemed to be a short term fix (daily), but even that eventually stopped working. I ended up being able to jump into an "open enrollment" period for adding insurance for the phone with Verizon and then was able to use their extended warranty system to get a replacement phone (which was confusing since they said it was not an insurance claim since it appeared to be a phone defect out of my control, so I'm not 100% sure I even needed the insurance? Your mileage may vary.) The replacement was a refurb but has worked perfectly ever since I got it. They still had them in stock at the time or else I'd have tried to push for a 2 (or maybe now push for a 3 or 3a?). Good luck!
just went through the same thing. research shows it was most likely a known motherboard issue. its out of warranty so i bought a used one on swappa for 80 bucks and then sold my non functioning one at an ecoATM for 30 bucks. so im only net -50.
tgumina said:
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z
↑extract and fastboot flash this