A205u bootloader unlock, twrp and root - Samsung Galaxy A20 Guides, News, & Discussion

*****I am not responsible for anything you do to your device. Do this at own risk***** If all goes bad just flash Factory firmware with PIT file.
Credit goes to those who built twrp.img and the vbmeta image for the A30/A70. I am no dev, I read somewhere about the crossflash to DS firmware but cannot find it any more.
This is for people who understand Odin and have some experience flashing firmware.
Maybe someone will make noob friendly instructions, please feel free.
I currently have an a205u with an unlocked bootloader root and twrp.
1. Using Patched odin crossflash to DS firmware. OEM toggle-download mode-unlock bootloader.
2. You are now able to flash back to the W/U firmware keeping an unlocked Bootloader even though you will not see an oem toggle in developer options
3. Patch boot with magisk 8.02 compress it to tar file along with A30 vbmeta.
***** Important***** make sure to use 7zZ for all steps, and rename boot from magisk_patched_image to boot.img or you will receive errors.
( I may have used a70 vbmeta as I was trying various ideas someone will have to try this and let us know) It will hang at samsung logo for a while on first boot.
4. Then flash A30 TWRP using flashify. Probably works with odin too. Boot to recovery- Perform format data, reboot recovery, flash dmverity+magisk. May be able to get it to work in less steps that's just what I did to make it work.
Link containing vbmeta , magisk patched boot Patched odin . Bootloader 4
First time flashing I got a pass in Odin and fail on phone Flash the second time everything was good
https://drive.google.com/file/d/1F_Bjv8YzPqJLk4YqbXLjYamlPgIZ3nGN/view?usp=drivesdk

Drop that DS firmware.

Johnmoerike said:
*****I am not responsible for anything you do to your device. Do this at own risk***** If all goes bad just flash Factory firmware with PIT file.
Credit goes to those who built twrp.img and the vbmeta image for the A30/A70. I am no dev, I read somewhere about the crossflash to DS firmware but cannot find it any more.
This is for people who understand Odin and have some experience flashing firmware.
Maybe someone will make noob friendly instructions, please feel free.
I currently have an a205u with an unlocked bootloader root and twrp.
1. Using Patched odin crossflash to DS firmware. OEM toggle-download mode-unlock bootloader.
2. You are now able to flash back to the W/U firmware keeping an unlocked Bootloader even though you will not see an oem toggle in developer options
3. Patch boot with magisk 8.02 compress it to tar file along with A30 vbmeta.
***** Important***** make sure to use 7zZ for all steps, and rename boot from magisk_patched_image to boot.img or you will receive errors.
( I may have used a70 vbmeta as I was trying various ideas someone will have to try this and let us know) It will hang at samsung logo for a while on first boot.
4. Then flash A30 TWRP using flashify. Probably works with odin too. Boot to recovery- Perform format data, reboot recovery, flash dmverity+magisk. May be able to get it to work in less steps that's just what I did to make it work.
Click to expand...
Click to collapse
You have the only A205U in existence that is rooted.
Congratulations
Could you please change the title to A205U so others can find it

https://linksharing.samsungcloud.com/jQ6RcTYUMPxR
ninjasinabag said:
Drop that DS firmware.
Click to expand...
Click to collapse
I do not have the DS firmware, I did the unlock months ago then proceeded to break my phone screen. I just replaced it and came to xda to find custom roms. Thought this method would have been old news. Try flashing F firmware as they are identical processors. LINK TO PROOF ABOVE

physwizz said:
You have the only A205U in existence that is rooted.
Congratulations
Could you please change the title to A205U so others can find it
Click to expand...
Click to collapse
So you know what he means by ds firmware?

ninjasinabag said:
So you know what he means by ds firmware?
Click to expand...
Click to collapse
No.
I will try yo find out

DS could mean Dual Sim in firmware , Like mine is and SM-A205F/DS.
It is dual sim. @physwizz @ninjasinabag

