Develop Bugs

[Q] Help!! SIM not recognized after updating bootloader

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?

[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

Need help returning verizon s8+ to stock

howdy. Need help returning Verizon s8+ to stock after rooting and using a custom rom. every time I try to flash the stock firmware it says "FAIL! Model dismatch fail". also cant add user data in the ums slot, doesn't let me click on it. I've tried different sources but can't seem to get it to work. any help would be greatly appreciated.

now when i try to flash a custom rom it says "FAIL! (Auth)"

captaingohan said:
now when i try to flash a custom rom it says "FAIL! (Auth)"
Click to expand...
Click to collapse
Going through the same exact thing here. Trying to flash G950USQS2BQL1 that I got from Sammobile and first got the mismatch then I tried flashing with Prince Comsy's version of Odin and got the Fail auth. Now it's just stuck at SetupConnection. Let me know if you find any way that works please. I'll keep you updated if I figure it out.

I actually accidentally fixed it yesterday and successfully returned to stock. Even got Samsung pay and Android pay to work. I'll check out what files I used when I get home and let you know.

Try getting the firmware from updato instead of sammobile.

got mine working from sam mobile. https://dl.sammobile.com/M1FcRjxCIS...kRYXA../G955U1UES2AQL1_G955U1OYM2AQL1_VZW.zip

this link says user not logged in

Gents, can somebody help me? I've got a unlocked S8+ that I got from Samsung not knowing that key features I need like wifi calling wouldn't work. My current software is U1. So, how can I flash the stock Verizon firmware on my phone so that I get the wifi calling? I travel overseas a lot and need it. I'm tech/computer savy but am clueless on cell phones.. So any step by step instructions would be most appreciated.
Thanks!

nd3 said:
Gents, can somebody help me? I've got a unlocked S8+ that I got from Samsung not knowing that key features I need like wifi calling wouldn't work. My current software is U1. So, how can I flash the stock Verizon firmware on my phone so that I get the wifi calling? I travel overseas a lot and need it. I'm tech/computer savy but am clueless on cell phones.. So any step by step instructions would be most appreciated.
Thanks!
Click to expand...
Click to collapse
You need to flash the stock verizon files in ODIN. You can search XDA or Google it. There are threads that explain it. Backup your phone, download the files - might take a while, unzip, and flash. It will wipe your phone.

combination file Galaxy s9

hello, guys!
I'm not too good in this, I have tried to find a combination file for G960WVLU4CSD2 (Samsung Galaxy S9), but no luck! frp hijacker tool is not working too. Any ideas?

utahhh said:
hello, guys!
I'm not too good in this, I have tried to find a combination file for G960WVLU4CSD2 (Samsung Galaxy S9), but no luck! frp hijacker tool is not working too. Any ideas?
Click to expand...
Click to collapse
which S9 do you have? the F or the U?

Youdoofus said:
which S9 do you have? the F or the U?
Click to expand...
Click to collapse
not sure exactly if i have the right answer, but in the back is SMG960U. Is this what you asked?

utahhh said:
not sure exactly if i have the right answer, but in the back is SMG960U. Is this what you asked?
Click to expand...
Click to collapse
its the U hold on a sec

https://samsungcombinationfile.com/samsung-sm-g960w

md5 error! Binary is invalid

ok, so finally I was able to find the combination file on another site (but the link you gave me was very useful).
i had the first error SHA256 is invalid (I have changed Odin with pa patched Odin -> ok). This error is because i have tried to change service provider.
my second error:
An error has occurred while updating the device software. Use the Emergency recovery function in the Smart PC software.
Still trying to figure it out. getting back with updates...

tried to use CSC.md5 instead of home_CSC.md5, everything seams to be good!
thx a lot for help!

Hey I am having a problem on finding the files for two Samsung s9 I’ll looked everyee we here and can’t find matching ones

SM-T325 PIT

Hi,
Does anyone have one or know how to get it?
Odin is not able to download one.
Thanks,
Maced

maced said:
... Does anyone have one or know how to get it?
Odin is not able to download one......
Click to expand...
Click to collapse
Odin was not made for downloading anything.
Afaik it's integrated in the CSC.... file.
I've extracted it once and you're free to use it of course no warranty or anything.
Btw. what happened that you have to repartition it?

Thanks, actually I am not sure I have to.
To be totally honest - its first time I am trying to install a new OS on this device - it has original version now.
Was just following instructions online - I am not 100% aware about ins and outs. Also it seems JOdin does not allow install without PIT.
It says that the your PIT is corrupted.
Thanks!

maced said:
Thanks, actually I am not sure I have to.
To be totally honest - its first time I am trying to install a new OS on this device - it has original version now.
Was just following instructions online - I am not 100% aware about ins and outs. Also it seems JOdin does not allow install without PIT.
It says that the your PIT is corrupted.
Thanks!
Click to expand...
Click to collapse
Usually you uncheck repartition.
pit may afaik only be needed when device has lost it.
Odin works without.
You only flash TWRP with it and after that you don't need it anymore until you wanna turn back to stock.
Mine is from dbt stock firmware perhaps that's why.
Silly question but you've unpacked it?

@maced now that I'm home I've checked.
Extracted it from this stock file I've got via samfirm_reborn0.3.6.2: "CSC_OXA_T325OXA1BQB3_CL10765915_QB12683141_REV00_user_low_ship_MULTI_CERT.tar" what you can do yourself from the file suitable for your device.