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 ?
Related
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?
I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app
Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings
CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.
I have been using Cyanogenmod 11 Nightlies for my device for about as long as they have been out, so I know it is still a work in progress, and most of the issues I have faced have gone away as newer nightly builds have been released, so I have not reported any issues as of yet.
Within the last month or so, I have noticed a new issue. The mobile data has been randomly cutting out, allowing only emergency phone calls. It only goes out for about a minute or two, but it is still a huge inconvenience. It seems to happen randomly, except after I finish a phone call -- it almost always cuts out immediately after (very frustrating for when calls are dropped, because I need to wait a minute or two before I can call back).
Has anyone else experienced this or know of a fix? I just tried re-flashing the latest radio and that did not seem to help. I have also tried full system/data wipes as well and none of the Nightly builds for the last month or so have been able to fix it.
Thanks, everyone.
You need to flash any touchwiz rom in order reset your nvram.
Corvetrims77 said:
You need to flash any touchwiz rom in order reset your nvram.
Click to expand...
Click to collapse
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
pravus87 said:
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
Click to expand...
Click to collapse
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Corvetrims77 said:
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Click to expand...
Click to collapse
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
pravus87 said:
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
Click to expand...
Click to collapse
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Corvetrims77 said:
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
pravus87 said:
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
Click to expand...
Click to collapse
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
mreadshaw said:
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
Click to expand...
Click to collapse
I actually did not use Odin at all. I was able to find a thread that posted a 4.1.1 stock .zip, a .zip to keep root, and a .zip to keep custom recovery. (I have tried searching for the thread to share with you but am unable to find it). I was definitely over-thinking it. Just install the .zips from TWRP or CWM as you would any other custom ROM -- just make sure you do not have the 4.3 bootloader installed. That's it.
Sorry for the delayed response!
I am trying to get my WiFi working on .96 stock rom and optino to turn on is faded out., Tried resetting many times tried re installing software and moving everything on to stock rom kernel and firmware etc still does not work.
Was originally it was working on .96 firmware but done some updates went on a custom rom and found wifi not working. So reverted back to stock again and now to only find WiFi is not working on it again.
Any one here know how to fix this problem.
mentalghost said:
I am trying to get my wifi working on .96 stock rom and optino to turn on is faded out., Tried resetting many tiems tried re installing software and moving everything on to stock rom kernel and firmware etc still does not work.
Was originally it was working on .96 firmware but done some updates went on a custom rom and found wifi not working. So reverted back to stock again and now to only find wifi is not working on it again.
Any one here know how to fix this problem.
Click to expand...
Click to collapse
Try flash the wifi modules http://forum.xda-developers.com/showthread.php?p=46145682&highlight=module#post46145682 this will happen when you come from custom kermel like trinity kernel, you must flash back stock wifi modules to make the wifi working
chrissiong said:
Try flash the wifi modules http://forum.xda-developers.com/showthread.php?p=46145682&highlight=module#post46145682 this will happen when you come from custom kermel like trinity kernel, you must flash back stock wifi modules to make the wifi working
Click to expand...
Click to collapse
Thanks for the link. Do I just add them to my phone somewhere and then flash with recovery program?
Also will these work on other roms?
Flashed to phone however didn't work still no wifi after flashing with recovery program. Is it meant to say android devices updating as i didn't see that happen this time
mentalghost said:
Thanks for the link. Do I just add them to my phone somewhere and then flash with recovery program?
Also will these work on other roms?
Flashed to phone however didn't work still no wifi after flashing with recovery program. Is it meant to say android devices updating as i didn't see that happen this time
Click to expand...
Click to collapse
you are on .96 firmware right? Try flash the baseband from the original .96 ftf with flashtool, make sure exclude all the option except the baseband. Hope it helps
chrissiong said:
you are on .96 firmware right? Try flash the baseband from the original .96 ftf with flashtool, make sure exclude all the option except the baseband. Hope it helps
Click to expand...
Click to collapse
Just tried as advised and still the same working between 2 threads 5 people in different places and trying so many things lol its crazy. Am sure ill get to the bottom of this sooner rather than later I hope.
mentalghost said:
Just tried as advised and still the same working between 2 threads 5 people in different places and trying so many things lol its crazy. Am sure ill get to the bottom of this sooner rather than later I hope.
Click to expand...
Click to collapse
Just take it easy dude sometimes i wasted a couple hours just to search for solutions and i often get mad but i didnt give up since flashing baseband didnt work, i suggest you to flash back to original ftf since this is the last option
chrissiong said:
Just take it easy dude sometimes i wasted a couple hours just to search for solutions and i often get mad but i didnt give up since flashing baseband didnt work, i suggest you to flash back to original ftf since this is the last option
Click to expand...
Click to collapse
Where would I look at getting the original one that was gingerbread or first releases as ftf i have is .96 baseband
XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf
Also took phone to shop and they even advised it is some software glitch bug hes had a few people with the same sort of problem and its sony that needs to fix it he was on about some part of the software when flashing is not being wiped out and re applied with new stuff and have to remove the files he even checked to see if the files where their and he said well its not that as plugged phone into a reader and shows the files being removed and re applied from new flash.
What other onces besides the XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf I have is their ? might jsut get every single one of them starting from oldest to new n seeing if any work.
mentalghost said:
Where would I look at getting the original one that was gingerbread or first releases as ftf i have is .96 baseband
XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf
Also took phone to shop and they even advised it is some software glitch bug hes had a few people with the same sort of problem and its sony that needs to fix it he was on about some part of the software when flashing is not being wiped out and re applied with new stuff and have to remove the files he even checked to see if the files where their and he said well its not that as plugged phone into a reader and shows the files being removed and re applied from new flash.
What other onces besides the XperiaS_LT26i_6.2.B.1.96_1257-6919.ftf I have is their ? might jsut get every single one of them starting from oldest to new n seeing if any work.
Click to expand...
Click to collapse
Just use the latest .96 ftf, make sure do the clean install
chrissiong said:
Just use the latest .96 ftf, make sure do the clean install
Click to expand...
Click to collapse
Well still not working. Solely beginning to give upon this.
mentalghost said:
Well still not working. Solely beginning to give upon this.
Click to expand...
Click to collapse
Hmm... Try to reflash to your previous ROM and kernel that has working WiFi. If this also doesn't helps, then I think is hardware related
chrissiong said:
Hmm... Try to reflash to your previous ROM and kernel that has working WiFi. If this also doesn't helps, then I think is hardware related
Click to expand...
Click to collapse
I know its not hardware related as I see my wifi option it comes on and goes out and fades away sometimes when hard resetting settings it will light up but then get stuck again, I been reading more about it and found it to be some bug within it and sony have yet to fix the bug that many devices have. tried reverting back to backed up firmware and kernel and no joy still
chrissiong said:
Hmm... Try to reflash to your previous ROM and kernel that has working WiFi. If this also doesn't helps, then I think is hardware related
Click to expand...
Click to collapse
Tried going right back to jingerbread on this it turns on starts scanning and then says error. When using wifi tools I get the error wifi stuck and have looked at sonys database and seems many are reporting the same sort of bugs on the xperia s and other devices with stuck wifi and cant turn on not matter what is done or they have tried.
Well I look and looked and looked.
RESOLVED after 4 bloody days.
After a shocking discovery this actually worked. But think it might be some bug that is within Sky WiFi thats resolved the problem
1 went to https://play.google.com/store/apps/details?id=com.bskyb.cloudwifi
Downloaded installed. Next logged into my account and shortly after I seen devices available to connect to but their cloud. Shortly after saving my settings phone locked up froze and restarted on me n rebooted and then noticed that my ? option was on for saying WiFi available clicked on it and wifi on powered phone down and back on and still on.
mentalghost said:
Well I look and looked and looked.
RESOLVED after 4 bloody days.
After a shocking discovery this actually worked. But think it might be some bug that is within Sky WiFi thats resolved the problem
1 went to https://play.google.com/store/apps/details?id=com.bskyb.cloudwifi
Downloaded installed. Next logged into my account and shortly after I seen devices available to connect to but their cloud. Shortly after saving my settings phone locked up froze and restarted on me n rebooted and then noticed that my ? option was on for saying WiFi available clicked on it and wifi on powered phone down and back on and still on.
Click to expand...
Click to collapse
Glad to know that your wifi is fixed:good::good:
chrissiong said:
Glad to know that your wifi is fixed:good::good:
Click to expand...
Click to collapse
Me to but guess what...... Its stopped working again. the rom I went on is bugy and it crashed n didn't come back on. Booted recovery back up i made and no wifi so this has goto be rom related somewhere or a problem in the builds
mentalghost said:
Me to but guess what...... Its stopped working again. the rom I went on is bugy and it crashed n didn't come back on. Booted recovery back up i made and no wifi so this has goto be rom related somewhere or a problem in the builds
Click to expand...
Click to collapse
Did you format system before flashing a rom? when doing major update, this step is optional
chrissiong said:
Did you format system before flashing a rom? when doing major update, this step is optional
Click to expand...
Click to collapse
I always do to make sure stuff is working like flashing rom wiping data cash etc n then flash and start up.
mentalghost said:
I always do to make sure stuff is working like flashing rom wiping data cash etc n then flash and start up.
Click to expand...
Click to collapse
Emm, i mean format system, it is under mount and storage in recovery. It shouldn't have any problem if you wipe the system before flashing
chrissiong said:
Emm, i mean format system, it is under mount and storage in recovery. It shouldn't have any problem if you wipe the system before flashing
Click to expand...
Click to collapse
Will give it a go now and see if this resolves the problem by wiping everything on it then flashing
Still no joy on this. Looks like something is totally messed up in the software firmware or rom not doing as it is meant to.
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Maybe flashing unikernel will help, it can be found here: https://www.androidfilehost.com/?fid=24269982087012055
Just flash it in Odin, if that does not work you may want to try bringing it to where you bought it for warranty.
No luck, unfortunately.
offthatwall said:
No luck, unfortunately.
Click to expand...
Click to collapse
Idk, @koop1955 any suggestions?
1619415 said:
Idk, @koop1955 any suggestions?
Click to expand...
Click to collapse
Posted this in the other thread: http://forum.xda-developers.com/showpost.php?p=64735692&postcount=19
That is all that I have for you.
offthatwall said:
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Click to expand...
Click to collapse
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
x1xmadex1x said:
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
Click to expand...
Click to collapse
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
koop1955 said:
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
Click to expand...
Click to collapse
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed
x1xmadex1x said:
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed[/Q
Im have the constant reboot now. Im gonna try another pb6 6.0.1 tar file only one ive tried was the sprint worker one said revo in in it. That didnt not fix my constant rebooting issue. So far any rom even after odin stock still rebooting every 2 minutes.
Click to expand...
Click to collapse
will get that logcat
Saafir said:
Note the time and grab a logcat.
Ok i left the phone at home but i did look at the log cat about the first ten lines all had emmc in them im not quite sure. Well I cant read it lol. when i get home il flash twrp and restore a back up let reboot a few times get a log cat and post it will twrps log cat work? If im lucky i might get a app installed to do it. I no longer got adb and fastboot on my computer but will download if needed.
im waiting for a replacement to get to the sprint store. i flashed stock and took it in rebooting sprint guy tried factory resetting it and clearing cache which got it stuck in the pre load starting or optimizing apps before itd finish it it would reboot and if i kept going id beable get to start up settings thats it. now i can flash twrp still it does restores my back ups and after that itl boot the system i can uninstall or install something or what not maybe 1 min after im able to get into it it reboot. only wifi connects though.
Again i had about all roms we got on sprint forum on that phone worked awesome loved it til the time i restored the efs on 6.0.1 with a twrp thats a unofficial build modded to work on 920p.
Click to expand...
Click to collapse
Sounds good thanks man.
Seems as maybe a somewhat common issue unfortunately thats happening for s6 as well as sprint note 5 as there are a few threads regarding the same issue. Theres a thread for s6 on this issue and on 2nd page appears as if someone found a fix having something to do with letting it die completely etc.. http://forum.xda-developers.com/sprint-galaxy-s6/help/constant-rebooting-t3287213
I figured my rebooting issue was corrupted data becausr i was transferring from phone to pc to phone and no md5 check. Though now i will use it. Good luck
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.