Related
I'm not sure what happened but this morning I installed Codename Android's rom since everyone's been speaking so highly of it. I immediately got reboots right after starting. The screen would freeze and then the phone would reboot. I figured there was something wrong so I formatted data/factory reset, formatted cache and even formatted /system and installed it again. No reboots but the earpiece would not work on phone calls (speaker phone does). I also noticed that the screen doesn't turn off when I hold the phone to my face (so the proximity sensor seems to be messed up too). So I installed another rom: Redemption Rom. Same problem. I installed GummyNex, same problem.
I even unrooted and relocked the bootloader and EVEN THEN the earpiece did not work.
I feel like this is a software issue because it happened after installing a rom AND the proximity sensor doesn't work which seems strange for both that and the earpiece to stop working at the same time...
Is there something else that I haven't tried yet? Any suggestions??
I've only had the phone for a couple days so it could easily be a hardware issue I suppose, but I wanted to check if anyone had anything like this happen to them.*
Thanks guys!
Codename Android....if everyone's so highly speaking of it how come I haven't heard of it?
- Which version of the phone you have? CDMA? I'm assuming?
- What kernel?
Codename Android is one of the most popular roms on Rootzwiki
HeliosAI said:
Codename Android is one of the most popular rom on Rootzwiki
Click to expand...
Click to collapse
This is XDA, not Rootzwiki. I googled it. Answer the rest of the questions.
Have you tried flashing another ROM? Flashing stock images provided by Google?
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
I tried a few other roms and the issue was still there as well.
HeliosAI said:
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
Click to expand...
Click to collapse
And you've checked the obvious that the headphones work on another device correct? Tried another headphone on the phone?
If you fully wiped the phone and tried it with another ROM then it's most likely a hardware problem. And maybe it was a coinicidence that it broke right when you flashed the ROM.
Go into your about phone and tell me what it says for "kernel version"
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
HeliosAI said:
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
Click to expand...
Click to collapse
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
zephiK said:
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
Click to expand...
Click to collapse
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
HeliosAI said:
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
Click to expand...
Click to collapse
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
zephiK said:
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
Click to expand...
Click to collapse
Yeah very weird. Thanks again man, really appreciate it.
HeliosAI said:
Yeah very weird. Thanks again man, really appreciate it.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck with your new replacement when you get it though.
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 ?
I bought a Galaxy S Glide (I think the same as the Blaze) from an outlet in Hong Kong on import from Canada (on boot it says "Rogers" so I can assume it's from Canada).
After using it for a week it suddenly stopped using the network and said that I need a lock code.
I went back to the shop where I bought it and they said they couldn't do anything immediately and would I like a replacement, which seemed like a nice thing to do.
However, after a couple of days I notice a glitch on the screen happen a couple of times.
I refused to believe it was a big problem (because it was my new phone right!) within a week the screen started to totally crash to the point that it would freeze in the boot up process.
You can see a picture attached of how the screen looks after I managed to do a hard reset.
When it starts to go like this, you cant do anything with it.
The guy at the shop wont change it or refund it, he claims I dropped it.
Samsung Hong Kong don't support it because it's from Canada and the only shop that knows what to do with it is the guy that sold it to me.
I'm taking the guy to the small claims court, but I'd rather have a fixed phone.
Any ideas please?
Thats happen to me, is a problem with the roger version. Everything in internet say the problem is hardware, but now mines works perfect. So, is like a bug in the rogers, maybe hardware problem, but if can be fixed with software i dont think so.
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
links
lorddavid said:
........... problem with the roger version. Everything in internet say the problem is hardware, but ..............
Click to expand...
Click to collapse
I have searched for more information about this problem, but couldn't find anything, do you have any links to anything?
Thanks again for your help.
they dont say exactly, but if you see users with similar problem, they have rogers version, at least all the user that i see with this problem.
Just do what i say, install ICS; and the problem will solve.
Follow this http://www.theandroidsoul.com/andro...ich-update-for-att-captivate-glide-i927uclg9/ for installing the one click.
Sent from my SGH-I927 using xda app-developers app
lorddavid said:
Thats happen to me, is a problem with the roger version. Everything in internet say the problem is hardware, but now mines works perfect. So, is like a bug in the rogers, maybe hardware problem, but if can be fixed with software i dont think so.
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
Click to expand...
Click to collapse
I strongly doubt this, that looks and sounds like a hardware fault. But hey, if there's no warranty option, you've got nothing to lose...
-E- FWIW, I would boot it into download mode, and let it sit on that screen for an hour. Then plug it into your computer and make sure Odin sees it. If it hangs while in download mode DO NOT FLASH ANYTHING. You REALLY don't want your phone to hang mid-bootloader-flashing, that's an automatic fullbrick...
roothorick said:
I strongly doubt this, that looks and sounds like a hardware fault. But hey, if there's no warranty option, you've got nothing to lose...
-E- FWIW, I would boot it into download mode, and let it sit on that screen for an hour. Then plug it into your computer and make sure Odin sees it. If it hangs while in download mode DO NOT FLASH ANYTHING. You REALLY don't want your phone to hang mid-bootloader-flashing, that's an automatic fullbrick...
Click to expand...
Click to collapse
That was all say, but, in odin my glide never freeze, only freeze while booting or charging too. But not in odin. And right now is working without any screen freeze.
lorddavid said:
users with similar problem, they have rogers version, at least all the user that i see with this problem.
Click to expand...
Click to collapse
So you have seen others with this problem? Where have you have seen these?
lorddavid said:
Just do what i say, install ICS; and the problem will solve.
Click to expand...
Click to collapse
Can this be rolled back ?
hkcharlie said:
So you have seen others with this problem? Where have you have seen these?
Can this be rolled back ?
Click to expand...
Click to collapse
If the device is no more under warranty, I would say trying this would not harm the device anymore. Also this is a samsung released update so nothing unofficial about it.
Sent from my SGH-I927 using xda app-developers app
if you search in internet about freeze problem in glide you will see. Can be roll back with odin. But, if you have no warranty on your device, you dont have nothing to lose, and much to win if the problem solve
My brother had this same problem on his glide (bought at newegg). I got him to install galaxym unlock (galaxsim? Something like that), and you purchase an inapp unlock for $3, and it runs, reboots your phone and you regain unlock. They claim its permanent. So far my brother didnt get locked again.
Is cheap, fast and you can also see in the reviews that there are more glides that used it and worked.
Hope this helps!
Sent from my SGH-I927 using Tapatalk 2
luquiyahni said:
My brother had this same problem on his glide (bought at newegg). I got him to install galaxym unlock (galaxsim? Something like that), and you purchase an inapp unlock for $3, and it runs, reboots your phone and you regain unlock. They claim its permanent. So far my brother didnt get locked again.
Click to expand...
Click to collapse
This helped with the frozen screen as shown in the picture?
thats for unlock, is possible that your phone will lock again when update to ICS. my phone was too from newegg and is rogers, thats why i say is a problem with rogers version.
Do what i tell you, you have nothing to lose
lorddavid said:
thats for unlock, is possible that your phone will lock again when update to ICS. my phone was too from newegg and is rogers, thats why i say is a problem with rogers version.
Do what i tell you, you have nothing to lose
Click to expand...
Click to collapse
Thanks for thinking about my problem, but this solution misses one very big point, the phone that was locked was changed for the phone that has a screen that doesn't work.
I do not have the locked phone any more.
probably will lock again after you flash ICS via odin, thats happen to me. Is not a screen problem, again, if you want to try to solve, do what i say before.
I have the exact same problem, was just about to post in the other thread about this: http://forum.xda-developers.com/showthread.php?t=1953672
Bought my phone from Amazon US marketplace about a month ago (but live in the UK), and suddenly the phone did that on start up one day. However, I agree with lorddavid, it is not a hardware fault as it does not freeze in download mode. Samsung service centres won't repair as it does not have a UK warranty, and although I can get a refund by returning I would rather have a working phone.
lorddavid said:
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
Click to expand...
Click to collapse
Was very happy to read this, seems like I'll have to try it. Have been putting it off as it will wipe my phone which I did not want to do just yet - I have a lot of photos and clips which I can't exactly back up as it does not boot normally. Really annoying. Any way to access these/back up before flashing?
And another question, that ICS update is the first leaked one which carried a few bugs (as did the official UCLH2 one) - can I install the fixed UCLJ3 straight away? And do I need a rooted phone in the first place? In Rawr0w0's initial post it seems to suggest I do. Sorry for all the questions, and thanks in advance.
dont remember, i think is the UCLH2, and i think that there was a odin flashable of the latest version (with bug fixes), you can try that (but dont know where download it :/ )
Do you have the photos in your internal storage? i think if you flash with one click, it will delete it, but if you flash the firmware via odin, it doesnt delete it (but i am not 100% sure)
And no, you dont need root to install roms via odin
This is UCLH2 without one click
http://androidromupdate.com/2012/09...-firmware-upgrade-official-kiesota-stock-rom/
And here is the latest version with bug fixes (like keyboard light)
http://androidromupdate.com/2012/11/10/i927uclj3-new-ics-4-0-4-for-samsung-sgh-i927-captivate-glide/
These are the officials. But the second link i never try it to flash because when i has the problem there wasnt that version
Thanks, yeah that's where I was getting the files from, I'll try it tonight, will probably go for the second link, the UCLJ3 rom.
lorddavid said:
And here is the latest version with bug fixes (like keyboard light)
These are the officials. But the second link i never try it to flash because when i has the problem there wasnt that version
Click to expand...
Click to collapse
YES WAHOO!! My phone works! Thank you for the advice! I mainly got it from the other thread but without having read your attempt at flashing I would never have tried it - I'm so happy! I managed to make a back up and copy my media via CWM anyway, but everything was still on there including all my texts and whatsapp messages, and now I have ICM 4.04 too!
Phew I thought I would have to send it back, get a refund and order another one which is a massive pain and lose everything on my phone.
Hkcharlie, you need to try this!
lyricalwax said:
YES WAHOO!! My phone works! Thank you for the advice! I mainly got it from the other thread but without having read your attempt at flashing I would never have tried it - I'm so happy! I managed to make a back up and copy my media via CWM anyway, but everything was still on there including all my texts and whatsapp messages, and now I have ICM 4.04 too!
Phew I thought I would have to send it back, get a refund and order another one which is a massive pain and lose everything on my phone.
Hkcharlie, you need to try this!
Click to expand...
Click to collapse
thats cool Enjoy the phone, is a great phone
Lately I have been getting random reboots and random black screens. The phone will either reboot itself show the galaxy s3 screen then go to complete darkness or vibrate and go straight to complete darkness. This seems to be random and usually starts happening a week or so after flashing a rom or kernel. Right now I am using my own TW rom (in dev section) with kt kernel and team kernalizer scripts. But the kernel doesn't seem to matter as this happens regardless. Does anyone know whats going on? Also this started happening after I ran aokp 4.2.2 for awhile, then odin back to stock and issues started. I've also been having less battery life since then.
Someone please help
anyone?
aamir123 said:
anyone?
Click to expand...
Click to collapse
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Aerowinder said:
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Click to expand...
Click to collapse
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
aamir123 said:
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
Click to expand...
Click to collapse
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Aerowinder said:
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Click to expand...
Click to collapse
ok I guess I'll go back but I don't see why the md5 firmware would be a problem now after I was using it with no problem for a while.
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I flashed the LJC fw and so far it's been pretty stable, only having trouble with excess heat but will probably get better with time. Also I'm having trouble getting a logcat app running (catlog etc). The app opens I give it root permissions, then I get a black screen with loading ring. No log whatsoever, is that normal? tried on both fw btw.
just got another random reboot on ljc fw. any other ideas?
aamir123 said:
just got another random reboot on ljc fw. any other ideas?
Click to expand...
Click to collapse
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
cboss718 said:
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
Click to expand...
Click to collapse
Idk what the issue is I'm gonna go stock for a while without recovering and see if that will fix anything, if not maybe tmobile is the way to go. Btw I tried taking a log cat but get error saying that dev/log/main doesn't exist.
Ok I was doing good for a few hours after flashing stock and not restoring Google account until I got a random reboot just now. I was able to get a log cat tho so I'd anyone can look at it and help.
Sent from my SGH-T999 using xda app-developers app
anybody? Does anyonehave any ideas?
aamir123 said:
anybody? Does anyonehave any ideas?
Click to expand...
Click to collapse
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Aerowinder said:
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Click to expand...
Click to collapse
ok I will try to get that the next time it reboots. Hopefully it's a simple fix, but just not sure what the problem could be.
So I went all these days without a random reboot and finally got one today, but was unable to pull a dmesg as it said does not exist. What can I try to get a dmesg now?
Also the phone feels like it never shuts down, even when I choose to shutdown in the menu it ends up restarting itself then bootlooping or just restarting. I've also noticed that holding home and power to turn phone on works most of the time to get it back to the os only to have it crash shortly after. I press home and power until I see the white splashscreen then let power button go. but staying in os for more than a few mins right now is impossible.
Okay, so I warrantied another m7 last week or so, and the replacement is now having one of the issues I got rid of the old one for.
I flashed the nusense 7 lp, and really enjoyed it, but like the last phone, about 3-4 days after it was up and running, any web pages I try to go to will time out after a couple of minutes of tether being on. Even without tether it won't connect to websites (using mobile data, the whole time) it also drops calls after a few minutes of talking. I've tried the steps listed in the FAQ thread to no avail, twice now. I tried another rom as well, thinking it might be that, no dice. Any idea what's going on or how to fix it?
I don't know if this helps any, but the first time it does this, windows complained about an IP address conflict. Even though tether worked great for 3 days straight.
Interesting development, I tried re-flashing nusense with the verizon kernel option selected today, and when it booted it said "this isn't a verizon sim card" or something to that effect, with no data or anything. So I went to a verizon store and got a new sim card, which solved nothing. Still no network connection (4g or otherwise) so I flashed candycat which brought back my data and everything seems to work. I don't know how long it's going to last, but I wonder if it would be safe to try reflashing nusense at some point?
Also, I wonder if I followed the (vague) steps correctly when I tried to repair this the first time. Assuming it was the corruption issue that the FAQ thread talks about, nothing I tried fixed it. That thread also says that it's a rare issue, but I had it happen with two separate phones, so does that mean there is something wrong with nusense? On my old phone I had been running a different rom for quite a while, but wanted to try out the newest android version. Unfortunately when I got my replacement phone, I had to use it for internet right away, so the only rom I still had on my computer was nusense. I don't know if there is something wrong with that build, but I am always careful to do MD5 checks.
Anyway, for now the phone seems stable, though I wish I had a less barebones rom on my phone. I'm just afraid it's going to start messing up if I flash something else. I also might switch from CWM recovery to TWRP, since I always had better luck with it.
All of Santod's roms recommend twrp. If you are flashing with cwm, that could be the issue. I suggest flashing the recommended recovery in the Rom thread if you decide to run nusense again.
Edit: nesense7 thread recommends the below linked twrp 2.8.3.0
http://forum.xda-developers.com/showthread.php?p=57813724
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
All of Santod's roms recommend twrp.
Click to expand...
Click to collapse
To be honest, I can't even remember why I didn't use it to begin with. Are these issues possible symptoms of that do you think?
Though I'm a little dubious that this is the cause, since I used TWRP on my old phone and updated it before I installed that rom. But I will definitely CWM cause I don't like it.
It could have caused the issue. If you feel adventurous, you can try flashing with the recommended twrp and see if that works.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
It could have caused the issue. If you feel adventurous, you can try flashing with the recommended twrp and see if that works.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I'm dumbfounded. So when I install nusense with the verizon kernel selected as an option, my phone breaks, either it won't fully boot, or if it does it doesn't recognize the sim card. However, if I then install another rom (or I'm guessing the same one, but without the verizon kernel) it works perfectly for a few days, I can tether, I can browse the web, I can reply to you. But it still breaks after a few days, and I need to "break" it again to fix it.
squat251 said:
I'm dumbfounded. So when I install nusense with the verizon kernel selected as an option, my phone breaks, either it won't fully boot, or if it does it doesn't recognize the sim card. However, if I then install another rom (or I'm guessing the same one, but without the verizon kernel) it works perfectly for a few days, I can tether, I can browse the web, I can reply to you. But it still breaks after a few days, and I need to "break" it again to fix it.
Click to expand...
Click to collapse
And this is flashing with the recommended twrp? How did you flash the recovery?
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
And this is flashing with the recommended twrp? How did you flash the recovery?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
adb.
squat251 said:
adb.
Click to expand...
Click to collapse
Are you on the latest firmware? Sorry for to my through the basic questions, just want to make sure everything is set right. I know you posted you got a replacement phone, but sometimes they can come with older firmware. Do a fastboot getvar all and be sure your firmware version is the latest from santod's thread of flashable firmwares.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Are you on the latest firmware?
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.13.41.0702
version-cpld: None
version-microp: None
version-main: 5.28.605.2
Correct recovery, correct firmware... Only other thing I could think of is bad download, but you said MD5 was good... I am stumped. Maybe @dottat or @santod040 would know another avenue to see why you are having issues with just one Rom.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Correct recovery, correct firmware... Only other thing I could think of is bad download, but you said MD5 was good... I am stumped. Maybe @dottat or @santod040 would know another avenue to see why you are having issues with just one Rom.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
No no, see I'm having trouble with every rom, that's the issue. I don't mind swapping to something else, but it's the same story no matter what I do. It will work fine for a week or so, but if I leave my house it will tether for about 5-10 minutes, then everything times out. Some times if I'm on like youtube, it will still load videos, but other times it won't. It doesn't matter what rom I'm running, this has been happening. And now I can't even fix it to work. This is driving me nuts.
As far as I know, it's not a defective phone, since the symptoms are the same between this refurb phone and the one I sent in. The issue only started after I installed nusense.