[Q] Help!! SIM not recognized after updating bootloader - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I was trying to install the Quantum Rom on my ATT Samsung Galaxy S3.
It failed a few times until someone posted that I need to update my bootloader to I747UCUEMJB. I was able to install the ROM after the update but now my phone won't recognize the SIM card that's worked flawlessly till I performed the bootloader update.
Is my phone done for good or is there something I can do here? Please help!!

Did you flash a compatible or updated modem?

audit13 said:
Did you flash a compatible or updated modem?
Click to expand...
Click to collapse
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?

There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898

audit13 said:
There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Yeah figured as much, especially after looking at the contents of the file, I decided not to use it.
Thanks for the link. Just downloaded modem_CWM_I747UCUEMJB.zip and I have my network signal back up now. I am hoping this means I am good. Will let you know soon. Thanks!!!

theproman23 said:
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?
Click to expand...
Click to collapse
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.

Larry2999 said:
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.
Click to expand...
Click to collapse
I completely understand what you're saying. Truth is I don't enough about all this to do what I did. Lesson learned for sure!
So. I was able to install the Modern bootloader and have my LTE signal back up and confirmed things are working given someone already called me and the call came through fine.
Now, the last thing I need to figure out is how to get WIFI to work. It's connecting to my router and has gone through authentication and has saved my network on the list of WIFI spots but I can't seem to connect and start downloading apps without eating my data.
Never mind, finally got wifi to work. Thanks again!!

Are you using any sort of encryption on your wifi network (i.e. WPA, WPA2, etc.)? Can it connect if you disable encryption?

Related

[Q] Stock T-Mobile Image and Baseband

Anyone have these yet by chance?
I am sure it is coming. I would like to get my hands on it also.
Would be nice to have as I've already screwed it up.
liquidblue1985 said:
Would be nice to have as I've already screwed it up.
Click to expand...
Click to collapse
did you flash the n7100 stock firmware?
JoJo2211 said:
did you flash the n7100 stock firmware?
Click to expand...
Click to collapse
Nope. Downloading that right now actually. The only issue I'm having is that it's not recognizing the baseband.
It would be nice to be able to flash the Tmobile modem.
gedster314 said:
It would be nice to be able to flash the Tmobile modem.
Click to expand...
Click to collapse
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
liquidblue1985 said:
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
Click to expand...
Click to collapse
+1 I need the modem or a stock tar to odin asap, hope it drops soon...
The non-ISIS sim card did not change anything.
Looks like I need the stock rom also.
:/
luser01 said:
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
Click to expand...
Click to collapse
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
liquidblue1985 said:
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
Click to expand...
Click to collapse
luser01 said:
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
Click to expand...
Click to collapse
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
I will try that..
I called Samsung last night and they gave me the same run around.
liquidblue1985 said:
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
Click to expand...
Click to collapse
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
liquidblue1985 said:
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
Click to expand...
Click to collapse
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
How hard is it to extract a baseband image?
Could someone that has one do it easily?
MikeBrWade said:
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
Click to expand...
Click to collapse
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
anoneemooz said:
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
Click to expand...
Click to collapse
luser01 said:
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
Click to expand...
Click to collapse
Oh so wait. You're using a T-Mobile Note 2 and managed to flash an international ROM with everything working and functional (except for signal/sms/data/call) ? No reboots?
I ask because I've been wanting to somehow "convert" my T-Mobile Note 2 to an international Note 2 (as in, be able to flash the updates the international version gets instead of waiting on T-Mobile). I'm not US based so I don't need it to work with T-Mobile SIM anyhow...

SIM no longer recognized as being inserted; IMEI not visible in software

Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
dhmmjoph said:
Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
Click to expand...
Click to collapse
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
BWolf56 said:
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
Click to expand...
Click to collapse
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
No, sorry. And I doubt you'll find one.
dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
http://www.androidfilehost.com/?fid=23212708291680823
Larry2999 said:
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
Click to expand...
Click to collapse
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
BWolf56 said:
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
Click to expand...
Click to collapse
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
dhmmjoph said:
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
Click to expand...
Click to collapse
I'm not so sure what file you downloaded but it should be a zip. In order to flash, you need a zip with META-INF folder in it (to put it simply).
Here's what you need: http://forum.xda-developers.com/showthread.php?t=1831898 (The MJB one).
dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Larry2999 said:
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Click to expand...
Click to collapse
Here's a TWRP flashable zip for the modem if the CWM doesn't work.

