Help with "new" s5 replacement phone - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Recently bought a replaced for my wife's dead s3 with a supposedly new unused non-dev s5. Arrived in perfect physical condition and CID starts with 15 but recovery screen revealed it has been OTA updated to 6.0.1 PF4. Can the bootloader be unlocked or downgraded then unlocked ?

rostar17 said:
Recently bought a replaced for my wife's dead s3 with a supposedly new unused non-dev s5. Arrived in perfect physical condition and CID starts with 15 but recovery screen revealed it has been OTA updated to 6.0.1 PF4. Can the bootloader be unlocked or downgraded then unlocked ?
Click to expand...
Click to collapse
Yes! You can unlock the bootloader. Not problem with your bootloader version. Try this:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529

enmanuel255 said:
Yes! You can unlock the bootloader. Not problem with your bootloader version. Try this:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
I saw that but isn't that just loading roms through safestrap? The bootloader itself remains locked then correct? Also won't safestrap will eat up what little storage she has on a 16g phone (couldn't find 32g).
Thanks

rostar17 said:
I saw that but isn't that just loading roms through safestrap? The bootloader itself remains locked then correct? Also won't safestrap will eat up what little storage she has on a 16g phone (couldn't find 32g).
Thanks
Click to expand...
Click to collapse
People unlock bootloaders for to boot non-native kernels, not to load/flash ROMs.
Safestrap "eats" very little space, 20 MB on /data or so. EMMC partitioning remains the same and you don't really see what's free there on /system.
It's used for unlocking process and there's no need to keep it further in the system.

bbsc said:
People unlock bootloaders for to boot non-native kernels, not to load/flash ROMs.
Safestrap "eats" very little space, 20 MB on /data or so. EMMC partitioning remains the same and you don't really see what's free there on /system.
It's used for unlocking process and there's no need to keep it further in the system.
Click to expand...
Click to collapse
Thanks for clarifying. I have used safestrap before on others phones as a work around for locked bootloader phones. There I was using the ROM slots so of course consuming memory. Does using this method restrict what you can load for kernels and ROMs vs bootloader unlocking in kitkat versions?

rostar17 said:
Thanks for clarifying. I have used safestrap before on others phones as a work around for locked bootloader phones. There I was using the ROM slots so of course consuming memory. Does using this method restrict what you can load for kernels and ROMs vs bootloader unlocking in kitkat versions?
Click to expand...
Click to collapse
ROM slots do not work for SM-G900V.
Everything is simple:
- If your phone has CID15 (check with EMMC Brickbug Check from the Market) then you can unlock it's bootloader and use non-native kernels (say, LOS kernel, TWRP, custom kernels and ROMs that require custom non-Verizon kernels).
- If your phone has CID11 then you cannot unlock the bootloader and you're restricted to native Verizon-Samsung kernels for any Android version. This means no root on 6.0.1 also because you need a modified kernel for to have root on 6.0.1 and above.
That method restricts nothing itself. It's only a modern method of installing a custom ROM and unlocking the bootloader, if possible.
The files like bla-bla-bla-Bootloader_Unlock_AIO.zip usually contain a tool for bootloader unlocking. It's convenient to apply them from Safestrap Recovery.
It's also convenient to flash custom ROMs from Safestrap Recovery.
Safestrup Recovery itself needs root to be installed.
Root itself may be easily gained on Combination 4.4 ROM for any CID.

bbsc said:
ROM slots do not work for SM-G900V.
Everything is simple:
- If your phone has CID15 (check with EMMC Brickbug Check from the Market) then you can unlock it's bootloader and use non-native kernels (say, LOS kernel, TWRP, custom kernels and ROMs that require custom non-Verizon kernels).
- If your phone has CID11 then you cannot unlock the bootloader and you're restricted to native Verizon-Samsung kernels for any Android version. This means no root on 6.0.1 also because you need a modified kernel for to have root on 6.0.1 and above.
That method restricts nothing itself. It's only a modern method of installing a custom ROM and unlocking the bootloader, if possible.
The files like bla-bla-bla-Bootloader_Unlock_AIO.zip usually contain a tool for bootloader unlocking. It's convenient to apply them from Safestrap Recovery.
It's also convenient to flash custom ROMs from Safestrap Recovery.
Safestrup Recovery itself needs root to be installed.
Root itself may be easily gained on Combination 4.4 ROM for any CID.
Click to expand...
Click to collapse
Thanks again for the help. At present there are several posts about unlocking bootloaders and rooting but they are not all up to date and trying to decypher what applies to later verizon (PF4) OTA MM firmware was confusing. I guess I will keep the phone since I can unlock bootloader and load what I want with root. Looking for the unicorn phone (factory new untouched) is elusive to say the least.

Related

[HOW-TO] bootloader unlock 4.67.651.3 OTA

1. Unlocking bootloader via htcdev.com (selecting All Other Supported Models)
2. Flashing recovery via fastboot (./fastboot flash recovery cwm-4.0.1.4-supersonic.img)
3. Reboot recovery and flash latest su.
4. Profit.
PROOF:
Code:
[email protected] ~/evo_s-off $ ./fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
===========bla-bla-bla=============
---checking my e-mail for Unlock_code.bin---
[email protected] ~/evo_s-off $ ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
[email protected] ~/evo_s-off $ ./fastboot flash recovery cwm-4.0.1.4-supersonic.img
sending 'recovery' (3074 KB)... OKAY
writing 'recovery'... OKAY
this is very strange. nobody interested in unlocking bootloader?
there is no official info, but works fine for me.
I'm one of the ones on the newest ota. This helps out a lot, thank you
I already have root, but I am rooting someone else's phone that has new hboot. Thanks!
Sent from my PC36100 using Tapatalk
people with unlocked bootloaders please leave comments here.
Total noob mistake.
OK i ended up updating my evo to the new 4.67.651.3 update. big mistake
I ended up stumbling across this post. (thx wardriva)
I was able to unlock the bootloader and use the ADB method mentioned in this thread to flash recovery.
after looking around I came across brad560's thread and flashed the deodex'ed rom with no problems.
so far everything is working. I also kept looking around and came across the Collection Project (thx Tommytomatoe) and flashed the hot spot hack by SOS. so far its working.
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Thx to all the DEV's.
wardriva said:
this is very strange. nobody interested in unlocking bootloader?
Click to expand...
Click to collapse
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
coldroy said:
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Click to expand...
Click to collapse
you don't need S-OFF with unlocked bootloader. you can flash any rom you want with any kernel you wish. i just checked.
Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
what are you talking about? the latest OTA let us unlock bootloader.
wardriva said:
what are you talking about? the latest OTA let us unlock bootloader.
Click to expand...
Click to collapse
my fault, apologies reading to fast and totally thinking rooting instead unlocking??lol!
hmmm. From the little bit I had read on Evo 3d forum, I thought that even with unlocked bootloader, s-on means no flashing of kernels? Or maybe it's different on 3d cuz it uses EMMC ? Does a custom kernel remain after reboot?
Would love clarification from anyone who knows better than I. Thanks.
Also, this comes just in time for evos EOL status lol. Coincidence ?
Sent from my PC36100 using xda premium
Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?
To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
shortydoggg said:
Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?
Click to expand...
Click to collapse
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.
shortydoggg said:
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.
Click to expand...
Click to collapse
S-ON + Locked means that all partitions(other than data / sdcard) are write protected. The only way to write to the partitions is with an official OTA or RUU signed by HTC. The reason why "deleted" items return after reboot is because the deletion never actually occurred on the partition itself. It was temporary because the write was blocked by the security.
S-ON + Unlocked means that HTC removed the write protection from: boot, recovery, and system.
For HTC's official FAQ see my post immediately before yours.
illogos said:
To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Click to expand...
Click to collapse
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done
.Elite_The_King. said:
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done
Click to expand...
Click to collapse
thanks Cap. but I was not rooted before OTA. and after OTA there is no other way to root or flash custom ROM.
WIP Guide for achieving S-OFF after unlocking Bootloader with HTCDev.com
[GUIDE][WIP] How to achieve S-OFF after unlocking 2.18 HBOOT with HTCDev.com - No More Watermark! )
Still working on the details, but a shell of the instructions is there .
Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
DISCLAIMER: I'm a noob in this root world.....and enjoying the freedom to use my phone as I choose.
With that said, if you do not recommend updating OTA, then how would a person do such? I'm asking for my friends who are run stock on their phones.

[Q] Bootloader Unlock for a Razr M with the latest update?

So I have heard that it is nearly impossible to do a Bootloader unlock for a razr m with the latest update because they patched the hole that was originally exploited, I am wondering if this is indeed true. If so what recovery options are there since CWM and TWRP both need a unlocked device. I would LIKE to have the recovery program so I could switch between multiple roms, but im also able to just flash whatever rom I want and then flash a stock rom back on if I need it, without a recovery program aren't I?
WhatTheCuss said:
So I have heard that it is nearly impossible to do a Bootloader unlock for a razr m with the latest update because they patched the hole that was originally exploited, I am wondering if this is indeed true. If so what recovery options are there since CWM and TWRP both need a unlocked device. I would LIKE to have the recovery program so I could switch between multiple roms, but im also able to just flash whatever rom I want and then flash a stock rom back on if I need it, without a recovery program aren't I?
Click to expand...
Click to collapse
Yeah, so far you can't unlock the BL if you are the newest update. However, you can run SafeStrap and it will allow you to flash custom ROMs to Slot 1. SS is based off of TWRP, but it's not a true recovery replacement. Your stock recovery will still be intact. You won't be able to flash a true custom recovery on a locked BL. There are a few ROMs that were originally designed for SS. IIRC, Energy, Eclipse V1.2, older builds of CM10, Flying Jelly (was originally designed for SS, but may have been re-designed for unlocked BL), and DeadCalm (also originally designed for SS, but may have been redesigned for unlocked BL) all were made for SS.
How to SafeStrap:
http://blog.hash-of-codes.com/how-to-safestrap/

[Q] Everyone keeps talking about bootloader downgrade

But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Zalmoxis12 said:
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Click to expand...
Click to collapse
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
simon_lefisch said:
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
Click to expand...
Click to collapse
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
http://searchenterpriselinux.techtarget.com/definition/boot-loader
Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
bootloader loads all the partitions and makes sure they work together, two examples of the stuff bootloader handles:
-bootloader boots
-bootloader then loads kernel making sure nothing wrong and if there is then you get no boot and instead you are thrown to fastboot to fix the problem
-after kernel loads bootloader loads system if corrupted/missing you get stuck in a bootloop unless you have custom recovery then you get stuck in recovery
-bootloader loads rest of partitions while the system/kernel begin to boot rom
when doing ota:
-phone reboots and loads bootloader
-bootloader loads ota into a partition on phone designed to decompile and apply ota into system/kernel partitions
-bootloader makes sure that system/ota are correct and compatible to apply update
-bootloader does root check process in the rtf partition and if rooted bootloader cancels ota process
so in short bootloader is most important asset, it is what decides the kernel to boot(you can mod a bootloader so that you can have too kernels and this is also how you create multi boot for boot more than one rom), it boots the rom, and it handles all other partitions in more than one way

can't update to marshmallow

Hello friends
My phone is HTC One m8w
There isn't "update" in
Setting
About
Android version,
5.0.1
Software number
1.0.0.m8w
Build number
4.19.1402.15 CL458284 release-keys
Please help me for this problem
How can I update my phone?
Thanks a lot
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Ta3miyyasandwich said:
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Click to expand...
Click to collapse
There isn't any update for my build number
Sent from my HTC_M9pw using Tapatalk
if you are willing to, just root your phone and flash the marshmallow rom on to your phone and use titanium backup to backup everything before you do so.
you can root your phone,flash twrp recovery,flash Marshmallow rom.
lmentor said:
you can root your phone,flash twrp recovery,flash Marshmallow rom.
Click to expand...
Click to collapse
That's exactly what I just said
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom on to your phone
Click to expand...
Click to collapse
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
redpoint73 said:
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
Click to expand...
Click to collapse
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone. Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
justinchao740 said:
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone .
Click to expand...
Click to collapse
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
justinchao740 said:
Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
Click to expand...
Click to collapse
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
redpoint73 said:
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
Click to expand...
Click to collapse
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
justinchao740 said:
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
Click to expand...
Click to collapse
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
redpoint73 said:
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
Click to expand...
Click to collapse
Agreed plus my post never stated anything about rooting.
justinchao740 said:
Agreed plus my post never stated anything about rooting.
Click to expand...
Click to collapse
While my intent is not to be the guy that always has the last word; I also can't let you state a complete falsehood.
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom
Click to expand...
Click to collapse

Freshly bought Mi A1 - to OTA or not to OTA?

Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
zroice said:
Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
Click to expand...
Click to collapse
If security matters for you yes
The only thing you'll share with a custom ROM is the bootloader
Since may update locking or relocking the bootloader will wipe your data
It's your choice
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
You have to enable it in Developer settings.
zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Dead-neM said:
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Click to expand...
Click to collapse
alright. thanks very much for explaining in details - exactly what i was looking for.
What's the use of your android one device if you will not update it, that's what you pay for.
HidekiRyuga said:
What's the use of your android one device if you will not update it, that's what you pay for.
Click to expand...
Click to collapse
hahahaaa exactly the point :laugh:
well once you have everything "perfectly set up" updates can ruin it. but yea relocking the bootloader really was a stupid idea - it was the idea to make it tamper proof but since custom kernels wont boot with locked bootloader that wouldnt work.

Categories

Resources