physwizz said:
No.
I will try yo find out
Click to expand...
Click to collapse
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
KineSight said:
DS could mean Dual Sim in firmware , Like mine is and SM-A205F/DS.
It is dual sim. @physwizz @ninjasinabag
Click to expand...
Click to collapse
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.

ninjasinabag said:
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
Click to expand...
Click to collapse
Awesome, glad I could be of help. @ninjasinabag

ninjasinabag said:
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
Click to expand...
Click to collapse
So you're going to do it?

physwizz said:
So you're going to do it?
Click to expand...
Click to collapse
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today

ninjasinabag said:
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
Click to expand...
Click to collapse
Good Luck

Re:
Omg I've been waiting almost 2 years for this metropcs a205U to be rooted can you please PM me if mine can be rooted and sent me the Odin and combination firmware so I can root mine to PLEASE bro this phone is complete ass with so many Samsung restrictions please let this be real!!

your instructions are completely vauge with no links and no clarification between which vbmeta to flash and your picture shows your on A205W VLU 4BTE3 which is a Canada variant of the phone..gah this is just too complicated for me can someone please reiterate with a proper guide to root a205U (metropcs)

Johnmoerike said:
https://linksharing.samsungcloud.com/jQ6RcTYUMPxR
I do not have the DS firmware, I did the unlock months ago then proceeded to break my phone screen. I just replaced it and came to xda to find custom roms. Thought this method would have been old news. Try flashing F firmware as they are identical processors. LINK TO PROOF ABOVE
Click to expand...
Click to collapse
Can you please post odin, vbmeta, patched boot.img ?

physwizz said:
Can you please post odin, vbmeta, patched boot.img ?
Click to expand...
Click to collapse
Its added to the first post, sorry I would wasn't able to be more clear. I unlocked the bootloader couple months ago, not realizing that I was the only one to have done so. If I can be of any more help let me know

Johnmoerike said:
Its added to the first post, sorry I would wasn't able to be more clear. I unlocked the bootloader couple months ago, not realizing that I was the only one to have done so. If I can be of any more help let me know
Click to expand...
Click to collapse
Thanks.
There are a lot of people who are waiting to root their a205U.
---------- Post added at 11:39 PM ---------- Previous post was at 11:21 PM ----------
ninjasinabag said:
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
Click to expand...
Click to collapse
Tar and odin in post 1

The firmware I downloaded was a205fn. That's the answer let me know how it goes

Johnmoerike said:
The firmware I downloaded was a205fn. That's the answer let me know how it goes
Click to expand...
Click to collapse
Thanks

physwizz said:
Thanks
Click to expand...
Click to collapse
Any progress in the a205u root?

Related

OTA for 4.4.4

nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
I am unlocked and rooted but the download from verizon automatically started. It did nothing after it was done downloading. I dont know what to expect of this?? I am on viper rom 2.5.
Here's the link folks
https://www.androidfilehost.com/?fid=95747613655049317
Only for stock recovery and untouched system users
dottat said:
Here's the link folks
https://www.androidfilehost.com/?fid=95747613655049317
Only for stock recovery and untouched system users
Click to expand...
Click to collapse
Hey dottat what is the correct directory that the file gets saved to on the phone?
lucky_strike33 said:
I am unlocked and rooted but the download from verizon automatically started. It did nothing after it was done downloading. I dont know what to expect of this?? I am on viper rom 2.5.
Click to expand...
Click to collapse
Won't flash if you have custom recovery or modified system.
krazie1 said:
Hey dottat what is the correct directory that the file gets saved to on the phone?
Click to expand...
Click to collapse
/cache/fumo
dottat said:
Won't flash if you have custom recovery or modified system.
Click to expand...
Click to collapse
Thank you!
Sent from my HTC6525LVW using XDA Premium HD app
Is there a full change log somewhere?
all good here, just reflashed @dottats RUU and updated the organic way. SOFF is good, it even says official in the software status in HBOOT
hboot- 3.19.0.0000
radio- 1.09.20.0926
dsp - v46.2.2-00564-m8974_F0.0811
os- 3.28.605.4
dottat said:
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
Click to expand...
Click to collapse
Ready for that RUU.... It saved me 1,000 million times...
JB_Da_Greatest said:
Ready for that RUU.... It saved me 1,000 million times...
Click to expand...
Click to collapse
You can just use the 4.4.3 ruu and do the OTA, then your firmware is done all in 1 shot
can someone upload a 4.4.4 system dump? or point me to one if someone has already? thanks!
I have looked around and found all kinds of different answers so can someone here help me out a bit?
I got the phone when it first came out, have S-OFF, root, TWRP custom recovery but have version 4.4.2 still installed with everything being left pretty much stock. I would prefer to keep things pretty much stock so what would I need to do to update to 4.4.4? Do I need to get 4.4.3 first? Do I need to flash stock recovery first before doing anything? Anything with firmware or radios?
Resputan said:
I have looked around and found all kinds of different answers so can someone here help me out a bit?
I got the phone when it first came out, have S-OFF, root, TWRP custom recovery but have version 4.4.2 still installed with everything being left pretty much stock. I would prefer to keep things pretty much stock so what would I need to do to update to 4.4.4? Do I need to get 4.4.3 first? Do I need to flash stock recovery first before doing anything? Anything with firmware or radios?
Click to expand...
Click to collapse
well, this is my idea for you
1. Flash the stock 4.4.2 recovery over the TWRP, then just do the OTA's
aer0zer0 said:
well, this is my idea for you
1. Flash the stock 4.4.2 recovery over the TWRP, then just do the OTA's
Click to expand...
Click to collapse
Reasonable enough, sorry if this is another dumb question but I havent been paying much attention to these boards since I rooted, I see that recent phones require Sunshine to root, is that because of the firewater method being patched via a software update (4.4.3?) or some other manufacturer change that I shouldnt be concerned with if the old root method already works for me?
aer0zer0 said:
You can just use the 4.4.3 ruu and do the OTA, then your firmware is done all in 1 shot
Click to expand...
Click to collapse
I already updated... I was just saying for safe keeping just in case I get in some unforseen trouble.
Go here http://forum.xda-developers.com/showthread.php?t=2723159 and just flash the 4.4.3 with not boot img. YOu dont need to flash the recovery to accept ota's. YOu can just flash this and you will get the updated radios and h boot.http://forum.xda-developers.com/showthread.php?t=2723159
Downloaded OTA and updated, they added file manager and flashlight back ~!
JB_Da_Greatest said:
I already updated... I was just saying for safe keeping just in case I get in some unforseen trouble.
Click to expand...
Click to collapse
yup, its saved a billion times too
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
lchupacabras said:
Downloaded OTA and updated, they added file manager and flashlight back ~!
Click to expand...
Click to collapse
i know, right that was such an awesome surprise
---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------
Resputan said:
Reasonable enough, sorry if this is another dumb question but I havent been paying much attention to these boards since I rooted, I see that recent phones require Sunshine to root, is that because of the firewater method being patched via a software update (4.4.3?) or some other manufacturer change that I shouldnt be concerned with if the old root method already works for me?
Click to expand...
Click to collapse
nope, if your already SOFF, you will stay SOFF. might break your root, but all you need to do is reinstall supersu when you put twrp back on
dottat said:
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
Click to expand...
Click to collapse
Hi dootat, Hope you remember me. You help me restore my mobile Via team viewer. Thanks for the RUU i am trying to flash but nothing going. Copy zip to SD card rename to 0p6bimg.zip and hit Hboot. i can see it installing and then ask for reboot but when check in mobile still 4.4.3. Any help?
thanks
Best regards

OTA Update

I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
you can remove mcafee after the update.
Can anyone upload ota?
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse
tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.

New Update - QF2

