Tweet
So I got the new motherboard for my S4. I cannot get it to detect my T-Mobile SIM, which works in other devices, but not in my SGH-M919. T-Mobile told me that it was because my S4 was trying to register on the network but can't. I verified that the mobo I bought had a clean IMEI, and that this IMEI was from T-Mobile USA. It will detect older T-Mobile SIMs, but not newer ones. I have bought multiple SIM trays, and with my old mobo, it would work for a couple weeks, then randomly give me the "No SIM" error. In my new motherboard, which has older 4.3, iit will not detect at all, but it will detect my SIMple mobile card, that has a larger chip.
My question is this: I am currently in the process of making a full backup (image file mode) of my S4 using the JTAG DCC read in JTAG manager. (16GB so it is taking 48hr). If I update to the latest version OTA to make sure it works, then root it with ODIN, and find that I don't like it (can't root it, Knox etc), can I use the DCC in JTAG manager to write this image back, and will it work as it did?
It would make sense to me it would, but I figure I'd check with a more experienced user to see if it would or not. Furthermore, does anyone know of a fix for this SIM issue? Maybe there's something I can change in a HEX editor and flash this back. I don't know.
There are also 2 flash chips detected in JTAG manager. One 16GB, one 4MB. My guess is that the 4MB contains the IMEI, unlock code, etc however reading it I get only "zeroes". I searched for my IMEI, and found some data on it, but it may be encrypted as I cannot find the number itself.
Any ideas on full backup / restore, has anyone had success after upgrading on the SGH-M919, restoring with JTAG manager and gotten it back the way it was?
I get about 100kB/sec reading the eMMC and it's taking forever. I bought the eMMC/SD activation, but I don't think it is even using this, as it is reading through the ARM over JTAG. My JTAG wires are about 12" long, they are 30 ga stranded, that are twisted together with a grounded wire and grounded at both ends. I can sample RTCK at 12MHz, but not max, and if I get close enough to the RIFF / S4, it will give me a "READ not recognized". Furthermore, the RIFF DCC over USB will not work, even with the phone ON, which I assume the S4 does not support this and will have to wait for the slow JTAG getting 16GB through the TDO.
Sorry if this is a stupid question, help a newbie brother out.
My question is this: I am currently in the process of making a full backup (image file mode) of my S4 using the JTAG DCC read in JTAG manager. (16GB so it is taking 48hr). If I update to the latest version OTA to make sure it works, then root it with ODIN, and find that I don't like it (can't root it, Knox etc), can I use the DCC in JTAG manager to write this image back, and will it work as it did?
It would make sense to me it would, but I figure I'd check with a more experienced user to see if it would or not. Furthermore, does anyone know of a fix for this SIM issue? Maybe there's something I can change in a HEX editor and flash this back. I don't know.
There are also 2 flash chips detected in JTAG manager. One 16GB, one 4MB. My guess is that the 4MB contains the IMEI, unlock code, etc however reading it I get only "zeroes". I searched for my IMEI, and found some data on it, but it may be encrypted as I cannot find the number itself.
Any ideas on full backup / restore, has anyone had success after upgrading on the SGH-M919, restoring with JTAG manager and gotten it back the way it was?
I get about 100kB/sec reading the eMMC and it's taking forever. I bought the eMMC/SD activation, but I don't think it is even using this, as it is reading through the ARM over JTAG. My JTAG wires are about 12" long, they are 30 ga stranded, that are twisted together with a grounded wire and grounded at both ends. I can sample RTCK at 12MHz, but not max, and if I get close enough to the RIFF / S4, it will give me a "READ not recognized". Furthermore, the RIFF DCC over USB will not work, even with the phone ON, which I assume the S4 does not support this and will have to wait for the slow JTAG getting 16GB through the TDO.
Sorry if this is a stupid question, help a newbie brother out.
Comment