Related
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this
Hi all,
I am a newbie and don't know much. So please bear with me.
I was trying to root my Galaxy S5(SM-G900H) by using the tutorial given on http://forum.xda-developers.com/showthread.php?t=2696537 but the process did not go as planned as keep struck on recovery.img on odin3.10 so I googled and found that changing USB port will help so I take out the battery changed the port and try again but this time I soft-bricked the phone as odin struck on cache.img and now when i try to start my phone I get Firmware upgrade encountered. So now I again googled and found about unified toolkit and install it on my windows 10 ,now when i choose option 6 (i.e. flash stock boot image to your device) it says waiting for usb debugging to be enabled ,now I remember I turn USB debugging on but it is still struck here. Now what should I do? My parents gave this phone just a week ago and I am in deep trouble.
P.S.-I am only able go into the download mode not recovery mode.
Boot into Download Mode and use Odin to install the original firmware. Might require a factory reset after if still bootlooping. Here is a link to 6.0.1 from Sri Lanka https://mega.nz/#!YMAFhR4a!pZmf7OEWgzDzET1FLGsAOQ5XyVlvE8y4pJfB8KDNbMI . Any region firmware should work for the F model. If you want your specific one then check sammobile.com. I just linked to the other because it is a much faster download.
Problem encountred while installing original firmware
I tried to use Odin to install original firmware , I started the process but Odin got struck on sboot.bin (Also I read somewhere that whole process does not take more than 10 minutes). So please help me.
Which firmware did you try?
You might be able to use Kies to recover your device as well.
es0tericcha0s said:
Which firmware did you try?
You might be able to use Kies to recover your device as well.
Click to expand...
Click to collapse
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
ratcoder said:
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
Click to expand...
Click to collapse
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
es0tericcha0s said:
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
Click to expand...
Click to collapse
Well I downloaded another one from http://firmwarefile.com/samsung-sm-g900h the second one, before it all started I was on 5.0 and the link you give does not work anymore. Anyway I tried with the firmware with upper link. And Odin is struck with sboot.bin for more than an hour. And have no idea what's going on? So what should I do?
Also someone suggested to use Pit. Should I use it?
No, don't use the pit. Try the newer firmware for 6.0
es0tericcha0s said:
No, don't use the pit. Try the newer firmware for 6.0
Click to expand...
Click to collapse
So I downloaded the 3rd link from http://firmwarefile.com/samsung-sm-g900h for newer version and try Odin 11.2 with it. I try two times to flash the firmware first time it struck on sboot.bin and second time it just showed fails(I used Odin with administrative rights this time) .Please see the attached images. Please tell me what should I do now. I want to repair it ASAP.
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
es0tericcha0s said:
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
Click to expand...
Click to collapse
I think I should mention that the firmware I used was INS not INU and if you have a genuine link for version 6 for INU with fast download speed, please share it (different than sammobile because it has only fast speed only for premium users). Should I use PIT or try something else than Odin. Anything that might help please tell me. I have got this phone just a week ago and my parents are not gonna give me a new one so please help me.
I keep encountering sboot.bin error ,maybe there is a way to resolve it?
I'd just try to load TWRP and a custom rom at this point.
es0tericcha0s said:
I'd just try to load TWRP and a custom rom at this point.
Click to expand...
Click to collapse
Actually I have no idea what TWRP is so any link or anything that can help without ruining the situtation.
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
es0tericcha0s said:
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
Click to expand...
Click to collapse
I want to know one more thing on the above link there is a custom firmware and there is a custom ROM with bootloader and all. So should I flash custom firmware or use the instructions given on thread to flash custom ROM?
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
es0tericcha0s said:
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
Click to expand...
Click to collapse
Finally seen some progress, thank you very much. I successfully flashed TWRP recovery, but I got a couple of questions. Firstly I should flash ROM from recovery mode and then go to download mode to flash boot-loader and Modem files right? Should I flash ROM from SD card? And if this custom ROM causes problem is there a way to get to stock ROM? And is this custom ROM rooted or I have to root it via CF-Auto root or try anything else?
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
es0tericcha0s said:
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
Click to expand...
Click to collapse
Thank you very much.phone is working again with custom ROM.just one more thing if I upgrade from custom ROM what will happen?
:good::highfive::victory:
It should work to reflash the original firmware through Odin. Just get the one that matches your baseband version.
You may need to use Odin3_v3.12_PrinceComsy
- G930UUEU4BQD2_G930UOYM4BQD2_ATT.zip
Thanks a bunch! I've been trying to download it with no success
Thank you. Time to tinker again...haha
Yeah I'm gonna get this rooted and hopefully get some performance back after UPDATE: i rooted successfully but after i tried to fix the fingerprint sensor issue my phone would only boot to recovery and download mode so i flashed to stock
It turns out that when I flashed those files it kept trying to activate my phone on the sprint network instead of att and also it made my settings go wonky so I'm downloading the u firmware with the att product code again because it messed it all up
Just a heads up, I was unable to get the EngBoot Kernel working on this ROM. It would reboot on its own every 2-3 minutes. I spent about 6 hours on this until I gave up and flashed the ATT ROM and then EngBoot. That worked just fine (except for the performance issues).
fatbas202 said:
Just a heads up, I was unable to get the EngBoot Kernel working on this ROM. It would reboot on its own every 2-3 minutes. I spent about 6 hours on this until I gave up and flashed the ATT ROM and then EngBoot. That worked just fine (except for the performance issues).
Click to expand...
Click to collapse
Can you link to ATT Nougat EngBoot rom? I wanted to upgrade to Nougat, wipe, and then get Nougat EngBoot rom on their, but I don't want to use Sprint or whatever that other carrier was. (Prefer to use ATT on ATT devices, ya know?)
Hey I finally was able to get my phone working right I forgot to flash the csc
loganbeck14 said:
Hey I finally was able to get my phone working right I forgot to flash the csc
Click to expand...
Click to collapse
Glad to hear it.
muniz_ri said:
Glad to hear it.
Click to expand...
Click to collapse
Hey can you get the usc product code version for me I have tried to download that specific version but it always corrupts itself and i could only use this version but I had my phone unlocked which means I need a different version so that I can detect my sim card and hopefully set the apn settings acordingly
loganbeck14 said:
Hey can you get the usc product code version for me I have tried to download that specific version but it always corrupts itself and i could only use this version but I had my phone unlocked which means I need a different version so that I can detect my sim card and hopefully set the apn settings acordingly
Click to expand...
Click to collapse
I will try to download it from Sammobile at some point but they seem to be doing maitenance on the site this weekend.
Ok I just want to make sure I'm not going crazy over this so thanks
If I'm using a G930T but using Cricket at my carrier should I flash this or.the TMO variant that you posted in the T-Mobile S7 forum?
A0425A said:
If I'm using a G930T but using Cricket at my carrier should I flash this or.the TMO variant that you posted in the T-Mobile S7 forum?
Click to expand...
Click to collapse
I don't know if it will make any difference but I would try the t-mo version to match your device.
Help!!! I went ahead and flashed the TMO version of the 930u code. I downloaded the ZIP. Placed all the right files in the correct place in Odin (comsey odin) and finished the process. The phone didn't reboot even though reboot was checked. Now I'm in a boot loop. Help!!
Update:. For it to work after flashing a second time. Not sure what happened the first time.
Sent from my Nexus 7 using Tapatalk
Hey guys,
Bought the galaxy s8 plus from a store thinking it was factory unlocked version directly from samsung, but it wasnt. Its the unlocked sprint version based on the radio, and it had a tmobile app or two already installed. I am using AT&T and would like to change the carrier to at&t so that I can get a few features for at&t (Mainly being able to send mms while on wifi). I updated to the latest online update (which im guessing i shouldnt have) and i would like to know if its possible to easily change the carrier still, and or if i can downgrade safely to change the carrier. If so, what files are the latest that I can get the ball rolling with? Using the AT&T version is completely fine.
I came across this youtube video that shows how to easily change carrier without flashing: https://www.youtube.com/watch?v=msAHhCVF-F8
Basically i am a bit lost and would like to know if anyone can help at this point. Here are my software information:
Bootloader Version: G955USQU1AQGL
Build number NRD90M.G955USQU1AQGL
Active CSC Code: XAS
Please advise, thanks guys!
jxs714 said:
Hey guys,
Bought the galaxy s8 plus from a store thinking it was factory unlocked version directly from samsung, but it wasnt. Its the unlocked sprint version based on the radio, and it had a tmobile app or two already installed. I am using AT&T and would like to change the carrier to at&t so that I can get a few features for at&t (Mainly being able to send mms while on wifi). I updated to the latest online update (which im guessing i shouldnt have) and i would like to know if its possible to easily change the carrier still, and or if i can downgrade safely to change the carrier. If so, what files are the latest that I can get the ball rolling with? Using the AT&T version is completely fine.
I came across this youtube video that shows how to easily change carrier without flashing: https://www.youtube.com/watch?v=msAHhCVF-F8
Basically i am a bit lost and would like to know if anyone can help at this point. Here are my software information:
Bootloader Version: G955USQU1AQGL
Build number NRD90M.G955USQU1AQGL
Active CSC Code: XAS
Please advise, thanks guys!
Click to expand...
Click to collapse
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
kleen3r said:
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
Click to expand...
Click to collapse
Sorry, double post. Final below
kleen3r said:
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
Click to expand...
Click to collapse
Hey my friend,
Thanks so much for reaching back with an update and for the support! Awesome! So, youre 100% sure downgrade procedure wont brick the device? Also, do you know if this will this trip knox? Last question: do you think this will solve the red tint on the edges of the phone? I heard this was supposedly a software issue, not hardware.
jxs714 said:
Hey my friend,
Thanks so much for reaching back with an update and for the support! Awesome! So, youre 100% sure downgrade procedure wont brick the device? Also, do you know if this will this trip knox? Last question: do you think this will solve the red tint on the edges of the phone? I heard this was supposedly a software issue, not hardware.
Click to expand...
Click to collapse
I'm pretty confident downgrading will not brick. It will definitely not trip Knox. Here's is a link someone says they fixed it: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810.
kleen3r said:
I'm pretty confident downgrading will not brick. It will definitely not trip Knox. Here's is a link someone says they fixed it: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810.
Click to expand...
Click to collapse
Hey Kleen3r,
Thanks for the update and support. Looks great. Going to try the downgrade and possibly also the link sent and reach back with an update in a few hours
kleen3r said:
I'm pretty confident downgrading will not brick. It will definitely not trip Knox. Here's is a link someone says they fixed it: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810.
Click to expand...
Click to collapse
kleen3r said:
Goto updato.com to download the latest AT&T stock firmware. Extract and flash the files in Odin. If you flash all the files (AP, BL, CP And CSC) you will wipe everything on the phone so backup first. If you don't want to start over, then just flash CP and CSC.
There are two versions, 955U and 955U1. The U version is carrier specific and will contain their own software bloat. The U1 version is unbranded so no carrier bloat.
If you need more details, search for carrier switch.
Edit: Here is the link: https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473.
Click to expand...
Click to collapse
Ok, so I tried it and with the unbranded XAA version and I am getting a "FAIL! Model dismatch fail" in odin. Even tried renaming files to tar and removing md5 at the end.
I also noticed that when in download mode, there are no green words going across the screen like I see in youtube videos who get it after they connect it. Could it be i do not have specific drivers installed? I installed the samsung usb drivers.
EDIT: Scratch that, the odin PrinceComsy version (Has to have the banner at the top) seems to be working fine. I am currently flashing
jxs714 said:
Ok, so I tried it and with the unbranded XAA version and I am getting a "FAIL! Model dismatch fail" in odin. Even tried renaming files to tar and removing md5 at the end.
I also noticed that when in download mode, there are no green words going across the screen like I see in youtube videos who get it after they connect it. Could it be i do not have specific drivers installed? I installed the samsung usb drivers.
Click to expand...
Click to collapse
Download quick reboot for your phone and use the app to get into download mode. Make sure you have debug settings turned on in phone. Also check if you can access the phone when its plugged into your computer. If you see it as a drive, then the drivers were installed correctly. If not, uninstall and reinstall.
Edif: Response below
kleen3r said:
Download quick reboot for your phone and use the app to get into download mode. Make sure you have debug settings turned on in phone. Also check if you can access the phone when its plugged into your computer. If you see it as a drive, then the drivers were installed correctly. If not, uninstall and reinstall.
Click to expand...
Click to collapse
Awesome. ok, so i got it to work. But now when i reflash the rom back for sprint, the splash screen is stuck to AT&T and does not remove or go unbranded no matter what i do. It even has bloatware for att when the system starts. I never flashed att rom, only sprint unbranded XAS, not sure how this is happening. How can i get unlocked gsm and cdma back unbranded for sprint? I even formatted everything and flashed the user data, still the same. Its weird
Also, I am flashing it back to return the phone to store the way I received it. This red tint is just unacceptable.
jxs714 said:
Awesome. ok, so i got it to work. But now when i reflash the rom back for sprint, the splash screen is stuck to AT&T and does not remove or go unbranded no matter what i do. It even has bloatware for att when the system starts. I never flashed att rom, only sprint unbranded XAS, not sure how this is happening. How can i get unlocked gsm and cdma back unbranded for sprint? I even formatted everything and flashed the user data, still the same. Its weird
Also, I am flashing it back to return the phone to store the way I received it. This red tint is just unacceptable.
Click to expand...
Click to collapse
You need to flash the XAA not XAS U1 firmware.
kleen3r said:
Download quick reboot for your phone and use the app to get into download mode. Make sure you have debug settings turned on in phone. Also check if you can access the phone when its plugged into your computer. If you see it as a drive, then the drivers were installed correctly. If not, uninstall and reinstall.
Click to expand...
Click to collapse
kleen3r said:
You need to flash the XAA not XAS U1 firmware.
Click to expand...
Click to collapse
Hey man, thanks for the update. So I should flash XAA to change splash screen to samsung and be able to have both sprint cdma and all bands of gsm enabled again?
jxs714 said:
Hey man, thanks for the update. So I should flash XAA to change splash screen to samsung and be able to have both sprint cdma and all bands of gsm enabled again?
Click to expand...
Click to collapse
Yes that firmware is unbranded. The CSC from XAA will automatically detect your carrier's sim and use that network.
kleen3r said:
Yes that firmware is unbranded. The CSC from XAA will automatically detect your carrier's sim and use that network.
Click to expand...
Click to collapse
Hey man,
Thanks for this! Also, do you know if it will allow you to choose cdma as an option as well?
jxs714 said:
Hey man,
Thanks for this! Also, do you know if it will allow you to choose cdma as an option as well?
Click to expand...
Click to collapse
Yes it will.
kleen3r said:
Yes it will.
Click to expand...
Click to collapse
Ok, so just tried it and the sprint CDMA is no longer available in the Mobile Networks menu., only the following:
Mobile Data
International Data Roamin
Disable 2G
Access Point Names
Network Operators (AT&T underneath)
There is no option to choose CDMA like there was before I just firmware changed. The XAS firmware that I had offered the option to choose automatic, LTE/3G, CDMA. Now its gone from the menu after the XAA flash.
jxs714 said:
Ok, so just tried it and the sprint CDMA is no longer available in the Mobile Networks menu., only the following:
Mobile Data
International Data Roamin
Disable 2G
Access Point Names
Network Operators (AT&T underneath)
There is no option to choose CDMA like there was before I just firmware changed. The XAS firmware that I had offered the option to choose automatic, LTE/3G, CDMA. Now its gone from the menu after the XAA flash.
Click to expand...
Click to collapse
I don't understand. Who is your carrier?
---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------
kleen3r said:
I don't understand. Who is your carrier?
Click to expand...
Click to collapse
Edit: Download Shortcut Master and open Preconfig. It will let you pick your carrier.
kleen3r said:
I don't understand. Who is your carrier?
---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------
Edit: Download Shortcut Master and open Preconfig. It will let you pick your carrier.
Click to expand...
Click to collapse
Hey bud,
Thanks for this. My actual carrier is AT&T, but id like to keep the option of having CDMA available if I ever decide to go with sprint. I have the app installed, When i tried to launch Preconfig (com.sec.android.Preconfig.Preconfig) and it gives an error "su: not found"
jxs714 said:
Hey bud,
Thanks for this. My actual carrier is AT&T, but id like to keep the option of having CDMA available if I ever decide to go with sprint. I have the app installed, When i tried to launch Preconfig (com.sec.android.Preconfig.Preconfig) and it gives an error "su: not found"
Click to expand...
Click to collapse
Forgot you have to be rooted use the app. There's an adb command you can use instead. Just do a search in xda for preconfig carrier switch.
I flashed my spring s8 plus with Odin and now I can't get it to read my sim at all ,says will not register on network , where the carrier usually is it says 12345 , I've tried to flash back to stock and nothing works ...im at a loss this is my only phone ,I've tried to do a stock reflash and still nothing , I even did a emergency recovery through smart switch and still ...please help
Is it still possible to go back to an earlier version of Android?
It used to be possible to do so by flashing the bootloader from an earlier version of Android.
A guy called @freeza used to make bootloader packages back in the galaxy note 4 days.
Is it still possible?
i am wondering too...
You can still go back to Android 10 firmware without any special packages. Just use Odin to flash previous firmware.
Samsung did not update the bootloader version with Android 11.
Still on bootloader U1 for Android 10 and 11.
Is there a guide to using Odin to flash previous firmware? I hate Android 11!I woke up this morning to find my tablet had been updated to it and I want to go back to Android 10.
Search for the wanted firmware on this site and read the instructions on the right side of the page
Download Samsung Galaxy Tab S7 Plus SM-T970 XNZ New Zealand T970XXU1BUAA firmware
Fast download latest Samsung Galaxy Tab S7 Plus firmware SM-T970 from New Zealand with T970XXU1BUAA and Android version 11
www.sammobile.com
I have successfully reverted back to android 10 ATK4 using the directions from the Sammobile site linked above, however I got my firmware from Samfw website, much faster download. Quick and easy.
BlackHawkSI said:
I have successfully reverted back to android 10 ATK4 using the directions from the Sammobile site linked above, however I got my firmware from Samfw website, much faster download. Quick and easy.
Click to expand...
Click to collapse
I can confirm. Android 10 (ATJ4) coming from Android 11 with ODIN.
did you unlock bootloader before flahing?
088x880 said:
did you unlock bootloader before flahing?
Click to expand...
Click to collapse
I'm rooted so yes the bootloader is unlocked.
088x880 said:
did you unlock bootloader before flahing?
Click to expand...
Click to collapse
Just a reminder, the bootloader does not need to be unlocked to flash stock firmware.
The only thing you cannot do is flash firmware that has an older bootloader version. Most of the time it will simply fail, but you can soft brick your device as well.
I also managed to install android 10 like you guys, but how do you keep it from updating?
Any ideas?
FYI, didn't root or unlock the bootloader, but it still worked, yay!
Michiel46 said:
I also managed to install android 10 like you guys, but how do you keep it from updating?
Any ideas?
FYI, didn't root or unlock the bootloader, but it still worked, yay!
Click to expand...
Click to collapse
if you root you could use an app to freeze the update service I believe you can. like using titanium backup.
My tablet version is T970OXM2BUC1, is this method impossible anymore?
Even if I try,
sw rev check fail abl fused 2 binary 1 image extract failed
Error was displayed.
Or is it possible if it is rooted?
I want to use wm overscan command...
The screen is too big to play the game comfortably.
It wasn't good that I didn't update often.
If I had updated it a month ago, I should have been able to get back easily...
I'm not good at English, so I'm sorry if the sentences are strange.
having damndest time helping my bro in law try to move his Tab S7 (T870) back from A11 to A10. All attempts have failed. Have tried multiple PC's, multiple USB cables, Multiple versions of the XAR A10 firmware. Have even unlocked OEM bootloader, still same errors in Odin. Have seen others say they can get back from A11 to A10. But for some reason this damn tablet won't work. Beginning to think something with the updates on it have made it incapable of going back to A10. Keep getting SW REV CHECK FAIL: [abl] Fused 2 > Binary 1 error on Download screen on tablet itself. Odin just has failed after it gets to xbl.elf. Thoughts?
opera01 said:
My tablet version is T970OXM2BUC1, is this method impossible anymore?
Even if I try,
sw rev check fail abl fused 2 binary 1 image extract failed
Error was displayed.
Or is it possible if it is rooted?
I want to use wm overscan command...
The screen is too big to play the game comfortably.
It wasn't good that I didn't update often.
If I had updated it a month ago, I should have been able to get back easily...
I'm not good at English, so I'm sorry if the sentences are strange.
Click to expand...
Click to collapse
That's a bootloader 2 image. No going back.
T970OXM2BUC1
drewski83 said:
having damndest time helping my bro in law try to move his Tab S7 (T870) back from A11 to A10. All attempts have failed. Have tried multiple PC's, multiple USB cables, Multiple versions of the XAR A10 firmware. Have even unlocked OEM bootloader, still same errors in Odin. Have seen others say they can get back from A11 to A10. But for some reason this damn tablet won't work. Beginning to think something with the updates on it have made it incapable of going back to A10. Keep getting SW REV CHECK FAIL: [abl] Fused 2 > Binary 1 error on Download screen on tablet itself. Odin just has failed after it gets to xbl.elf. Thoughts?
Click to expand...
Click to collapse
The tablet is already on bootloader 2.
"[abl] Fused 2> Binary 1" is what you get when you try and flash a lower bootloader image.
No going back., even root can't change that.
Well... You can go back from BUAC (I did it) but personally I don't know if you can from beyond that.
So there is no going back for peeps like me who have the following
RP1A.2000720.012.T970XXS2BUC1 ?
samsha said:
So there is no going back for peeps like me who have the following
RP1A.2000720.012.T970XXS2BUC1 ?
Click to expand...
Click to collapse
Nope... you now have a version 2 bootloader.
You can only go forward at this point, or remain where you are.
rjohnstone said:
That's a bootloader 2 image. No going back.
T970OXM2BUC1
The tablet is already on bootloader 2.
"[abl] Fused 2> Binary 1" is what you get when you try and flash a lower bootloader image.
No going back., even root can't change that.
Click to expand...
Click to collapse
well damn that sucks. my bro in law had me convinced he hadn't upgraded it. turned out he had updated it to that newer service update which patched the bootloader. pretty crappy of Samsung to do that, when only trying to flash back to older Android version. I dont care about keeping same bootloader, just want to help him get A10 back on this thing. guess he gonna return it now. lol thanks for the info.