According to the Verizon Galaxy S5 Update Page:
Android® security patches and bug fixes.
Resolved a ring-back tone issue on calls to non-Verizon phones.
Fixed an issue where some users reported difficulty making calls to non-Verizon customers.
Click to expand...
Click to collapse
The security patch included is (most likely) the July one, since Samsung also just released a new software update to international models which includes the July security patch and Verizon has been updating the "Galaxy S" series phones with the July update over the past few weeks.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME_No_Aboot.tar.md5.zip
Appreciate that, but how do you get the Odin firmware file out of curiosity?
drewcu said:
Appreciate that, but how do you get the Odin firmware file out of curiosity?
Click to expand...
Click to collapse
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
drewcu said:
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
Click to expand...
Click to collapse
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Dudash said:
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Click to expand...
Click to collapse
Is this flashable with Odin only or possibly need to already be on a specific kernal? I have tried on two S5900V's through TWRP and both result in a failure message. Both are on jkruse de-bloated MM rom at the moment.
Kaliaila said:
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
Click to expand...
Click to collapse
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Odd. It works for me.
Sent from my SM-G900V using Tapatalk
Since no one wanted to chime in and help me out in my post, you need to unzip the file and load the md5 into Odin's AP slot and flash it. Then let the phone do its thing and flash the latest TWRP with odin after. Then go back into TWRP and flash supersu to gain root again. Trying to flash right within TWRP is not an option, not sure why its not explained.
So this update wont "factory reset" my device?
AWESOME1092387456 said:
So this update wont "factory reset" my device?
Click to expand...
Click to collapse
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
stuck on Verizon boot screen
After the update via OTA, my aunt's phone has been stuck on Verizon boot screen. Tried booting into safe mode, with same result. Any ideas on how not to lose all her data? Thanks!
This sucks I wanna download this so bad but my computer is down smdh is it possible someone can make and ota update zip file for me so can flash this through stock recovery on my phone ?
Sent from my SM-G900V using Tapatalk
I guess no one knows how to do it huh smdh
Sent from my SM-G900V using Tapatalk
Rumsfield said:
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
Click to expand...
Click to collapse
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
mastertech007 said:
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
Click to expand...
Click to collapse
I always flash super su and whatever else I need in recovery after I've flashed the rom so I cant give you a definitive answer. Both phones did upgrade without data loss and now advanced calling/wifi calling actually work now which is why I flashed in the first place.
Working?
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
JasonD1180 said:
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
Click to expand...
Click to collapse
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
JasonD1180 said:
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
Click to expand...
Click to collapse
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Rumsfield said:
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Click to expand...
Click to collapse
Ive not had twrp or root on this device but it went from saying vzw official binary to samsung original. Will i be able to root as long as twrp flashes?

Flash back to stock T-mobile ROM but keep root?

Rooted and running international firmware, can't seem to find the US t-mobile ROM file though, Sorry if this has been asked before, i just need to be pointed in the right direction.
ripgut said:
Rooted and running international firmware, can't seem to find the US t-mobile ROM file though, Sorry if this has been asked before, i just need to be pointed in the right direction.
Click to expand...
Click to collapse
You cannot be rooted on T-Mobile FW.
what I did with my 6t was flashed the stock TMobile boot image, flashed twrp, rebooted recovery, flashed magisk then factory reset... not sure if it'll work for the 7 pro I may try it though
I don't see why you can't perform this.
GuestK00279 said:
what I did with my 6t was flashed the stock TMobile boot image, flashed twrp, rebooted recovery, flashed magisk then factory reset... not sure if it'll work for the 7 pro I may try it though
Click to expand...
Click to collapse
Can I use fastboot to get back to Tmobile stock?
https://forum.xda-developers.com/on...le-stock-o-t4027825/post81354727#post81354727
There is an entire thread with different releases of the MSM tool. Search in Google 'msm tool OnePlus 7 pro'
---------- Post added at 11:00 PM ---------- Previous post was at 10:56 PM ----------
csmooth2001 said:
Can I use fastboot to get back to Tmobile stock?
https://forum.xda-developers.com/on...le-stock-o-t4027825/post81354727#post81354727
Click to expand...
Click to collapse
Use the T-Mobile msm tool

Categories

Resources