unstable notice after 4.08.605.15 update - Droid Incredible Q&A, Help & Troubleshooting

Ok,my mom has a Dinc just like me. However,her's is completely stock except an unlocked bootloader. She installed the update and everything ran smooth. With the occasional freeze. But today she turned it to go to school and turned it back on and she was prompted that her Dinc has become unstable. Can anyone explain this or tell me how to fix it?

ironside2011 said:
Ok,my mom has a Dinc just like me. However,her's is completely stock except an unlocked bootloader. She installed the update and everything ran smooth. With the occasional freeze. But today she turned it to go to school and turned it back on and she was prompted that her Dinc has become unstable. Can anyone explain this or tell me how to fix it?
Click to expand...
Click to collapse
Something got corrupted during the update it sounds like. You can first try a factory reset from hboot, if that dosent work you can do an ruu. However there is no 4.08.605.15 ruu and im not sure if it will let you flash an older version. If it dosent let you do the ruu, your only option would be to try to root and hope you can get a working rom on there.

oh boy
cmlusco said:
Something got corrupted during the update it sounds like. You can first try a factory reset from hboot, if that dosent work you can do an ruu. However there is no 4.08.605.15 ruu and im not sure if it will let you flash an older version. If it dosent let you do the ruu, your only option would be to try to root and hope you can get a working rom on there.
Click to expand...
Click to collapse
I figured those would be my only options. But why would Verizon send out a corrupted update to a phone?

ironside2011 said:
I figured those would be my only options. But why would Verizon send out a corrupted update to a phone?
Click to expand...
Click to collapse
Not really a corrupt update my self and many others had no issues. It is more likley that it was just one of those rare times that things just mess up.

ah
cmlusco said:
Not really a corrupt update my self and many others had no issues. It is more likley that it was just one of those rare times that things just mess up.
Click to expand...
Click to collapse
What shame! Seems like this phone is just on its last leg and can't handle updates of any kind since Froyo

Related

major problem. Need some help. Loopbooting

So I'm at work and go to look at my phone and notice its rebooting which it never does. I watch it and notice its loopbooting at the white Evo screen. Ive never as much as had a random reboot before. I try to boot into recovery and can get to hboot but as soon as I try to select recovery it loop boots at the same point. I tried pulling the battery and that didn't help either. I'm running cm6.1 rc1 with stock kernel and no over or under clocking. I haven't made any changes in a while. Not even any new apps.
Any ideas?
I just went through and read every thread with loop in the title and it seems like with everyone else they had this issue while rooting or flashing or making some sort of change. Nor just on an idle phone
You may need to RUU your phone and start over if you arent able to get into any type of recovery mode...
Sent from my froyo using the xda app
I can get into hboot but that's about it
Just got home finally.. Gonna try to get this bs fixed. I wish I knew what caused it. I can't have this randomly happening again.
I was able to run RUU app and install the update from here;
http://forum.xda-developers.com/showthread.php?t=747319
It just finished and I'm still in a boot loop. Ugh.
I've been searching for hours now and I'm not finding much help
Ugh.. I'm giving up for the night. Been searching for hours and can't find anything that seems to work. And of course today is Thanksgiving and there's no chance of me even getting a new phone.
did you try a 3.29 ruu i'm surprised that sync let you flash a 3.26 if your phone updated to newer that might help also if you used unrevoked you need to flash thier s-on tool
Jbcarrera said:
did you try a 3.29 ruu i'm surprised that sync let you flash a 3.26 if your phone updated to newer that might help also if you used unrevoked you need to flash thier s-on tool
Click to expand...
Click to collapse
The only RUU I was able to flash with the RUU app was the 3.26 one I posted. I downloaded like 10 others and RUU app doesn't see them for some reason.
Also, how can I send a file to the phone with fastboot? I've searched and searched and I'm not sure of the exact syntax to use.
I had S-OFF and was fully rooted untill I ran RUU app.
Any other suggestions? I'm really trying to avoid getting a new phone.
Grabbed a card reader and adapter and trying some other RUU's I found now.. Hopefully something works.
thenags said:
Grabbed a card reader and adapter and trying some other RUU's I found now.. Hopefully something works.
Click to expand...
Click to collapse
i was going to suggest that but you beat me to it have been away all day
thenags said:
Any other suggestions? I'm really trying to avoid getting a new phone.
Click to expand...
Click to collapse
Jbcarrera said:
i was going to suggest that but you beat me to it have been away all day
Click to expand...
Click to collapse
Right now I'm just downloading another RUU to use with RUUApp. Do you have any other suggestions if this doesn't work?
Attempting the .exe found here;
http://forum.xda-developers.com/showthread.php?t=819771&highlight=mirror&page=3
thenags said:
Right now I'm just downloading another RUU to use with RUUApp. Do you have any other suggestions if this doesn't work?
Attempting the .exe found here;
http://forum.xda-developers.com/showthread.php?t=819771&highlight=mirror&page=3
Click to expand...
Click to collapse
Just finished installing that RUU and no change. Still the same boot loop.
Downloading the following RUU now and going to try again.
RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe
And for anyone looking for stock RUU's and having a hell of a time. Here's a good link I found with a bunch of them;
http://shipped-roms.com/shipped/Supersonic/
That one didn't work either.. Still just loop booting. Looks like this thing is just completely eff'd and I need a new one. Damn.
Well, just got home with a brand new phone. It's got hboot 2.20.. Time to get rooting. Ugh.
Just search for a pc3600.img file that is rooted and put on sd and boot to bootloader and flash
sent from my white w/ red trim Evo
krazydude4g said:
Just search for a pc3600.img file that is rooted and put on sd and boot to bootloader and flash
sent from my white w/ red trim Evo
Click to expand...
Click to collapse
I did that as well.. Nothing was working on that thing. Got a new phone now and just finished rooting it and getting it all set up.

