Related
Stuck! For some God forsaken reason, when my phone is in DL mode Odin or any computer that i tried will read the phone. I have tried different drivers thats been posted in this forum along with different settings like turning on/off developer mode before going to DL mode.
So I cant use Odin to update my modem on my phone.... is there a file that i can roll back to the DI18? I use the update.zip from DI18>DK28 and hoping that i can revert that way and go get EC05 through CWM.
This doesn't belong in development, hopefully impaler will be here to move it soon.
We need more info to be able to help, like:
What OS is the computer running?
Do you have the Samsung drivers installed?
063_XOBX said:
This doesn't belong in development, hopefully impaler will be here to move it soon.
We need more info to be able to help, like:
What OS is the computer running?
Do you have the Samsung drivers installed?
Click to expand...
Click to collapse
>_< sorry for putting this in the wrong spot.
i have tried in different computers from win xp 32bit to win 7 32/64 bit
along with different drivers that have been posted here that people chimed in
and said that it worked for them.
my primary computer is win7 64 and i tried every driver that i can find under the sun and to no avail i fail.
try this
http://forum.xda-developers.com/showthread.php?t=1012384
I have the same problem myself.
DK28 is an unsupported build. The update script posted above won't work.
In DK28 USB communication died and as such Odin is not an option. The only option as far as I know is to flash a FULL ROM which has a DI18 modem as part of the ROM using CWM. You will just have to put the file on the SD card manually using a PC since USB is not an option.
After you go to DI18 just follow the regular steps to go from DI18 -> EC05 (may need multiple steps with EB13 intermediate step)
I haven't gotten around to doing this myself yet, still stuck on DK28.
LiberatorUSA said:
I have the same problem myself.
DK28 is an unsupported build. The update script posted above won't work.
In DK28 USB communication died and as such Odin is not an option. The only option as far as I know is to flash a FULL ROM which has a DI18 modem as part of the ROM using CWM. You will just have to put the file on the SD card manually using a PC since USB is not an option.
After you go to DI18 just follow the regular steps to go from DI18 -> EC05 (may need multiple steps with EB13 intermediate step)
I haven't gotten around to doing this myself yet, still stuck on DK28.
Click to expand...
Click to collapse
so flash a rom that have a di18 rom and hope for the best?
it seems that i have that i cannot find a rom that is supported with cwr 3.0+ to flash back to di18 =(
There is no reason DK28 should have effected being able to use Odin at all as LiberatorUSA has suggested, as many here running custom roms have more than likely run a version of DK28 at one time, and the only way to update the modem from DK28 is through Odin. And while you can flash a different rom through CWM (such as those based on DI18, EB13, or even EC05), you will still need to use Odin to update the modem. If you really think DK28 is to blame, then you can flash to an EC05 rom (such as SRF 1.1.0, as it supports CWM3) and then try to re-Odin from there.
Here are some basic things to try, as I don't see them listed in what you have done... Have you tried using every usb port on your computer? Are you using the stock usb cable? Have you tried other cables? Completely uninstall all previous drivers before trying to install different drivers. Open your device manager and connect your phone in DL mode, watching to see what devices appear, then manually attempt to uninstall those specific devices.
Download the epic drivers direct from Samsung. The first time connecting may take up to 15 minutes as there are some parts that Windows 7 seems to want to find on the net. After all drivers report installed then put your phone in download mode (hold 1 key while booting on) start Odin then plug your phone in. A COM number should show up on the computer screen. If this doesn't work try another data cable.
Do you BONSAI?
Have u tried different versions of odin?
Different usb ports?
Does the com port pop up?
Sent from my SPH-D700 using XDA App
I just posted a cwm zip to update your modem to ec05 regardless of what your current modem version is
keith5039756827 said:
Have u tried different versions of odin?
Different usb ports?
Does the com port pop up?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
kennyglass123 said:
Download the epic drivers direct from Samsung. The first time connecting may take up to 15 minutes as there are some parts that Windows 7 seems to want to find on the net. After all drivers report installed then put your phone in download mode (hold 1 key while booting on) start Odin then plug your phone in. A COM number should show up on the computer screen. If this doesn't work try another data cable.
Do you BONSAI?
Click to expand...
Click to collapse
Koadic said:
There is no reason DK28 should have effected being able to use Odin at all as LiberatorUSA has suggested, as many here running custom roms have more than likely run a version of DK28 at one time, and the only way to update the modem from DK28 is through Odin. And while you can flash a different rom through CWM (such as those based on DI18, EB13, or even EC05), you will still need to use Odin to update the modem. If you really think DK28 is to blame, then you can flash to an EC05 rom (such as SRF 1.1.0, as it supports CWM3) and then try to re-Odin from there.
Here are some basic things to try, as I don't see them listed in what you have done... Have you tried using every usb port on your computer? Are you using the stock usb cable? Have you tried other cables? Completely uninstall all previous drivers before trying to install different drivers. Open your device manager and connect your phone in DL mode, watching to see what devices appear, then manually attempt to uninstall those specific devices.
Click to expand...
Click to collapse
I have tried it in multiple computers and the odin do recognize the phone untill i go to DL mode, i Dl the drivers directly from samsung and it did took awhile to find the drivers. It recognize the device until i go to DL mode, I have used my samsung cable , my wifes htc evo cable and my mom's droid x cable. All the same result, i spent the whole day trying to figure it out. I had a fresh install of winxp and win7 on two different laptops.
I installed the DK28 through a CWM, i have been having odin problems since day one and not just this time.
You guys might want to check the discussion going on here:
http://forum.xda-developers.com/showthread.php?t=1026886&page=4
meh might just get a refurb from sprint later on. or get a new phone all together. I cant find a solution w/ or w/o odin >_<
Ok i rooted the phone when it was on 2.1 & it worked just fine, after the root it said system update, so i said ok to froyo, now i can't for the life of me seem to be able to root this phone the Samsung one click root dosen't work, & my PC won't recognize the phone so i can't use Odin, It's really pissing me off, if anybody can help me i'd sure be greatfull.
jaaydogg said:
Ok i rooted the phone when it was on 2.1 & it worked just fine, after the root it said system update, so i said ok to froyo, now i can't for the life of me seem to be able to root this phone the Samsung one click root dosen't work, & my PC won't recognize the phone so i can't use Odin, It's really pissing me off, if anybody can help me i'd sure be greatfull.
Click to expand...
Click to collapse
Make sure you have the latest drivers from Samsung installed on your PC. Reboot the phone, reboot the PC, start as fresh as you can. Best way to go about it is to Odin EC05, One Click root with CM3 (purple version) and go from there.
Check the stickied thread with the old stickies in it, you'll find everything you need in there. And last but not least, for the love of everything holy, don't use the stock cord. Get something decent, blackberry cables seem to work the best for me. Make sure the port you're plugged into on your PC is on the back (so it's direct into the board) not one of the front ones.
Well first off, having the thread title as "???" does not help anyone with searching for answers.
I'm trying to understand your situation: So you say you were on Eclair and rooted, and then was able to upgrade to Froyo while rooted? That's not possible. The update would have failed after seeing a file system mismatch.
For Eclair and Froyo, the 1-click root method works. However, for Gingerbread you have to Odin a custom kernel and recovery, then install the Superuser app. Once you have CWM installed you can flash any EL30 rom you wish. The modem is upgraded manually. Look in the dev section for the sticky thread that has the thread link in it.
Video 1: http://youtu.be/kwFRzzIqouE
Video 2: http://youtu.be/jWOLEXqAeCc
To follow up on your Odin woes: use a different USB port that is directly on the motherboard; and a different cable.
http://forum.xda-developers.com/showthread.php?t=1009997
Go to that thread, and it will tell u everything u need to know
Sent from my SPH-D700 using xda premium
2.1? Froyo? You know the Epic has official Gingerbread right? And stable ICS?
Sent from my SPH-D700 using Tapatalk
Well i know that but the site wouldn't let me name it anything, I mean like 15 different titles that i wasan't allowed to use. Anyway I was able to fix the phone up, i was having a driver issue & that's what was stopping Odin from detecting the phone in downloader mode.
I have an epic sitting at home that is useless as of right now because I no longer have a plan through sprint for it. I have a samsung replenish that I am using right now with Boost, and I am considering making it a donor phone and flashing the Epic over to Boost. Having this little thing really makes me realize just how awsome those Super AMOLED displays are. Anyway, I have a few questions before getting neck deep in this little endevour. First off, I don't want to be stuck on Eclair, but as I understand a Factory reset is necessary to get the 3G working, I read that people were abale to flash to Froyo using a few tricks, I was just wondering if the same works for Gingerbread. If anyone is running a Boost Epic on GB I would like to know how it is working out. Also, once the phone is flashed to said version of Android, can I just flash any rom on top of it through CMW without having to make tweaks?
And finally, I can not get either the Replenish or the Epic to read on CDMA Workshop, I have tried debug, non-debug, and diag modes and any combination, I have tried reading the phones in recovery mode, I have rebooted, restarted, unplugged, switched cables and ports....nothing...the phones both show up as modems and have their ports listed in device manager, but they absolutely refuse to show up, if anyone has any tricks that they could share regarding this issue it would be much oblidged
I know it's a lot but I figured I would try and cover all of my questions in one thread rather than making a bunch of seperate ones. BTW I have been researching for 2 days now, if there is something obvious that I missed, I apologize in advance, but I have tried other methods of resolution before creating this thread...Thanks in advance for any advice that you guys can offer...
We have a guide on here did you consult that? And I know that there is an alternative carrier fix for cm9 so you "could" get that puppy on android 4.0 =]. As for the computer not detecting... did you install the mobile drivers for the phones? I think you might need to if you haven't. I know when odining you need those I suppose the same for cdma workshop. Hope this helps at all =]. if you need the guide ill link it here.
Flashing Epic 4g to Boost Mobile Guide.
In this guide he is using the incognito but as long as you have a cdma phone to use as a donor phone you should be fine. If you havnet installed the drivers for either phones then this is most likely your issue. Also according to the guide you CAN flash other ROMs. The only thing that needs to be tweaked is the sms settings.
Yeah, I have looked at the guide, I was hoping to clarify on the few items that I wasn't clear on. I have installed the drivers for both phones and Odin does infact recognize each one, I use it to verify the Com ports that the phones are on...i'm baffled :/
After hours more of trying...and researching..I still can not get past the initial step of getting cdma to read my phones...either of them. Is there a section on this forum for requesting services? I dont care if I have to pay to get it done, I want my epic on boost...
bugzy3188 said:
After hours more of trying...and researching..I still can not get past the initial step of getting cdma to read my phones...either of them. Is there a section on this forum for requesting services? I dont care if I have to pay to get it done, I want my epic on boost...
Click to expand...
Click to collapse
I doubt it... but who knows. I dont see why they wont detect. They should if you have the drivers installed... maybe try just having one of the phones drivers installed at once... which ever phone you have to start off with have that phones drivers installed only. so unistall both then install just one that you need then unistall that one when the other one needs to be used... and you might want to reboot in between driver installations. drivers can be very picky. Or you could try another computer...
I'll give it a shot, its something new at least...I will post my results when I am done..
bugzy3188 said:
I'll give it a shot, its something new at least...I will post my results when I am done..
Click to expand...
Click to collapse
I know some having success doing this because they had their epic touch and epic 4g drivers installed once they unistalled both and just installed the epic 4g the computer would recognize it.
tried uninstalling all samsung mobile drivers and installing the drivers for each phone by themselves, still nothing...I am downloading a new set of drivers now, they are generic Samsung mobile drivers.I'm not expecting much but its all I got at this point...
bugzy3188 said:
tried uninstalling all samsung mobile drivers and installing the drivers for each phone by themselves, still nothing...I am downloading a new set of drivers now, they are generic Samsung mobile drivers.I'm not expecting much but its all I got at this point...
Click to expand...
Click to collapse
HMM i know which samsung drivers work great for the epic but i think you need device specific drivers for the replenish.
32 and 64 bit Drivers I know the drivers here work great and i have used them with every epic i've rooted... I just learned that the drivers im linking you to work for the replenish .
awesome, I am trying them as we speak...
ah crap, those were the same drivers that I downloaded for the Replenish, still a no go...the fact that neither phone works would tell me its on the PC end, and drivers would be the number one suspect, but alas...they just aren't making a difference in my results..
bugzy3188 said:
ah crap, those were the same drivers that I downloaded for the Replenish, still a no go...the fact that neither phone works would tell me its on the PC end, and drivers would be the number one suspect, but alas...they just aren't making a difference in my results..
Click to expand...
Click to collapse
Yeah you might need to try another computer. The usb ports could be bad/out on that one depending on how old it is. Or it could be the usb cable as well you'd be amazed at how much trouble is cause by those. Have you tried a brand new blackberry cable? those are the best cables at getting things recognized. What i dont get is that odin will COM the phone.... and this is in download mode right?
no, it coms both phones in debug mode, I have a few blackberry cables lying around that I have picked up on Amazon that I bought for Odin. Thats what kind of has me scratching my head too. It is an older laptop though, Id say about 4 years old, running windows 7 x64...I have checked QPCT as well just to see if it recognizes the phones and it doesnt either, so I guess it's some issue with my com port's compatibility with the mobile phone software....I will see if I can get away with doing this at work tomorrow, it may be tricky but my boss is old and senile lol
Well I tried it at work with no luck yet, which just leaves human error in to play...not sure what though, I've covered all of the options that I have come across. The replenish I could understand, but the Epic is documented to work just fine with CMDA WS...I just don't get it...
A couple things to try...
1. Connect the phone in normal mode (so it asks mass storage, etc) and let the drivers install.
2. Unplug, turn on USB debugging (Settings -> applictaions -> Development), plug the phone in and let it install ADB driver
3. With phone plugged in switch to dialer and hit ##8778#, then switch USB from PDA to Modem. Your PC should install another driver (Diag port).
Make sure you leave the Epic on this screen while accessing it via CDMAWS or any other program that uses the diag port.
I had major issues with the Epic, but that sequence finally got everything working. I still need to plug the phone in before enabling the diag port, otherwise stupid things happen.
This was all with an XP computer (three actually, before I figured out all the correct steps).
Thanks, I'll try that when I get home, I actually haven't tried putting it in diag mode while plugged in yet, I have always put it in diag and connected it...heres hoping..
ok, I finally got the replenish to connect, I found a way to root it and that worked like a charm....the epic however is still a no go...rooted running CWM 5, in diag mode, switched to modem, recognized as a modem....but still..failed...phone does not answer...any other suggestions guys?
Needs download mode not diag mode whatever that is... hold the 1 on the keyboard and the power button (yellow triangle) make sure is not in modem mode and you must flash the kernel from mkasick for ei22 search in xda "epic 4g gb kernel source" should me the first thread (ei22) kernel source with keyfix. Scroll to the bottom and find the gb3a.tar this is what you odin before cwm5 and it should stick. Then you can flash an su.zip and your done.
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Needs download mode not diag mode whatever that is... hold the 1 on the keyboard and the power button (yellow triangle) make sure is not in modem mode and you must flash the kernel from mkasick for ei22 search in xda "epic 4g gb kernel source" should me the first thread (ei22) kernel source with keyfix. Scroll to the bottom and find the gb3a.tar this is what you odin before cwm5 and it should stick. Then you can flash an su.zip and your done.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I was on EL30, which from my understanding worked as well. I flashed the gb3a and I am rooted with CWM and I installed SU, I just still can't get cdmaws to see the phone...I tried fix permissions, in CWM, not even sure what that does, but I tried it...i'm desperate lol. I have tried tether mode, switching ports, attempting while in recovery, and I get nadda....EL30 was what I had factory reset to, are you saying that I should flash back to ei22 for cdma or were you saying to do that to get it rooted?
No my appologies I, just read you rooted correctly. I'm not sure why it refuses to recognize the epic. Other than a better cable, or different usb port. I dunno. That or there is gunk in the epics usb port or in the computers. Should be in modem mode I'm assuming if your messing with the phoney. Stuff ='[ sorry.
Sent from my SPH-D700 using xda premium
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
premington said:
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
Click to expand...
Click to collapse
First u got check USB debugging ON (on the phone)
disable anti virus on the pc/laptop
kies will put your phone into download mode and will take awhile (Kies is super slow) for good reasons
Also consider rooting your phone and install custom recovery (CWM) and flash all the rom(s) you wish [if that's an option]
hit Thanks if i helped
Thanks for the help, Sam.
I'll try it again with the virus protection off. I disabled the Windows firewall and that did nothing. I've tried it about 12 to 15 times, which takes a long time because Kies takes so long to download what it needs.
Can I root a T-Mobile phone? I used to have a Motorola Atrix 2 and rooted that and did manual firmware and ROM upgrades, but that was an unlocked and rooted phone. I'm afraid I may screw up the phone or my T-Mobile service by rooting it and doing custom installs. Does anyone have experience with this on a T-Mobile phone they purchased at T-Mobile? I don't want to mess the phone up.
At this point, I think that's the only way I'm going to go Jelly Bean on my wife's phone.
-Paul
Rooting your s2 is simple and easy to do. Go to the dev section and look at the threads on how to do it.
You will use Odin to flash a custom recovery such a TWRP whick will install supersu. At that point you can flash the ROM of your choice and not have to deal with Kies anymore.
Hope this helps
Sent from my SAMSUNG-SGH-T989 using xda premium
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
sam.balia1012 said:
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
Click to expand...
Click to collapse
This is all great information... Thanks so much. I've pressed "Thanks" to each of you. :good:
-Paul
I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk
LanceDiamond said:
I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.
ciphercodes said:
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.
Click to expand...
Click to collapse
Can't seem to get KIES to connect - the most definitive result I got was a device not supported by KIES message after uninstalling/reinstalling drivers, making sure the phone is in the right mode etc. For the most part KIES just sits at connecting forever. This is the case with both the Note 2 and a Samsung Galaxy S4. KIES isn't exactly inspiring confidence it can magically restore my entire efs & all NV items...
Just to clarify, I can access recovery just fine - I can use Odin to flash to whatever albeit the bootloader is 4.3/Knox locked. I can flash modems, ROMS, etc and access ADB shell or whatever else I'd need to do with ADB. Can't seem to get KIES to work and as I understand it what you're telling me to do in KIES won't actually restore efs, it just resets it to a stock state and lets efs rebuild - assuming the NV items are still there, which they are not. I really hope I'm wrong and I'll have to come back here once I get KIES sorted out and tell you how silly I was for not believing you in the first place!
I did re-flash the modem using TWRP, no change there.
Here's the text of the warning I foolishly ignored:
Warning: Must read below guide
All Communication between AP/CP-
will be disconnected!
To return to normal mode,you
must download efs12.tar file!
All NV data will be erased!
Really want to use RmNET?
Click to expand...
Click to collapse
This was in the ServiceMode menu accessed with dialer code *#9090# but now there isn't a menu there - just a blank screen that says ServiceMode at the top. Dialer code *#0011# produces the same result - no menu where there used to be one, just blank screen/ServiceMode. Based on that warning, this isn't something I expect KIES to fix - but as I said, I hope I'm wrong about that...
Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Switching to KIES 3 got KIES talking to the phone. It says I'm on the current version of the firmware (because I am - it's what I just flashed with Odin.) If I go into Tools/Emergency nothing is listed. If I go into the second choice and enter the model number with the phone plugged in, it tells me it doesn't support firmware initialization. If I do it without the phone plugged in, it works and accepts the serial number from the phone. If I plug the phone in right after I've gotten past this point, KIES winds up going off into never never land a bit later after it tells me everything is going to be wiped and the phone will be put back to its initial state (which does sound somewhat promising.)
Its spawning this AdminDelegator process which seems to just be sitting doing nothing and the KIES window is shaded. I can close it but that's about the only interaction possible with it in this state - none of the menus work and it seems like it's waiting on something to be clicked maybe in the AdminDelegator process but that process has no window anyplace.
It's possible there is something useful buried in KIES but it's a horrible piece of software. They seem to be authoring it on at best 32bit Windows 7 and that's a stretch, I suspect they're still targeting 32bit XP. I'm on x64 Windows 8.1. I could rant much more but I'll leave it at that.
I'm going to keep working with it and see if I can get around how they've written it or I might just stick it in a 32bit XP VM and see if it's happy back in 2005, software-wise. <G>
I may wind up giving up and just getting another phone - I've already read up some on my options and the funny thing is, I still want a Note 2 - they can be had for more reasonable $ now than a year ago anyway...
LanceDiamond said:
Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
Did you verify the IMEI after this flash ?
ciphercodes said:
Did you verify the IMEI after this flash ?
Click to expand...
Click to collapse
Short answer: IMEI & baseband same as before the flash - both are "Unknown".
Prior to my messing with the dialer menu, everything was fine. I'd used Odin or TWRP recovery to flash a variety of different ROMs the last of which was the 4.3 we're talking about here and it was working. I'd used it for several days. Everything but screen mirroring worked without any problem and I had service - I read up on the screen mirroring problem and it sounded like getting the device to show "Official" might help so I tried to reset my flash counter which I did not do before going to 4.3. Flash counter wouldn't reset so I decided to go back as far as I could on modem/ROM and see if I could reset flash counter then. (I know my Knox flag is not fixable - I was just trying to change the flash counter.)
Using TWRP, I installed UVALJ1 modem & associated ROM, leaving the 4.3 Knox locked bootloader in place to see if that'd work. It did, it booted and I had service. I was actually playing with the menus to see if the old dialer code free unlock menu settings still seemed to work because someone had posted about needing to unlock - looked like the menus were still there for doing an unlock. In messing with the menus I picked the option that messed everything up and since doing that, no matter what I flash, IMEI & baseband are unknown.
Unless KIES rebuilds the entire radio - which it very well might based on it needing the correct model and then wanting a valid serial # - I think I need an efs restore to get the phone communicating with anything now.
One thing I just now did - using the free NV Items Reader Writer from this thread: http://forum.xda-developers.com/showthread.php?t=1804117
On my Note 2 configured as "DM+Modem+ADB" in Qualcomm USB settings (the only of several dialer menus I know of that still actually exists & seems to work), I can see the modem & port in device manager. But the app cannot communicate with the phone. If I change nothing, unplug the Note 2, plug in my Galaxy S4 in "DM+Modem+ADB" mode, I see modem & ports pop up in device manager and now the app can communicate with the phone.
I'm afraid, based on the text of that warning and searching for what "AP" and "CP" are, that the phone isn't going to be able to communicate with much of anything until it gets its efs fixed. This test where I just swap phones seems to be comfirming that this phone isn't responding like it should. Basically my modem & the rest of the phone are disconnected right now - at least that's my understanding. If the modem really is disconnected then obviously trying to do something to fix it via the modem is never going to work. The KIES may work - if I can ever get it sorted out. Haven't yet tried it in a VM might do that right now...
Edit:
Got KIES3 & drivers working in Windows XP SP3 VM. KIES connects to phone but if I pick Tools/Firmware Upgrade with the phone connected it just says "SGH-T889 does not support initializing" and my only choice is "OK". If I go Tools/Firmware without the phone plugged in, I can enter the model # and then it asks for serial #. If I plug the phone in at the point it goes all the way to where it says it's downloading firmware and then same result as on Windows 8 - an AdminDelegator process gets started, KIES gets sort of dimmed like it's waiting on something and nothing ever happens. If I never connect the phone KIES goes through the downloading process then gets an error with options to send a message or cancel - no information about what the message is, what the error is - just I can send it, it won't contain personal information or I can cancel.