hi, i recently got a droid razr hd,, its on ics system version 7.21.11.xt925.skt.en.kr build number vanquish_u
_skt-userdebug 4.0.4 ,,7.7 1q-126_VQS-11 14 test-keys,, how do i update,, which are the correct files to dowload, and where to download them.....,.,.,.
seriosly?? atleast abuse me for this annoying question!!! cum on man,, someone reply
Bump!! Why this forum is so queit?
Sent from my HTC Desire S using xda app-developers app
Not many people have these phones, so traffic is very slow on this forum.
You have an engineering device with a userdebug testkeys firmware on it.
The good news is that your device can run any firmware because it has an unlocked bootloader, so all you need to do is download the full XML.zip for the current release for your region and flash it using RSD Lite.
The bad news is that a stock OTA update cannot be loaded successfully on that firmware because it's a testkeys build with different signatures and other debugging components, so you will have to manually upgrade it to a stock build.
You have a very unusual device and must have purchased it from someone who was a tester originally.
Enjoy it!
Edit: Here is the best link to find the right firmware files.
http://sbf.droid-developers.org/vanquish_u/list.php
cellzealot said:
Not many people have these phones, so traffic is very slow on this forum.
You have an engineering device with a userdebug testkeys firmware on it.
The good news is that your device can run any firmware because it has an unlocked bootloader, so all you need to do is download the full XML.zip for the current release for your region and flash it using RSD Lite.
The bad news is that a stock OTA update cannot be loaded successfully on that firmware because it's a testkeys build with different signatures and other debugging components, so you will have to manually upgrade it to a stock build.
You have a very unusual device and must have purchased it from someone who was a tester originally.
Enjoy it!
Edit: Here is the best link to find the right firmware files.
http://sbf.droid-developers.org/vanquish_u/list.php
Click to expand...
Click to collapse
U mean , I can download any firmware file and flash it via RSD? ,, hey. , wait a minute, my country/region is not in the list , what now? Which will be the correct firmware to use?
P.s I'm now looking forward to root and flash a custom JB rom, my bootloader is already unlocked, so if I manage to root my device,, can I just flash cwm recovery and start flashing wiping and flashing Roms? Btw , what do you recomend , upgrade or root?
Sent from my HTC Desire S using xda app-developers app
Yes, you should be able to just fastboot the latest CWM or TWRP recovery image for the xt925 and then flash anything you want because a status 1 device is a true engineering model that is NS(Non Secured) and performs no signature checks at all on the bootchain.
Rooting these devices is simply a matter of flashing a zip from the custom recovery and no exploits are required.
You also already have root in adb shell, that is what userdebug means.
You will have to find the best firmware for your region and carrier and it may take some experimenting and/or reading to find which is best for you.
Definitely make a full backup of your current build so you can restore it as needed.
You have more possibilities due to the completely unlocked status of the device but it also means you are on your own and must manage it yourself and be responsible for understanding how to do that.
Fair deal!
cellzealot said:
Yes, you should be able to just fastboot the latest CWM or TWRP recovery image for the xt925 and then flash anything you want because a status 1 device is a true engineering model that is NS(Non Secured) and performs no signature checks at all on the bootchain.
Rooting these devices is simply a matter of flashing a zip from the custom recovery and no exploits are required.
You also already have root in adb shell, that is what userdebug means.
You will have to find the best firmware for your region and carrier and it may take some experimenting and/or reading to find which is best for you.
Definitely make a full backup of your current build so you can restore it as needed.
You have more possibilities due to the completely unlocked status of the device but it also means you are on your own and must manage it yourself and be responsible for understanding how to do that.
Fair deal!
Click to expand...
Click to collapse
thanks for your response!! im pretty sure mine is a test model, there is also a label on the side of the screen "Not for sale" !! so, im just gonna boot in fastboot mode and flash twrp, do a nandroid,, flash cyanogenmod 10.1!! and thats it! i will not flash a firmware, i have heard the 4.1.2 update has reboot issues,, so im gonna go with a custom rom, :highfive: , a qusetion, since im a total noob in motorola! so , i wanna know , in motorola , unlocked bootloader means im free to do everything!?! i mean, in HTC , if i unlock my bootloader, i always have flash the boot.img seperatley from fastboot,, so i wanna know , if there are any issues in motorola like that? sorry for silly Q!!
Related
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
ImmoralCore said:
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
Click to expand...
Click to collapse
Your DRM keys are lost forever.
TheTeslaCoil said:
Your DRM keys are lost forever.
Click to expand...
Click to collapse
Ok, so they are lost even if I use the first backup that was made by the person I bought it from ?
DRM=Hardcoded=Once unlocked, always DRM free, even if you use the recovery image ?
And the rest of the questions, what am I supposed to do to get stock lollipop?
In the matter of fact it does not matter if its unlocked or locked, I just want legit lollipop, with the possibility to update regularly. (But if root is possible at the same, it can still be rooted)
Thanks for your reply !
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
TheTeslaCoil said:
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
Click to expand...
Click to collapse
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
ImmoralCore said:
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
Click to expand...
Click to collapse
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
gregbradley said:
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
Click to expand...
Click to collapse
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
ImmoralCore said:
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
Click to expand...
Click to collapse
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
gregbradley said:
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
Click to expand...
Click to collapse
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
ImmoralCore said:
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
Click to expand...
Click to collapse
Good luck.
Hello everyone.
I live in Brazil and I bought at the Aliexpress MI4C Xiaomi. I haven't received it yet, but I've already started researching ways to use it with another ROM than the original. The seller sends the device with google apps and multilanguage option. So, he makes some modification in the ROM, and says to not update the ROM officially on Xiaomi servers.
I see a lot of complaints about the Chinese bloatwares in ROM and so I wanted to install one that was good, but nothing with applications in Chinese or unnecessary ones.
My question is: in this case the bootloader is already unlocked?
In the meantime, I sent my request for unlocking bootloader to Xiaomi and received the SMS containing a link. As soon as I get the cellphone I intend to do the procedure. There is a risk of bricking the phone?
I’ll do appreciate good links with how-to and good ROM to daily use.
Thank you.
The seller shipping a modified ROM and telling you not to update the official would suggest your bootloader will not be locked. For now only flashing the latest official China dev builds will lock your bootloader.
Getting pre-approved for unlocking couldn't hurt though I guess.. just in case. You might need to have a working Xiaomi framework in your ROM to register your phone once though. If your ROM does not have the xiaomi services, I would suggest either Xiaomi.eu or sMiUI as a ROM, both are pretty much stock MIUI with some chinese bloat trimmed.
But most likely you will not need to unlock your bootloader anyway. You will need to check your bootloader through adb anyway before doing the steps to flashing a new ROM. You will best be flashing your recovery through adb, the instructions can be found through most ROM pages or simply searching TWRP Mi 4C. The command to check if it's unlocked is
Code:
fastboot oem device-info
A very extensive directory can be found in the INDEX thread, first in this forum.
Logic_ said:
The seller shipping a modified ROM and telling you not to update the official would suggest your bootloader will not be locked. For now only flashing the latest official China dev builds will lock your bootloader.
Getting pre-approved for unlocking couldn't hurt though I guess.. just in case. You might need to have a working Xiaomi framework in your ROM to register your phone once though. If your ROM does not have the xiaomi services, I would suggest either Xiaomi.eu or sMiUI as a ROM, both are pretty much stock MIUI with some chinese bloat trimmed.
But most likely you will not need to unlock your bootloader anyway. You will need to check your bootloader through adb anyway before doing the steps to flashing a new ROM. You will best be flashing your recovery through adb, the instructions can be found through most ROM pages or simply searching TWRP Mi 4C. The command to check if it's unlocked is
Code:
fastboot oem device-info
A very extensive directory can be found in the INDEX thread, first in this forum.
Click to expand...
Click to collapse
you cannot check the bootloader locked or not by that way. My phone when checking this, gets the input "bootloader unlocked: false" but I can flash other recovery freely.
in his case, he is using a modified rom, it means his bootloader is not yet unlocked. Right now, if he wants to come back to chinese rom, he should use Mi flash to flash his phone. If he wants other rom like CM13, he should download the latest TWRP and the rom, put the rom into his phone storage. Then try to go to fastboot to flash the recovery, then go to the recovery and flash the rom.
tuanhung303 said:
you cannot check the bootloader locked or not by that way. My phone when checking this, gets the input "bootloader unlocked: false" but I can flash other recovery freely.
in his case, he is using a modified rom, it means his bootloader is not yet unlocked. Right now, if he wants to come back to chinese rom, he should use Mi flash to flash his phone. If he wants other rom like CM13, he should download the latest TWRP and the rom, put the rom into his phone storage. Then try to go to fastboot to flash the recovery, then go to the recovery and flash the rom.
Click to expand...
Click to collapse
Ah, that might be incorrectly reporting indeed. In any case when trying to flash recovery, if you're locked it'll simply fail and won't be harmful.
But why would you think his bootloader is not unlocked? If he's using a modified rom, it was probably flashed through fastboot or a custom recovery, both require the bootloader to be unlocked.
But even if he was not on a modified rom, stock Mi 4c have always come bootloader unlocked. Someone would have to have gone out of their way to lock the bootloader and I doubt any reseller would do that, they would risk a lot of refunds from angry customers.
I strongly advise against using miflash to flash any official rom unless you have no choice, since then there's a chance you WILL lock your bootloader. For now only dev builds are locking it, but the next stable release might very well too.
The first step should be to flash TWRP
The second step to stay away from Official China build
The third step to keep away from Official China build
The fourth st...
^ sorry my bad.... I was not focused. Actually I mean his bootloader is unlocked .
The safest way is flashing via computer, using mi flash or flash twrp image. You are right
1. Ur phone not lock bootloader
2. U can flash custom recovery...(TWRP)
3. "MUST" Stay away from official MIUI ROM
4. Flash whatever u want...sMiui, CM13, etc,etc
5. Remember Point No.3
***Btw, download official Fastboot ROM and keep it to ur drive, for just in case if u want to sell it again
Hello. Thank you all. I just received my phone. Great, btw. I'll read again and again all instructions and try. Thanks again!
Cadimarco said:
Hello. Thank you all. I just received my phone. Great, btw. I'll read again and again all instructions and try. Thanks again!
Click to expand...
Click to collapse
Even as a last resort to getting your phone working if you did something wrong, please don't install the newer official roms, it's the mistake I did this weekend now I have a locked phone with a rom that has force-closes everywhere and absolutely no way back.
vletrmx21 said:
Even as a last resort to getting your phone working if you did something wrong, please don't install the newer official roms, it's the mistake I did this weekend now I have a locked phone with a rom that has force-closes everywhere and absolutely no way back.
Click to expand...
Click to collapse
yes, or the safer way is always flash the latest chinese rom via miflash. twrp does not like Chinese roms
tuanhung303 said:
yes, or the safer way is always flash the latest chinese rom via miflash. twrp does not like Chinese roms
Click to expand...
Click to collapse
No
No No
No No No
No No
No
No.
Don't flash the latest chinese rom.
No.
The only scenario where you would want to use miflash to flash a chinese rom would be as a last resort to flash the fastboot version of V7.1.6.0.LXKCNCK to restore your phone. Any later version will lock your bootloader.
If you don't care about locking your bootloader and the arduous process of unlocking it, you're easier off just taking all the latest updates OTA via the updater.
Hello everyone. Thanks for the help. In fact my bootloader was unlocked. I flashed twrp 3.0.0.3 and flashed the CM13 teamluminial, Android 6.0.1. Excellent. Thank you.
Hi!
Same scenario here..
I will receive Mi 4c with the Bootloader Unlocked, Rooted and the Multilanguage ROM.
But I have already received from Xiaomi after my request also the number for the official unlock procedure but now I'm a bit confused..
Do I have to unlock the bootloader once and for good with the official way?
Because I've read that the unofficial way isn't so secure in long term.
Do I have to install from the Updater the latest Cina Dev ROM and after that to proceed with the official unlock? Or it is better to use the Fastboot ROM?
Please could some one tell me in any case what to do ?
Thanks !
If you don't flash something that will lock your BL, no need to Unlock.
Ok first I must check the status of the bootloader to be sure that it is unlocked (via cmd control or cpu-z)
And after that can I choose an unofficial weekly miui.eu international ROM and install it?
Can I download and also update every week via Updater this ROM without issues?
At the moment my problem with flashing is that I don't have my pc (the one I have now runs win xp) and I don't want to stuck with the eventually malware or fully spammed modified rom of the reseller..
Which options do I have?
How does TWRP nandroid work with no sd card?
stillsober said:
How does TWRP nandroid work with no sd card?
Click to expand...
Click to collapse
TWRP works perfectly. The backup is simply stored in your internal storage。
According to the Verizon Galaxy S5 Update Page:
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
The security patch included is the April (2017-04-01) one.
Stock No-Wipe FW. Will remove Developer Status Bootloader:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME_No_Aboot.tar.md5.zip
what does the Developer Bootloader Friendly mean or differ from Stock No-Wipe FW. Will remove Developer Status Bootloader?
Thankyou!
knight194 said:
what does the Developer Bootloader Friendly mean or differ from Stock No-Wipe FW. Will remove Developer Status Bootloader?
Thankyou!
Click to expand...
Click to collapse
If you have a Developer Edition phone, the Stock one will remove the Developer status. The Developer Bootloader Friendly one won't.
Quick question... I've been on Lineage, and have flashed this and gone back (to update the baseband). But, do you know off-hand, how do I easily root on this image? My BL is still unlocked and I've got TWRP reinstalled.
Thanks!
sry this is off subject but what is the latest modem update for the 900v or the best one in regards to best lte signal?
nictabor said:
Quick question... I've been on Lineage, and have flashed this and gone back (to update the baseband). But, do you know off-hand, how do I easily root on this image? My BL is still unlocked and I've got TWRP reinstalled.
Thanks!
Click to expand...
Click to collapse
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
KazuDante said:
sry this is off subject but what is the latest modem update for the 900v or the best one in regards to best lte signal?
Click to expand...
Click to collapse
Normally the latest update provides the latest/best modem.
Dudash said:
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
Normally the latest update provides the latest/best modem.
Click to expand...
Click to collapse
where can i find the latest modem for the 900v , and im guessing its a flash process using odin correct?
KazuDante said:
where can i find the latest modem for the 900v , and im guessing its a flash process using odin correct?
Click to expand...
Click to collapse
It depends. It could be a .tar file you flash via Odin or it could be a flashable zip via TWRP. It depends on the maker of the file.
It's just the modem.bin file from the update. I don't have the time to make one for it right now.
Dudash said:
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
Normally the latest update provides the latest/best modem.
Click to expand...
Click to collapse
I actually figured it out while waiting. Thank you for responding though!
nictabor said:
I actually figured it out while waiting. Thank you for responding though!
Click to expand...
Click to collapse
You're welcome.
On a side note, it seems like Verizon read the recent articles where the Galaxy S5 was still rated as the most popular smart phone being used on any network. Meaning, they are updating the phone monthly now, which is good news for us. We won't ever get Nougat but apparently we'll get Security Patches monthly now.
Dudash said:
It depends. It could be a .tar file you flash via Odin or it could be a flashable zip via TWRP. It depends on the maker of the file.
It's just the modem.bin file from the update. I don't have the time to make one for it right now.
Click to expand...
Click to collapse
so can i take the modem.bin file from this update and replace it with the one from a 7.1.2 rom ? also i used to mess with porting roms but on mediatek platform , are the modem files still located in /system/etc/firmware directory?
because what i see is modem.b00-b27 ,modem.mdt
---------- Post added at 08:04 PM ---------- Previous post was at 07:08 PM ----------
i tried flashing the dev friendly one and the md5 check failed....am i missing something?
Dudash said:
According to the Verizon Galaxy S5 Update Page:
The security patch included is the April (2017-04-01) one.
Stock No-Wipe FW. Will remove Developer Status Bootloader:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Developer bootloader friendly??? Do 11 EMMC Chips finally have freedom???
how do we flash this update , odin fails on md5 check
Deleted
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
KazuDante said:
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
Click to expand...
Click to collapse
I would not do it.
erw38 said:
I would not do it.
Click to expand...
Click to collapse
Since there no tut regarding an unlocked version of this update I simply updated from bpb1 to qa1 , just needed my modem to be somewhat up to date , but it seems that it's def a tx rx issue in my case , so my best bet is a custom kernel with that feature included.
KazuDante said:
Since there no tut regarding an unlocked version of this update I simply updated from bpb1 to qa1 , just needed my modem to be somewhat up to date , but it seems that it's def a tx rx issue in my case , so my best bet is a custom kernel with that feature included.
Click to expand...
Click to collapse
I didn't think a tutorial was necessary as I've never had to give one in the past. If your device is unlocked, you should know it. That's the only reason there is a Dev Friendly version of the update. It won't unlock your bootloader, but it won't lock it if it is unlocked. That's the only reason I make a Developer Bootloader Friendly version of updates.
If you want to update your modem but not the firmware, open either of the files in 7zip/WinZip, extract the modem.bin, then repackage it as a .tar file and flash it in Odin.
KazuDante said:
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
Click to expand...
Click to collapse
In regard to your previous post, there is no problem with the MD5 for either file or any problem with the files themselves. I test them both before uploading them to prevent problems like this for people. I flashed the Dev Friendly version on both of my eMMc 15 S5's and experienced zero problems. The phone will hang on the "Verizon logo" for a minute or two at first boot but it will go past it and continue to "Optimizing" after that.
If you flash the Stock version, if your bootloader is unlocked, it will lock it and in order to re-unlock it, you'll have to use jrkruse's unlock method which requires you to go back to PB1. As of this post, he has not created a QD1 bootloader unlocker. The latest bootloader unlocker he has created is for QC2, which still requires you to have an unlocked bootloader prior to flashing it.
EDIT: Also, if you use an app like Package Disabler Pro to disable applications without root, it can cause updates to hang indefinitely at first boot if you don't re-enable all disabled applications and turn off/remove Admin rights for Package Disabler Pro prior to updating. I've experienced this in the past with both of my S5's and my S7. I'm not directing this at you KazuDante, this is just a warning to all.
21-Savage said:
Developer bootloader friendly??? Do 11 EMMC Chips finally have freedom???
Click to expand...
Click to collapse
No. The Developer Bootloader Friendly version is just that, friendly to devices with a Developer Bootloader. Meaning it won't remove Developer Bootloader status/lock the bootloader.
If I had figured out a way to help all of the eMMc 11 people unlock their bootloader, I would've made a thread that clearly stated that.
I think the only way people with Toshiba eMMc's will get an unlocked bootloader is if either
A: Verizon provides an update to unlock the bootloaders on all S5's AFTER they stop putting out Security Updates, which is highly unlikely since it is Verizon, they've never done it before, and there's no end to Security Updates in sight.
B: Someone at Samsung or Verizon leaks an engineering bootloader. This is the most likely scenario since it's happened before. First, in my experience, with the VZW S3, and the latest being with the S7. There's still hope but it may rely on someone from within Verizon or Samsung feeling bad for us.
Sorry
@Dudash Any idea how to go from the Dev-friendly QD1 version you uploaded to a TWRP flashable zip file which resembles the jrkruse VZW_QA1_STOCK_ROOTED_DEODEXED.zip? I really like to debloat and root before flashing. Thanks!
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.