Related
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
I have an unlocked bootloader.
Can anyone upload to a Dropbox, or somewhere else, just the system partition so I can restore via nandroid on TWRP? Otherwise I am stuck waiting for the SBF, since I can no longer downgrade.
Thanks
Sent from my Moto X using Tapatalk
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att: http://www.androidfilehost.com/?fid=23329332407581236
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
cpetersen2791 said:
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Exactly.
I see it was downloaded 9 times before me. I didn't have any luck with both TWRP and Philz's recovery. Flash stalled on "extracting system files" for 5+ minutes.
I would take the entire TWRP backup if you can upload that.
UPDATE: I deleted the boot.img out of the zip file, and it flashed, then manually flashed boot.img.
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
Ctrl-Freak said:
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Click to expand...
Click to collapse
OMG, I think this file will help me to rescue my brick!!!!!
Can I manually flash this firmware on my device using fastboot tool?I have no idea about what safestrap is,please no hate.
It's still a WIP, after flashing, I didn't have radio. Will work on that tomorrow. If we get it going, I'll post something, with Ctrl-Freak's approval.
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
Exactly.
Click to expand...
Click to collapse
I download your zip and find out this is not a firmware...OTZ
I can only wait until the sbf file released.
cpetersen2791 said:
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
...
It's still a WIP, after flashing, I didn't have radio...
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Safestrap Version
-If you are already on 4.4.2 then boot into Safestrap and factory reset, do not wipe the system then install to the STOCK slot.
-If your not on 4.4.2 then go here and follow the instructions from my stock rom thread http://rootzwiki.com/topic/116025-ro...52-kitkat-442/ I don't feel like reposting them in here.
Click to expand...
Click to collapse
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Ctrl-Freak said:
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Click to expand...
Click to collapse
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
cpetersen2791 said:
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
Click to expand...
Click to collapse
Sorry. I wasn't telling you to get that rom or the Verizon radio, I was pointing out that a factory reset in TWRP may help with the radio issue.
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
Click to expand...
Click to collapse
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Ctrl-Freak said:
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Click to expand...
Click to collapse
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
cpetersen2791 said:
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
Click to expand...
Click to collapse
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Another thought. Maybe I have to flash the radio, even though I haven't changed. Kind of like flashing the boot.img. I haven't changed that either, but it had to be flashed to boot.
Do you know where I can grab the radio IMG? Can't seem to find it around.
I supposed I can pull it from Att 4.4 sbf. Which files tho, just the Non-hlos.bin file? I don't have the xml here @ the office so I don't know what to look for.
Thanks again for your help
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Click to expand...
Click to collapse
Found this...
it's OS 4.4 (140.44.5), will that run into the brick issue?
Hi to everyone who has been having problems with domestic unlock, after updating to OD2 lollipop.
I myself have been experiencing some problems with OD2 and domestic unlock, one of which is the "INVALID SIM CARD". I did not get any service after updating. I tried downgrading my modem to NG2 and i got service, but the wifi was not working. I tried every other modem available to the SPH-L720, and the still the wifi did not work. So i worked night, and day, trying to figure out how to make it work. Then i thought to myself, hmm... why not create my own modem?? and so i did. It is currently working on OD2 stock lollipop.
**NOTE** This is ODIN flash-able. there is a .7z file inside the zip file, it must first be decompressed.
!!USE AT YOUR OWN RISK!!
For anyone who is wondering how i did this: Here is a short video containing, the simplest way of creating the modem. it is in a zip file. it is .mp4 format. Do not upload it to youtube.
IMAXuOUT How to create modem 2015-05-24.zip
You're Welcome!
updated version
click here : View attachment 3331378
Please give credit, where and when credit is due.
click here : View attachment 3331378
Could you provide a little more detailed info on what you mean by "created your own modem" ? This is a risky partition to flash to.
Exactly that is why i said "!!USE AT YOUR OWN RISK!!". For if i had to take the time to explain to you what i did, and how i did it, that would be a waist of my time. i have real work to do.
Lol....... pardon me for questioning your methods sir!
Ill just leave this here:
http://forum.xda-developers.com/showthread.php?p=58940258
:laugh::laugh::laugh::laugh::laugh:Ha ha. As you can see; the little that i have learned in the past four months, has taught me quite a bit. Now i am moving up in the world of sph-l720..... LOL .... i went from NooBie to Just Noob... this is quite an accomplishment for me, i am really proud of my self... he he...:laugh::laugh::laugh::laugh::laugh::laugh:
i did not bite off any ones head....
maybe later tonight if i have the time; i will post the details of how my modem, came to Fruition...
judge me not by my words, but only by my deeds. lol.
imaxuout said:
What... Am i some kind of vampire, or werewolf? i did not bite off any ones head....
maybe later tonight if i have the time; i will post the details of how my modem, came to Fruition...
judge me not by my words, but only by my deeds. lol.
Click to expand...
Click to collapse
We all just need to know what exactly you did so we can be sure we don't end up with bricked devices. Flashing a bad or wrong modem could possibly turn a device into a paperweight. That's the point we are trying to make here.
Please keep in mind that if in fact this is all good, it could be a VERY popular mod!
jstntp said:
We all just need to know what exactly you did so we can be sure we don't end up with bricked devices. Flashing a bad or wrong modem could possibly turn a device into a paperweight. That's the point we are trying to make here.
Please keep in mind that if in fact this is all good, it could be a VERY popular mod!
Click to expand...
Click to collapse
I HAVE FLASHED IT ON MY DEVICE SEVERAL TIMES. NOT ONES WAS MY PHONE BRICKED. MY PHONE IS THE "SPH-L720 16GB", NOT THE TRI-BAND MODEL. I USED THE "MUNIZ_RI L720_OD2_Stock_Rooted_ROM".
***NOTE ***I DID "NOT" ATTEMPT THIS ON ANY CUSTOM ROM'S .
I AM ON ULTRA MOBILE, WHICH IS AN "MVNO" UNDER T-MOBILE.
HERE IS ANOTHER PEACE OF INFORMATION. IF THE MODEM/NON-HLOS IS NOT COMPATIBLE WITH YOUR PHONE, IT WILL NOT FLASH (VIA ODIN3 V3.09), IT WILL FAIL. AND NO YOUR PHONE WILL NOT GET BRICKED. IT MAY HAVE SOMETHING TO DO WITH KNOX, OR JUST FIRMWARE I DO NOT KNOW.
DOES THAT HELP?
Ok, good info...... but how did you go about modifying the modem itself? A short version of what you did would be fine..... maybe a link or two to what resources you used? Modifying or "creating" a modem is not very common at all. If it were, there would be custom modems all over the place.
jstntp said:
Ok, good info...... but how did you go about modifying the modem itself? A short version of what you did would be fine..... maybe a link or two to what resources you used? Modifying or "creating" a modem is not very common at all. If it were, there would be custom modems all over the place.
Click to expand...
Click to collapse
i just created a short video, with the simplest way of creating the modem.
it is in a zip file. it is .mp4 format. Do not upload it to youtube.
You're Welcome!View attachment 3329665
I am currently working De-compiling and editing all of the files, then recompiling them, and testing.
it will take me a while so please be patient.
i could use all the assistance that i can get.
Thank You.
Alright...... because your video shows how to make a zip file, but doesn't show how to modify/create a modem.
Just to clarify, the modem you posted in the OP was modified by you personally? And it unlocks sim access on OD2? So anyone who flashes it on a sprint L720 (non tri-band) stock rooted rom will be able to use their phone on T-Mobile or another GSM carrier?
jstntp said:
Alright...... because your video shows how to make a zip file, but doesn't show how to modify/create a modem.
Just to clarify, the modem you posted in the OP was modified by you personally? And it unlocks sim access on OD2? So anyone who flashes it on a sprint L720 (non tri-band) stock rooted rom will be able to use their phone on T-Mobile or another GSM carrier?
Click to expand...
Click to collapse
you would fist have to unlock your phone the regular way like over here before you have updated your rom/firmware/kernel. to OD2.
and then you will have to update the modem to the one i uploaded to remain unlocked after updating to OD2.
Probably should include all those type details in your OP.
jstntp said:
Probably should include all those type details in your OP.
Click to expand...
Click to collapse
if you read my op, you would then know that i stated, after i updated i got an "invalid sim error". That would suggest that i had previously been unlocked, and that after updated it was locked again.
I assume that anyone reading my post would understand that, because he or she had the same issue and knows how to unlock a Samsung SPH-L720 running MDC,MDL,MF9,NAE,NG2.
Alright....... but again, just to clarify, you modded the modem.bin file yourself?
That's the info I'm trying to get out of you....... what is it that you changed in that .bin file to get unlock to work on OD2?
I know that the NON-HLOS.bin file wasn't changed at all from the stock version.
jstntp said:
Alright....... but again, just to clarify, you modded the modem.bin file yourself?
That's the info I'm trying to get out of you....... what is it that you changed in that .bin file to get unlock to work on OD2?
I know that the NON-HLOS.bin file wasn't changed at all from the stock version.
Click to expand...
Click to collapse
If you observe his video, he is combining NG2 modem.bin with OD2 NON-HLOS.bin. Now, I don't know what function each of those bins do, but I am pretty sure that OD2 'modem.bin' is what you need in order to have OD2 baseband, right?
mastmaker said:
If you observe his video, he is combining NG2 modem.bin with OD2 NON-HLOS.bin. Now, I don't know what function each of those bins do, but I am pretty sure that OD2 'modem.bin' is what you need in order to have OD2 baseband, right?
Click to expand...
Click to collapse
Oh now that's funny! I did not catch that because I didn't watch it all that close.
So...... NO..... he did not modify any modem.bin file...... he is just using a the NG2 radio and calling it OD2!
I think we are done here.
Well, has anyone with domestic unlock on NG2 try his file on OD2 and retain domestic unlock?
Sent from my Nexus 5 using Tapatalk
OD2 domestic unlock
optimummind said:
Well, has anyone with domestic unlock on NG2 try his file on OD2 and retain domestic unlock?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did try. No, it doesn't retain domestic unlock. It says 'invalid SIM'. Fortunately, I could flash NG2 back and all is well.
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
steam374 said:
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
Click to expand...
Click to collapse
What is required for root work?
Root adds a binary file and some scripts to the /system partition
What happens when you flash a system.img?
Everything in the /system partition is wiped and replaced with the contents of the system.img
So, basically as long as I flash super su in twrp I'll be good to go?
steam374 said:
So, basically as long as I flash super su in twrp I'll be good to go?
Click to expand...
Click to collapse
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
danarama said:
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
Click to expand...
Click to collapse
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
steam374 said:
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
Click to expand...
Click to collapse
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
danarama said:
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
Click to expand...
Click to collapse
Okay! Thank you very much! This is the help I needed.
steam374 said:
Okay! Thank you very much! This is the help I needed.
Click to expand...
Click to collapse
No probs
danarama said:
No probs
Click to expand...
Click to collapse
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
steam374 said:
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
Click to expand...
Click to collapse
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
danarama said:
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
Click to expand...
Click to collapse
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
steam374 said:
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
Click to expand...
Click to collapse
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
danarama said:
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
Click to expand...
Click to collapse
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
steam374 said:
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
Click to expand...
Click to collapse
Hey, don't worry. We prefer "noob" questions to "noob-help-me-i-screwed-up" requests
I went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.
Before I start, I apologize and I know this shouldn't be in the Q&A Thread but I am a new user and unable to post it in the other thread
So I recently purchased a Galaxy S10 from Best Buy and I noticed I didn't have Advanced Call features such as Wifi-Calling and Video Calling. When I had asked about this, it turns out that I had purchased the unlocked S10 and had them set it up with my provider as Verizon.
I have been reading some posts by iBowToAndroid and I am wondering if I would be able to flash my phone into being locked with Verizon and get the Advanced Calling features without losing anything on my phone currently.
I already have the G973U firmware files from iBowToAndroid's post as well as the Verizon USERDATA file. I also tried setting up Samsung USB Drivers but the install failed. I'm not sure if this is necessary as I am still very new to this whole thing.
If this is possible, what version of Odin should I be downloading?
Is there anything else that I would need?
I'm using v3.13.3 and it's working perfectly fine.
romcio47 said:
I'm using v3.13.3 and it's working perfectly fine.
Click to expand...
Click to collapse
I've always used that same version and the patched one.
Sent from my LM-V405 using Tapatalk
romcio47 said:
I'm using v3.13.3 and it's working perfectly fine.
Click to expand...
Click to collapse
I've been trying to use that as well but it fails every time before it is able to download anything.
Not sure if I am doing something wrong but I have all the files necessary for it
CosmicNinja said:
I've been trying to use that as well but it fails every time before it is able to download anything.
Not sure if I am doing something wrong but I have all the files necessary for it
Click to expand...
Click to collapse
I had this happen as well...then got a firmware image (from sammobile) with a later date than the firmware that was on my phone already. Flashing that newer firmware image was successful the first time through. Although in my case I was flashing back from T-Mobile firmware to unlocked firmware, same idea. I think that it might have been related to needing a newer boot version or something, but until I got the later version of unlocked firmware, the flash would fail reliably at abl.elf, before it got rolling.
And the version of Odin that worked for me was the patched Odin3_v3.13.1_3B. Didn't try the unpatched version.