Hi,
at first i try to post in the related thread, but i havn't enough posts to do this.
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-beta-t2535996
After flashing the latest ROM my phone can't get a network connection. Wifi works. I used CWM 6.0.4.7, SlimKat Build 3.6 and the latest gapps from SlimRom (Build 3). I can't receive baseband, network, phone number or IMEI in the settings. All is unknown. Also when the phone starts, it doesn't ask for my PIN.
Re-install doesn't work. Another SIM doesn't work, too. CM 10.1.3 works fine.
Model: GT-I9305
Provider: Vodafone
Baseband: I9305XXUEMK1
Some ideas?
That is not a rom problem, for sure.. What can I say, you are doing everything right, but I might recommend using Philz recovery, I've never had any problem with it. Reboot recovery, full wipe and then flash
Try to flash with Odin latest stock 4.3 kernel and then try again with wiping everything before.
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Druffbold said:
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Click to expand...
Click to collapse
For sure it was problem with ROM. Actually with radio ROM, not the Android itself.
Make a backup of your ROM and save radio image from it.
Then you can flash some other ROM you like and flash this working radio image after that.
Related
Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!
elsaphnite said:
Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!
Click to expand...
Click to collapse
have you tried the official stock 4.1.2 rom?
I would say even before answering above question, have you done a factory reset? (Be on a safe kernel of course)
Sent from my GT-N7000 using Tapatalk 2
yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?
elsaphnite said:
yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?
Click to expand...
Click to collapse
i suggest you download latest firmware from sammobile.com and flash using pc odin...
Mayank Chandwani said:
i suggest you download latest firmware from sammobile.com and flash using pc odin...
Click to expand...
Click to collapse
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.
asf58967 said:
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.
Click to expand...
Click to collapse
You really seem to be sure of you, cowboy!! OK I will try it as soon as I finished this message an d I'll tell you about it.
Thanks !
The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3
asf58967 said:
The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3
Click to expand...
Click to collapse
I agree to the principle : putting the cleanest installation, it's ok for me.:good:
now, I found those data:
http://forum.xda-developers.com/showthread.php?t=2274152&highlight=lt5
http://d-h.st/users/philz_touch/?fld_id=16061#files (PhilZ-cwm6-v5.03.0)
Could somebody tell me if they're effectively compatible and if it's OK to flash those without risk ?
I can't wait to see my Spen running again !
Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?
georgekg said:
Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?
Click to expand...
Click to collapse
When you say it stops working, does it mean it will give not response at all? I have tried spen on cm12. 1 and cm13 night owl and works on both.
Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.
georgekg said:
Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.
Click to expand...
Click to collapse
Did you ever find out was happened with your spen?
Yesterday I noticed this problem on my note. I thought it could be the latest kernel i've had flashed, so I flashed another one. I rebooted, tested my spen and everything was good, so I forget about it. But today my spen is not working at all. I wiped my phone and reinstalled the same rom and it worked at first, but then stopped working forever (I flashed a kitkat rom, then a touchwiz, and it never worked again). I don't know anyone else with this phone so I cannot test if it is the spen :/
Unfotunately not. I stopped thinking about it. I tought to buy new Spen from AliExpress (not expencive solution) and try it...
Hi guys , I already posted thread here about internet not working after flashing radio because I thought that flashing radio messed up connection on my phone, so i reflash rom and everything was working fine although I didnt figured out what happened.
Today i went to twrp 2.6.0 and did nandroid backup of my current rom (viper one) ,so everything passed fine. After that since I reboot I am not available to access to internet over phone. wifi or 3g doesnt matter.
I have a lot of UnknownHostExceptions in logcat. I dont know what can cause this because I had internet then I did nandroid backup and I rebooted.
Tried to wipe out dalvik but that didnt help .
So exactly happen the same thing that happened to me when i was flashing radio through recovery , just in that case i thought it is related with radio so i reflashed rom. I wouldnt like now to reflash rom , so if someone can give me advice what to try ..
Thanks in advance
petarku said:
Hi guys , I already posted thread here about internet not working after flashing radio because I thought that flashing radio messed up connection on my phone, so i reflash rom and everything was working fine although I didnt figured out what happened.
Today i went to twrp 2.6.0 and did nandroid backup of my current rom (viper one) ,so everything passed fine. After that since I reboot I am not available to access to internet over phone. wifi or 3g doesnt matter.
I have a lot of UnknownHostExceptions in logcat. I dont know what can cause this because I had internet then I did nandroid backup and I rebooted.
Tried to wipe out dalvik but that didnt help .
So exactly happen the same thing that happened to me when i was flashing radio through recovery , just in that case i thought it is related with radio so i reflashed rom. I wouldnt like now to reflash rom , so if someone can give me advice what to try ..
Thanks in advance
Click to expand...
Click to collapse
I'd flash the ROM again with a clean install and see if the problem persists. It's not ideal with having to set up everything again but it normally solves any issues.
i would like to try to solve it differently
AllAboutTheCore said:
I'd flash the ROM again with a clean install and see if the problem persists. It's not ideal with having to set up everything again but it normally solves any issues.
Click to expand...
Click to collapse
thanks for your response.
I already solve same problem last time with reflashing. Wanted to try to solve situation where I have that problems with internet every time when I install something from recovery , I wonder if it is something with twrp 2.6.0
did anyone have similar issue ?
If it is from any help i am using elemetalx kernel .
Thanks in advance
petarku said:
thanks for your response.
I already solve same problem last time with reflashing. Wanted to try to solve situation where I have that problems with internet every time when I install something from recovery , I wonder if it is something with twrp 2.6.0
did anyone have similar issue ?
If it is from any help i am using elemetalx kernel .
Thanks in advance
Click to expand...
Click to collapse
Well I'd upgrade to the latest version of TWRP for sure but I use the stock Kernel so can't help with that side of it.
AllAboutTheCore said:
Well I'd upgrade to the latest version of TWRP for sure but I use the stock Kernel so can't help with that side of it.
Click to expand...
Click to collapse
Actually I have latest twrp 2.6.0.1 , i couldnt find later on their site ..
It looks like some problem with dns , but I dont get it why as it was working everything fine before going to recovery to do nandroid backup.
I will provide logcat here as well if will be anyone that can help
I have a S3 Mini I8190N, Baseband I8190NXXALL6, on Three Ireland.
I've tried all of Maclaw's CM10.2 roms for the last month, along with some of OliverG96's releases, and none of them show up any network signal for me, and won't let me search for networks, almost as if the rom can't use the hardware radio.
The stock 4.1.2 rom works perfect.
I've tried changing my baseband from I8190NXXALL6 to I8190NXXAMG1, and that made no difference.
(Stock still has perfect signal, Maclaws CM10.2 has no signal at all)
I've also looked through the build.prop files and compared them to the working stock build.prop, but I don't really think tweaks in there will fix this.
Seeing as this possibly could be a hardware issue, is there a file defining what radio hardware my phone has, like /proc/cpuinfo does for the cpu?
Anyone have suggestions on how i could fix (or help fix) this issue?
I can test suggestions and provide logcats if anyone requires?
EDIT:
Problem solved! seems there were some issues with my modemfs, and golden-guy's suggested fix here worked.
did you make a clean or dirty install?
if dirty try a clean install.
Same bug here and also Oliver96 has the same problem s.s
Sent from my GT-P3100 using xda app-developers app
JackoMJ said:
did you make a clean or dirty install?
if dirty try a clean install.
Click to expand...
Click to collapse
I've tried a dirty install, a clean (factory reset) install, and I've even went into ODIN, flashed a complete stock rom, TWRP, and then put CM10.2 on after that with a factory reset.
alexmarra3000 said:
Same bug here and also Oliver96 has the same problem s.s
Click to expand...
Click to collapse
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
same problem
i have got the same problem too.
got back to original samsung firmware und stock recovery... nothing
i am from germany und tried out any available basebands... nothing
on any stock, theres no problem, but if i want to get some roms e.g. from maclaw.pl i cant get signal at all
greez
EccTM said:
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
Click to expand...
Click to collapse
No, I have the I8190 normal version like OliverG96, and I don't know if he is working on a fix.
The strange thing is some users have the bug and some users not.
Also I have this bug with paranoid rom, pac rom and aokp.
On the contrary with Dmod v6 I don't have any issue, probably because it is based on official firmware, I don't know sincerly.
Sent from my GT-P3100 using xda app-developers app
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
mausdefekt said:
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, i also use O2 (directly) and had never problems with any CM-ROM of Maclaw.
You checked the APN??? Maybe you have to use a different one.
build.prop tweaks
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
I did not try these myself, as I don't have any RIL issues, so use them at your own risk. Reboot afterwards for the changes to apply.
Source: http://geekyogi.tumblr.com/post/24692879082/android-build-prop-tweaks-root-only
Hi
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
golden-guy said:
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Click to expand...
Click to collapse
I compared the maclaw 10.2 build.prop with my own functioning stock build.prop and changed most of the attributes about with no luck. I've also tried both those suggested options, but they seem to be more for improving signal strength rather than actually getting a signal, I didn't see any changes using them.
stenc55 said:
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
Click to expand...
Click to collapse
Like mausdefekt, I get two slightly different results from *#06#.
My IMEI matches up, but when i'm running a non-stock based rom, my IMEI SV is 00 for some reason.
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
joelalmeidaptg said:
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
Click to expand...
Click to collapse
Ive tried that too, no difference. Also tried it with factorymode set both on and off.
I'm using Maclaw's TWRP 2.6.3.0 with kitkat support atm, I've never used any non-TWRP recovery.
mausdefekt said:
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hey,
I am running CM-10.2 on my S3 Mini (Oliver's cm-10.2-20131116-UNOFFICIAL-golden) and RIL is working just fine. So I would not think that there is a general issue with RIL on custom ROMs. Rather, the way how you switch from stock to custom might have an impact on RIL...
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Since when I switched from stock to custom, I exactly did that. And I never had any issue with RIL on any custom ROM I have installed since then - which was basically all versions since the 20130928 release.
Cannot tell if that works out for you, but it's definitely worth a try
Btw, I did not check the additional "/01" in the IMEI output when I was still on stock. Running custom I get the very same output - just the IMEI, without this suffix. In the "about phone" section, the relevant IMEI SV entry does read "01" for me.
I wonder if your cellphone is SIM-locked...
hi
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
I've tried setcpu to raise min. cpu to 1ghz, nothing.
What's wrong? On AC all works fine!
golden-guy said:
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Click to expand...
Click to collapse
I factory reset, flashed back to complete stock I8190NXXALL6 (it's 4.1.2) using ODIN, and everything worked perfect. From there I followed your guide to flash CWM recovery, then flashed maclaw's cm 10.2 (20131123) but I still had the same RIL issue.
Then I tried flash the stock rom with heimdall instead of ODIN initially and then follow your guide, same result.
Then I downloaded the odin version of maclaw's CM 10.2 (20131122) and flashed it directly with heimdall. same result.
After that, I took apart both the stock and odin cm 10.2 versions, and tried use heimdall to flash a hybrid version of the two:
Stock: STEboot1.img, STEboot2.img, Modem.bin
CM10.2: boot.img, system.img, recovery.img
Still had no signal at all, so I flashed TWRP 2.6.3.0 recovery and restored back to my usual stock-based backup.
joelalmeidaptg said:
I wonder if your cellphone is SIM-locked...
Click to expand...
Click to collapse
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Timewolf said:
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
Click to expand...
Click to collapse
I just tried to see if i'd get any sort of signal on maclaw roms by plugging my phone into AC... no joy for me there either
Does it have signal if its plugged in then the phone is turned on, or can you get signal at any time just by plugging into AC? like:
*Turn on phone* > standby (on battery) - no signal > *plug into AC* > standby (on AC) - signal > *unplug AC* > standby (on battery) - no signal
Sounds like your problem could be more hardware based than mine? something to do with voltages possibly? I'm really not sure what to suggest.
EccTM said:
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Click to expand...
Click to collapse
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
joelalmeidaptg said:
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
Click to expand...
Click to collapse
So assuming thats the issue, would getting a network unlock code allow me to use custom kernels and roms?
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
Hi all!
First sorry if this is not the right Forum.
I have flashed many roms In my xt1502
But by now it does not matter the ROM i try, WiFi will not work
I am using clockmod recovery.
Thanks of backup i can still keep using pac-man ROM but none of the other roms based on CM11
Thanks for your help.
I have googled and the answers are not clear
I have tried to change kernels and recovery but issues remain still!
When flashing CM12 based ROM, WiFi works again... So i guess the problem is the build?
Solution
Thanks to myself...
I solved the problem: install TWR 2.6 version, then factory reset. Version 2.8 of TWRP makes sometimes "update binary" error.
You must install a ROM based on any CM11 before 20141104, and then you always do a dirty flash of later version of the choosen rom
I guess there must be something ROM in The versions of cm11 after that date, at least form xt1502 model.