[Q] Need Help!! First time EVO Root/CM6 gone bad...

OK....long story short...finally decided to delve into rooting and custom roms. Flashed CM6 yesterday and everything was going great. Then suddenly yesterday evening as I was swiping between home screens on my device everything froze, and I have been trying to recover ever since.
Anything I flash now just freezes, and i have a touch panel-fail so even when i do get a rom to boot i cant actually get into set it to usb mode or anything.
using bootloader i can not get it to connect using the adb driver so that I can push via adb.
about an hour ago I was successfully able to run the latest RUU and it ran successfully, but device is still way laggy (takes 15 minutes to boot) and no touch screen.
Any help would be greatly appreciated!!! don't know where to go from here. From what I have read its not bricked because I can get into Bootloader and Recovery???
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
lil-dice said:
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
Click to expand...
Click to collapse
Is there way I can verify that the RUU did indeed flash *EVERYTHING* back to stock?
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
jalexishg said:
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
Click to expand...
Click to collapse
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Also looks like i can not get into recovery now, when I select the option in the bootloader it just takes me to the screen with a picture of a device and a red triangle
azkevman said:
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Click to expand...
Click to collapse
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
jalexishg said:
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
Click to expand...
Click to collapse
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
you got it...just put it on the root of sdcard and good luck.
Sent from my PC36100 using Tapatalk
azkevman said:
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
Click to expand...
Click to collapse
Yeah... Good luck... Let me know how everything went..
OK, so I loaded this ROM: http://forum.xda-developers.com/showthread.php?t=874091 onto my sd card as PC36IMG.zip
It loads the zip then says parsing for about 1 second then just reverts back to the HBOOT option ???
Doesn't ask me if i want to install????
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
azkevman said:
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
Click to expand...
Click to collapse
I can upload the version I use... Give a sec.(Uploading)
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
jalexishg said:
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
Click to expand...
Click to collapse
Thanks, I will let you know how it goes.
is nand unlocked on the phone?
asafegous said:
is nand unlocked on the phone?
Click to expand...
Click to collapse
I think so, on the bootloader it still shows "S-off" ...doesn't that indicate it is still unlocked?
OK, so I was able to flash the file in the bootloader. It looks like it won't load past the 'HTC EVO 4g' splash screen.
ARGGGGGGGGGGGGGG!!!!!!!!!!!!
But the Installation finish without problems ?
jalexishg said:
But the Installation finish without problems ?
Click to expand...
Click to collapse
yeah, as far as i can tell. It said it completed and gave me the option to press the power button to reboot.
It did finally load up...after about 15 minutes, but touchscreen is still erroring out and not funtional.

Semi-bricked Incredible?

