Related
Hi, I have a problem with my nexus s.
Since yesterday my phone is stuck on "Only Emergency Calls"
I tried an hard reset, i tried to flash another rom (i used to run cm 7) but nothing works.
If i insert another sim card (different carrier) in the mobile it works!
If i insert my sim card in another mobile it works!
That's very strange!
I got this trouble twice, whit CM7 and CM7.1.
Did you used power widget control to switch between 2G/3G on CM7? I did, and twice, the network gone k.o. Yesterday that happened again, and after a little bit of swearing, I tried a cache/dalvik wipe and a permissions fix, and now it seem to be ok. Of course, I'll never use that damned widget again.
Yes i used it.
But unfortunately with cache/dalvik wipe but the device is still stuck!
What happen when you boot your phone? It ask you for pin code? Have you tried to manually scan for available carrier and eventually set 2g or 3g through settings?
Yes it asks me for the pin code.
I tried to switch 2g/3g and airplane mode on/off but nothing change.
If i tried to scan for the available carrier it shows me my carrier but i can not catch it.
In the notification bar appears the network indicator without the X (when you run the phone without sim) so it's like it knows that there is a network but it can't catch it!
PS: I tried a sim with my same carrier (vodafone) and it doesn't works.
Other carriers works!
Could be the efs folder?
The imei looks good, is the same on the mobile's box
Flash a stock rom and then see whether it works. If it works then do a clean install of CM7, I had an data issue, My data din't work.
I did a full wipe and then installed a stock ROM, It started working/
I wipe data cache, dalvik cache, everything i suppose.
I tried to install a stock rom via odin.
But it doesn't works.
Flash a stock ROM for your phone from here in recovery,
http://forum.xda-developers.com/showthread.php?t=1063664
Do a full wipe before flashing. Don't use ODIN.
saranyan said:
Flash a stock ROM for your phone from here in recovery,
http://forum.xda-developers.com/showthread.php?t=1063664
Do a full wipe before flashing. Don't use ODIN.
Click to expand...
Click to collapse
why not odin?
Odin sometimes can terribly go wrong, That's why its advisable to flash stock rom from recovery,
Safest way.
Besides rom, have you tried reflashing radio?
Sent from my Nexus S using XDA App
saranyan said:
Odin sometimes can terribly go wrong, That's why its advisable to flash stock rom from recovery,
Safest way.
Click to expand...
Click to collapse
Ok, i hope nothing went bad with odin
gnaurittiello said:
Besides rom, have you tried reflashing radio?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I suppose.
When i flash the rom with odin I insert a file called mobile, is this the radio?
However how can i flash a new radio?
I never used Odin for Nexus S, so I don't know if it can cause issue with flashing. However, flashing recovery, rom, radio (even manually restore nandroid if you want..) is very simple with fastboot:
Code:
fastboot flash radio radio.img
If you haven't fastboot, you can follow this guide
flashed two different radios from modaco
XXKB3
XXKB1
Nothing change :|
It's strange..
You can try flashing last OTA update (2.3.6, GRK39F build, KA3 bootloader, KF1 radio) through CWM:
1) Install CMW using fastboot
2) Reboot into recovery
3) Wipe Data/Cache/Dalvik Cache and format System (mounts and storage=>format /system)
4) Install OTA update from SD
PS. I think you have i9020T or i9023, so that OTA will be fine. Instead, if you have i9020A, dowlonad this package .
PPS. I don't think it would make any difference, but I suggest you to remove SIM before flashing.
No way man, it doesn't works
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app
Hi everyone,
I have an SM-P900 rooted via the latest Chainfire Auto-Root. After that I installed the custom recovery TWRP 2.8.0.0 via Odin.
Through this custom recovery I installed the cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip
Before I flashed CM I wiped everything except the internal and external storage. Then I installed the latest gapps and after that the thouchscreen stopped working. The S-Pen is working but I cant use it with my fingers anymore.
Greetings,
Andre
I flashed the latest stock rom (PHN-P900XXUANI1-20141010224130) with Odin, the touchscreen (without SPen) still doesn't work.
Has anybody an idea how I could get it back working?
Flashed an older Stock ROM for my region (DBT, P900XXUANAE) and updated with Kies to P900XXUANC4.
Then I did a factory reset.. still no touchscreen. But the SPen is working fine.
Volans21 said:
Flashed an older Stock ROM for my region (DBT, P900XXUANAE) and updated with Kies to P900XXUANC4.
Then I did a factory reset.. still no touchscreen. But the SPen is working fine.
Click to expand...
Click to collapse
That's very strange - does the touchscreen work in TWRP?
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Volans21 said:
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Click to expand...
Click to collapse
flashing stock firmware with odin doesn't delete user data.
i have two versions:
1. it's hardware issue
2. flash twrp. wipe everything including internal data, then flash with odin your origianl stock firmware for your region. if it doesn't help, see above.
edit: i read your posts again. it looks like a hardware issue...
I agree, that's why I asked if it worked in TWRP - I feel it may be a hardware issue, coincidental timing?
bonuzzz said:
flashing stock firmware with odin doesn't delete user data.
i have two versions:
1. it's hardware issue
2. flash twrp. wipe everything including internal data, then flash with odin your origianl stock firmware for your region. if it doesn't help, see above.
edit: i read your posts again. it looks like a hardware issue...
Click to expand...
Click to collapse
Volans21 said:
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Click to expand...
Click to collapse
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
natives bookmul
bonuzzz said:
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
Click to expand...
Click to collapse
would KIES allow him to update to P900XXUANC4 if he was on a p901, or would it not know the difference.?
bonuzzz said:
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
Click to expand...
Click to collapse
notspike said:
would KIES allow him to update to P900XXUANC4 if he was on a p901, or would it not know the difference.?
Click to expand...
Click to collapse
@bonuzzz
No, I didn't find a three-part-firmware for my SM-P900.. maybe you missunderstood me: Years ago I flashed my Samsung Galaxy S2 (SGS2) with such a firmware.. I always thought, that the PIT file repartitioned my SGS2 and so the ROM was set to factory defaults. And thats why I was asking for a three-part-firmware with PIT file
I'm 100% sure that I have a SM-P900 (No LTE/4G, only Wifi). And thats what I did before the touchscreen stopped working:
A firmware update with Kies 3 to P900XXUANI1
Rooting with CF-AutoRoot (CF-Auto-Root-v1awifi-v1awifixx-smp900.zip)
Flashed TWRP 2.8.0.0 with Odin 3.07
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip) and started CM11 successfully
Flashed gapps for CM11 (gapps-kk-20140606-signed.zip)
Decided that I want to have a gapps version without all those bloatware, so I did:
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip)
Flashed gapps (pa_gapps-modular-pico-4.4.4-20141011-signed.zip) and started CM11 successfully
Worked some minutes with the tablet, rebooted the tablet and after that..
..the touchscreen stopped working.
@notspike
Kies knows the difference.. it even knows for which region the installed firmware is and installs the corresponding update.
Volans21 said:
@bonuzzz
No, I didn't find a three-part-firmware for my SM-P900.. maybe you missunderstood me: Years ago I flashed my Samsung Galaxy S2 (SGS2) with such a firmware.. I always thought, that the PIT file repartitioned my SGS2 and so the ROM was set to factory defaults. And thats why I was asking for a three-part-firmware with PIT file
I'm 100% sure that I have a SM-P900 (No LTE/4G, only Wifi). And thats what I did before the touchscreen stopped working:
A firmware update with Kies 3 to P900XXUANI1
Rooting with CF-AutoRoot (CF-Auto-Root-v1awifi-v1awifixx-smp900.zip)
Flashed TWRP 2.8.0.0 with Odin 3.07
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip) and started CM11 successfully
Flashed gapps for CM11 (gapps-kk-20140606-signed.zip)
Decided that I want to have a gapps version without all those bloatware, so I did:
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip)
Flashed gapps (pa_gapps-modular-pico-4.4.4-20141011-signed.zip) and started CM11 successfully
Worked some minutes with the tablet, rebooted the tablet and after that..
..the touchscreen stopped working.
@notspike
Kies knows the difference.. it even knows for which region the installed firmware is and installs the corresponding update.
Click to expand...
Click to collapse
@Volans21
I've been experimenting with Cyanogen on my sm-p900 for about a week & 1/2 flashing back & forth with stock roms as well. Learning from the thread that Cyanogen is very different from the other roms, I wiped EVERYTHING except external sdcard when flashing back & forth & have not had any issues. Have you disabled Kies before trying to install as it will cause issues when flashing custom roms as well. Try disabling kies & doing a wipe of everything except external sdcard & then reflash the rom. I'm just a newbie trying to help so I hope this helps.
I also noticed that you didn't mention doing a backup in TWRP before doing anything. It would definitely serve you well to do so in the future as you will always be able to go back to what was working.
What do you mean with "disable Kies"? I know Kies as the software for managing a Samsung device with a PC.. but I didn't know that I could disable it on the phone/tablet.
Of course I did a backup with TWRP, I just didn't list i because I thought doing a backup can not cause the touchscreen to not work. Maybe I should have said that I tried to fix the touchscreen by restoring the TWRP backup.. but it didn't help. :/
Volans21 said:
What do you mean with "disable Kies"? I know Kies as the software for managing a Samsung device with a PC.. but I didn't know that I could disable it on the phone/tablet.
Of course I did a backup with TWRP, I just didn't list i because I thought doing a backup can not cause the touchscreen to not work. Maybe I should have said that I tried to fix the touchscreen by restoring the TWRP backup.. but it didn't help. :/
Click to expand...
Click to collapse
That really is sounding more and more like a hardware issue the more I look at the steps you've tried. If even wiping all data/cache/dalvik and flashing from odin stock firmware isn't fixing it it could be. The fact in twrp it's acting that way too sort of supports this.
Yes, I think so, too.
Volans21 said:
Yes, I think so, too.
Click to expand...
Click to collapse
To close this case: I sent the device back to the distributor, it was a HW issue and fixed.. even after flashing a custom ROM.
Now I flashed CM11 again.. 2 days ago. Touchscreen is still working!
I have a Moto G XT1540 US Retail 2GB running stock 5.1.1 System version 23.31.33.osprey_retus_2gb Build number LPI23.72-33. Data (LTE) working fine.
There is an update available to 23.46.4, but I have not bothered to update as I'd rather run CM12.1.
I've tried flashing 4 different CM12.1 roms
- cm-12.1-20150922-UNOFFICIAL-osprey.zip
- cm-12.1-20150925-NIGHTLY-osprey.zip
- cm-12.1-20150926-NIGHTLY-osprey.zip
- Random-Radium-1.4-OFFICIAL-osprey-20150917.zip
and data is not working in any of them - I can make/receive calls and send/receive texts, but data always shows !
The APN looks correct to me, and I've tried adding a new APN with the same info as stock and rebooting, but it still doesn't work.
I restored to a nandroid backup of stock and data (LTE) is working fine again.
Any ideas or suggestions for how to debug this?
Thanks.
Bob
The first time you flash a custom rom its recommended that you do a factory reset.
so there are no leftovers of the stock system.
just backup your data (and store that backup on a sd) and try a factory reset.
i hope this solves the problem
(sorry for bad english)
HelpMeruth said:
The first time you flash a custom rom its recommended that you do a factory reset.
so there are no leftovers of the stock system.
Click to expand...
Click to collapse
Yes, I did. I used TWRP to do a factory reset, flash ROM, flash Gapps, wipe Dalvik and cache, and reboot before each
of the above 4 ROMS.
Bob
Hmm thats werd, maybe try flashing a custom kernel. Otherwise i realy dont know how tot help you
HelpMeruth said:
Hmm thats werd, maybe try flashing a custom kernel. Otherwise i realy dont know how tot help you
Click to expand...
Click to collapse
cm-12.1-20150922-UNOFFICIAL-osprey.zip, which contains squid2 custom kernel, was one of the ones I tried where data was not working for me.
Can anyone verify that they have tried any of those same roms and had data work for them?
Bob
Have you enable data in setting and try in quick setting tiles pressing the mobile signal icon it should then turn on if not restore firmware then try installing custom rom again
I have tried several roms but fail, no signal. I tried to go back to stock and then flash again, no luck. Tried all the radios provided. Maybe a 6.0.1 6045O modem can fix it but I do not see it yet. Has anyone succeed? Please share your thoughts. I also tried to backup modem and reflash modem, using the zip provided by xda but still no luck. I guess stay in LP is not a bad idea though.
The way I revert back is by restoring from my previous twrp backup. I am not sure if that is the right way. I did flash the 6045I radio to try too. I am guessing maybe I messed up and it is stuck in someways. But once I back to stock I get the signal back. Maybe I should totally return to stock and root again flash recovery again......?! Omg that much work.
Here is how I did it
eddie24902005 said:
The way I revert back is by restoring from my previous twrp backup. I am not sure if that is the right way. I did flash the 6045I radio to try too. I am guessing maybe I messed up and it is stuck in someways. But once I back to stock I get the signal back. Maybe I should totally return to stock and root again flash recovery again......?! Omg that much work.
Click to expand...
Click to collapse
Here is how I did it on my 6045O (originally on Lollipop):
1. Unlocked bootloader
2.Rooted using the Dallas CZ guide (and his root utility. Alex's utility did not work for me)
3. Installed TWRP 3.0.0 from Alex's utility
4. In TWRP wiped down cache, dalvik, data and system
5. Format data (in the same wipe screen, but a separate button underneath)
6. Installed DCZ 2.2 rom and 6045I -6.0.1 modem from @wolfi
7. Do not install hybrid bootstack (did not work for me)
8. Reboot and enjoy . Everything works- MMS, rotate screen on dialer, lockscreen and LTE
radkapatka said:
Here is how I did it on my 6045O (originally on Lollipop):
1. Unlocked bootloader
2.Rooted using the Dallas CZ guide (and his root utility. Alex's utility did not work for me)
3. Installed TWRP 3.0.0 from Alex's utility
4. In TWRP wiped down cache, dalvik, data and system
5. Format data (in the same wipe screen, but a separate button underneath)
6. Installed DCZ 2.2 rom and 6045I -6.0.1 modem from @wolfi
7. Do not install hybrid bootstack (did not work for me)
8. Reboot and enjoy . Everything works- MMS, rotate screen on dialer, lockscreen and LTE
Click to expand...
Click to collapse
really appreciated your reply! I will try and see how it goes!!!
eddie24902005 said:
really appreciated your reply! I will try and see how it goes!!!
Click to expand...
Click to collapse
Were you able to get this to work? I have tried many things with no luck. Also can someone link the modem file from @wolfi?
Yes, I was able to do it
Just follow my instructions and you will be able to do it
I can't post a link because I haven't posted 10 times yet. Just go a search @ xda for famewolf
Thanks
Rasnav said:
Were you able to get this to work? I have tried many things with no luck. Also can someone link the modem file from @wolfi?
Click to expand...
Click to collapse
i gave up.because i can only get 4g but no lte with MM as I am on Tmobile.