Any please HELP!! Stock S6 edge firmware.

Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
samanbabah said:
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
Click to expand...
Click to collapse
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Protomize said:
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Click to expand...
Click to collapse
That doesn't fix issues for those of us that need to have the full stock firmware to re-Odin with. Guess those of us in the same boat wait a week or so. My problem was removing the knox files with root explorer. Bad move. Makes the phone unbootable. Called Samsung tech support and they confirmed that. Rooting no problem. Recovery screen totally blank. Never get to see the the white/green screen some say they have for a recovery screen. The magic use volume up keys 7 times etc I have seen posted don't work for me. Samsung specifically told me the stock firmware is proprietary, so they wouldn't give it to me. I can wait a week or so for developers to get their hands on appropriate files, including a custom recovery that actually works...like good old TWRP :victory:
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
have you tried to flash the S6 file? not the S6 edge but the S6. Try to get yourself in download mode and do that. Make sure you are using the correct odin. That is what happened to me and I was able to obtain ROOT.
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
SuperSport said:
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
Click to expand...
Click to collapse
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Docmjldds said:
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Click to expand...
Click to collapse
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
SuperSport said:
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
Click to expand...
Click to collapse
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Docmjldds said:
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Click to expand...
Click to collapse
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
SuperSport said:
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
Click to expand...
Click to collapse
it's weird I can't use Kies at all.
samanbabah said:
it's weird I can't use Kies at all.
Click to expand...
Click to collapse
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Wait
I think you should wait until pushed ODIN firmware over web...
dreamytricks said:
I think you should wait until pushed ODIN firmware over web...
Click to expand...
Click to collapse
Well, someone (Pagel) already posted the 920 stock tar file in the S6 thread. so there MUST be a source currently. Wish I knew why Sammobile web site returns errors for me about unable to open web page. That's the source most state is where to go.
Docmjldds said:
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Click to expand...
Click to collapse
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
samanbabah said:
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Click to expand...
Click to collapse
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
SuperSport said:
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
Click to expand...
Click to collapse
oh OK I didn't see your previews post.
samanbabah said:
oh OK I didn't see your previews post.
Click to expand...
Click to collapse
No problem, as long as we all get there at some point. The temp file that Kies downloads is called tmpE635.tmp It ends up being about 1.6GB in size. I tried to open it using 7-Zip and WinRar, but neither will open it. I'll post it in case anyone wants to try using it in ODIN. I don't know if it is specific to MY phone, or the T-Mobile S6 Edge in general (SM-G295T).
But, honestly, I would suggest you use Kies yourself so you are positive to get the correct file. You WILL get the error message that says Kies does not support your phone, just ignore that and keep going.
Phone Serial Number
I just realized that the Serial Number Kies is asking for is not on my Box. It's in the settings/about/status menu, and also on a sticker that is stuck to the Plastic Wrap that was around the phone in the box. Looks sort of like this: R58G31D1PBA. So, if you cannot get into your settings, or don't have that plastic, I'm not positive how you will get it to start the download. Maybe if you just use someone elses serial number, that will start the download???
EDIT: Link to the Temp File from Kies (not sure you'll be able to do anything with it)
https://mega.co.nz/#!39gwRAKS!H81yfo1vCQkMOujTaQJaU2INXoPNtUF6cgnF46jAfXI
WTF
Had the download stall on me twice, 35 and 47 percent.

[Q] ATT ZE500CL/Z00D Bricked After OTA Update - HELP (ZenFone 2E)

I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere
also
please pm me if u fixed yours
Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now
Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?
The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.
I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore
need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?
Hola, alguien lo consiguiĆ³ hacer..???
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/
m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse
ayuda
ATT ZE500CL/Z00D rom

How do I Upgrade from PF3 to PG2?

Mods/Admins - Please move this thread if necessary. I wasn't sure if I should post it here or in a Troubleshooting forum.
Thanks to one of my previous threads, I kind of know how to do it, at least from PD1 to PF3. That said, I have questions.
Can someone link me to the correct file to flash to upgrade from PF3 to PG2?
Process wise, is this any different than upgrading from PD1 to PF3? That is, will I need to re-unlock/re-root?
Will I need to FDR after flashing via Odin in Download Mode or do any form of wiping in TWRP?
Check out the first post in this thread:
http://forum.xda-developers.com/note-4-verizon/development/rom-paulpizz-rom-t3360469?nocache=1
Scroll down to the part of the post that starts with this:
**Important information to hopefully clear up some of the confusion on updating to VRU2CPG2**
I downloaded the 'N910VVRU2CPG2_bootloaders_NoAboot' file and odin'd it to my phone since I was already on MM. It worked fine. It did not re-lock my bootloader and I remained rooted.
driguy said:
Check out the first post in this thread:
http://forum.xda-developers.com/note-4-verizon/development/rom-paulpizz-rom-t3360469?nocache=1
Scroll down to the part of the post that starts with this:
**Important information to hopefully clear up some of the confusion on updating to VRU2CPG2**
I downloaded the 'N910VVRU2CPG2_bootloaders_NoAboot' file and odin'd it to my phone since I was already on MM. It worked fine. It did not re-lock my bootloader and I remained rooted.
Click to expand...
Click to collapse
Did you download and install BOTH N910VVRU2CPG2_bootloaders_NoAboot & the N910VVRU2CPG2_modems files??
JOSHSKORN said:
Did you download and install BOTH N910VVRU2CPG2_bootloaders_NoAboot & the N910VVRU2CPG2_modems files??
Click to expand...
Click to collapse
I did, but you shouldn't need to. The N910VVRU2CPG2_bootloaders_NoAboot file should have the modem in it. I'm pretty sure I downloaded both, flashed the modem file first, and then the firmware file.
driguy said:
I did, but you shouldn't need to. The N910VVRU2CPG2_bootloaders_NoAboot file should have the modem in it. I'm pretty sure I downloaded both, flashed the modem file first, and then the firmware file.
Click to expand...
Click to collapse
Last time I didn't flash a modem file, I ended up with no WiFi, so I'd better.
JOSHSKORN said:
Last time I didn't flash a modem file, I ended up with no WiFi, so I'd better.
Click to expand...
Click to collapse
I just did both out of habit. Wifi works fine for me doing it the way I did.
driguy said:
I just did both out of habit. Wifi works fine for me doing it the way I did.
Click to expand...
Click to collapse
Do you notice any speed or battery differences?
The reason I upgraded to cpg2 was so I could use the new PaulPizz rom. It's stable for me but it's not like the older version was unstable to begin with. I am also running a 3rd party kernel, it didn't seem to affect battery life one way or the other. Then again, my phone setup/usage habits are probably different than yours.
---
driguy said:
Check out the first post in this thread:
http://forum.xda-developers.com/note-4-verizon/development/rom-paulpizz-rom-t3360469?nocache=1
Scroll down to the part of the post that starts with this:
**Important information to hopefully clear up some of the confusion on updating to VRU2CPG2**
I downloaded the 'N910VVRU2CPG2_bootloaders_NoAboot' file and odin'd it to my phone since I was already on MM. It worked fine. It did not re-lock my bootloader and I remained rooted.
Click to expand...
Click to collapse
I noticed now it's called CPJ2, same process though, same post, right? Just a newer version?
JOSHSKORN said:
I noticed now it's called CPJ2, same process though, same post, right? Just a newer version?
Click to expand...
Click to collapse
I'm guessing it would be. I haven't taken the time to try it out yet but plan to within the next few weeks.

Categories

Resources