Related
I upgraded my moms nexus s tmobile version from 2.3.6 to ics 4.0.4. She doesn't like the gui and the performance. It seems slow.
I looked online here and downloaded the rom for the tmobile nexus s but it wont install. It keeps showing error code 7 and it fails when verifying the rom.
What going on. Is it possible to downgrade back to 2.3.6 stock without rooting or modding?
Please help. Thanks.
Sent from my SGH-T989 using XDA
Not possible from a strictly stock sense. Generally, you'll need to unlock the bootloader and lose all data on the phone and then flash 2.3.x with a custom recovery like CWM.
terryjohnson16 said:
I upgraded my moms nexus s tmobile version from 2.3.6 to ics 4.0.4. She doesn't like the gui and the performance. It seems slow.
I looked online here and downloaded the rom for the tmobile nexus s but it wont install. It keeps showing error code 7 and it fails when verifying the rom.
What going on. Is it possible to downgrade back to 2.3.6 stock without rooting or modding?
Please help. Thanks.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Try nexus s hacks. Hope it helps.
Sent from my Nexus S 4G using xda premium
terryjohnson16 said:
I upgraded my moms nexus s tmobile version from 2.3.6 to ics 4.0.4. She doesn't like the gui and the performance. It seems slow.
I looked online here and downloaded the rom for the tmobile nexus s but it wont install. It keeps showing error code 7 and it fails when verifying the rom.
What going on. Is it possible to downgrade back to 2.3.6 stock without rooting or modding?
Please help. Thanks.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Make a factory reset and tell your mom to use ICS at least for a month.
terryjohnson16 said:
I upgraded my moms nexus s tmobile version from 2.3.6 to ics 4.0.4. She doesn't like the gui and the performance. It seems slow.
I looked online here and downloaded the rom for the tmobile nexus s but it wont install. It keeps showing error code 7 and it fails when verifying the rom.
What going on. Is it possible to downgrade back to 2.3.6 stock without rooting or modding?
Please help. Thanks.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
If your device is a i9020t then flash the 'soju' images for 2.3.6 direct from Google here:
https://developers.google.com/android/nexus/images
It'll probably keep notifying you to update to 4.0.4 though.
I'm about to downgrade to Gingerbread as well. I'm fed up with the mute call bug. I can't believe Google has not released any fix yet, what a lack of professionalism.
Bls440 said:
I'm fed up with the mute call bug..
Click to expand...
Click to collapse
What mute call bug? Can you elaborate as i've never noticed it.
Whenever I make a call, I can't hear the person and can't be heard neither. I have to call down and call right away a 2nd time to make it work.
A couple of NS users reported the problem on xda
HA! Something similar happened to me last night. It has never happened to me before. I recently had to fix my phone's mic and thought me tinkerning with it resulted in the issue. Glad to see it wasn't just me. I cleared the data for the phone application and it's working again. Not sure if that was how it was fixed but I rebooted and the problem was still there and I promptly cleared the data after the initial try on the reboot. Did you guys have an issue with the phone not giving you the ringing tone when making the outgoing call?
xdatastic said:
If your device is a i9020t then flash the 'soju' images for 2.3.6 direct from Google here:
https://developers.google.com/android/nexus/images
It'll probably keep notifying you to update to 4.0.4 though.
Click to expand...
Click to collapse
I tried that. It still gives the unverified error code 7 message.
Are you following the exact instructions on the google page and using fastboot to flash?
wipe cache partition then wipe dalvik cache wipe batter stats and make sure device is rooted and the bootloader is unlocked then make sure you have the 2.3.6 for your version of the device then flash hopefully should work
Flash Oxygen if you don't want ICS!! Enough said.
So I started today feeling a little creative so I flashed the newest MIUI ROM, there was a data issue that I tried to work out and in the end screwed everything up.
I lost signal but I have data.
I have tried probably 10 ROMs and the same has happened, I am getting a roaming sign, but it shows I have bars (I am connected to a wireless repeater so full service all the time on 3g).
What in the world do I do? I've seriously tried everything. I flashed back to stock through ODIN and nothing still.
PLEASE tell me someone has seen heard this problem... WHAT DO I DO?
Thanks in advance...
Go to settings - about phone - status and tell us if your IMEI is a bunch of zeros or a string of numbers.
Sent from my Nexus 7 using xda premium
It's not I its still the right one, that was something I checked... I considered doing a IMEI restore anyway and maybe that would fix the problem but I still definitely have it there. Thanks
tanpatnode said:
It's not I its still the right one, that was something I checked... I considered doing a IMEI restore anyway and maybe that would fix the problem but I still definitely have it there. Thanks
Click to expand...
Click to collapse
Read the thread and go into Mobile settings and fix the settings. After that you'll be good to go.
Sent from my SCH-I535 using xda app-developers app
How I Fixed It
Hey there. Not sure if your still having this problem, but I ran into the same issue with my new phone after rooting, unlocking bootloader, and flashing MIUI. To fix it, I had to odin to stock (Pre-Jellybean for the Samsung Utility), which I got from here: http://hotfile.com/dl/169363562/8975152/SCH-I535_VZW_I535VRALG1_I535VZWALG1.zip.html%20
Then I ran the Samsung Repair Utility from here: http://forum.xda-developers.com/showthread.php?t=1867442&page=18
The Samsung Repair Utility said my ERI was present and my IMEI was accurate per the back of my phone. Desperate, I ran the "Repair ERI" anyway which made no difference until I followed the OP's directions to dial the code to run the factory reset if the tool didn't work. That seemed to do the trick :victory:
Good Luck.
I did a full wipe and flashed the CM10.1 nightly released for the d2vzw this morning. When it rebooted I had no cell service. Looking in settings i have the proper IMEI number but my cell number is listed as 000-000-1361, MIN is 1361, PRL is 1. what can I do to fix it? I tried restoring a nandroid but the result is the same. Any help would be greatly appreciated!
RESOLVED
james3kral said:
I did a full wipe and flashed the CM10.1 nightly released for the d2vzw this morning. When it rebooted I had no cell service. Looking in settings i have the proper IMEI number but my cell number is listed as 000-000-1361, MIN is 1361, PRL is 1. what can I do to fix it? I tried restoring a nandroid but the result is the same. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Okay so i believe this was my fault for flashing the latest cm 10.1 nightly with my build.prop edited to galaxy nexus values to allow google wallet functionality. removing sim card, starting phone, shutting down phone, inserting sim card, and starting phone fixed the problem
james3kral said:
Okay so i believe this was my fault for flashing the latest cm 10.1 nightly with my build.prop edited to galaxy nexus values to allow google wallet functionality. removing sim card, starting phone, shutting down phone, inserting sim card, and starting phone fixed the problem
Click to expand...
Click to collapse
I ran into the same problem but after trying you fix I still have no service. ?????
TheBurgh said:
I ran into the same problem but after trying you fix I still have no service. ?????
Click to expand...
Click to collapse
I am having the same problem. The phone wont still activate. Please help!!
james3kral said:
Okay so i believe this was my fault for flashing the latest cm 10.1 nightly with my build.prop edited to galaxy nexus values to allow google wallet functionality. removing sim card, starting phone, shutting down phone, inserting sim card, and starting phone fixed the problem
Click to expand...
Click to collapse
Any one try Odin back to stock?
I have a similar issue and I have been going around and around with it without any luck. I restored my latest backup and I still have 000-000-3257 with a PRL of 1. I will try the ops recommendation and will report back.
Odin to stock is my next move unless someone else can think of something else to try.
Try clearing dalvik cache in recovery. Fixed it for me on AOKP. Had the exact same thing where my phone number was a bunch of zeroes. Still had service though when I hit the home button to bypass the activation screen.
Sent from my SCH-I535 using Tapatalk 2
I tried to remove the sim, and boot, and readd the sim and boot but no go. I will try it again but then I think I am going back to stock to see if that works.
Everything still works fine. No need to get worried......it just doesn't report your phone number accurately. Its not like it actually effects functionality. I ran it with an f'ed phone number for 3 days. Everything ran fine. Don't sweat it. If its a problem, wait until tomorrows official nightly comes out tonight and you'll be set.
TechSavvy2 said:
Everything still works fine. No need to get worried......it just doesn't report your phone number accurately. Its not like it actually effects functionality. I ran it with an f'ed phone number for 3 days. Everything ran fine. Don't sweat it. If its a problem, wait until tomorrows official nightly comes out tonight and you'll be set.
Click to expand...
Click to collapse
My issue is it is affecting my functionality. My phone is not working and whenever I call out I get a generic message saying my phone is not active.
I restored a backup from when I first rooted. Now my phone number is listed properly and when I get into a 4G coverage area I can get data, but I still can't call out and it shows I am roaming when I am in a 3G area.
OP on CM10.1 says that dirty flashing Unofficial 10.1 build 12/17/12 will restore data. Any luck with this fix?
Sent from my SCH-I535 using xda app-developers app
dknell said:
OP on CM10.1 says that dirty flashing Unofficial 10.1 build 12/17/12 will restore data. Any luck with this fix?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
you can try that or mastamoons both have been reported to work
mastamoon said:
Here is my unofficial 10.1 build as of 3:00pm EST.
Has working data and increased MMS picture size mod. Otherwise is stock CM10.1
http://bit.ly/12yrtcw
Click to expand...
Click to collapse
Droosh said:
Thanks for sharing! I did a full data wipe and installed this and it activated right away.
Click to expand...
Click to collapse
I was very unlucky and the dirty flash didnt work for me. However, I did have a backup of my IMEI and was able to flash it back to my phone.
I ran into the same problem after flashing 10.1... lost IMEI and stuck on roaming, had no backup.
To fix it i did the following
1) Odin back to stock
2) use this tool http://forum.xda-developers.com/showthread.php?t=1867442
3) reprovish the phone using this code in the dialer *2767*3855#
IMEI restored and no longer on roaming
brandao.gabe said:
I ran into the same problem after flashing 10.1... lost IMEI and stuck on roaming, had no backup.
To fix it i did the following
1) Odin back to stock
2) use this tool http://forum.xda-developers.com/showthread.php?t=1867442
3) reprovish the phone using this code in the dialer *2767*3855#
IMEI restored and no longer on roaming
Click to expand...
Click to collapse
THANK YOU!. I could not get the IMEI/ERI tool to work, but I did get *2767*3855# code to work. I had to roll back to a older version of the official rom (I think rolling back the radio would have been OK) but I am not up and working.
fowen said:
THANK YOU!. I could not get the IMEI/ERI tool to work, but I did get *2767*3855# code to work. I had to roll back to a older version of the official rom (I think rolling back the radio would have been OK) but I am not up and working.
Click to expand...
Click to collapse
I flashed back to stock as well and then used the same number to reprovision. After that everything worked fine it fixed the roaming, incorrect number, PRL, and all. I never lost my IMEI so I didnt do that step. but if you flash back to the cm 10.1 before they fix the data it will happen again :laugh:
Please read forum rules before posting
Questions go in Q&A
Thread moved
Just change CDMA subscription to ruim/sim and toggle airplane mode...
I've never found a reason to have to Odin to anything.
Sent from my SCH-I535 using xda app-developers app
ajrty33 said:
Just change CDMA subscription to ruim/sim and toggle airplane mode...
I've never found a reason to have to Odin to anything.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can't remember for sure, but I think that is something that the VZW tech had me do, and it didn't work. Maybe someone else who is having the issue can test and comment.
ajrty33 said:
Just change CDMA subscription to ruim/sim and toggle airplane mode...
I've never found a reason to have to Odin to anything.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This fixed it for me! Thank you very much!
Sent from an unlocked Galaxy S 3! Screw you Verizon!
I've been running the CM10 nightly builds, and earlier today I updated to CM10.1. Immediately upon updating, I had no service with Verizon. I tried to roll back to my previous build, but it was stuck in a boot loop. After many hours of frustration I returned the phone to stock only to face the same issue. I cannot get any service. I show bars, but can't actually connect to the network. Can anyone please point me in the right direction?
bagellord said:
I've been running the CM10 nightly builds, and earlier today I updated to CM10.1. Immediately upon updating, I had no service with Verizon. I tried to roll back to my previous build, but it was stuck in a boot loop. After many hours of frustration I returned the phone to stock only to face the same issue. I cannot get any service. I show bars, but can't actually connect to the network. Can anyone please point me in the right direction?
Click to expand...
Click to collapse
Have you tried dirty flashing 12/17 Unofficial?
Maybe you lost your imei
Check the development section
Sent from my SCH-I535
It is now fixed. I have no real idea how, but I pull SIM, rebooted and connected to wifi. Let it sit on activating for a bit then I killed it and replaced SIM. Working now.
bagellord said:
I've been running the CM10 nightly builds, and earlier today I updated to CM10.1. Immediately upon updating, I had no service with Verizon. I tried to roll back to my previous build, but it was stuck in a boot loop. After many hours of frustration I returned the phone to stock only to face the same issue. I cannot get any service. I show bars, but can't actually connect to the network. Can anyone please point me in the right direction?
Click to expand...
Click to collapse
bagellord said:
It is now fixed. I have no real idea how, but I pull SIM, rebooted and connected to wifi. Let it sit on activating for a bit then I killed it and replaced SIM. Working now.
Click to expand...
Click to collapse
Good to hear! I nearly died when my phone lost IMEI.
Working again
I had the same problem. Did not fix it in CM 10.1, but using ROM manager I was able to restore from sdcard the backup I made of the rooted stock rom (ICS 4.0.4). I wiped user data firstt, and at the end cleared the cache files you would when installing a rom.Everything works like it did before I installed CM10 M2. Hope this helps someone. This is a US Cellular SCH-R530U, and I did use the correct nightly cw-10.1-20122120-NIGHTLY-d2usc.zip
Does anyone have a link that can tell me how to fix this?
crazytalk151 said:
Does anyone have a link that can tell me how to fix this?
Click to expand...
Click to collapse
You will need to re-provision the phone. it just worked for me. I believe you must be on TW and im pretty sure this wipes the sdcard too.
enter this in dialer: *2767*3855#
Thank imnuts for this.
Why make a thread on this though when it's all over the cm10.1 ROM thread
Sent from my SCH-I535 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=35600769
Go to post #2
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have been unable to send or receive MMS messages to/from anyone. Outgoing messages just get stuck at "sending" and I've had multiple people try to send me an MMS. I believe my APN settings are correct based on other threads here. Has anyone else seen/dealt with/have a solution for this bug?
I'm currently running CM10.1 April 8 Nightly off of a clean complete wipe flash, but I believe the problem has occurred with prior versions as well.
dcvito said:
I have been unable to send or receive MMS messages to/from anyone. Outgoing messages just get stuck at "sending" and I've had multiple people try to send me an MMS. I believe my APN settings are correct based on other threads here. Has anyone else seen/dealt with/have a solution for this bug?
I'm currently running CM10.1 April 8 Nightly off of a clean complete wipe flash, but I believe the problem has occurred with prior versions as well.
Click to expand...
Click to collapse
I saw some commits related to unicode encoding with the MMS app. It's possible (Disclaimer: I am not a dev, these are just theories) that these have something to do with the MMS issue. You could extract the MMS.apk from a prior build (where your MMS was still functional) and push it to /system/apps, rename your current MMS.apk to MMS.bak (just in case), set permissions to R-W, R, R, then reboot. If that works then we know there's an issue with the CM commits to the MMS.apk.
Had the same problem this morning. Turns out I had mobile data turned off.
Sent from my SAMSUNG-SGH-I727 using xda premium
Nope, mobile data is on and I have no idea when the last time it was working.
I can't be the only one dealing with this... Anyone? Now running CM 10.1 4/22 Nightly.
dcvito said:
I can't be the only one dealing with this... Anyone? Now running CM 10.1 4/22 Nightly.
Click to expand...
Click to collapse
I've been having the same issue since sometime in march. Also running CM nightlines. I've read it may be something to do with the Access Point Names but no solution is given
briguy42 said:
I've been having the same issue since sometime in march. Also running CM nightlines. I've read it may be something to do with the Access Point Names but no solution is given
Click to expand...
Click to collapse
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
mrfeuss said:
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
Click to expand...
Click to collapse
I've checked out and even rebuild my APN's multiple times to troubleshoot to no avail.... Let's see what ideas we can come up with... Thanks for the help so far.
dcvito said:
I've checked out and even rebuild my APN's multiple times to troubleshoot to no avail.... Let's see what ideas we can come up with... Thanks for the help so far.
Click to expand...
Click to collapse
Hmm. Interesting. And you're using the stock MMS app in the CM Nightlies? Have you tried updating to a newer version?
mrfeuss said:
Hmm. Interesting. And you're using the stock MMS app in the CM Nightlies? Have you tried updating to a newer version?
Click to expand...
Click to collapse
Yes, stock messaging app included with the CM nightlies. What are you recommending that I update?
mrfeuss said:
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
Click to expand...
Click to collapse
Tried using this APN config too and it still didn't work, thanks for the suggestion though.
I have this issue on rooted stock jelly bean I had to set sms to convert the images to smaller resolution to get it to send. Been working for now but would like to be able to send hi res pics
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I had that issue at one time on my stock rooted unit. Turns out that AT&T had changed something on the network side and my account didn't get changed. You might call them and check the settings.
Sent from my GT-N8013 using xda app-developers app
bryanclane said:
I had that issue at one time on my stock rooted unit. Turns out that AT&T had changed something on the network side and my account didn't get changed. You might call them and check the settings.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I've put in a trouble call with AT&T hopefully they find something....
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
dcvito said:
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
Click to expand...
Click to collapse
If I were you I'd just make a nandroid backup of my current setup, transfer that (and any other important data) to either my external or PC, ODIN back to stock and head over to an AT&T store. Just my two cents. You can always re-root and flash a custom ROM again. If you'd corrupted something through flashing (not saying you did, just a thought) getting AT&T to straighten it out and then going custom from there might be your best option.
dcvito said:
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
Click to expand...
Click to collapse
Sinnce AT&T uses the IMEI number as the ID for the device, that wouldn't be the issue you aren't receiving push messages. I agree with mrfeuss, back up the phone, flash the stock rom, and go have AT&T fix it on their end. Then you can re-root and install your custom ROM again. Better to have them look at it than live without MMS.
bryanclane said:
Sinnce AT&T uses the IMEI number as the ID for the device, that wouldn't be the issue you aren't receiving push messages. I agree with mrfeuss, back up the phone, flash the stock rom, and go have AT&T fix it on their end. Then you can re-root and install your custom ROM again. Better to have them look at it than live without MMS.
Click to expand...
Click to collapse
Check mms after returning to stock as that may solve your problem.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I was afraid that was going to be the suggestion.... Guess I'll start my Firmware DL and backup now... here we go lol
mrfeuss said:
If I were you I'd just make a nandroid backup of my current setup, transfer that (and any other important data) to either my external or PC, ODIN back to stock and head over to an AT&T store. Just my two cents. You can always re-root and flash a custom ROM again. If you'd corrupted something through flashing (not saying you did, just a thought) getting AT&T to straighten it out and then going custom from there might be your best option.
Click to expand...
Click to collapse
Just used Odin to flash back to stock. After the Odin reboot how long should it take for the phone to start up? I've been sitting on the ATT logo screen for a few minutes now.... please don't tell me I bricked....
Never mind, figured out my own mistake..... Always factory reset/clear data before flashing!