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.
Related
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 ?
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
It was perfect, a match made in heaven!
I had the Dirty Unicorn mod installed on my phone with all the modem drivers working, all my software configured. But.... it seems there were some old CWM backup files left on the SD card which were taking up a bunch of space. So i backed up my system and formatted the sd card, and when i reboot i got the "missing modem" problem, where nothing modem related works. After several attempts I was able to restore the ASOP rom and install the modem driver zip immediately after the rom in CWM recovery.
But i was missing all my settings and apps. So i thought hey, i got it to work, i should be able to run my restore again. Nope... screwed, and now i cannot even do the first fix. nothing is working.
o if any one has any tips, i would greatly appreciate it!
Tmobile T889
Running Dirty Unicorn ASOP 4.4.2 (was really loving this rom)
I am getting the "Signal Strength 2147483647 dBm 255asu" issue, and thus there is no connectivity.
My SD card is working
rigzin said:
It was perfect, a match made in heaven!
I had the Dirty Unicorn mod installed on my phone with all the modem drivers working, all my software configured. But.... it seems there were some old CWM backup files left on the SD card which were taking up a bunch of space. So i backed up my system and formatted the sd card, and when i reboot i got the "missing modem" problem, where nothing modem related works. After several attempts I was able to restore the original rom and installed the modem driver zip immediately after the rom in CWM recovery.
So i thought hey, i got it to work, i should be able to run my restore again. Nope... same thing again, and now i cannot even do the first fix. nothing is working.
so wish me luck. I am getting ODIN and restoring my phone back to stock.
Click to expand...
Click to collapse
Why don't you try looking for your modem online. The phone should be able to flash the modem in recovery mode. Im assuming you have a tmobile note 2 so try looking for tmobile ntoe 2 modems. There is a forum post that has the modems on it.
ce321 said:
Why don't you try looking for your modem online. The phone should be able to flash the modem in recovery mode. Im assuming you have a tmobile note 2 so try looking for tmobile ntoe 2 modems. There is a forum post that has the modems on it.
Click to expand...
Click to collapse
thanks for the reply.
But I tried 3 different versions.
And at one point they were working
I tried
T889UVALJ1
T889UVBMD1
T889UVUCMK7
rigzin said:
thanks for the reply.
But I tried 3 different versions.
And at one point they were working
I tried
T889UVALJ1
T889UVBMD1
T889UVUCMK7
Click to expand...
Click to collapse
No problem and damn that sucks. Ill odin to stock and try to reflash the rom and before rebooting I would flash the modem
By the way how was the dirty unicorn rom
ce321 said:
No problem and damn that sucks. Ill odin to stock and try to reflash the rom and before rebooting I would flash the modem
By the way how was the dirty unicorn rom
Click to expand...
Click to collapse
Alright,
I just installed slimkat (it is 4.4 but only a 140 meg file) and the modem is still not working. Now it says 0db, and i tried flashing the modem.
I also switched to TWRP in case CW was the problem. But this did not work either.
the Tmobile stock version is over a gig, and here in the nether regions of the planet the connection is very slow. So ill have to go to town and have someone download it for me.
I can sing the praises of the DU mod all day long, it is pretty and super fast/smooth! Great mod features and hacks. It was working perfectly, but my SD card reported having only 2 gigs free, and after formatting it has 10 gigs free but no modem function
i cannot even run USSD codes!!!
rigzin said:
Alright,
I just installed slimkat (it is 4.4 but only a 140 meg file) and the modem is still not working. Now it says 0db, and i tried flashing the modem.
I also switched to TWRP in case CW was the problem. But this did not work either.
the Tmobile stock version is over a gig, and here in the nether regions of the planet the connection is very slow. So ill have to go to town and have someone download it for me.
I can sing the praises of the DU mod all day long, it is pretty and super fast/smooth! Great mod features and hacks. It was working perfectly, but my SD card reported having only 2 gigs free, and after formatting it has 10 gigs free but no modem function
i cannot even run USSD codes!!!
Click to expand...
Click to collapse
Damn bro that sucks. I get fast good signal and lte so I would only take 20-30 minutes to download.
I would flash asop roms but I eventually switch back to touchwiz. Mostly due to the fact that I like using my headset and I need aifi calling for certain places. And the last 4.4 rom I had was omni rom but I would lose root. Dn3 rom is the best touchwiz rom but unfortunately no wifi calling
Try this link I just found it http://forum.xda-developers.com/showthread.php?t=2551748
ce321 said:
Damn bro that sucks. I get fast good signal and lte so I would only take 20-30 minutes to download.
I would flash asop roms but I eventually switch back to touchwiz. Mostly due to the fact that I like using my headset and I need aifi calling for certain places. And the last 4.4 rom I had was omni rom but I would lose root. Dn3 rom is the best touchwiz rom but unfortunately no wifi calling
Try this link I just found it http://forum.xda-developers.com/showthread.php?t=2551748
Click to expand...
Click to collapse
bro i was so stoked!
first i ran it on DU rom and it crashed it.
then ran on SLIM but had no change
i guess ill be downloading the stock...
i really hope i dont end up with a really fancy Ipod
rigzin said:
bro i was so stoked!
first i ran it on DU rom and it crashed it.
then ran on SLIM but had no change
i guess ill be downloading the stock...
i really hope i dont end up with a really fancy Ipod
Click to expand...
Click to collapse
Haha I dont think so bro. Odin should be able to fix it. As long as you havent ota update to 4.3 you should be fine. If you dont need wifi calling give DN3 rom a try. Just follow the post and it should go smooth. Just dont reboot and install mk7 modem. DN3 is cool because it has Note 3 features
to fix this issue download selinux mode changer from play store and set to permissive
mattlowry said:
to fix this issue download selinux mode changer from play store and set to permissive
Click to expand...
Click to collapse
I did this but it did not work
rigzin said:
I did this but it did not work
Click to expand...
Click to collapse
now reflash the rom
mattlowry said:
now reflash the rom
Click to expand...
Click to collapse
no it still did not work
rigzin said:
no it still did not work
Click to expand...
Click to collapse
Hmm did you try to odin it. Odin back to stock and try to reinstall the rom. Hopefully that should work
that is the next plan of action, but it is going to take two days to download, esp with all the power outages in Nepal
rigzin said:
that is the next plan of action, but it is going to take two days to download, esp with all the power outages in Nepal
Click to expand...
Click to collapse
ooh damn that sucks. Hopefully you get your phone fixed
Protip if you don't already do this: especially with frequent power outages or unreliable internet connections, check your MD5 or SHA1 checksums when you download ROMs before flashing them.
On Windows, you can use md5sum in Cygwin or Hashtab (which is a Windows Explorer extension that give you a tab in a file's properties). On Linux, most distros have the binaries included by default.
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 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