Related
please mod delete
my favorite part
eduardmc said:
After you have completed your ps3 hack
1- remove battery from EVO
2- Hold Volume Down and power to get into recovery mode again
Click to expand...
Click to collapse
lol just kidding, im pretty sure i know what you meant.
is there some sort of problem flashing directing from the psfreedom enabled kernel back to your preferred one? Does that break wifi and 4g or something? If so then I understand the middle step of flashing the psfreedom disable file, but if not it seems like a useless extra step.
deathsled said:
is there some sort of problem flashing directing from the psfreedom enabled kernel back to your preferred one? Does that break wifi and 4g or something? If so then I understand the middle step of flashing the psfreedom disable file, but if not it seems like a useless extra step.
Click to expand...
Click to collapse
It brakes 4G & WIFI with psfreedom from what i know
sent from htc evo 4g
a little unnecessary....
you dont have to use the disable and then flash the kernel. If you are using a rom that doesnt have a dedicated disable.zip made for it (Fresh and Baked Snack have one) then all you do is need to flash the kernel you want of top. This is how I've did it since day one without any issues or lost data of anything. I usually do a Dalvik/cache wipe before flashing the kernel but im not certain that its necessary. Im glad some one made a thread to at least let people know that a nandroid backup isnt needed, cause those take forever...
where can i find the fresh dedicated disable hack, thanks!
zeeyo987 said:
where can i find the fresh dedicated disable hack, thanks!
Click to expand...
Click to collapse
Its somewhere in the original Psfreedom for evo thread. start and the back and work your way forward and you'll find it.
all this does is avoid the nand restore by flashing back your original kernal. The reason i didn't include this in my thread was because everyone has their own kernal. Sure many use the same but to make it a one step no mess up without people who can't read posting OMG OMG, just nand restore...done. But ya, i chose not to include a "disable" which is essentially a reverting of the kernal.
Hey theres a PSFreedom recovery now! Hopefully well get one for the EVO 4G like this one...
http://forum.xda-developers.com/show...72&postcount=1
so when u jailbreak the ps3 with the evo. do u need to plug it in again when u turn off the ps3. does it require the phone everytime to see the install package files icon?
stanik1 said:
so when u jailbreak the ps3 with the evo. do u need to plug it in again when u turn off the ps3. does it require the phone everytime to see the install package files icon?
Click to expand...
Click to collapse
Yep. Every time. Small price to pay though if you ask me. Ive backed up 2 games so far and they work flawlessly. No glitches, lag, nothing. I'll plug my evo in a hundred times for that.
Tiffany84 said:
Yep. Every time. Small price to pay though if you ask me. Ive backed up 2 games so far and they work flawlessly. No glitches, lag, nothing. I'll plug my evo in a hundred times for that.
Click to expand...
Click to collapse
I meant do i have to redo the whole re flashing of the zips. Because i dont mind pluging the phone into the ps3 every time. but reflashing the phone is the tidiest part.
U have to flash the psfreedom kernel every time.
Sent from my PC36100 using XDA App
i guess thats the price we have to pay. hopefully in the near future someone will come up with an app. on and off switch for jailbreak. or maybe do a dual boot switching kernels . i can dream
Hello, I have tried a few things, and so far have made no progress. Kies can't find any new updates, and now, after a reinstall, can't even find my device in the firmware update manager. Help!
EDIT: Kies can find the device, but under the Update Manager, it doesn't list anything needing an update.
If you have a US version of Captivate, it doesn't matter which version of Kies you use. Your phone reports its product id to Kies and it checks Samsung server to see if there is any updates. Right now, there is no update yet for US Captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm using a Canadian i896 with Rogers.
how is it possible that rogers gets an update faster than att when att released frist lol
Getting kies to work is a huge hassle. Took at least a few hours to get kies to recognize on a friebds phone after trying so many methods. Kies just sucks, especially for the captivate. Try rooting abd flashing a new rom. It is much faster to get 2.2 or even 2.2.1
Sent from my SGH-I897 using XDA App
The thing is, I've had troubles with custom ROMs messing up my MMS settings, data settings, and the like, and I just want to get the stock 2.2 firmware.
EDIT: What steps did you use to get it to see your phone?
MorganFreeman911 said:
The thing is, I've had troubles with custom ROMs messing up my MMS settings, data settings, and the like, and I just want to get the stock 2.2 firmware.
EDIT: What steps did you use to get it to see your phone?
Click to expand...
Click to collapse
Since you've installed custom ROMs, the issue you are having is that the product code in your nv_data.bin has been changed to something other than what it needs to be for Kies to report that it's a Rogers I896 and should be eligible for the 2.2 upgrade. You can check what the product code it's reporting to Kies by using regedit. Go to HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\1 and look in the right hand pane at the Product Code entry. If it says anything other than SGH-I896ZKARWC it is not going to show that 2.2 is available to upgrade to.
If it is reporting another product code there then you need to either 1) modify your nv_data.bin to match the Rogers product code or 2) put a copy of your original nv_data.bin back on the phone and then try Kies again and it should detect that there is an update available almost right away. Have you restored to Rogers 2.1 stock, yet?
HTH
Riker2k said:
Since you've installed custom ROMs, the issue you are having is that the product code in your nv_data.bin has been changed to something other than what it needs to be for Kies to report that it's a Rogers I896 and should be eligible for the 2.2 upgrade. You can check what the product code it's reporting to Kies by using regedit. Go to HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\1 and look in the right hand pane at the Product Code entry. If it says anything other than SGH-I896ZKARWC it is not going to show that 2.2 is available to upgrade to.
If it is reporting another product code there then you need to either 1) modify your nv_data.bin to match the Rogers product code or 2) put a copy of your original nv_data.bin back on the phone and then try Kies again and it should detect that there is an update available almost right away. Have you restored to Rogers 2.1 stock, yet?
HTH
Click to expand...
Click to collapse
My product code is correct, I repaired it earlier, but I'm having the same issue.
Awesome, that's a good start. Are you on Rogers stock 2.1? Does Kies detect your device? When you click the update firmware button what does it say? Does the Kies entry in the registry show that it detects it as that product code? Does it show I896UXJI2/I896RWCJI2/I896UXJI2/I896UXJI2 in the HIDSWVER entry?
have Windows 7 Ultimate and Hard time Kies Recognizing my Phone. I used the same method which used to fix an iPhone Issue ages back
1) Download Your Uninstaller 2010 ( Free trial ) and removed currently installed KIES - it removes it plus cleans up form the registry
2) Download everything from http://www.voidtools.com/ - it's like an interactive search and picks everything in your PC. Search for Samsung and Kies, delete all files and folders which say Samsung and Kies
3) Reboot PC
4) Install Canadian Kies Ver http://www.samsung.com/ca/support/de...ub_class_cd=P#
5) Open Kies (You have to be in TW Launcher, not LauncherPro or other for Kies to detect the phone and do a firmware update)
6) Plug in your phone with Kies firmware update On (in Settings/Application/usb settings)
7) Select Firmware Update in Kies
8) Click the Update button
9) Wait for the download to finish then you will see another Windows POP up, DONT PRESS OK
10) Disconnect USB | Power OFF Phone
11) Power Phone ON with VOL Buttons ON, it will come to Downloading... Download mode (Black/yellow screen with a shovelling droid)
12) Connect USB after 5 seconds
13) Press OK on Kies so it pushed the update to the phone
14) Kies will say Update Completed and your phone should be sitting on Galaxy S, diconnect cable and you enter Froyo
Riker2k said:
Awesome, that's a good start. Are you on Rogers stock 2.1? Does Kies detect your device? When you click the update firmware button what does it say? Does the Kies entry in the registry show that it detects it as that product code? Does it show I896UXJI2/I896RWCJI2/I896UXJI2/I896UXJI2 in the HIDSWVER entry?
Click to expand...
Click to collapse
Yep, odin'd back to JI2. Kies connects no problem, but once I hit update firmware, and get to the list of devices that need firmware updates, it's empty. I've got 3 entries under DeviceDB, one of them has the correct info. Under HIDSWVER, I have I896UXJI2//I896UXJI2/I896UXJI2 instead. I'm betting I can't just edit it through there, can I?
TheEscapist said:
Yep, odin'd back to JI2. Kies connects no problem, but once I hit update firmware, and get to the list of devices that need firmware updates, it's empty. I've got 3 entries under DeviceDB, one of them has the correct info. Under HIDSWVER, I have I896UXJI2//I896UXJI2/I896UXJI2 instead. I'm betting I can't just edit it through there, can I?
Click to expand...
Click to collapse
Lol, unfortunately no, tried that myself for the product code and it just puts it back. One question, is your SIM installed when you connect it to Kies? Wondering because mine was and I'm wondering if maybe the fact that I have that 4th entry on HIDSWVER is related to that?
Riker2k said:
Lol, unfortunately no, tried that myself for the product code and it just puts it back. One question, is your SIM installed when you connect it to Kies? Wondering because mine was and I'm wondering if maybe the fact that I have that 4th entry on HIDSWVER is related to that?
Click to expand...
Click to collapse
Sim card is in. I'll try with it out.
TheEscapist said:
Sim card is in. I'll try with it out.
Click to expand...
Click to collapse
Ah, if SIM is in then that rules that out because I had mine in. It almost looks like a bad flash or something didn't get reverted quite right. Only difference is that I reflashed mine to stock with Heimdall and not Odin. A little more of a pain but worked great... You running Kies 1.53.something something?
Another question, when you fixed your nv_data.bin did you reset the ownership and permissions to the right ones in the /efs folder? Can't imagine that it should make a difference but...
Riker2k said:
Ah, if SIM is in then that rules that out because I had mine in. It almost looks like a bad flash or something didn't get reverted quite right. Only difference is that I reflashed mine to stock with Heimdall and not Odin. A little more of a pain but worked great... You running Kies 1.53.something something?
Another question, when you fixed your nv_data.bin did you reset the ownership and permissions to the right ones in the /efs folder? Can't imagine that it should make a difference but...
Click to expand...
Click to collapse
Maybe. I didn't use the .pit file when using Odin, maybe that's it? I'll reflash. And yeah, i have the right Kies.
And I would assume, I did the same method as the other guy in the main thread.
Edit: I don't seem to have a pit file.
TheEscapist said:
Maybe. I didn't use the .pit file when using Odin, maybe that's it? I'll reflash. And yeah, i have the right Kies.
And I would assume, I did the same method as the other guy in the main thread.
Edit: I don't seem to have a pit file.
Click to expand...
Click to collapse
No, don't use the pit and select repartition. The Rogers stock rom tar doesn't contain the dbdata partition and your phone will just end up stuck in recovery mode. You'll then have to flash the Odin 1-click to the AT&T firmware and then reflash to Rogers stock again. Learned that the hard way last night.
When you say the other guy in the main thread, which instructions? I'm only asking because there's a thread about fixing the nv_data.bin and the instructions are for the AT&T I897 version so it's not exactly the same for our I896. Very, very close but not quite. Obviously you've corrected the product code to match the Rogers one but wondering about the owner and group ownership settings + the permissions. The file should be owned by radio.radio and the permissions should be 700 (rwx --- ---) if you check with adb shell from a command line. Probably telling you stuff you already know, sorry if I'm going to far into the basics. Just want to try and cover that stuff to weed out potential issues. Took me almost 3 hours to fix mine last night because I had to search through many threads and places to finally piece it all together.
Riker2k said:
No, don't use the pit and select repartition. The Rogers stock rom tar doesn't contain the dbdata partition and your phone will just end up stuck in recovery mode. You'll then have to flash the Odin 1-click to the AT&T firmware and then reflash to Rogers stock again. Learned that the hard way last night.
When you say the other guy in the main thread, which instructions? I'm only asking because there's a thread about fixing the nv_data.bin and the instructions are for the AT&T I897 version so it's not exactly the same for our I896. Very, very close but not quite. Obviously you've corrected the product code to match the Rogers one but wondering about the owner and group ownership settings + the permissions. The file should be owned by radio.radio and the permissions should be 700 (rwx --- ---) if you check with adb shell from a command line. Probably telling you stuff you already know, sorry if I'm going to far into the basics. Just want to try and cover that stuff to weed out potential issues. Took me almost 3 hours to fix mine last night because I had to search through many threads and places to finally piece it all together.
Click to expand...
Click to collapse
It boots to recovery, but if you clear cache and user data, it boots fine after. Trust me, I've bricked enough times.
EDIT: Just realized you were talking about repartitioning, which I've never done, or had to. Whoops. >.>
And it suddenly works after a fresh flash, and master clear. Here goes.
Thanks for the time/help.
TheEscapist said:
It boots to recovery, but if you clear cache and user data, it boots fine after. Trust me, I've bricked enough times.
EDIT: Just realized you were talking about repartitioning, which I've never done, or had to. Whoops. >.>
And it suddenly works after a fresh flash, and master clear. Here goes.
Thanks for the time/help.
Click to expand...
Click to collapse
Yea, that repartitioning things cost me big time last night. I really, really didn't want to flash the odin 1 click to AT&T cause now I have that damn white AT&T worldphone logo which I hate but my phone is now running stock Rogers 2.2.
So far I'm kinda meh with it. It works, couple wonky things with haptic feedback and the wireless doesn't seem very stable, at least for me. Think I'm going back to di11igaf's 3.0.2 rom. Loved that one!
Enjoy your Cappy and glad to help.
Riker2k said:
Yea, that repartitioning things cost me big time last night. I really, really didn't want to flash the odin 1 click to AT&T cause now I have that damn white AT&T worldphone logo which I hate but my phone is now running stock Rogers 2.2.
So far I'm kinda meh with it. It works, couple wonky things with haptic feedback and the wireless doesn't seem very stable, at least for me. Think I'm going back to di11igaf's 3.0.2 rom. Loved that one!
Enjoy your Cappy and glad to help.
Click to expand...
Click to collapse
You can get rid of the AT&T logo, eh? There's a thread in the dev section about it.
I haven't had any issues, other than z4 not working. I'll super one click tomorrow. I have yet to find a rom for me to stick with though. CM 6.x is too laggy, CM 7 isn't ready yet, neither is sense, and everything else is just modded i9000 roms. No offense to the devs.
Sent from my SAMSUNG-SGH-I896 using XDA App
TheEscapist said:
You can get rid of the AT&T logo, eh? There's a thread in the dev section about it.
I haven't had any issues, other than z4 not working. I'll super one click tomorrow. I have yet to find a rom for me to stick with though. CM 6.x is too laggy, CM 7 isn't ready yet, neither is sense, and everything else is just modded i9000 roms. No offense to the devs.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Yea, going to look into the ATT logo replacement tomorrow. Too tired to take that on tonight.
As for ROMs, yea - tough call. I settled on Di11i's ROMs cause I liked the theme work and they are REALLY smooth and fast. I had a Galaxy S Vibrant before and one application I use - Touchdown for Exchange - was so damn slow on it I could barely stand to check my email. On the cappy with Di11i's ROM it's literally like butter. I coupled his ROM with the latest glitterballs kernel and BAM, wicked ROM with all the features I need, a nice theme and excellent battery life. Very happy with that.
I actually only upgraded to the stock Rogers 2.2 to do a /system pull for him to work with. Going back to it tomorrow, I think.
At least we have choices now, cause if it was left up to the carriers and manufacturer we'd suffer with whatever craptastic releases they come out with. To be fair, the Rogers ROM is really bloat free and actually pretty decent. With a change to Launcher Pro or Go Launcher I could probably deal with it for awhile.
Anyway, hope you find a rom you like or at least the Rogers 2.2 hangs on strong for ya!
Basically I restored from a nandroid backup and I can no longer connect to wimax
Itll say authenticating with sprint....and then scanning again.
here is my wimax_mtd: http://pastebin.com/bpzYi1E2
and when I ran joeykrims Wimax RSA key checker it said I was missing them.
Im pretty sure an RUU will work but its alot of trouble AND I am out of town with no wifi (only tethering) so im stuck on 3g and cant dl a RUU.
any suggestions would be great
I have already flashed a new radio
DL the RUU or flash a radio.
hoesnaps said:
DL the RUU or flash a radio.
Click to expand...
Click to collapse
Lmao the magic of IRC
BTW his post was an inside joke. Not an actual solution if you couldn't read the thread and understand it
still open to solutions
what rom/version?
VICODAN said:
what rom/version?
Click to expand...
Click to collapse
ive tried multiple its not a problem with the ROM. my RSA keys are gone. Guess i gotta RUU was just hoping somebody might know of a different solution
notsointeresting said:
ive tried multiple its not a problem with the ROM. my RSA keys are gone. Guess i gotta RUU was just hoping somebody might know of a different solution
Click to expand...
Click to collapse
Yeah that sucks, but good thing is it should not take very long to RUU then re root
Sent from my PG06100 using Tapatalk
His problem is that he is out if town with no ruu on hand and can't dl it over 3g.
Sent from my PG06100 using XDA Premium App
Ive just read that if you lose your rsa keys then you lose em forevor even with RUU
this is really starting to scare me
In my nandroid backup i have a wimax.XXXXXXX.img but i cant restore it from a nandroid in recovery (even in advanced restore)
I dont know what else to do
ANY help would be great please....
I'm sure someone will yell at me, but whatever, maybe take this to the og evo or even 3d forums where they have some more devs. Maybe someone over there will know. Because as of right now it's looking like no one here does.
Sent from my Shifty Speedy using Tapatalk
Sorry
notsointeresting said:
Ive just read that if you lose your rsa keys then you lose em forevor even with RUU
this is really starting to scare me
In my nandroid backup i have a wimax.XXXXXXX.img but i cant restore it from a nandroid in recovery (even in advanced restore)
I dont know what else to do
ANY help would be great please....
Click to expand...
Click to collapse
I had this problem before. I tried rruing and it does nothing. The RSA keys are made from the factory for each specific device. You cannot get them back with a rru. And the way clockwork works it can backup wimax keys on the shift, but cannot restore them (this is, among other reasons, why we need twrp.) Unless you made a backup of your keys with the terminal commands from the old froyo root instructions, or with shiftRR, you're screwed.
If your still under warranty, or pay for it each month, the only option is to take it back to sprint for a replacement ("I don't know what happen, I was playing fruit ninja, it froze, got really hot, it died, and when I plugged it back in, I couldn't connect to 4g, can you fix it?" was my excuse)
Really sucks, and had my on ginger**** for a long time cause of it.
Have ## access?
##data# if you're rooted download msl reader to get your msl # to edit. look under wimax and see if you're NAI is set to the mac address on the sticker behind your battery
so like if your NAI is [email protected] just do a profile update
you can also test it thru the clear network by changing the realm from sprintpcs.com to clears address which i'll update this post in a few minutes for you.
update test wimax by altering the NAI to your [email protected]
notsointeresting said:
Ive just read that if you lose your rsa keys then you lose em forevor even with RUU
this is really starting to scare me
In my nandroid backup i have a wimax.XXXXXXX.img but i cant restore it from a nandroid in recovery (even in advanced restore)
I dont know what else to do
ANY help would be great please....
Click to expand...
Click to collapse
Are you using clockwork recovery or RA recovery?
grab your wimax image, look at it with the attached file, it's the only hex editor i know of that reads the .img's correctly.
Next take off your battery and note your wimax MAC id on the sticker.
open the .img file with the hex editor and do a search for your mac address.
alter it as needed..
on another note, if you have the msl# for your phone. ##data# it and check your NAI against you mac address. if they are different, change the NAI to that mac address. hit menu and commit changes.
phone will reboot and you should be golden
tbh...neither of those would work for many reasons..and the fix is quite involved..catch me or indirect on irc....there's a few tricks up our sleeves.
otaking71 said:
tbh...neither of those would work for many reasons..and the fix is quite involved..catch me or indirect on irc....there's a few tricks up our sleeves.
Click to expand...
Click to collapse
I'll be on irc soon thanks for the responses guys
Sent from my Supreme Shift on Wires!
Evil_DevNull said:
Are you using clockwork recovery or RA recovery?
grab your wimax image, look at it with the attached file, it's the only hex editor i know of that reads the .img's correctly.
Next take off your battery and note your wimax MAC id on the sticker.
open the .img file with the hex editor and do a search for your mac address.
alter it as needed..
on another note, if you have the msl# for your phone. ##data# it and check your NAI against you mac address. if they are different, change the NAI to that mac address. hit menu and commit changes.
phone will reboot and you should be golden
Click to expand...
Click to collapse
Umm, there is no Amon Ra recovery for the shift yet...
I did it to my test shift. Alter the image m5 it then zip it, run in recovery is my test a fluke or ?
Yeah umm.... there is no amon ra recovery for the evo shift, clearly evil_devnull isn't sure what he's talking about.
Sent from my PG06100 using Tapatalk
Guys, Lay-off devnull. I'll tell you what. If I find his advice to be poor, I'll tell him myself. I just spent around 30 minutes talking to him and restoring his wimax (regardless of previous events) and I have to say, he's not -that- bad of a guy. Now, I can tell you that devnull's advice was poor in this situation because of the fact we all know from the huddle derpy mc-derpenstein (N-S-I) lost his 4g RSA keys.
Indirect said:
.... because of the fact we all know from the huddle derpy mc-derpenstein (N-S-I) lost his 4g RSA keys.
Click to expand...
Click to collapse
^lol
Sent from Gingerbread Speedy 4G
I don't have a shift. Wife does, I mailed out all the test units so my exp with shifts tetarded engineering is low to say the least. My keys where there, just my lock was fubared. Thank again indirect
Hi,
I'm trying to find specifically the right radio for rogers, for the infuse 4g.
I checked the "please have a look @ those threads b4 start new one" and none are related.
I've seen the full list of basebands, they look amazing, all those letters and numbers. But I have NO clue how to interpret which one is which. And i'm sure someone here will slap me a picard facepalm... ascii style... Or equivilant... maybe even a twihard facepalm...
However, i'm kinda needing this radio...asap... as I have no working radio on the infuse4g and its for work... the simcard does work in a sony erricson x1... 3g at least.. and that is for work, but I need the new one working asap...
Can anyone point me in the right direction? I don't just want to try every single one... and test radio range... etc... I'm needing kinda to get this perma working, immediately...
- rmleloup
Read the posts in the following link. Make sure your APN is set up for Rogers. The is also an Odin post with Rogers root somewhere in the forum. Look for it.
http://forum.xda-developers.com/showthread.php?t=1514886
Sent from my SGH-i997 using xda premium
psal217050 said:
Read the posts in the following link. Make sure your APN is set up for Rogers. The is also an Odin post with Rogers root somewhere in the forum. Look for it.
http://forum.xda-developers.com/showthread.php?t=1514886
Sent from my SGH-i997 using xda premium
Click to expand...
Click to collapse
Would you mind saving me the hassle and locating it? As I can't seem to presently locate it. I can setup the proper apn at some point, as the sim card provides 3.... oddly... but I still can't connect...
- rmleloup
The radio that comes on the stock rogers firmware (also the one that works the best imo) is UCKL2
threi_ said:
The radio that comes on the stock rogers firmware (also the one that works the best imo) is UCKL2
Click to expand...
Click to collapse
Trying it now, hopefully I get something, and i'm redoing the apns fresh hopefully that fixes it.... oi...
After some testing, it clearly still didn't work... I found out the why...
From my personal gnex, I threw its sim into the phone, and voila...signal... Problem isn't entirely the modem (more of identifying which is better). I even tried a gnex modem... (not kidding, it worked... oddly?).
Basically seems my corporate account messed up things.. and I can't fix it until tuesday 6am my time (canada holiday weekend...yay)
Thank you ALL for the support thoroughly.
I have a Rogers Infuse 4G and it I don't think I did any official updates to it. It had UXKG3; I just finished flashing up to CM10 and am now using UCLB3 which I think may have some signal issues for me out here but still in the process of testing.
I did a full backup using CWM as well as backing up my EFS... I don't know if that was before or after my modem changed, but if the UXKG3 modem isn't available online and you can tell me how I can "rip" it out of my backup files, I'll surely provide it to you since I too am thinking of going back to it if it turns out UCLB3 isn't doing too well.
I have seen posts that other people are having trouble switching modems on cm10, maybe it could be done with 7 zip before you flash. Also you need to hit menu button then select save then reboot after changing APN.
The problem flashing modems on CM10 are fixed... it was because of a new filesystem format for the /radio mountpoint and a different method of flashing the new modem. There are some modem threads here:
http://forum.xda-developers.com/showthread.php?p=31097259
http://forum.xda-developers.com/showthread.php?t=1342978
with working modems you can flash from CWM (I tried one earlier, worked perfectly).
Hey guys, I am at the end of my rope here, so maybe you can help me out.
I have been dealing with the Media service bug that drains battery super fast for the last few days on my wifes rooted SGS3, and I have been jumping between roms, deleting SD files, searching for corrupt apps/media all to no avail. Tonight, in an effort to fix this issue, I flashed the most recent CM10 nightly as I heard it had a fix for this issue. I have no idea if that is true, because when I got to the setup screen after flashing, I kept getting an error that said that setup crashed and could not run. I had to boot back in to recovery, flash again, only to find the same error.
I then attempted to flash clean rom, except now I see that her phone is always roaming where my Note2 right next to it is on 4G. I flashed an older CM10 nightly for her, and the same issue popped up where it is only roaming.
Did the failed CM10 flash screw something up? How can I get her off roaming and back on 3/4G? Thanks!
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.
x714x said:
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.
Click to expand...
Click to collapse
Good advice, but I'm pretty sure he would need to repair his imie before the code
If I helped you in some way.... pass on the favor and help the next person!
x714x said:
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.
Click to expand...
Click to collapse
OK, so I was able to get signal back (shows 4/3G), however she is unable to actually text or call from her number. She can use google voice though, so I am guessing it is something specifically with her number. Maybe the IMEI thing you mentioned. Assuming she has her signal back, would dialing that set of numbers reactivate her, or would I still have to do the ODIN steps?
It there is data then that dialer code should fix the calling, but you need to be in ics to do it
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
It there is data then that dialer code should fix the calling, but you need to be in ics to do it
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Yeah, I am pretty sure she has data. She is not at home, and when she left a bit ago we thought all was well (since she had the 4G indicator whereas before it said roaming) but she just used GVoice to text me to say that she cannot call or text using her VZW credentials. When you say that she needs to be in ICS, would any ICS rom do? She is in the newest version of Cleanrom right now, so I will have to flash something else I think. As for using ODIN, that is kinda out of the question because we are on vacation and the internet here sucks. It would take 2 weeks to download the stock VZW image, but if that is the only option then I guess that is how i goes. Thank you in advance for all your help!
Mindstar1 said:
Yeah, I am pretty sure she has data. She is not at home, and when she left a bit ago we thought all was well (since she had the 4G indicator whereas before it said roaming) but she just used GVoice to text me to say that she cannot call or text using her VZW credentials. When you say that she needs to be in ICS, would any ICS rom do? She is in the newest version of Cleanrom right now, so I will have to flash something else I think. As for using ODIN, that is kinda out of the question because we are on vacation and the internet here sucks. It would take 2 weeks to download the stock VZW image, but if that is the only option then I guess that is how i goes. Thank you in advance for all your help!
Click to expand...
Click to collapse
I know it didn't work on some custom. I do know it works on route 66, but I've got a solution. Use mobile Odin and download the ROM straight to the phone.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
I know it didn't work on some custom. I do know it works on route 66, but I've got a solution. Use mobile Odin and download the ROM straight to the phone.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Im actually downloading a torrent of the stock image for regular desktop ODIN and it is moving fairly quickly. That being said, using a custom rom would be easier (wouldnt I not have to use ODIN at all, just flash it like a normal rom?). If that is the case, can I download your route 66 rom, boot into recovery, wipe, flash then use the dialer code?
EDIT: Whoops, I misunderstood your previous post. I think we are talking about the same thing. I am torrenting the route 66.tar file right now. You are suggesting that I use VZW 4G on her phone to dl the tar file then flash with mobile ODIN? I have never used mobile ODIN to my knowledge so I am not sure how to go about that.
EDIT 2: I just checked out mobile ODIN on the market, and that seems easy enough. So I just finish this .tar dl, put it on her SD, load the app and follow its directions to flash it. Once that is flashed, reboot and dial that code. Then Flash whatever rom I want (say, back to cleanrom). Is that about right?
Mindstar1 said:
Im actually downloading a torrent of the stock image for regular desktop ODIN and it is moving fairly quickly. That being said, using a custom rom would be easier (wouldnt I not have to use ODIN at all, just flash it like a normal rom?). If that is the case, can I download your route 66 rom, boot into recovery, wipe, flash then use the dialer code?
EDIT: Whoops, I misunderstood your previous post. I think we are talking about the same thing. I am torrenting the route 66.tar file right now. You are suggesting that I use VZW 4G on her phone to dl the tar file then flash with mobile ODIN? I have never used mobile ODIN to my knowledge so I am not sure how to go about that.
EDIT 2: I just checked out mobile ODIN on the market, and that seems easy enough. So I just finish this .tar dl, put it on her SD, load the app and follow its directions to flash it. Once that is flashed, reboot and dial that code. Then Flash whatever rom I want (say, back to cleanrom). Is that about right?
Click to expand...
Click to collapse
That's pretty much it, with mobile Odin you'll just click open file. It will put the different parts (kernel, recovery,etc) in the correct section. Then you click flash, support easy and faster then normal Odin. Also if you make a backup before doing this you can just restore your backup after fixing the network problem.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
That's pretty much it, with mobile Odin you'll just click open file. It will put the different parts (kernel, recovery,etc) in the correct section. Then you click flash, support easy and faster then normal Odin. Also if you make a backup before doing this you can just restore your backup after fixing the network problem.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
You are awesome! I am sure you factored this in to your suggestion, but if I backup her current rom, then ODIN, then restore, it will not undo what I did with ODIN, correct? Again, I am pretty sure it wont, but I was also pretty sure I knew what I was doing when I flashed CM last night and look how that turned out. Thanks again!
Same problem!!!
Mindstar1 said:
Hey guys, I am at the end of my rope here, so maybe you can help me out.
I have been dealing with the Media service bug that drains battery super fast for the last few days on my wifes rooted SGS3, and I have been jumping between roms, deleting SD files, searching for corrupt apps/media all to no avail. Tonight, in an effort to fix this issue, I flashed the most recent CM10 nightly as I heard it had a fix for this issue. I have no idea if that is true, because when I got to the setup screen after flashing, I kept getting an error that said that setup crashed and could not run. I had to boot back in to recovery, flash again, only to find the same error.
I then attempted to flash clean rom, except now I see that her phone is always roaming where my Note2 right next to it is on 4G. I flashed an older CM10 nightly for her, and the same issue popped up where it is only roaming.
Did the failed CM10 flash screw something up? How can I get her off roaming and back on 3/4G? Thanks!
Click to expand...
Click to collapse
Can someone give me a very simplified rundown to fix this problem. I flashed the CM10.1 nightly and lost service as well. I noticed someone posted the solution in the comments but i don't understand all that funky talk. PLEASE HELP
Mindstar1 said:
You are awesome! I am sure you factored this in to your suggestion, but if I backup her current rom, then ODIN, then restore, it will not undo what I did with ODIN, correct? Again, I am pretty sure it wont, but I was also pretty sure I knew what I was doing when I flashed CM last night and look how that turned out. Thanks again!
Click to expand...
Click to collapse
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
stk162 said:
Can someone give me a very simplified rundown to fix this problem. I flashed the CM10.1 nightly and lost service as well. I noticed someone posted the solution in the comments but i don't understand all that funky talk. PLEASE HELP
Click to expand...
Click to collapse
Haha, this is why CM warns us not to flash the nightlies unless we know what we are doing, which you and I did not I guess.
Basically, to get your cell signal back you need to flash back to a different firmware version. You do this through a program called ODIN which is a desktop program for Windows or a paid app in Android. I am going the paid app route mostly because it is a bit easier, but the desktop version is free.
I have not tested the solution yet, but I have read on other posts that it works. If you do the app route, you select the firmware file with the app, run the process (it should be self-explanatory in the app), then once the new firmware is on, you dial a special verizon code to get your signal stuff fixed. Below are the files you need.
http://forum.xda-developers.com/showthread.php?t=1762204 (this is the firmware file that you will flash using ODIN)
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en (this is the mobile ODIN app)
Dial *2767*3855# once you have the firmware on to in theory fix the signal issue
After that, you can reflash your rom, but do not flash the CM nightly again!
kintwofan said:
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
OK, so a bit of a hiccup. I ran ODIN with the .tar file you suggested, and after going through the expected flashing and what not, the screen went black with my LED notification light blinking blue. I pulled the battery after about 10 minutes of this, booted into recovery then rebooted and it did the same thing. Ideas?
kintwofan said:
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
To clarify, it takes me to a menu called "Android System Recovery" with the following options:
reboot system now (takes me to the black screen)
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Any idea what I should be doing or what I did wrong?
Mindstar1 said:
To clarify, it takes me to a menu called "Android System Recovery" with the following options:
reboot system now (takes me to the black screen)
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Any idea what I should be doing or what I did wrong?
Click to expand...
Click to collapse
That's stock recovery. Not sure why it's not booting correctly. I would say just use desktop Odin and re flash
If I helped you in some way.... pass on the favor and help the next person!
Did you get this fixed?
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Did you get this fixed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Its not looking good... I am in desktop ODIN and it is running, but already there was a failure in the first block, and the log says "cant open serial COM port"
Mindstar1 said:
Its not looking good... I am in desktop ODIN and it is running, but already there was a failure in the first block, and the log says "cant open COM port"
Click to expand...
Click to collapse
Make sure you have the drivers installed and have rebooted computer. Also did you verify the md5 of your download
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Make sure you have the drivers installed and have rebooted computer. Also did you verify the md5 of your download
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did not reboot after the driver install, so I will do that. As for the MD5, what is that and how do I verify? You are talking about the firmware download, right?