So I flashed Skyraider tonight, wiped data, installed the ROM, and booted up the phone. I was halfway through setting up my Google account when the phone froze and rebooted. Except, it didn't boot back up. It did the "vibrate five times and flash the LED" thing. Didn't think it was a big deal, so I pulled the battery, tried to boot it back up. But it does the same thing.
I can get into the hboot menu, and if the phone is plugged into the computer, it'll boot up into Skyraider, but it can't read the SD card or the internal storage. So, essentially, a pretty screwy phone. I also cannot boot back into recovery. It just does the vibrating thing when I try. My computer doesn't detect the SD card or storage, either. (The SD card is fine, though. I put it in another phone and everything is still there.)
I have no idea what happened with it. I don't know if this is some random hardware damage, or if I should find an RUU and try to fix it or what.
I've had the worst luck with phones these past few weeks.
Any suggestions?
What version of CM Recovery do you have?
I would go back to stock and redo everything again. Download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it PB31IMG.zip and put it on the root of your SD card, boot into the bootloader and let the update run its course. This will bring you back to a completely stock 2.2. From there you can re-root and do as you please.
I was on CW 2.5.1.2. But everytime I try to get into the recovery, the phone just vibrates five times and the LED flashes green. I'm also not sure that hboot is seeing my SD card. I'm going to try it, though.
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
g00s3y said:
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
Click to expand...
Click to collapse
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
godsmacked4653 said:
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
Click to expand...
Click to collapse
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
g00s3y said:
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
Click to expand...
Click to collapse
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
godsmacked4653 said:
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
Click to expand...
Click to collapse
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
g00s3y said:
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
Click to expand...
Click to collapse
I do have the stock drivers. I used unrevoked on Linux, and I've tried the RUU in Windows. But still no go.
I'm probably just going to take it up to Verizon today. If it can't boot, they really can't see that I've changed anything, right?
very true, good luck
g00s3y said:
very true, good luck
Click to expand...
Click to collapse
yes, good luck let us know ho it goes....
Kent_Davis said:
yes, good luck let us know ho it goes....
Click to expand...
Click to collapse
The sales rep looked at it for two minutes, and they're overnighting another Incredible to me.
So on one hand, I'm pretty happy about how easy it was.
On the other hand, I'd rather keep the AMOLED screen.
Does anybody know if I'm going to get a refurb, or will I get a new SLCD model?
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
dpwhitty11 said:
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
g00s3y said:
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
Click to expand...
Click to collapse
Yep. I got my replacement today. It's an AMOLED. As far as I can tell, all the hardware is working like it should.
This is probably the easiest time I have EVER had with Verizon.
But for future reference, five vibrations + blinking green LED = replacement.
I had same problem yesterday, five vibr.+ green blinks, but I had access into bootloader. I decided to reflash stock rom. Finally fixed problem
Sent from my ADR6300 using XDA Premium App

[Q] primoc cdma kernel crash (all kernels)

RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app
cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.
patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.
patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?
MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.
Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...
More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?
Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?

Unable to install latest M8s OTA update v2.20.401.1

Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
spiderwebmkd said:
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Click to expand...
Click to collapse
If you are willing to, you can unlock the bootloader from http://www.htcdev.com/bootloader/ and flash a stock sense ROM or other custom ROMs and that might solve the app crash problem.
bilal.fanatic said:
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
Click to expand...
Click to collapse
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
ckpv5 said:
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
Click to expand...
Click to collapse
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
spiderwebmkd said:
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
Click to expand...
Click to collapse
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
bilal.fanatic said:
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
Click to expand...
Click to collapse
I'll try with @ckpv5 suggestion, to install 2.10.401.1 RUU and then try OTA upgrade to 2.20.401.1. If it fails, or if it succeeds but apps are still crashing as they were before, I'll definitely switch to cm, whatever version is stable at the moment. Double tap to wake is really annoying and I don't need it, I don't use 3rd party camera apps, and I guess I'll have to live without boomsound Thanks for the tip, though.
ckpv5 said:
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
Click to expand...
Click to collapse
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
does someone have stock marshmallow twrp backup. I accidentally deleted mine and now stuck with cm only
spiderwebmkd said:
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
Click to expand...
Click to collapse
I can't access that site but it is the same file that I have that I got from different link.
Yes .. use that one.
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
parser said:
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
Click to expand...
Click to collapse
It passed after you flashed the RUU? the same procedure that I'm about to do?
spiderwebmkd said:
It passed after you flashed the RUU? the same procedure that I'm about to do?
Click to expand...
Click to collapse
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
parser said:
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
Click to expand...
Click to collapse
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
spiderwebmkd said:
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
Click to expand...
Click to collapse
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
parser said:
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
Click to expand...
Click to collapse
I don't have a backup of v2.20. I flashed the v2.10 from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC) , and then I downloaded the OTA update on top of it.
spiderwebmkd said:
https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
Click to expand...
Click to collapse
no no not that. I mean TWRP backup. I dont want to go back to zero relock the phone and flash the zip and re-unlock the phone root again bla bla.
Since you did the same process, I thought maybe you took a backup of the rom after you updated it.
I made a mistake by not taking a backup of it so now it is a problem for me :/
Edit: damn! thanks anyway. I have a long night in front of me clearly. I hate this phone :/
V4A is not working anymore with the latest update. Is it me or everyone has the same problem.

Categories

Resources