hello please help me i need this programe this programe is only in phone please upload for me this programm my phone is bricked and need flash
https://www.verizonwireless.com/support/knowledge-base-116950/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You opened 2 topics. I answered in another one. Anyway here is the link for program www.motorola.com/verizonsoftwareupdatewin.
Thank you but this program is not the same
This programe cant to repair my phone this programe only install update if not update available so this program cant help me
Please sameone upload this program from the phone
From what I'm seeing, the repair program you linked IS the one for the DTurbo, so I'm not sure what you're looking for. Go download it from the link you provided, and use it.
If you want more advanced repair processes, you're probably looking for RSD flashing using Motorola's RSDLite software. You'll need an RSD-compatible image to flash (you can't use a TWRP or such image). As far as I know, there is no RSD image for the latest Marshmallow release, so you'll probably have to try the older LP version and see if you can apply that. Eg, see this page for info on how to use RSD: https://www.andromods.com/unroot-lo...-moto-droid-turbo-restore-unroot-unbrick.html
The software upgrade assistant can do the full firmware, but currently only the lollipop full firmware is available. When Verizon adds the marshmallow firmware, it will do that as well. Just not available yet.
BBB
Red Knot
Sent from my XT1254 using Tapatalk
realbbb said:
The software upgrade assistant can do the full firmware, but currently only the lollipop full firmware is available. When Verizon adds the marshmallow firmware, it will do that as well. Just not available yet.
BBB
Red Knot
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Doesn anybode know how long does it take usually for vzw to push new firmware out? Is there any way to rush it?
Having it as backup would be great, because I know I'll brick it sooner or later xD
hamza_iraki said:
hello please help me i need this programe this programe is only in phone please upload for me this programm my phone is bricked and need flash
https://www.verizonwireless.com/support/knowledge-base-116950/
Click to expand...
Click to collapse
schwinn8 said:
From what I'm seeing, the repair program you linked IS the one for the Droid Turbo, so I'm not sure what you're looking for. Go download it from the link you provided, and use it.
Click to expand...
Click to collapse
Yes, very strange. He provides a LINK to the software and says he needs a link to the software. There's even a choice of Windows or Mac downloads on that very page!
realbbb said:
The software upgrade assistant can do the full firmware, but currently only the lollipop full firmware is available. When Verizon adds the marshmallow firmware, it will do that as well. Just not available yet.
BBB
Red Knot
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Right. Unless your XT1254 bootloader is unlocked Verizon still owns your phone.(Even for those who are not Verizon customers, but are just using the Droid Turbo on other networks.) And they laugh at you.
please help i need this programe
hamza_iraki said:
please help i need this programe
Click to expand...
Click to collapse
You provided the download link yourself. That webpage link has the downloads for both Windows and Mac. Do you not see my screenshots? That arrow is point to the DOWNLOAD LINKS on the web page YOU posted.
Plus, someone already posted the exact download URL, even though it's from the page YOU gave.
Ej?iSixo said:
You opened 2 topics. I answered in another one. Anyway here is the link for program www.motorola.com/verizonsoftwareupdatewin.
Click to expand...
Click to collapse
See? Click that link, and it that program will automatically start downloading.
But that's not going to help you with locked bootloader to reinstall 6.0.1 until Verizon releases full firmware.
Always, always unlock your bootloader before installing any new firmware like this or you may never be able to do it. Plus, if something screws up, with an unlocked bootloader you have more options to fix it than with a locked bootloader.
Thank you sir i download this programe but is not same i can only with this programe upgrade the problem my phone have latest version so i cant upgrade again
Please you can tell option to fix my phone
Thank you
hamza_iraki said:
Thank you sir i download this programe but is not same i can only with this programe upgrade the problem my phone have latest version so i cant upgrade again
Please you can tell option to fix my phone
Thank you
Click to expand...
Click to collapse
This isn't the software (Windows version), here at this link?
http://www.motorola.com/VerizonSoftwareUpdateWin
The problem is you have taken the 6.0.1 OTA on a locked bootloader and Verizon has NOT yet released the full firmware version. You cannot use this tool until they do. See this quote from the Software Upgrade Assistant website?
The most recent software version (full firmware) will be available on the SUA/SRA tool within a week of a new software update. During this time, the SUA/SRA is unavailable for usage.
Click to expand...
Click to collapse
Obviously, it's been well over a week since 6.0.1 was released for the Droid Turbo -- but Verizon doesn't care. If they did, they wouldn't demand Motorola keep the bootloader locked in the first place! Motorola give free bootloader unlock codes for all the other Quarks (XT1250, XT1225). Only Verizon demands locked down bootloader for their variant. And then they have this OTA repair software which doesn't work unless they provide the full firmware to go along with it.
I'm sorry Verizon still controls your phone. With an unlocked bootloader we could help you. Right now you have to wait until Verizon posts the full firmware.
He can try using the repair function with the software
ChazzMatt said:
This isn't the software (Windows version), here at this link?
http://www.motorola.com/VerizonSoftwareUpdateWin
The problem is you have taken the 6.0.1 OTA on a locked bootloader and Verizon has NOT yet released the full firmware version. You cannot use this tool until they do. See this quote from the Software Upgrade Assistant website?
Obviously, it's been well over a week since 6.0.1 was released for the Droid Turbo -- but Verizon doesn't care. If they did, they wouldn't demand Motorola keep the bootloader locked in the first place! Motorola give free bootloader unlock codes for all the other Quarks (XT1250, XT1225). Only Verizon demands locked down bootloader for their variant. And then they have this OTA repair software which doesn't work unless they provide the full firmware to go along with it.
I'm sorry Verizon still controls your phone. With an unlocked bootloader we could help you. Right now you have to wait until Verizon posts the full firmware.
Click to expand...
Click to collapse
Interesting.. When did MM OTA started rolling out approximately?
I tried software myself and there indeed isn't option for "repair" , it simply says phone is up to date. Maybe it has to be on older ver SW or when they release firmware more options will pop out..
From this quote it seems to me that even when full firmware gets out it will only be available through SUA/SRA until somebody doen't extract it somehow.
Or VZW has place where it publishes firmwares?
I'm getting deeper with my downgrading experiment and it's just a matter of time when I'll brick phone.
koftheworld said:
He can try using the repair function with the software
Click to expand...
Click to collapse
He can TRY, but it won't work. Until Verizon realists releases the full firmware. I sound like a parrot, I keep repeating the same answer over and over. I'm sorry people don't like the answer.
It really depends on what exactly he did and what is wrong. Most likely he will need the full firmware, but that is exactly why I stated TRY. I appreciate that you are on here a lot answering questions, but please keep the snark down.
koftheworld said:
It really depends on what exactly he did and what is wrong. Most likely he will need the full firmware, but that is exactly why I stated TRY. I appreciate that you are on here a lot answering questions, but please keep the snark down.
Click to expand...
Click to collapse
Read my post with the quote directly from Motorola and Verizon and I clearly explained why it will NOT work right now, and exactly when it would start working.
Also, we know exactly what he did. He has a locked bootloader with 6.0.1 and tried downgrading via ADB to Lollipop. He's screwed up his phone and he also bought a phone with a "locked Google account". Ignoring the fact the phone may be "lost" or stolen, we are still trying to help him.
He's posting in two different threads about the same thing and we've been trying to help him -- but at this point he can only wait for the full firmware:
hamza_iraki said:
hello please help me i have phone xt1254 but not worked i need flash my phone with fastboot but the problem my bootloader is locked
please this my informations about my phone . i can flash my phone without unlock bootloader?
Click to expand...
Click to collapse
hamza_iraki said:
first i buy this phone locked with google account access and after i try to flash my phone with other firmware with fastboot mode
now my phone is bricked i can only enter to recovery and fastboot
please samone give me rom for adb flash i need original firmware
Click to expand...
Click to collapse
hamza_iraki said:
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
Click to expand...
Click to collapse
ChazzMatt said:
Read my post with the quote directly from Motorola and Verizon and I clearly explained why it will NOT work right now, and when it would start working.
Click to expand...
Click to collapse
I understand completely, and I'm saying that if the repair option is available he can try it. I'm going to to be so glad to not have this phone anymore so that I don't have to read your posts.
koftheworld said:
It really depends on what exactly he did and what is wrong.
Click to expand...
Click to collapse
We know exactly what he did. It's not a mystery. But besides him...
Most of these people bricking their phones on the 6.0.1 OTA are installing the OTA, then either
1) trying to install the OTA file again to "fix" something or
2) trying to downgrade back to Lollipop.
See this thread from a week ago for examples of both. I could show you even more if you wish. Like here:
babalovemaker said:
i updated twice and now holding a bricked driod turbo with bootloader locked. no back and no solution to downgrade or install yet
Click to expand...
Click to collapse
(If they had UNLOCKED bootloaders with TWRP installed, we could help them.)
Or third cause of bricking is ...
3) trying to install OTA on an encrypted phone.
Initially, encrypted phones couldn't handle the 6.0.1 OTA. Verizon paused the 6.0.1 OTA rollout for a few days, told people with bricked phones to send them in for replacement, and then resumed the OTA rollout -- without ever confirming they fixed the issue.
For the first two points, you can't reinstall OTA update again on a locked bootloader as it's basically only a partial firmware file which looks for the previous Lollipop firmware.
You also can't downgrade from Marshmallow back to Lollipop on a Droid Turbo locked bootloader.
Even if the cause was neither of those two scenarios -- or the encryption problem, it doesn't matter. Regrettably, his phone is a brick until Verizon decides to release the full firmware. Then he and others can use the Repair Assistant or flash via RSD. That's been said time and time and time again.
Or unless some dev comes up with some magic?
This situation has been going on for for WEEKS, in various threads with several people. Maybe you haven't kept up?
I feel very sorry for him, but there's nothing we can do.
Here's what he says the reason is:
hamza_iraki said:
hello please help me i have phone xt1254 but not worked i need flash my phone with fastboot but the problem my bootloader is locked
please this my informations about my phone . i can flash my phone without unlock bootloader?
Click to expand...
Click to collapse
hamza_iraki said:
first i buy this phone locked with google account access and after i try to flash my phone with other firmware with fastboot mode
now my phone is bricked i can only enter to recovery and fastboot
please samone give me rom for adb flash i need original firmware
Click to expand...
Click to collapse
hamza_iraki said:
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
Click to expand...
Click to collapse
And THAT has not been released yet. OK? This has already been discussed many, many, many times over the past few weeks. New people coming in with this problem are not aware and we are having to give them the bad news.
It's Verizon's fault for not making the full firmware available.
---------- Post added at 07:05 PM ---------- Previous post was at 06:55 PM ----------
koftheworld said:
I'm going to to be so glad to not have this phone anymore so that I don't have to read your posts.
Click to expand...
Click to collapse
Look, I don't know everything. I'm not a dev. But I try to help people and I have helped lots of people. I do tons of research for my answers or it's based on hard won experience.
If I don't know an answer, I'm not going to pull one out of thin air. My answers are based on facts or personal experience.
I'm the one two years ago who pointed out the XT1250 = XT1254 (same radio bands, same FCC ID)when Verizon Droid Turbo owners didn't even know about that or even wanted to admit it -- and Verizon was lying through their teeth they had a worldwide exclusive, when they didn't even have a U.S. exclusive. I proved it to all the naysayers. I knew this because of my research/knowledge of the U.S. cell phone industry.
I'm the one who found the XT1225 had LTE band 5 (which AT&T uses) and HSPA band IV (which T-mobile uses) by doing modem software scan when Motorola didn't want to initially admit it. They left those bands off the official specs for some reason. (I know why, but too long a story for here.)
If I do answer and I even post direct links to manufacturer/carrier statements (research), and then someone else comes along right behind me and says the exact opposite -- then yes I will probably point out that is not correct answer.
But I'm always glad to help.
The reason for the confusion is that the GUI of the update assistant has been redesigned and it no longer looks like the screenshots that were provided in the OP. However, it still performs the same functions as the old version.
Related
I'm not really sure what I'm doing, I changed my country code from "demo" to eu and I'm on EVA-L09C432B182. There's so many different versions and I don't know which is good or even compatible. What would be the next thing you guys would do in order to get the most from my phone?
Edit - I just jumped in at the deep end and everything wen't well, I'm now on Nougat with emui 5.0, if you're in the same boat as I was, I used the Huawei Update in the second post of this thread: https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754"]https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754
worked a bloomin treat for me!
C900 country demo ?
Thorpy4p said:
I'm not really sure what I'm doing, I changed my country code from "demo" to eu and I'm on EVA-L09C432B182. There's so many different versions and I don't know which is good or even compatible. What would be the next thing you guys would do in order to get the most from my phone?
Edit - I just jumped in at the deep end and everything wen't well, I'm now on Nougat with emui 5.0, if you're in the same boat as I was, I used the Huawei Update in the second post of this thread: https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754"]https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754
worked a bloomin treat for me!
Click to expand...
Click to collapse
I have an eva-L09 with C900B190 and have country "demo" ??
I read a lot of posts how to get from the C900B190 to a Rom that has ota updates.
Before I start and because I am a bit of a noob I want to be absolutely sure I get all steps correct...please help me out and confirm/correct this
1) set develloper usb debugging
2) make sure phone connects to pc
3) install latest twrp
4) unlock boot loader with tool (https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358)
5) make note of unlock code
6) use twrp to flash B136 (still have to find zip)
do I get ota to android 7 or I have to flash latest Rom meself (what is the best version for eva-L09?)
After that can I lock the boot loader and stay on android 7 or will the phone reset with locking and revert to android 6 again?
Thanks for helping
Contacted huawei, they were very helpful I will probably go to the service center to hopefully reset my phone to receive updates.
I also asked for an unlock code in case I need a plan B.
djaccob said:
Contacted huawei, they were very helpful I will probably go to the service center to hopefully reset my phone to receive updates.
I also asked for an unlock code in case I need a plan B.
Click to expand...
Click to collapse
Seems I have no warranty (I got the phone from a friend and have no papers or anything) and have to pay for service centre. So I will try unlocking myself...
If anyone can help me out with all the steps in the right order I would be very grateful.
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.
Real appreciated, will keep you updated, if anything works ill post it here.
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536
Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?
mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu
mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.
mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo
TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards
ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
One thing I wanna ask everyone here: Amazon also sells the 6GB int'l version (H9493) of the XZ3 for cheaper than the U.S. one, and this site seems to confirm that it not only has all the exact same bands one would need for T-Mobile (2, 4, and 12) and prob AT&T too, but also VoLTE. It's also a Dual SIM version too, though I would only ever use one SIM card.
But if the bands are all the same ones we use in the U.S., would we need to flash it with the U.S. software??
RockStar2005 said:
One thing I wanna ask everyone here: Amazon also sells the 6GB int'l version (H9493) of the XZ3 for cheaper than the U.S. one, and this site seems to confirm that it not only has all the exact same bands one would need for T-Mobile (2, 4, and 12) and prob AT&T too, but also VoLTE. It's also a Dual SIM version too, though I would only ever use one SIM card.
But if the bands are all the same ones we use in the U.S., would we need to flash it with the U.S. software??
Click to expand...
Click to collapse
If US software is not needed, that's is perfect. Anyone can confirm please?
tiunilohmu said:
If US software is not needed, that's is perfect. Anyone can confirm please?
Click to expand...
Click to collapse
I'm not saying I know for sure, but it APPEARS that all the models, or at least the single SIM H8416 and the dual SIM H9493 (both are sold on U.S. Amazon) have the same radio bands. The H8416 that I got off Amazon was supposed to be the "U.S. version" (with warranty), but when I got it, despite the LTE reception status being int'l and not U.S. in terms of looks (4G shows as LTE, 4G LTE shows as LTE+), VoLTE still works, and I definitely am getting all the T-Mobile bands at least (2, 4, and 12). So that is why I'm asking this? It APPEARS that all the models of the XZ3 have the same radio bands again, so yeah.
RockStar2005 said:
I'm not saying I know for sure, but it APPEARS that all the models, or at least the single SIM H8416 and the dual SIM H9493 (both are sold on U.S. Amazon) have the same radio bands. The H8416 that I got off Amazon was supposed to be the "U.S. version" (with warranty), but when I got it, despite the LTE reception status being int'l and not U.S. in terms of looks (4G shows as LTE, 4G LTE shows as LTE+), VoLTE still works, and I definitely am getting all the T-Mobile bands at least (2, 4, and 12). So that is why I'm asking this? It APPEARS that all the models of the XZ3 have the same radio bands again, so yeah.
Click to expand...
Click to collapse
Thanks for your info. Have you tried yours with at&t?
YW!
I haven't, but I started this thread which discusses both AT&T and T-Mobile and the XZ3. I suggest you check it out! Though it mainly looks at the single SIM H8416 version.
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
I have this model on AT&T but haven't flashed the US firmware. VoLTE is not available on the Taiwan firmware.
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
I don't think you can flash it. The H9493 is a dual sim model (please correct if I'm wrong), and on Xperifirm there is no Customized US version for it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And since it's a dual sim model, and you try flashing a single sim one, you won't be able to obviously use your 2nd sim. If that's not an issue for you, then I guess you can try it.
iArvee said:
I don't think you can flash it. The H9493 is a dual sim model (please correct if I'm wrong), and on Xperifirm there is no Customized US version for it.
And since it's a dual sim model, and you try flashing a single sim one, you won't be able to obviously use your 2nd sim. If that's not an issue for you, then I guess you can try it.
Click to expand...
Click to collapse
Very interesting!!
Yeah that's the thing, I could care less about using a 2nd SIM. I only need 1 and of course MicroSD card.
So you think it would work then, even though it's a Dual SIM phone?
RockStar2005 said:
Very interesting!!
Yeah that's the thing, I could care less about using a 2nd SIM. I only need 1 and of course MicroSD card.
So you think it would work then, even though it's a Dual SIM phone?
Click to expand...
Click to collapse
I read threads on the XZP forum about people flashing the single sim firmware on their dual sim phone. What I've gained from that is the phone will still work, minus the functionality for the 2nd sim, since the modem configs are different. I haven't tried it myself, don't see any harm in trying it anyway.
iArvee said:
I read threads on the XZP forum about people flashing the single sim firmware on their dual sim phone. What I've gained from that is the phone will still work, minus the functionality for the 2nd sim, since the modem configs are different. I haven't tried it myself, don't see any harm in trying it anyway.
Click to expand...
Click to collapse
Ok great! You da MAN iArvee! LOL :good:
Can you explain the process of flashing? How difficult is it? Does it involve rooting or unlocking bootloaders?? God I hope not. lol
I don't have an issue with Sony Companion as I've used it before though. But I'll admit I'm intimidated by anything complicated. I once unlocked the bootloader, rooted, and S-OFF'd my old HTC One M8. It wasn't fun. LOL
RockStar2005 said:
Ok great! You da MAN iArvee! LOL :good:
Can you explain the process of flashing? How difficult is it? Does it involve rooting or unlocking bootloaders?? God I hope not. lol
I don't have an issue with Sony Companion as I've used it before though. But I'll admit I'm intimidated by anything complicated. I once unlocked the bootloader, rooted, and S-OFF'd my old HTC One M8. It wasn't fun. LOL
Click to expand...
Click to collapse
It's fairly simple compared to other OEMs. You don't need to unlock the bootloader nor need root. It's as easy as downloading the firmware, repacking it, then flashing it. The easiest way to flash is using Flashtool, however I don't think that flashtool has been updated yet to support the XZ3.
There is another way using newflasher, no need to repack the firmware. Just place the .exe file in the folder of the downloaded firmware and flash. While it's the same as Flashtool, I prefer flashtool because there are settings you can change (if you want).
iArvee said:
It's fairly simple compared to other OEMs. You don't need to unlock the bootloader nor need root. It's as easy as downloading the firmware, repacking it, then flashing it. The easiest way to flash is using Flashtool, however I don't think that flashtool has been updated yet to support the XZ3.
There is another way using newflasher, no need to repack the firmware. Just place the .exe file in the folder of the downloaded firmware and flash. While it's the same as Flashtool, I prefer flashtool because there are settings you can change (if you want).
Click to expand...
Click to collapse
Ok. That doesn't sound too bad then. And AWESOME on no bootloader or root stuff! lol
But how did you do it then if Flashtool (which I HAVE heard of) doesn't support the XZ3 then?
Ok let's just say I use newflasher. That sounds MUCH easier! lol I'm assuming it's good then for the XZ3 right? Also, what's the link for the U.S. firmware please?
So I connect my phone to my PC.........put the downloaded firmware "folder" into say the root directory of my Xperia, then put in newsflasher.exe into that folder, and double-click on it (exe)? This is what the instructions here on XDA say to do. But it also (Step 2) says something about putting my phone into "flash mode"? WTF is that? lol Do I have to do that? If so, how??
Well, what settings does Flashtool allow you to change? I just wanna see if it's worth it to deal with it if I don't have to. lol
Thanks!!!!!!!
RockStar2005 said:
Ok. That doesn't sound too bad then. And AWESOME on no bootloader or root stuff! lol
But how did you do it then if Flashtool (which I HAVE heard of) doesn't support the XZ3 then?
Ok let's just say I use newflasher. That sounds MUCH easier! lol I'm assuming it's good then for the XZ3 right? Also, what's the link for the U.S. firmware please?
So I connect my phone to my PC.........put the downloaded firmware "folder" into say the root directory of my Xperia, then put in newsflasher.exe into that folder, and double-click on it (exe)? This is what the instructions here on XDA say to do. But it also (Step 2) says something about putting my phone into "flash mode"? WTF is that? lol Do I have to do that? If so, how??
Well, what settings does Flashtool allow you to change? I just wanna see if it's worth it to deal with it if I don't have to. lol
Thanks!!!!!!!
Click to expand...
Click to collapse
I used newflasher.
That's the wrong link for flashtool. Here's the correct one: https://forum.xda-developers.com/showthread.php?t=920746
You can download the firmware using a software called Xperifirm. The settings that Flashtool allows you to change is keep userdata, basically just flash the firmware but leave your installed apps, documents, whatever is on the internal storage intact (and more settings, but that's basically the gist of the settings). You can do that also using newflasher, however since there's no settings menu, you have to just not include a few files.
Flash mode is done by turning your phone off, then holding volume down while plugging your phone in to the PC. Once the notification LED turns green, that means it's in flash mode.
iArvee said:
I used newflasher.
That's the wrong link for flashtool. Here's the correct one: https://forum.xda-developers.com/showthread.php?t=920746
You can download the firmware using a software called Xperifirm. The settings that Flashtool allows you to change is keep userdata, basically just flash the firmware but leave your installed apps, documents, whatever is on the internal storage intact (and more settings, but that's basically the gist of the settings). You can do that also using newflasher, however since there's no settings menu, you have to just not include a few files.
Flash mode is done by turning your phone off, then holding volume down while plugging your phone in to the PC. Once the notification LED turns green, that means it's in flash mode.
Click to expand...
Click to collapse
Oh ok. Then I will use Newsflasher too! No repacking?? I'm IN!! LOL
Yeah I just had a random site for Flashtool bookmarked from a while ago. I'll remove it.
Ahh I see. Well I'd rather just do a clean flash. Less chance of issues. lol
Ok so using PC I download U.S. H9493 firmware folder (please confirm that is best site), and yes I know to find H9493 firmware now, and Newsflasher. Put Newsflasher.exe file INTO the firmware folder, then connect phone (turned off) to my PC via USB WHILE pressing the volume DOWN button until the green notification LED light on my XZ3 turns on. Then let it flash by double-clicking newsflasher.exe, and then after it's done, check log file for any errors, then unplug phone and start it up! And then finally put it through Sony Companion ("Software Repair") ftw for extra assurance. Sounds right??
Will Sony Companion know or detect the U.S. firmware? If I do a software repair, will it vary how it does that by model, or is the process the same for all models? I know you did it but you did it on the U.S. H8416 version. Do I have anything to worry about there? I'm guessing no since all the radio bands & VoLTE option are in all 3 models. But let me know if you think I should skip this or just do it.
RockStar2005 said:
Oh ok. Then I will use Newsflasher too! No repacking?? I'm IN!! LOL
Yeah I just had a random site for Flashtool bookmarked from a while ago. I'll remove it.
Ahh I see. Well I'd rather just do a clean flash. Less chance of issues. lol
Ok so using PC I download U.S. H9493 firmware folder (please confirm that is best site), and yes I know to find H9493 firmware now, and Newsflasher. Put Newsflasher.exe file INTO the firmware folder, then connect phone (turned off) to my PC via USB WHILE pressing the volume DOWN button until the green notification LED light on my XZ3 turns on. Then let it flash by double-clicking newsflasher.exe, and then after it's done, check log file for any errors, then unplug phone and start it up! And then finally put it through Sony Companion ("Software Repair") ftw for extra assurance. Sounds right??
Will Sony Companion know or detect the U.S. firmware? If I do a software repair, will it vary how it does that by model, or is the process the same for all models? I know you did it but you did it on the U.S. H8416 version. Do I have anything to worry about there? I'm guessing no since all the radio bands & VoLTE option are in all 3 models. But let me know if you think I should skip this or just do it.
Click to expand...
Click to collapse
Basically just leave everything in if you'll do a clean flash.
Download the one from XDA: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Sounds right! Just make sure you install the XZ3 drivers. Google Xperia XZ3 drivers. Should be a sony developer link. Yes, Xperia Companion will know what firmware you are on. When you do a software repair, it will just redownload and reflash whatever firmware is on your phone. However, if you flash the single sim version, I'm not sure if that will work on Xperia Companion. Again, you can try!
I'd just do it. It's really hard to brick Xperia phones. If you do something wrong, you can always just reflash again. But don't take my word for it. I've been rooting, flashing, created some mods, and have a lot of experience with Xperia phones since 2014. I'm just speaking from experience.
iArvee said:
Basically just leave everything in if you'll do a clean flash.
Download the one from XDA: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Sounds right! Just make sure you install the XZ3 drivers. Google Xperia XZ3 drivers. Should be a sony developer link. Yes, Xperia Companion will know what firmware you are on. When you do a software repair, it will just redownload and reflash whatever firmware is on your phone. However, if you flash the single sim version, I'm not sure if that will work on Xperia Companion. Again, you can try!
I'd just do it. It's really hard to brick Xperia phones. If you do something wrong, you can always just reflash again. But don't take my word for it. I've been rooting, flashing, created some mods, and have a lot of experience with Xperia phones since 2014. I'm just speaking from experience.
Click to expand...
Click to collapse
Ok I'll use your link. It looks exactly the same as what I got but no big deal. lol
Ok I found this for the drivers. Approve? But wait, when do I install them? lol That was never mentioned. So it's an additional step?
Ok. Well I'd be flashing the Dual H9493 version, not single, so it should be fine, right?
Yes I'll just reflash if not working right after completing the flashing process.
Thanks for all that!
RockStar2005 said:
Ok I'll use your link. It looks exactly the same as what I got but no big deal. lol
Ok I found this for the drivers. Approve? But wait, when do I install them? lol That was never mentioned. So it's an additional step?
Ok. Well I'd be flashing the Dual H9493 version, not single, so it should be fine, right?
Yes I'll just reflash if not working right after completing the flashing process.
Thanks for all that!
Click to expand...
Click to collapse
The drivers aren't automatically installed (well the right ones anyway) so it's best to install them yourself. Download the ZIP (yes thats the correct link), extract the zip, right click on the INF file, then click install.
Yep, should be fine.
iArvee said:
The drivers aren't automatically installed (well the right ones anyway) so it's best to install them yourself. Download the ZIP (yes thats the correct link), extract the zip, right click on the INF file, then click install.
Yep, should be fine.
Click to expand...
Click to collapse
So I would do that AFTER completing the flashing process and Companion part too?
Ok thanks!
RockStar2005 said:
So I would do that AFTER completing the flashing process and Companion part too?
Ok thanks!
Click to expand...
Click to collapse
Are you flashing the H9493?
Please let us know how it goes. If possible test out at&t too.
I recently bought what was supposed to be a "NEW Unlocked" Note 8 from seller on Ebay and when it arrived, I noticed that it was a few updates behind so I connected it to my WiFi and attempted to update it, but I received this error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I contacted the seller, but they were not helpful at all, so I installed the Phone INFO ★SAM★ app by vndnguyen to research the issue myself. The information the app provided was really confusing to say the least. First of all, the phones settings menu shows that the phones model number is SM-950U (US Market).
The model number provided by app however is SM-9500 (Chinese / Hong Kong Market)
Adding to that confusion, the phone seems to have both US and Chinese firmware components installed on it as shown by the following screenshot:
The CSC codes all seem to point to the phone originally being created for the Hong Kong market as shown in this screenshot:
However, when I checked the phones IMEI number, it comes back that it was originally a T-Mobile phone. Maybe that was just the last carrier that the IMEI was registered to I am not 100% certain about this, but there is definitely something very odd about this phone and so my questions are:
1.) Is there anyway (without tearing the phone apart) to tell exactly what model this phone is (950U or 9500) ?
2.) Why would anyone alter the phone like this / what advantages are there to doing this ?
3.) Is there anyway to actually update this device ?
mtcellph said:
3.) Is there anyway to actually update this device ?
Click to expand...
Click to collapse
You could update it with odin. It looks like the update center downloaded the wrong update.
SnowFuhrer said:
You could update it with odin. It looks like the update center downloaded the wrong update.
Click to expand...
Click to collapse
Thanks for the reply, but I do not think this was done by a bad OTA update or anything like that. I think this was done intentionally because I bought a different Note 8 about a month ago from a different seller and it had this same issue so I think this is done on purpose. What that purpose is I am not sure about yet, but I hope someone can help answer that question. As far as using ODIN to update is concerned I first have to figure out what the real model of the phone is so I can flash the right firmware, but thanks again for the reply.
mtcellph said:
Thanks for the reply, but I do not think this was done by a bad OTA update or anything like that. I think this was done intentionally because I bought a different Note 8 about a month ago from a different seller and it had this same issue so I think this is done on purpose. What that purpose is I am not sure about yet, but I hope someone can help answer that question. As far as using ODIN to update is concerned I first have to figure out what the real model of the phone is so I can flash the right firmware, but thanks again for the reply.
Click to expand...
Click to collapse
I'm more worried about that phone being a knock-off fake! If it really was N950U it would absolutely not be able to have that firmware on it that's currently on it. Also if you try to install the real firmware it's more than likely going to brick it especially if it's fake because that firmware is just not right. I would immediately send it back and get your money back!!
MrMike2182 said:
I'm more worried about that phone being a knock-off fake! If it really was N950U it would absolutely not be able to have that firmware on it that's currently on it. Also if you try to install the real firmware it's more than likely going to brick it especially if it's fake because that firmware is just not right. I would immediately send it back and get your money back!!
Click to expand...
Click to collapse
I doubt it's fake, just had some alterations on it. @mtcellph to see the model of the phone, boot into download mode. It should say.
--
@MrMike2182
I already got a refund from Ebay and they told me to keep the phone too so I am not worried about bricking it or anything like that.
@SnowFuhrer
This is the information from my Download Mode screen:
It shows the Carrier as TMB (T-Mobile) which would in theory be a SM-N950U model device, but I hoping more for an actual model number so I could be sure. Any other way to get a more definite answer would be welcome.
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
UnBeATaBLe~PrO said:
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
Click to expand...
Click to collapse
You might be right, but I would still like to update it if possible because everything else works on the phone.
Again if anyone has any sort of advice on figuring this mystery out, I would love to hear it.
UnBeATaBLe~PrO said:
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
Click to expand...
Click to collapse
I seen devices sold like this with the exact same setup. Usually done by third party refurbishers.
iceepyon said:
I seen devices sold like this with the exact same setup. Usually done by third party refurbishers.
Click to expand...
Click to collapse
So what is the use of it?
SnowFuhrer said:
So what is the use of it?
Click to expand...
Click to collapse
Most 3rd party device repair specialist would use working parts from similar devices to make a new device and sell it on for a profit.
The Phone INFO app did say it was a refurb which is the reason why Ebay let me keep it, but the mystery still remains. Is it a N9500 with N950U parts in it or vise versa?
Is there any sort of app / software that will work on a 9500 that will not work on a 950U? I did see the thread about unlocking using an app named 835crom.apk that will unlock the BL of a N9500 model, but apparently will just crash when ran on a N950U model, but it's from like 2017 and I am not trying to root or anything like that.
I simply want to update to the latest security patch available for the phone, but I first need to find out what firmware I need to flash to do that. Again any help in this are would be really appreciated.
From what I know the majority of the components used in the Note 8 are interchanged able with the exception of the SOC, motherboards and modems. While both the N9500 and the N950U run on the same SOC, they do not utilize the same modems. Which maybe what is causing your issue.
mtcellph said:
The Phone INFO app did say it was a refurb which is the reason why Ebay let me keep it, but the mystery still remains. Is it a N9500 with N950U parts in it or vise versa?
Is there any sort of app / software that will work on a 9500 that will not work on a 950U? I did see the thread about unlocking using an app named 835crom.apk that will unlock the BL of a N9500 model, but apparently will just crash when ran on a N950U model, but it's from like 2017 and I am not trying to root or anything like that.
I simply want to update to the latest security patch available for the phone, but I first need to find out what firmware I need to flash to do that. Again any help in this are would be really appreciated.
Click to expand...
Click to collapse
I really wouldn't flash anything to it period! Simply because you can't flash one hardware piece with the N9500 and then try to flash the N950U hardware piece because it doesn't work like that! If anything is going to work it would most likely be the unlocked N950U1 firmware but I would tread cautiously because if your modem needs N9500 and your board/CPU needs N950U it's just going to mess it up!
Edit: Also about wanting to update just for the security patch, it's highly unlikely that you'll EVER be the target of such security breaches.. Ask around, if you're not rooted it's seriously HIGHLY UNLIKELY!
If you knew what you were doing, you could flash the modem from one firmware and flash the rest from the motherboard model.
SnowFuhrer said:
If you knew what you were doing, you could flash the modem from one firmware and flash the rest from the motherboard model.
Click to expand...
Click to collapse
Yeah. But you would have to be extremely skilled in doing so.
Thanks for the replies and I don't really understand why this would be that complicated. It's obviously possible to mix & match the firmware on the phone and it still work (minus the non-updating issue) because that is how it is now, but from what everyone is saying it's a lot more difficult then just flashing the right firmware in ODIN, but I do not understand why and would appreciate some clarification on this.
If the hardware on both models is basically exactly the same thing with the exception of the modem and the current modem that is installed is from the US version, would I not just be able to flash the full US firmware using ODIN and call it a day? If not, why?
Right now the Baseband (modem) and Bootloader are both from the US model. The CSC (which could easily be changed later if I wanted / needed to do that) & PDA (which is basically just the android OS stuff) are from the Chinese model. I am far from an expert in this area but it seems that the PDA is the only thing that I would need to change or am I missing something ?
Finally, I should have included that the reason I NEED to get the security patch updated on the phone is because the firmware (CSC & PDA) that is installed on the phone now does not have VOLTE enabled/working on it and in a later security patch it does have it enabled/working & since I would be using the phone on the Verizon network I kind of have to have VOLTE or the phone will not work once they turn off 2G/3G in the near future.
mtcellph said:
Thanks for the replies and I don't really understand why this would be that complicated. It's obviously possible to mix & match the firmware on the phone and it still work (minus the non-updating issue) because that is how it is now, but from what everyone is saying it's a lot more difficult then just flashing the right firmware in ODIN, but I do not understand why and would appreciate some clarification on this.
If the hardware on both models is basically exactly the same thing with the exception of the modem and the current modem that is installed is from the US version, would I not just be able to flash the full US firmware using ODIN and call it a day? If not, why?
Right now the Baseband (modem) and Bootloader are both from the US model. The CSC (which could easily be changed later if I wanted / needed to do that) & PDA (which is basically just the android OS stuff) are from the Chinese model. I am far from an expert in this area but it seems that the PDA is the only thing that I would need to change or am I missing something ?
Finally, I should have included that the reason I NEED to get the security patch updated on the phone is because the firmware (CSC & PDA) that is installed on the phone now does not have VOLTE enabled/working on it and in a later security patch it does have it enabled/working & since I would be using the phone on the Verizon network I kind of have to have VOLTE or the phone will not work once they turn off 2G/3G in the near future.
Click to expand...
Click to collapse
I think it would work with an AP partition(pda) flash. It only flashes system, recovery and boot partitions.
SnowFuhrer said:
I think it would work with an AP partition(pda) flash. It only flashes system, recovery and boot partitions.
Click to expand...
Click to collapse
Thanks for the reply & I think so as well because I am just updating the version that is already flashed on the phone and the PDA is what contains the Android security updates I need if I not mistaken.
This seems like it would be a fairly trivial process, but other users have stated it's more difficult than it seems so I'm curious why they have come to that conclusion.
I think I'll give it a few more days to see if anyone else responds before moving forward just to be on the safe side.
Here's a free How-To on how i successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022 that was carrier locked to Verizon and now fully Unlocked.
DISCLAIMER:
*This does NOT trip Knox or Void your warranty and does NOT require a root or a paid service. **This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.***This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
You can read more on how this method works to force a carrier update to your device, here, on the Official Android dev site.
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here, Stock Firmware and ODIN Flashing Guide (XDA) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•(Optional?) Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process. Link: Android Dev Platform Tools (Official)
Step 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
NOTE:
It Is CRITICAL that we flash the U1 rom BEFORE putting in the desired carriers SIM, then reboot, let phone fully boot, ONLY THEN should we insert the desired carriers SIM.
Step 1b:
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE.
IMPORTANT! MAKE SURE YOU DOWNLOAD BOTH THE "U" ROM FOR THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED (XAA) ROM/Firmware.
IF YOU ALREADY HAVE U1 FIRMWARE
I.e "SM-G998U1xxxxxxx" - you can skip to step 2, but I would recommend reading through the next part.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm the device is now showing the "U1_XAA" in the Service Provider Software Version - it should say something like "SM-G998U1_XAA blah blah blah" - you just want to see the "U1" bit.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device.
! CRITICALLY IMPORTANT STEP !
We will now initiate a reboot, but BEFORE the device fully restarts, we need to force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold them directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery, please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select & Execute.
AGAIN, Very Important step! We MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, we need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in, essentially it should remain plugged in throughout this process.
We should now be back in download mode and be on "U1" as we have verified in the steps above.
STEP 3:
Now it's time to flash the ROM/Firmware from the carrier you wish to use. Make SURE you have the SIM from the same carrier inserted during this process as mentioned at the beginning. It doesn't need to be a working or activated SIM, just simply one from the carrier you wish to have this S21 work on.
Flash all items from the "U" ROM/Firmware as you did earlier, ensuring to use the "U" ROM/Firmware for your desired carrier as described above. Same deal with CSC here, DO NOT use the "Home_CSC", use the other.
BE SURE that you use the USERDATA file that comes with the "U" ROM/Firmware. Its Critical in order to get the phone working properly on the new carrier.
Start the Odin flashing process & wait.
Phone will Auto-Reboot.....
Done!
You should now be on the carrier you wish to use.
This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung.
Please comment your experiences/ issues etc below. Don't be afraid to ask for clarity of something.
PoC, results after doing above process pictured in this screenshot.
Good luck.
-k0mrade
Send me Crypto if I helped?
Before process, this message would appear shortly after inserting a new SIM in testing devices:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After preforming above procedures I now find pictured below by running this activity:
com.samsung.ssu.unlock.MainActivity
And verify twice by checking my work in Settings>About>Software Information> Service Provider Software Version & Carrier Configuration Version.
For anyone whos still having trouble, try following the directions on this thread. Maybe they explain it a bit better or their process omits/includes parts ive missed.
Alternative Guide To Carrier Unlocking S21
Good Luck.
-
Have you attempted this on lower bootloader revisions?
iBowToAndroid said:
Have you attempted this on lower bootloader revisions?
Click to expand...
Click to collapse
I have not. But am very interested to see how it goes if you or anyone decides to give it a shot, it SHOULD work on any BL considering the method of attack. But I can't verify it does.
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason CCT remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
xDpakaX said:
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason XAS remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
Click to expand...
Click to collapse
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
What's the Baseband Version?
iBowToAndroid said:
What's the Baseband Version?
Click to expand...
Click to collapse
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
iBowToAndroid said:
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
Click to expand...
Click to collapse
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Yep then you're screwed. It can't done if Knox is tripped
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Is it still unlocked and rooted? That would make life another easier. We can repair the IMEI, baseband etc. It's worth a go if the phones just a paper weight right now imo. But ultimately up to you.
K0mraid3 said:
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Click to expand...
Click to collapse
Thank you! I'll give it a try and report how it goes.
Good luck! Worst case, look up a program called "Samsung TFT Module", just be sure to scan it for viruses and bad code if you have the ability.unless you are able to find the 2022 update of it, you'll have to settle for whatever version is available. It'll likely be old, clunky and out-of-date, half the program defunct, but a few key parts still work, and quite well. Don't forget ADB drivers. Let us know how it goes!
Proverbs2 said:
Thank you! I'll give it a try and report how it goes.
Click to expand...
Click to collapse
Ok, I tried to follow each step carefully, but I had to make one minor change to the procedure: after flashing the U1_XAA firmware, I had to power off the phone in order to insert the SIM card. (In the XCover Pro, the SIM card slot is obstructed by the battery, so there is no way to insert the card without powering off the phone and removing the battery.) After inserting the card, I booted directly into recovery and followed the other steps from there.
Unfortunately, it didn't work for me: the phone is still locked, showing the same message: "Sorry, your device can't be activated on another carrier's network..." Perhaps that's because I wasn't able to perform that one critical step, inserting the sim card while the phone is turned on. Any suggestions for a workaround?
K0mraid3 said:
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Click to expand...
Click to collapse
Yes, I followed the guide. The problem is that when I'm on U1 my phone doesn't ask me to reboot.
Hello. I did all on VZW SQU3AUDB phone. Did all steps.
I have question. But in first start after step 3 (i flash G998U VZW) i see: Sorry, your devic.... verizon message
STEP3: Now it's time to flash the ROM/Firmware from the carrier you wish to use
It min - i need to flash not VZW ROM? some other? I need to use Ukrainia operator sim. Or i need flash G998W or else?
can someone help me?
Does my bootloader need to be unlocked