Ok, so I am somewhat new to the whole rooting and flashing of phones. I own the Samsung Galaxy Ace, from Koodo, and last night following a tutorial to install CWM4 and updating it to CWM5, followed by making a Nandroid backup and flashing Ice Cream Sunday Final, I had some issues.
The flashing went without any real problems, except one with installing CWM, but I sorted that out. I booted into the new ROM, and liked it, but after testing it I noticed it wouldn't load anything from my Koodo SIM card, like my contacts, and in the notifications bar where it shows your service carrier, it just showed a number. I was still able to send and receive calls and messages, but it was as if it didn't fully support my SIM. After finding a few things I didn't like with the ROM, I decided to use my Nandroid backup to restore, and after following a tutorial, I "successfully" restored the backup, according to Nandroid... But upon booting the phone, it was stuck on the boot logo.
After about an hour of searching, I was able to find out that CWM5 has issues restoring backups through Nandroid, and that I was screwed out of using my restore. I found the stock Koodo 2.3.4 ROM, and flashed it with Odin, and had to do a Recovery System Wipe to get out of a bootloop. I thought I was back to square one, and began installing my apps again and such with no issues.
---------EDIT---------
So, after hours of fooling around I replaced my save file with Root Explorer, like I was before, but then gave Terminal Emulator SU Permissions and used it to give the save file the right APP ID and Permissions, and it's working without freeze-ups now. I also used SQLite DB Editor to edit a fresh save on Where's My Water to reset my progress back to where I was before the update broke my save.
I am still wondering why my SIM Card didn't work properly in that ROM, and if there is a way I could make it work.
Is your model number GT-S5830D with baseband S5830DTLKI4? This is my model of the SGA and I've been reluctant to try flashing any ROMs because I can't find any success stories for this exact model. I'm also with Koodo and have concerns about how the SIM card will handle the custom ROMs too. If you do have this model, what has your experience been since your original post?
Winner Winner Chicken Dinner!
dhx138 said:
Is your model number GT-S5830D with baseband S5830DTLKI4? This is my model of the SGA and I've been reluctant to try flashing any ROMs because I can't find any success stories for this exact model. I'm also with Koodo and have concerns about how the SIM card will handle the custom ROMs too. If you do have this model, what has your experience been since your original post?
Click to expand...
Click to collapse
My model is GT-S5830D and I am on that baseband and have tried a few ROMs, all of which work. I would say try a ROM as the you should be fine, and you can always do a CWM Backup.
The SIM issues I was having has been resolved, as it is simply caused by being in Canada, and my carrier not being in the phones list, so it still displays a number, but all of my features (Calling, SMS, MMS, Data, etc) work fine.
admiralspeedy said:
Ok, so I am somewhat new to the whole rooting and flashing of phones. I own the Samsung Galaxy Ace, from Koodo, and last night following a tutorial to install CWM4 and updating it to CWM5, followed by making a Nandroid backup and flashing Ice Cream Sunday Final, I had some issues.
Click to expand...
Click to collapse
Where is this tutorial??? I have yet to find one for the Koodo Ace that works.
Related
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
Why don't you try to Odin a pre-rooted Verizon stock can be found here http://forum.xda-developers.com/showthread.php?t=1984436 to see if it addressed both our your issues?
I just had some major issues with this as well. There is something wrong with the nightly versions of CM 10.1.
Like you - I flashed CM 10.1 12/18 and found that my data was not working. I then searched this forum and found that other users were having the no data issue as well. I decided that I would do the same and flash back to an earlier CM 10 release from December, but the update did not go as expected. Due to going 10.1 to 10 I had to wipe data/cache/dalvik. At this point I got CM 10 reinstalled, but the phone came up with NO cell coverage. I went to System Settings -> About -> Status and found that the phone was no longer registering my cellular network (Verizon) or phone number. My IMEI data was dead.
Luckily in my case I had already made backups of my IMEI data per this post: http://forum.xda-developers.com/showthread.php?t=1852255
I restored my IMEI and reflashed CM 10 12/16. Everything is now working as expected. Your issue sounds identical to mine - I just spent half the day fighting with the exact same issue. I definitely learned my lesson about staying so current with the NIGHTLY builds for day-to-day non-dev use. I knew it before, it just never bit me like this.
Anyways, I hope this information helps you somewhat. Good luck!
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Bought this for my daughter.
Rooted it, did a nandroid, then forgot to copy my nandroid to PC before I wiped the sd card for ext..
So, after looking all over the net, I have found Modded stock roms, but none with the update profile feature.
I rooted and flashed a rom before activating, so now I seem to be hosed....
Nothin for cricket seems to work as far as "back to stock". I tried these just in hopes that they might work.. Even if they didnt, Im no worse off. Seems ST is the oddball of the carriers, since you cant get into adb with it, only recovery.
If you have a copy of this rom, or know where to get one, please post. Again, I need Straight Talk Ascend II (M865c) STOCK rom with UPDATE PROFILE option.
Or, if you know a workaround on how to activate while running a modded or custom rom.
Thanks in advance.
Dj
Hey fellow XDA'ers, I have a strange problem on my G920T that's been bugging me for a while. After flashing a custom ROM, my EFS was messed up. Thankfully I had backed it up prior to any custom ROMs. All works well n the phone except whenever it's rebooted it fails to register to T-Mobile's network. So I have to bring up the dialer, type in *#2263# and choose Band Selection, then LTE, then LTE All (which is already asterisked) and tap it again. Only then will it register on the network and then works fine. I've tried everything under the sun including restoring EFS backup, flashing back to stock, etc., to no avail.
I'm wondering if anyone knows of or can write a script that automatically runs the above process after reboot. I don't know enough to do so, and I'm not sure one exists. Not a vital request, more of an "I'm not going to be beaten by my phone" kind of thing. I'm willing to throw a $$ donation if someone were to write or provide a working script. Thanks!
xJMHx said:
Hey fellow XDA'ers, I have a strange problem on my G920T that's been bugging me for a while. After flashing a custom ROM, my EFS was messed up. Thankfully I had backed it up prior to any custom ROMs. All works well n the phone except whenever it's rebooted it fails to register to T-Mobile's network. So I have to bring up the dialer, type in *#2263# and choose Band Selection, then LTE, then LTE All (which is already asterisked) and tap it again. Only then will it register on the network and then works fine. I've tried everything under the sun including restoring EFS backup, flashing back to stock, etc., to no avail.
I'm wondering if anyone knows of or can write a script that automatically runs the above process after reboot. I don't know enough to do so, and I'm not sure one exists. Not a vital request, more of an "I'm not going to be beaten by my phone" kind of thing. I'm willing to throw a $$ donation if someone were to write or provide a working script. Thanks!
Click to expand...
Click to collapse
Before you do that, is the custom ROM based on the same baseband your phone has?
Yes, the custom ROM is based on the same baseband - which is a great question. I’m using the stock rooted deodexed deKnoxed DOJ7 T-Mobile variant ROM with DOJ7 baseband. I’m DOJ7 across the board. This problem has persisted through multiple stock and custom ROMs. It seems to have started when I flashed the Back to N0t3 Note5 port to S6 ROM. I also get the Security Error: Your device has been flashed blah blah blah - but only when manually registering on the network.
I’ve been around the block as far as rooting and customizing my phone for a good while, and I’ve tried every trick I know to get this straightened out. SIM card works fine on my wife’s identical S6, so it’s not that. Short of hardware failure (which isn’t likely based on functionality when manually registered on network), something in some file was erased or corrupted and I can’t figure it out. Thanks for your question.
scrosler said:
Before you do that, is the custom ROM based on the same baseband your phone has?
Click to expand...
Click to collapse
Hi
Did you ever manage to get it fixed I'm having the same problem on my g920f and my imei is 350000000006 and serial all zeros
Thanks
Mav
I've searched the forums beforehand, so if someone finds something I missed, I apologize.
I have a Straight-Talk Samsung Galaxy S5.
Model Number from within Android says SM-S902L
Model Number on the battery cover says SM-G900P (B)
Currently running 4.4.2
I was wondering if someone would be able to show me how to root this, install a custom recovery, and tell me which roms I can install. The two different model numbers are confusing me.
EDIT: I rooted via CF Auto root using the sprint ktle .tar. Does this mean that most SM-G900P roms will work? I'm still confused on how to get from 4.4.2 to Android 5 or 6, if it's even possible.
Thank you very much.
i put a version of MOAR built for the vzw G900v on a 902L a few mos ago and its working fine. Just get TWRP on it and you can flash pretty much any snapdragon based ROM on it barring incompatible kernels and so forth
I got TWRP installed and it works fine, made sure the first thing I did was back everything up. It's just that, every post I've seen, the OP's Straight Talk S5 was just a rebranded Verizon S5, while mine is a rebranded Sprint S5. I just want to be certain flashing a Verizon ROM won't bork my "Sprint" phone. I can't find APN settings or anything. So I can't even copy them to change them later. So should I only try Sprint ROMs?
Tats the weird thing about the 902L, it says g900p on it, but i had to flash the vzw version of MOAR instead of the G900Ps version for it to work. But its seriously hard to bork your phone in such a manner that Odin cant fix it. I cant tell you how many times ive tried to install a ROM that was made for the g900p on my g900p and it failed, so, i just flashed MOAR in TWRP again and viola. Also, the backup thing isnt as vital as some make it seem if you have the tarball for the phone you own. Sure, it makes it easy to restore from an eff-up if you dont have your computer handy, but its just so unnecessary to make a backup of your original setup, just have a backup of a known to be fully working setup. Anyways, give vzw's MOAR a try. Its a great ROM and if anything goews wrong, just odin your phones original tarball back on it and all will be back to stock. You have to flash TWRP after the phones OG tarball tho
I don't have my phones OG tar. And is there a step I have to take before installing M.O.A.R or can I just jump from 4.x.x to 6.x.x?
im not aware of any 6.x.x ROMs that are compatible. MOAR is 5.0. Are you trying to get an app working that isnt compatible with 4.x.x? Like the car synch app? And to flash MOAR, just download it, wipe cache, dalvik and system in TWRP and install MOAR. Firstly tho, get the tarball from sammobile.com/firmwares. Its a super slow d/l, but youre gonna want to have it in case of a nuclear bomb restore necessity (not a likely scenario, but youre gonna want it. I have it and can host it for you on android file host later once i get home)
did you get the tarball for the 902L?
i ended up redownloading it from sammobile.com/firmwares. Took about 90 min because of their horrendous download speeds for non premium members, but i have 7 TB of storage, so im not wasting any space just having it since i have a G900P LoL (well, 2 of em along with the bovy of other phones i have for whatever reason i still keep them)
Thank you so much!, and Happy Thanksgiving if you celebrate. I've installed MOAR and the only thing I did was change the colors of the status bar icons and now all the phone does is boot to lockscreen then cycle back to boot animation. Something I did?
RRSJ392 said:
Thank you so much!, and Happy Thanksgiving if you celebrate. I've installed MOAR and the only thing I did was change the colors of the status bar icons and now all the phone does is boot to lockscreen then cycle back to boot animation. Something I did?
Click to expand...
Click to collapse
wipe all the appropriate caches before installing? and where did you get the version of MOAR youre using? Also happy thanksgiving to you too!
Ironically, I want to go back to 4.X.X for compatibility issues. Do I just wipe Dalvik and Cache and load OG tar through odin? I cant locate OG tar for 902L :/